Probably a debug log of the startup phase would be useful. Does it work without dropping privileges?
rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Brian Dorling > Sent: Wednesday, November 23, 2011 12:42 PM > To: [email protected] > Subject: Re: [rsyslog]Ominous "Called LogError, msg: Could not create tcp > listener, ignoring port 10514" message > > Brian Dorling <brian_dorling <at> t-online.de> writes: > > > > > Hi, > > saw all the infos about problems with ports below 1024, so chnaged my > > remote logging to use 10514 and am getting the same error. According > > to all the discussions I read, port 10514 should work with dropped > permissions. > > USing rsyslog 4.6.4, supplied with Ubuntu 11.04. > > Didn't find anything detailing exactly which version solved the > > dropped permissions problem. > > > > Has it been solved now? > > > > ANy ideas why I should get this error on a port > 1024? > > > > Thanks in advance Brian > > > > > Sorry, running this on Debian 6.0 with Kernel 2.6.32-5-686. Not Ubuntu. > Strange is that this has been working for months, and now it stopped. > Also, went to port 10514 after getting the same error on port 514. > > Cheers Brian > > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/
