← Back to team overview

touch-packages team mailing list archive

[Bug 789174] Re: rsyslog fails to create tcp socket.

 

On my Ubuntu 12.04 machine (upgraded from 10.04) it was apparmor
blocking the tcp listener. Adding the lines

network inet dgram,
network inet6 dgram,
network inet stream,
network inet6 stream,

to "/etc/apparmor.d/local/usr.sbin.rsyslogd" worked for me (as described
on http://serverfault.com/questions/450546/rsyslogd-not-listening-on-
port).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/789174

Title:
  rsyslog fails to create tcp socket.

Status in rsyslog package in Ubuntu:
  Fix Released

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://www.rsyslog.com";] (re)start
  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://www.rsyslog.com/e/2039 ]
  May 27 18:37:55 ubuntu01 rsyslogd-2077: Could not create tcp listener, ignoring port 514. [try http://www.rsyslog.com/e/2077 ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+subscriptions