04-03-2010
Well, /var/adm/messages is open as fd 5:
Quote:
5: S_IFREG mode:0644 dev:256,65539 ino:24998 uid:0 gid:0 size:0
O_WRONLY|O_APPEND|O_NOCTTY|O_LARGEFILE
/var/adm/messages
6: S_IFREG mode:0644 dev:256,65539 ino:25027 uid:0 gid:3 size:2134
O_WRONLY|O_APPEND|O_NOCTTY|O_LARGEFILE
/var/log/syslog
But the truss output only shows writes being done to fd 6, which is /var/log/syslog.
The gid on /var/adm/messages is 0, but the gid on /var/log/syslog is 3. Since the files are already open, I don't see how that can make any difference, but it's really easy to fix with chown or chgrp and then HUP the syslogd process. It might be revealing to have the truss output of the process when it gets HUP'd, too.
The only other thing I can think of is a typo or other mistake somewhere in syslog.conf. I know from experience that the way syslogd processes that file is very unforgiving.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Just want to check with all of you out there what does the following warning means in my "messages" file in /var/adm
the warning is Prevous Time Adjustment Incomplete , does it mean my hard ware is faulty if so which piece of hardware it is ? (1 Reply)
Discussion started by: owls
1 Replies
2. Solaris
Solaris 8/ sun 420R
Checked /var/adm/messages file and got the following message:
Dec 4 16:40:05 serverXYZ ConfigProvider: get_pkg_instdate: getdate failed for the standard C locale (7)
Does anyone know what this means? Looked up getdate but do not understand....
Thanks. (1 Reply)
Discussion started by: finster
1 Replies
3. Solaris
I'm running a Solaris 9 box with Oracle databases on it.
I'm getting the following messages in my /var/adm/messages log
"Jun 24 12:30:32 sundb01 bootpd: IP address not found: xxx.xxx.xxx.xxx"
...where xxx.xxx.xxx.xxx is DHCP IP addresses of Windows 2000 workstations in the organisation. ... (2 Replies)
Discussion started by: soliberus
2 Replies
4. UNIX for Dummies Questions & Answers
Hi,
No log entry is found in messages files. The file size is 0. We are using Solaris 9. Anyone knows what could be wrong. (3 Replies)
Discussion started by: FrankC
3 Replies
5. Solaris
Hello Friends,
I am geting the folowing error in /var/adm/message is it disl related problem?
if yes.. how to check all the disk are perfect or not?
Sep 15 06:01:12 scsi: WARNING: /pci@1f,700000/scsi@2/sd@2,0 (sd7):
Sep 15 06:01:12 Error for Command: write(10) Error Level:... (5 Replies)
Discussion started by: bullz26
5 Replies
6. Solaris
Check message file and result posted below.
Can anyone tell me what this is a sign of, what does it mean?
server1% more messages.0
Dec 02 09:35:06 server1 bsd-gw: Inval
id protocol request (65): AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA^\\2... (6 Replies)
Discussion started by: finster
6 Replies
7. Solaris
hi sirs
can u tell the difference between /var/log/syslogs and /var/adm/messages
in my working place i am having two servers.
in one servers messages file is empty and syslog file is going on increasing..
and in another servers message file is going on increasing but syslog file is... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
8. UNIX for Advanced & Expert Users
The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux.
I checked the log level in Linux and they seem OK.
Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
Discussion started by: gomes1333
2 Replies
9. Shell Programming and Scripting
grep \"^`date "+%b %d %T"`\" /var/adm/messages | egrep \"emerg|alert|crit|err|warning\
but get an output like this
ksh: alert: not found
ksh: crit: not found
ksh: err: not found
ksh: warning": not found
grep: can't open "19"
grep: can't open "16:27:16"" (1 Reply)
Discussion started by: arch12
1 Replies
10. Solaris
Hi,
Is the contents in /var/log/syslog and /var/adm/messages are same??
Regards (3 Replies)
Discussion started by: vks47
3 Replies
SYSLOGD(8) System Manager's Manual SYSLOGD(8)
NAME
syslogd - log systems messages
SYNOPSIS
syslogd [ -fconfigfile ] [ -mmarkinterval ] [ -d ]
DESCRIPTION
Syslogd reads and logs messages into a set of files described by the configuration file /etc/syslog.conf. Each message is one line. A
message can contain a priority code, marked by a number in angle braces at the beginning of the line. Priorities are defined in <sys/sys-
log.h>. Syslogd reads from the UNIX domain socket /dev/log, from an Internet domain socket specified in /etc/services, and from the spe-
cial device /dev/klog (to read kernel messages).
Syslogd configures when it starts up and whenever it receives a hangup signal. Lines in the configuration file have a selector to deter-
mine the message priorities to which the line applies and an action. The action field are separated from the selector by one or more tabs.
Selectors are semicolon separated lists of priority specifiers. Each priority has a facility describing the part of the system that gener-
ated the message, a dot, and a level indicating the severity of the message. Symbolic names may be used. An asterisk selects all facili-
ties. All messages of the specified level or higher (greater severity) are selected. More than one facility may be selected using commas
to separate them. For example:
*.emerg;mail,daemon.crit
Selects all facilities at the emerg level and the mail and daemon facilities at the crit level.
Known facilities and levels recognized by syslogd are those listed in syslog(3) without the leading ``LOG_''. The additional facility
``mark'' has a message at priority LOG_INFO sent to it every 20 minutes (this may be changed with the -m flag). The ``mark'' facility is
not enabled by a facility field containing an asterisk. The level ``none'' may be used to disable a particular facility. For example,
*.debug;mail.none
Sends all messages except mail messages to the selected file.
The second part of each line describes where the message is to be logged if this line is selected. There are four forms:
o A filename (beginning with a leading slash). The file will be opened in append mode.
o A hostname preceeded by an at sign (``@''). Selected messages are forwarded to the syslogd on the named host.
o A comma separated list of users. Selected messages are written to those users if they are logged in.
o An asterisk. Selected messages are written to all logged-in users.
Blank lines and lines beginning with `#' are ignored.
For example, the configuration file:
kern,mark.debug /dev/console
*.notice;mail.info /usr/spool/adm/syslog
*.crit /usr/adm/critical
kern.err @ucbarpa
*.emerg *
*.alert eric,kridle
*.alert;auth.warning ralph
logs all kernel messages and 20 minute marks onto the system console, all notice (or higher) level messages and all mail system messages
except debug messages into the file /usr/spool/adm/syslog, and all critical messages into /usr/adm/critical; kernel messages of error
severity or higher are forwarded to ucbarpa. All users will be informed of any emergency messages, the users ``eric'' and ``kridle'' will
be informed of any alert messages, and the user ``ralph'' will be informed of any alert message, or any warning message (or higher) from
the authorization system.
The flags are:
-f Specify an alternate configuration file.
-m Select the number of minutes between mark messages.
-d Turn on debugging.
Syslogd creates the file /var/run/syslog.pid, if possible, containing a single line with its process id. This can be used to kill or
reconfigure syslogd.
To bring syslogd down, it should be sent a terminate signal (e.g. kill `cat /var/run/syslog.pid`).
FILES
/etc/syslog.conf the configuration file
/var/run/syslog.pid the process id
/dev/log Name of the UNIX domain datagram log socket
/dev/klog The kernel log device
SEE ALSO
logger(1), syslog(3)
4.2 Berkeley Distribution November 16, 1996 SYSLOGD(8)