Sponsored Content
Full Discussion: Message in /var/adm
Operating Systems Solaris Message in /var/adm Post 302772123 by cjashu on Saturday 23rd of February 2013 10:50:27 AM
Old 02-23-2013
Those are invents happening in your box. The kernel is just notifying you of them. If you have messages like kern.emerg or kern.critic you should definitely check those. If I where you, i will set up syslog not to send me info messages. Your file system will get full fast with all these info messages
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

HELP! The '/var/adm/message' file increase every few seconds???

Hi, guys, I have a big problem. I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It soon becomes a large file. I wander if there are some mistakes configuring the workstation. the /var/adm/message is as follow: ... (1 Reply)
Discussion started by: cloudsmell
1 Replies

2. UNIX for Dummies Questions & Answers

HELP! The '/var/adm/message' file increase every few seconds???

Hi, guys, I have a big problem. I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It becomes a large file in a short time. I wander if there are some mistakes configuring the workstation. the /var/adm/message is as follow: ... (3 Replies)
Discussion started by: cloudsmell
3 Replies

3. UNIX for Advanced & Expert Users

an idea? /var/adm/message

hiho, my sun ultra1 print me in my /var/adm/message file: Aug 3 03:16:29 dazinger1 raid: AEN event = Host=3Ddazinger1 Ctrl=3D1T04359235 Dev=3Dc1t1d0 Aug 3 03:16:29 dazinger1 raid: ASC=3DA0 = ASCQ=3D00 FRU=3D00 LUN=3D00 LUN Stat=3D00 Aug 3 03:16:29 dazinger1 raid: =... (3 Replies)
Discussion started by: pressy
3 Replies

4. Solaris

NRPE message in /var/adm/messages

Hi Guru's On one of our servers we have every few seconds following error: Apr 28 10:15:27 svr10010 nrpe: connect from reno.customs.govt.nz Apr 28 10:15:29 svr10010 nrpe: connect from reno.customs.govt.nz Here are the details from this box: SunOS svr10010 5.10 Generic_125100-10 sun4v... (3 Replies)
Discussion started by: gnom
3 Replies

5. UNIX for Advanced & Expert Users

separate "named daemon" message from /var/adm/messages

Hello group, How can I separate "named daemon" messages to the other file instead of /var/adm/messages. I still want all other daemons log the messages to /var/adm/messages. i.e. named => /var/adm/named.message other daemons => /var/adm/messages. I searched unix.com, and google but I still... (5 Replies)
Discussion started by: dannytrinh
5 Replies

6. Solaris

diff b/w /var/log/syslog and /var/adm/messages

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

7. Solaris

Getting continually error message in /var/adm/messages.

Hi Friends, Please help me to resove this issue ASAP. Nov 17 16:25:52 server1 sendmail: pAH8Pnh22099: SYSERR: putoutmsg (NO-HOST): error on output channel sending "553 5.1.3 @123.com.... User address required": File too large Nov 17 16:25:53 server1 sendmail: pAH8Pnh22099:... (1 Reply)
Discussion started by: holds_me
1 Replies

8. Solaris

Mail loops back to me error in /var/adm/message after patching

Hi, I am getting the below messsage in /var/adm/message after patching but sendmail is working after restoring the backup file. sendmail: q4G7U1Cj014774: SYSERR(root): 127.0.0.1 config error: mail loops back to me (MX problem?) sendmail: q4G801cw025824: SYSERR(root): 127.0.0.1 config... (3 Replies)
Discussion started by: fayaz
3 Replies

9. Solaris

/var/adm/messages (interface turned off/restored) and link up & link down message.

Hi All I am facing an issue with our new solaris machine. in /var/adm/messages root@Prod-App1:/var/tmp# root@Prod-App1:/var/tmp# root@Prod-App1:/var/tmp# cat /var/adm//messages Apr 20 03:10:01 Prod-App1 syslogd: line 25: WARNING: loghost could not be resolved Apr 20 08:24:18 Prod-App1... (0 Replies)
Discussion started by: javeedkaleem
0 Replies

10. Solaris

/var/adm/messages (insterface turned off/restored) and link up & link down message.

