|
|
Sponsored Content
08-28-2006
I have experienced syslog refusing to accept logs. But only on a syslog dedicated server. One where the syslogs of all the other servers are being sent. Since syslog is a udp service, it will drop data if it's coming too fast. Plus Solaris had a problem back in 2.5 or 2.5.1 where syslog would bail with door errors (it'd stay running but if you looked at the running process, you'd see door commands and then waiting). The solution was to apply a syslog patch that became available after some complaining 
Oh and killing the daemon didn't fix it. You had to kill the daemon and delete the syslog.pid file or it'd stay lost.
Carl
Oh and killing the daemon didn't fix it. You had to kill the daemon and delete the syslog.pid file or it'd stay lost.
Carl
|
|
2 More Discussions You Might Find Interesting
1. Solaris
Hi Community
Which are the available entries to forward syslog in syslog.conf
i have put
*.err;kern.debug;daemon.notice;mail.crit;user.alert;user.emerg;kern.notice;auth.notice;kern.warning @172.16.200.50
and it's not going through.giving error message like below:
syslogd:... (2 Replies)
Discussion started by: bentech4u
2 Replies
2. AIX
Hi everyone,
I am trying to configure AIX 6.1 using syslogd to send syslog event to syslog server configured on RHEL. However, RHEL never receives the events.
I have tried to redirect the syslog event on AIX to a local file and successful. Only forwarding to remote server fails.
Firewall... (10 Replies)
Discussion started by: michael_hoang
10 Replies