Networker

Re: [Networker] Logger notifications from Networker 6.1.1 on Tru64 5.1

2003-03-27 01:56:05
Subject: Re: [Networker] Logger notifications from Networker 6.1.1 on Tru64 5.1
From: Tim Mooney <mooney AT DOGBERT.CC.NDSU.NODAK DOT EDU>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Thu, 27 Mar 2003 00:56:04 -0600
In regard to: [Networker] Logger notifications from Networker 6.1.1 on...:

>Hi -- the notifications from Legato 6.1.1 generally work OK, except
>occasionally when waiting for a tape to load ( oops - need to get in the
>car and grab an offsite volume for a restore ).  This message appears on
>the 2nd attempt ( Notification 1 is an email )

>Mar 27 10:44:24  syslog: NetWorker media: (critical) waiting for sdlt tape 
>PAK052 on js012fp02.jsds1.live

>The entry for this is 'logger -p local0.alert'    on
>Tape Mount Request 2.
>This is fine , except that occasionally users other than root or system
>are landed with it as well. They are not in any other group except for
>the standard 'users'.
>Has anybody dealt with this before? Thanks.
>Is there anywhere that local0 is defined --- the man page for logger does
>not mention it.

I'm not sure what you mean by "defined".  local0 is one of the standard
"facilities" for syslog (see syslog(3)).

Remember that syslog.conf entries can be "wildcarded", meaning that you
can't just look for `local0.alert' entries in /etc/syslog.conf, to see how
a message might be delivered.

For example, if you have the following entries in /etc/syslog.conf

*.err   /var/log/errors
*.notice        *
local0.alert    @remote.syslog.consolidation.host

then your critical tape mount message (at local0.alert) will end up going
into /var/log/errors, to all users logged in on the system, and to your
remote syslog consolidation host.  The last place is easy to see, but
the first two happen because the facilities are wildcarded and `alert'
is a higher priority than either `err' and `notice'.

In short, check your /etc/syslog.conf and look for a destination of `*'
or that mentions a list of users, and see if it's for all facilities
and a lesser priority than alert.

You can also run syslogd with a `-d' option, which will give you a lot
of information about why syslogd chooses to log something to a particular
destination.  This alone may turn up what's causing the problem.

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>