syslog Post: 302086939

Sponsored Content

Operating Systems Solaris syslog Post 302086939 by BOFH on Monday 28th of August 2006 10:06:32 PM

08-28-2006

Registered User

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 Smilie

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

BOFH

View Public Profile for BOFH

Find all posts by BOFH

2 More Discussions You Might Find Interesting

1. Solaris

Which are the available entries to forward syslog in syslog.conf?

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. AIX

Cannot send syslog event from AIX 6.1 to RHEL Syslog server

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...

LEARN ABOUT DEBIAN

log::agent::driver::syslog

Agent::Driver::Syslog(3pm)				User Contributed Perl Documentation				Agent::Driver::Syslog(3pm)

NAME

       Log::Agent::Driver::Syslog - syslog logging driver for Log::Agent

SYNOPSIS

	use Log::Agent;
	require Log::Agent::Driver::Syslog;

	my $driver = Log::Agent::Driver::Syslog->make(
	    -prefix	=> prefix,
	    -facility	=> "user",
	    -showpid	=> 1,
	    -socktype	=> "unix",
	    -logopt	=> "ndelay",
	);
	logconfig(-driver => $driver);

DESCRIPTION

       The syslog logging driver delegates logxxx() operations to syslog() via the Sys::Syslog(3) interface.

       The creation routine make() takes the following switches:

       "-facility" => facility
	   Tell syslog() which facility to use (e.g. "user", "auth", "daemon").  Unlike the Sys::Syslog(3) interface, the facility is set once and
	   for all: every logging message will use the same facility.

	   If you wish to log something to "auth" for instance, then do so via Sys::Syslog directly: there is no guarantee that the application
	   will configure its Log::Agent to use syslog anyway!

       "-logopt" => syslog options
	   Specifies logging options, under the form of a string containing zero or more of the words ndelay, cons or nowait.

       "-prefix" => prefix
	   The prefix here is syslog's identification string.

       "-showpid" => flag
	   Set to true to have the PID of the process logged. It is false by default.

       "-socktype" => (unix | inet)
	   Specifies the logging socket type to use. The default behaviour is to use Sys:Syslog's default.

CHANNELS

       All the channels go to syslog(), of course.

AUTHOR

       Raphael Manfredi <Raphael_Manfredi@pobox.com>

SEE ALSO

       Log::Agent::Driver(3), Log::Agent::Channel::Syslog(3).

perl v5.10.0							    2002-03-09						Agent::Driver::Syslog(3pm)