Sponsored Content
Operating Systems Solaris Facing problem in configuring syslog server in Solaris Post 302909915 by amity on Monday 21st of July 2014 10:42:55 AM
Old 07-21-2014
Facing problem in configuring syslog server in Solaris

I am trying to configure central syslog server

On hostA, in /etc/syslog.conf file,I am adding below line
Code:
*.err;kern.debug;daemon.notice;mail.crit        @hostB

then I am restarting syslog service
Code:
svcadm restart /system/system-log

In hostA, I have already added hostB entry in /etc/hosts file & in hostB , I have also added hostA entry in /etc/hosts file. Both server are pinging as well.

Now when I am running below command on hostA, it is logging to local /var/adm/messages file but not in hostB /var/adm/messages file
Code:
logger -p user.err  system will reboot

Please let me know where I am missing

Last edited by rbatte1; 07-26-2014 at 06:12 PM.. Reason: Code tags
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

need help on configuring LDAP server on solaris

HI All I need help to understand how the ldap works in Solaris 9 & Solaris 10. Kindly provide me some helpful commands related to LDAP Regards Jagan (2 Replies)
Discussion started by: jaganblore
2 Replies

2. Infrastructure Monitoring

Facing problem while configuring snmp

HI, I am facing these two errors while configuring snmp can any body guide me. vi /var/log/snmpd.log Error opening specified endpoint "udp:161" Server Exiting with code 1 i also tried bash-3.00# netstat -a | grep snm *.snmpd Idle bash-3.00# lsof -i :161 bash: lsof: command not... (2 Replies)
Discussion started by: nir1785
2 Replies

3. Solaris

Facing problem while doing FTp to solaris server

Hi All, I am facing problem while doing FTp to solaris server through Windows XP machine. showing msg as follows 220 matrix FTP server ready. User (*.*.*.*:(none)): Sun 331 Password required for Sun. Password: 530 Login incorrect. Login failed. ftp> bye also while doing vi or... (2 Replies)
Discussion started by: sunray
2 Replies

4. Shell Programming and Scripting

Facing Issue after configuring logrotate

Hi, I have a logrotate configuration which rotates a log every night 1 min before midnight, but somehow its not working and unfortunately not showing any error message as well. Sharing the code for the cron job as well as the conf file, I am using, if some one coule help me..whats wrong with... (2 Replies)
Discussion started by: Neeryan
2 Replies

5. Red Hat

Configuring SYSLOG Server

Hello, I have successfully configured a syslog server on Centos 5.7, I have to add few clients which are CISCO switches - can someone suggest how should I configure on SYSLOG server, so the each client's log messages should go to different location on syslog server not a default location... (9 Replies)
Discussion started by: bobby320
9 Replies

6. Solaris

Facing problem with installing CF engine software in solaris 10

Dear experts, I am using solaris 10 OS.I am installing CF engine software in the server while doing so ,i am getting following error checking for BerkeleyDB location in default... configure: error: >> Cannot find BerkeleyDB I am installing the Berkely DB 5.3.I am strugging... (1 Reply)
Discussion started by: muraliinfy04
1 Replies

7. HP-UX

Problem in Configuring kerberos Server on HPUX

Hi, I am getting this error during kerberos server setup in HPUX 11.31 : kdb_create: unknown LDAP backend error while adding master entry to the database ps -ef|grep ldap root 3905 1 0 13:11:36 ? 0:00 /opt/ldapux/bin/ldapclientd Unable to find out the meaning of this... (1 Reply)
Discussion started by: Amit Kulkarni
1 Replies

8. Solaris

Configuring Centralized Solaris Server to Receive Syslogs

Hello, I am new to Solaris. However, I was able to configure the Syslog server on Solaris. I am using a windows client to send logs to my Solaris syslog server. this is working fine. however, I have 23 servers which are sending their logs to the syslog server and it is very difficult to read all... (2 Replies)
Discussion started by: ravmohun
2 Replies

9. SuSE

Facing issue configuring network

Please let me know how to configure network in suse Linux, I have configured the network using ifup and network manager, it is not giving any error but not working, using suse Linux 11.0 sp3 I have checked network connectivity is working. (0 Replies)
Discussion started by: manoj.solaris
0 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)
All times are GMT -4. The time now is 05:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy