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
also fixed in 14.04, YEaaah :)
--
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:
Marking as Fix Released based on comment #20, thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed = Fix Released
--
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
Also seeing this in Raring. Was hoping to use this server for syslog,
this is pretty disappointing.
--
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.
I am experiencing this on Raring as well.
** Tags added: quantal raring
--
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
Hi,
an easy fix, but it almost takes 2 years :((( What horrible. But right now it
is running on port 514 . Thanks Rainer...
--
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
an easy fix...
http://www.rsyslog.com/ubuntu-repository/
--
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
I thing, it is a Bug. Normal for suid progs IMHO is: make thing which
need root privileges (e.g. bind to port below 1024) and then drop
privileges., or not ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This problem is still here..
for Server LTS this is bad..
i tried also the raring version, and...
GOOD WORK !!
Mar 5 21:37:09 oms kernel: imklog 5.8.11, log source = /proc/kmsg started.
Mar 5 21:37:09 oms rsyslogd: [origin software=rsyslogd swVersion=5.8.11
x-pid=25002
Can't quite believe it, centralized logging on standard 514 is not
possible while not running as root or without paying 2 weeks of upstream
redesign of a piece of code which could have been done correctly the
first time?
Going to reconsider syslog-ng...
--
You received this bug notification
** Tags added: precise
--
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:
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
The example server configuration listening on TCP 514 that fails.
** Attachment added: Ubuntu 12.04 LTS Server rsyslog.conf from rsyslog
5.8.6-1ubuntu8 Example
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+attachment/3265563/+files/rsyslog.conf
--
You received this bug
Ryan, the pipermail link above is to upstream discussion about this. Unless
there is something upstream newer than that 2 year old information, your
options are:
a.) run rsyslog as root by removing the $PrivDropToUser and $PrivDropToGroup
options, or possibly overriding them in
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
This worked for me also, port 1025.
--
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:
I changed the port from 514 to 1025(bigger that 1024 ) in /etc/rsyslog.conf
file in the TCP part nad this worked.
is this a wrong solution and if it is ok why don't change the port until the
bug fixed in rsyslog?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hacky workaround but if you have some devices that can only talk to port 514
drop privs and listen on a high port. (10514)
# redirect traffic to high port with iptables
/sbin/iptables -t nat -A PREROUTING -j REDIRECT -p udp --destination-port 514
--to-ports 10514
--
You received this bug
@phillyclaude Sleep will not solve the issue, the only workaround is in
my reaction on 2011-06-09
--
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
has anyone figured out a workaround for this? Maybe adding a sleep
somewhere might help?
--
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
** Changed in: rsyslog (Ubuntu)
Status: New = Confirmed
--
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
And a other problem with Drop Privileges.
If you use $template ApacheRemoteCustom,/some/path/%HOSTNAME%.log
rsyslog can create the file, but not write to it.
To make this possible you have to change /etc/rsyslog.conf
$PrivDropToGroup syslog
To
$PrivDropToGroup adm
--
You received this bug
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
** Attachment added: rsyslog.conf
https://bugs.launchpad.net/bugs/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
24 matches
Mail list logo
