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

[Ryan Kather]

Scott,

Thank you for the information.  In my initial browse I'm not seeing
anything updated regarding improved listener behavior, so I think that
sleep workaround stands.  I'm definitely looking into that over either
changing the port or running as root (which I'd like to avoid if at all
possible).

I'll solicit my work to see how they feel on reimbursement for the
proper bug fix to address the privilege race condition.  Chances are
they'll air on the side of cheap and stick with the ugly, unforunately.
Thank you again for your response.

Ryan

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
  Confirmed

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