I am also seeing this bug, and would like to see this resolved outside of the workaround to a port higher than 1024. It seems to be a problem relating to binding the TCP port later after it has already dropped permissions. My rsyslog.conf file (attached) is using the $PrivDropToUser syslog and $PrivDropToGroup syslog directives.
Ubuntu Process Info syslog 29622 0.0 0.3 262268 3404 ? Sl Jun12 7:33 rsyslogd -c5 My centos/rhel systems do not exhibit this bug, but after looking it seems they are running rsyslog as root by default. RHEL Process Info root 2347 2.6 0.0 416916 2088 ? Sl Jun20 2236:08 /sbin/rsyslogd -i /var/run/syslogd.pid -c 4 Package Version: rsyslog 5.8.6-1ubuntu8 ** Attachment added: "Ubuntu 12.04 LTS rsyslog.conf from rsyslog 5.8.6-1ubuntu8" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+attachment/3265553/+files/rsyslog.conf ** Attachment removed: "rsyslog.conf" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+attachment/2144742/+files/rsyslog.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789174 Title: rsyslog fails to create tcp socket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
