Sponsored Content
Full Discussion: Syslog - solaris 9
Operating Systems Solaris Syslog - solaris 9 Post 302446300 by snchaudhari2 on Wednesday 18th of August 2010 04:38:37 PM
Old 08-18-2010
# file /usr/sbin/syslogd
-r-xr-xr-x 1 root sys 79396 Jun 10 2008 /usr/sbin/syslogddynamically linked, stripped

# ls -l /usr/sbin/syslogd
-r-xr-xr-x 1 root sys 79396 Jun 10 2008 /usr/sbin/syslogd

# ls -l /dev/log
lrwxrwxrwx 1 root other 27 Sep 29 2006 /dev/log -> ../devices/pseudo/log@0:log

# ls -l /devices/pseudo/log\@0\:log
crw-r----- 1 root sys 21, 5 Sep 29 2006 /devices/pseudo/log@0:log

# /etc/init.d/syslog start
syslog service starting.
# tail -5 /var/adm/messages
Aug 17 09:06:06 eric krtld: [ID 819705 kern.notice] /kernel/sys/sparcv9/nfs: undefined symbol
Aug 17 09:06:06 eric krtld: [ID 826211 kern.notice] 'crsetugid'
Aug 17 09:06:06 eric krtld: [ID 472681 kern.notice] WARNING: mod_load: cannot load module 'nfs'
Aug 18 08:20:36 eric krtld: [ID 819705 kern.notice] /kernel/sys/sparcv9/doorfs: undefined symbol
Aug 18 08:20:36 eric krtld: [ID 826211 kern.notice] 'copyout_nowatch'


Here eric is my host name

# cat /etc/syslog.conf
#ident "@(#)syslog.conf 1.5 98/12/14 SMI" /* SunOS 5.0 */
#
# Copyright (c) 1991-1998 by Sun Microsystems, Inc.
# All rights reserved.
#
# syslog configuration file.
#
# This file is processed by m4 so be careful to quote (`') names
# that match m4 reserved words. Also, within ifdef's, arguments
# containing commas must be quoted.
#
*.err;kern.notice;auth.notice /dev/sysmsg
*.err;kern.debug;daemon.notice;mail.crit /var/adm/messages

*.alert;kern.err;daemon.err operator
*.alert root

*.emerg *

# if a non-loghost machine chooses to have authentication messages
# sent to the loghost machine, un-comment out the following line:
#auth.notice ifdef(`LOGHOST', /var/log/authlog, @loghost)

mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost)

#
# non-loghost machines will use the following lines to cause "user"
# log messages to be logged locally.
#
ifdef(`LOGHOST', ,
user.err /dev/sysmsg
user.err /var/adm/messages
user.alert `root, operator'
user.emerg *
)

#Save oracle rdbms audit trail to oracle_audit.log
local0.warning /var/log/oracle/oracle_audit.log
#Send oracle rdbms audit trail to remote syslog server
#local0.info @


I think all files are correct as they should be...Is it because of the dependancies that I mentioned in previous posts...???

---------- Post updated at 04:38 PM ---------- Previous update was at 08:23 AM ----------

Hi Citaylor/Niyazi,

Could you please go through my last post.....
It might help to recognize the solution.....


thnx

Last edited by snchaudhari2; 08-18-2010 at 11:44 AM..
 

10 More Discussions You Might Find Interesting

1. Solaris

Syslog-ng does not start Solaris 9

I have been installing syslog-ng on our Solaris 9 servers. All ov them are working except two which return the following error: # /etc/init.d/syslog start syslog-ng service starting. Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (125)' ... (6 Replies)
Discussion started by: takendal
6 Replies

2. UNIX for Dummies Questions & Answers

Solaris 10 question on syslog.conf file

Hi, I have a question on /etc/syslog.conf file in Solaris 10. Below is a line taken from /etc/syslog.conf file and I know that the last field (operator) is where the logs gets outputted but how do I find out what the output file name format is going to be and which directory it gets outputted... (1 Reply)
Discussion started by: stevefox
1 Replies

3. Solaris

Solaris Syslog Server

