Problem with syslogd and syslog-ng...
Hello Can some one help me with this? I have syslog-ng running on the loggserver and syslogd on the clients and syslog-ng servern dosn't trig on all levels. ex. on the client(etc/syslog.conf) *.debug @loghost *.info @loghost #*.notice @loghost #*.warning @loghost #*.err @loghost #*.crit @loghost #*.alert @loghost #*.emerg @loghost gives 2 entries in the logfile #*.debug @loghost *.info @loghost #*.notice @loghost #*.warning @loghost #*.err @loghost #*.crit @loghost #*.alert @loghost #*.emerg @loghost gives zero entries in the logfile?? I want to log all levels from warning to emerg. *.warning @loghost in the syslog.conf file would be enough or is in't? And this should gives one entrie in the logfile? the syslog-ng.conf looks like this: options { use_fqdn(yes); keep_hostname(yes); use_dns(yes); long_hostnames(off); sync(3); log_fifo_size(1000); }; source all { sun-streams ("/dev/log" door("/etc/.syslog_door")); internal(); udp(); }; # automatic host sorting # set it up destination hosts { file("/var/syslog/hosts/$HOST/$FACILITY_$YEAR-$MONTH-$DAY" owner(root) group(root) perm(0600) dir_perm(0700) create_dirs(yes)); }; # log by host log { source(all); destination(hosts); }; /Benke -- Bengt Olsson Blekinge Tekniska Högskola Datorenheten Campus Gräsvik Vallhallavägen 1 371 79 Karlskrona Mail: bol@bth.se Tel: 0455-385152 Mobil: 0708-787 780
On Thu, Aug 08, 2002 at 01:58:26PM +0200, BENGT OLSSON wrote:
Hello
Can some one help me with this?
I have syslog-ng running on the loggserver and syslogd on the clients and syslog-ng servern dosn't trig on all levels.
ex.
on the client(etc/syslog.conf)
*.debug @loghost *.info @loghost #*.notice @loghost #*.warning @loghost #*.err @loghost #*.crit @loghost #*.alert @loghost #*.emerg @loghost
gives 2 entries in the logfile
#*.debug @loghost *.info @loghost #*.notice @loghost #*.warning @loghost #*.err @loghost #*.crit @loghost #*.alert @loghost #*.emerg @loghost
gives zero entries in the logfile??
you should first check what kind of messages are generated. try strace-ing the client syslogd and see whether it sends messages or not. if you see a message using strace you should see something like this: <number>stamp host program message... number is a bitfield, lowest 3 bits specify the priority of the message (debug, info, notice, warning, err, crit, alert, emerg) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
Balazs Scheidler
-
BENGT OLSSON