Bug #14609
closed
When server syslog listen on another port than 514, it does not notify the agents with syslog
Added by Félix DALLIDET over 5 years ago.
Updated over 4 years ago.
Category:
System techniques
Description
On an old ubuntu server, freshly upgraded in 5.0.9, the server still listen on 5514.
A newly accepted agent did not adapt its syslog conf to send the logs on the adequate port and was sending them on 514 instead.
It was on a Slackware, using syslog.
it does work with rsyslog and syslog-ng
the issue is that syslogd dosn't support other port than 514
- Target version changed from 5.0.9 to 5.0.10
- Target version changed from 5.0.10 to 5.0.11
- Target version changed from 5.0.11 to 5.0.12
- Target version changed from 5.0.12 to 5.0.13
- Target version changed from 5.0.13 to 5.0.14
- Target version changed from 5.0.14 to 5.0.15
- Target version changed from 5.0.15 to 5.0.16
- Target version changed from 5.0.16 to 5.0.17
- Target version changed from 5.0.17 to 5.0.18
- Status changed from New to Resolved
I'm closing this one since it is resolved in 6.0 by not using syslog anymore and 5.0 is EOL.
Also available in: Atom
PDF