Hi all, I want to implement a Syslog Server but i'm new in this area. I donīt know how to configure it in Solaris. I should like send all the logs to a application(manipule the information, por example: do the alerts, configure it, etc...) How can I do that? or Which manual can help me? Exists... (2 Replies)
Discussion started by: yflores
2 Replies

4. UNIX for Dummies Questions & Answers

edit /etc/syslog.conf (Solaris 10)

Hi, Im editing the file /etc/syslog.conf for Solaris 10 server in production. I need to add "auth and authpriv.": someone set the same? Have been successful? I would appreciate any suggestions. Greetings. The unmodified arhive is: (0 Replies)
Discussion started by: musul
0 Replies

5. Solaris

Solaris syslog server and client

Hi folks, I am attempting to setup a Solaris 10 syslog server to receive logs from linux machines. Here's what I did: On the server (SunOS sun226 5.10), IP address: 192.168.212.226: 1. start syslogdby issuing $/usr/sbin/syslogd -T On a client (SunOS sun221 5.8): 1. Configured... (1 Reply)
Discussion started by: kimurayuki
1 Replies

6. Solaris

Solaris SYSLOG Help

We have this Sun Solaris that we use for SYSLOG. Existing firewalls send warning level to this SYSLOG and it works great. We added a new firewall, I pointed the firewall to this SYSLOG server but nothing is being logged (windows KIWI works but not UNIX & I dont like KIWI). I am wondering what to do... (10 Replies)
Discussion started by: fjm1502
10 Replies

7. Solaris

Solaris syslog messages cluttering screen

Well, this kind of silly but I think I am missing something. So we have this Solaris 10 server which acts as syslog server for network devices. Problem is the syslogs clutters whenever I use the screen utility for any work. I am posting the conetent of /etc/syslog.conf # more... (3 Replies)
Discussion started by: admin_xor
3 Replies

8. UNIX for Dummies Questions & Answers

Syslog in Solaris 11.1

Hi, I have a solaris 11.1 server with many network interfaces (real and virtual), and one is connected to another server. i need that syslog send the info through one specific interface, i know that in the syslog.conf file can write: *.* @xxx.xxx.xxx.xxx (remote server IP) but... (0 Replies)
Discussion started by: iocx
0 Replies

9. UNIX for Advanced & Expert Users

Syslog in Solaris 11.1

Hi, I have a solaris 11.1 server with many network interfaces (real and virtual), and one is connected to another server. i need that syslog send the info through one specific interface, i know that in the syslog.conf file can write: *.* @xxx.xxx.xxx.xxx (remote server IP) but... (1 Reply)
Discussion started by: iocx
1 Replies

10. Solaris

How can i send Solaris syslog loging server?

HI how can i send solaris syslog to centralized logging server? i have tried adding like below and got error: *.err;kern.debug;daemon.notice;mail.crit @172.16.200.50:5000 and the error i got in /var/adm/messages is: Jun 10 13:02:24 aresdb-new.alshaya.com syslogd: line 14:... (10 Replies)
Discussion started by: bentech4u
10 Replies
SYSLOG.CONF(5)						      BSD File Formats Manual						    SYSLOG.CONF(5)

NAME
syslog.conf -- configuration file for syslogd(8) 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 or space characters. A rule can be splitted in several lines if all lines except the last are terminated with a backslash (``''). 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, and is one of the following keywords: 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. 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 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. By default, a level applies to all messages with the same or higher level. The equal (``='') character can be prepended to a level to restrict this line of the configuration file to messages with the very same level. An exclamation mark (``!'') prepended to a level or the asterisk means that this line of the configuration file does not apply to the speci- fied level (and higher ones). In conjunction with the equal sign, you can exclude single levels as well. 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 five forms: o A pathname (beginning with a leading slash). Selected messages are appended to the file. You may prepend a minus (``-'') to the path to omit syncing the file after each message log. This can cause data loss at system crashes, but increases performance for programs which use logging extensively. o A named pipe (fifo), beginning with a vertical bar (``|'') followed by a pathname. The pipe must be created with mkfifo(8) before syslogd reads its configuration file. This feature is especially useful fo debugging. 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
syslog(3), syslogd(8) 4.4BSD June 9, 1993 4.4BSD
All times are GMT -4. The time now is 02:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy