[BusyBox] syslogd: remote logging failed

Nick Fedchik fnm at fusion.ukrsat.com
Thu Jan 23 09:44:04 UTC 2003


Hi ALL!

See the Subject! :(

My bb host:
~ # /sbin/syslogd -C -L -R 192.168.168.2 -m 600
~ # ps -ax
...
187 root   592 S   /sbin/syslogd -C -L -R 192.168.168.2 -m 600
...


My remote host with syslog-ng to receive syslog messages:
#tcpdump -vv -n -X port syslog and host 192.168.168.1
18:31:23.247769 192.168.168.1.32768 > 192.168.168.2.syslog: udp
62 (DF) (ttl 64, id 61470, len 90)
0x0000   4500 005a f01e 4000 4011 791f c0a8 a801       E..Z.. at .@.y.....
0x0010   c0a8 a802 8000 0202 0046 f438 3c34 363e       .........F.8<46>
0x0020   7379 736c 6f67 6420 7374 6172 7465 643a       syslogd.started:
0x0030   2042 7573 7942 6f78 2076 302e 3631 2e70       .BusyBox.v0.61.p
0x0040   7265 2028 3230 3033 2e30 312e 3138 2d30       re.(2003.01.18-0
0x0050   393a                                           9:

My bb host:
~ # logger test
syslogd: cannot write to remote file handle on 192.168.168.2:514
~ # ps -ax
no syslogd process
~ # logread
Jan 23 18:36:03 bbhost <46> syslogd started: BusyBox v0.61.pre
(2003.01.18-09:29+0000)

Is it a bug or I doing wrong something?

Combinations
 /sbin/syslogd -L -R 192.168.168.2 -m 600
 /sbin/syslogd -C -R 192.168.168.2 -m 600
 /sbin/syslogd -R 192.168.168.2 -m 600
 /sbin/syslogd -R 192.168.168.2
has same results.

-- 
Nick Fedchik, FNM3-RIPE(UANIC)
Internet Dept./ISP UkrSat, Kiev, Ukraine



More information about the busybox mailing list