rsyslog fails to create tcp socket.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rsyslog (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: rsyslog
My package:
ii rsyslog 4.6.4-2ubuntu4
The thing is that when starting rsyslog first drop privileges and then tries to create socket and more. This seems to be a bug, because the same configuration works fine on 10.04. Configuration is attached.
rsyslog output:
May 27 18:37:55 ubuntu01 kernel: imklog 4.6.4, log source = /proc/kmsg started.
May 27 18:37:55 ubuntu01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="5547" x-info="http://
May 27 18:37:55 ubuntu01 rsyslogd: rsyslogd's groupid changed to 103
May 27 18:37:55 ubuntu01 rsyslogd: rsyslogd's userid changed to 101
May 27 18:37:55 ubuntu01 rsyslogd-2039: Could no open output pipe '/dev/xconsole' [try http://
May 27 18:37:55 ubuntu01 rsyslogd-2077: Could not create tcp listener, ignoring port 514. [try http://
Changed in rsyslog (Ubuntu): | |
status: | New → Confirmed |
tags: | added: precise |
Hi,
I have the same problem.
Because rsyslog drops privileges to syslog, and the required port is 514, which can only be used by a process running with root privileges (every port below 1025)
http:// lists.adiscon. net/pipermail/ rsyslog/ 2010-April/ 011700. html
workaround is a port above 1024