Hi All I am facing an issue with our new solaris machine. in /var/adm/messages Apr 22 16:43:05 Prod-App1 in.routed: interface net0 to 172.16.101.1 turned off Apr 22 16:43:33 Prod-App1 mac: NOTICE: nxge0 link up, 1000 Mbps, full duplex Apr 22 16:43:34 Prod-App1 mac: NOTICE: nxge0 link... (2 Replies)
Discussion started by: javeedkaleem
2 Replies
SYSLOG.CONF(5)						      BSD File Formats Manual						    SYSLOG.CONF(5)

NAME
syslog.conf -- syslogd(8) configuration file DESCRIPTION
The syslog.conf file is the configuration file for the syslogd(8) program. It consists of lines with two fields: the selector field which specifies the types of messages and priorities to which the line applies, and an action field which specifies the action to be taken if a message syslogd receives matches the selection criteria. The selector field is separated from the action field by one or more tab charac- ters. The Selectors function are encoded as a facility, a period (``.''), and a level, with no intervening white-space. Both the facility and the level are case insensitive. The facility describes the part of the system generating the message. Legacy facility names are: auth, authpriv, cron, daemon, kern, lpr, mail, mark, news, syslog, user, uucp and local0 through local7. These keywords (with the exception of mark) correspond to the similar ``LOG_'' values specified to the openlog(3) and syslog(3) library routines. Apple System Log (ASL) messages, sent using the asl(3) library routines permit the facility name to be an arbitrary string, although users of the system are encouraged to use a ``reverse ICANN'' naming convention, for example ``com.apple.system.syslog''. Since these facility names may contain dot characters, the names may be enclosed in either singe quote or double quote characters. If facility is terminated by an asterisk (``*''), then facility names are matched using the prefix characters preceeding the asterisk. For example, ``'com.apple.abc.*''' matches any facility with the prefix ``com.apple.abc.''. These wildcard facility names typically must be enclosed in single or double quotes characters. The level describes the severity of the message, and is a keyword from the following ordered list (higher to lower): emerg, alert, crit, err, warning, notice, info and debug. These keywords correspond to the similar (LOG_) values specified to the syslog library routine. See syslog(3) for a further descriptions of both the facility and level keywords and their significance. If a received message matches the specified facility and is of the specified level (or a higher level), the action specified in the action field will be taken. Multiple selectors may be specified for a single action by separating them with semicolon (``;'') characters. It is important to note, how- ever, that each selector can modify the ones preceding it. Multiple facilities may be specified for a single level by separating them with comma (``,'') characters. An asterisk (``*'') can be used to specify all facilities or all levels. The special facility ``mark'' receives a message at priority ``info'' every 20 minutes (see syslogd(8)). This is not enabled by a facility field containing an asterisk. The special level ``none'' disables a particular facility. The action field of each line specifies the action to be taken when the selector field selects a message. There are four forms: o A pathname (beginning with a leading slash). Selected messages are appended to the file. o A hostname (preceded by an at (``@'') sign). Selected messages are forwarded to the syslogd program 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 whose first non-blank character is a hash (``#'') character are ignored. EXAMPLES
A configuration file might appear as follows: # Log all kernel messages, authentication messages of # level notice or higher and anything of level err or # higher to the console. # Don't log private authentication messages! *.err;kern.*;auth.notice;authpriv.none /dev/console # Log anything (except mail) of level info or higher. # Don't log private authentication messages! *.info;mail.none;authpriv.none /var/log/messages # The authpriv file has restricted access. authpriv.* /var/log/secure # Log all the mail messages in one place. mail.* /var/log/maillog # Everybody gets emergency messages, plus log them on another # machine. *.emerg * *.emerg @arpa.berkeley.edu # Root and Eric get alert and higher messages. *.alert root,eric # Save mail and news errors of level err and higher in a # special file. uucp,news.crit /var/log/spoolerr FILES
/etc/syslog.conf The syslogd(8) configuration file. BUGS
The effects of multiple selectors are sometimes not intuitive. For example ``mail.crit,*.err'' will select ``mail'' facility messages at the level of ``err'' or higher, not at the level of ``crit'' or higher. SEE ALSO
asl(3), syslog(3), syslogd(8) HISTORY
The syslog.conf file appeared in 4.3BSD, along with syslogd(8). BSD
June 9, 1993 BSD
All times are GMT -4. The time now is 08:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy