Menu
▾
▴
#104 Suse 10 issue - syslog-ng
Suse 10 uses Syslog-ng. Webmin can be configured to
use it, but it inserts something into the .conf file that
causes syslog to not start at next reboot. Hence
Webmin also doesn't start.
I can't find anything to indicate how to configure it
correctly... I may be doing somethign wrong! Would be
good it Webmin supported it "out of the box" with logs
being so important for admin.
Logged In: YES
user_id=129364
Syslog-ng uses a completely different (and hard to support)
config file format from normal syslog, so you cannot use the
existing Webmin module to configure it. I will add support
for syslog-ng some day, but it is tricky due to the
complexity of the syslog-ng config file :-(
Logged In: YES
user_id=493548
Thanks, appreciate the issue.
I've switching back to the old syslogd (on the Suse 10 CD's)
This issue seems to have masked another problem - Webmin
doens't auto start in Suse 10 when running syslog-ng, despite
a) being set to start in xinetd at runlevel 5 and
b) can start manually without error
Now back with old syslogd Webmin auto starts OK - nothing in
the log with syslog-ng to indicate the problem :-(
Logged In: YES
user_id=129364
Perhaps webmin is trying and failing to contact the syslog
server ..
Try editing /etc/webmin/miniserv.conf and removing the
syslog=1 line..