[syslog-ng] Re: syslog-ng 1.1.31 && Solaris 2.6 SPARC
Bradley Urberg Carlson
bradley@onvoy.com
Mon, 16 Aug 1999 21:15:49 -0500 (CDT)
Erik M. Beebe erik@infi.net wrote on Thu, 12 Aug 1999 16:56:37 -0400:
> I have recently installed syslog-ng 1.1.31 && libol-0.2.3 on a machine
> running SPARC Solaris 2.6; If I connect to port 514/UDP using NetCat,
> syslog-ng logs it just fine. If I try to use "logger" locally, it does
> not.
...
> I don't believe it's any problems with the destination/filter/log lines
> causing this problem -- it looks like syslog-ng just isn't getting what is
> sent to /dev/log. Anyone have any idea what could be causing this?
There are a bunch of messages in the June archive with the thread
"syslog-ng and solaris doors again". Apparently, there is still some work
going into logging messages locally under solaris.
I also tried v1.1.31 with Solaris and found the same problem. My
workaround was to run syslog-ng AND the Solaris syslogd, with syslogd
forwarding all local messages to syslog-ng on the localhost using UDP.
Since syslog-ng works fine from UDP, this gets all the messages
(network-generated + locally-generated) into syslog-ng.
Details:
-syslogd listens to bogus/unused UDP port 999,
and sends local messages to syslog-ng using UDP 999:
*** /etc/services~ Mon Aug 16 21:02:39 1999
--- /etc/services Mon Aug 16 20:28:30 1999
***************
*** 61,63 ****
who 513/udp whod
! syslog 514/udp
talk 517/udp
--- 61,63 ----
who 513/udp whod
! syslog 999/udp
talk 517/udp
*** /etc/syslog.conf~ Mon Mar 29 10:17:35 1999
--- /etc/syslog.conf Mon Aug 16 21:05:03 1999
***************
*** 1,1 ****
! *.debug @loghost
--- 1,1 ----
! *.debug @localhost
-syslog-ng listens to the network-generated messages coming in on
514/UDP, and also listens to locally-generated messages coming in from
syslogd on 999/UDP:
source s_network { udp(ip(0.0.0.0) port(514)); };
source s_syslogd { udp(ip(localhost) port(999)); };