> -----Original Message----- > From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog- > boun...@lists.adiscon.com] On Behalf Of Rainer Gerhards > Sent: Saturday, July 02, 2011 1:06 PM > To: rsyslog-users > Subject: [rsyslog] imudp activation failure - was: Remote syslogging > througha (broken) VPN
> > P.S. I've got messages: > > rsyslogd3: activation of module imudp.so failed [try > > http://www.rsyslog.com/e/-3 ] > > rsyslogd3: activation of module imudp.so failed [try > > http://www.rsyslog.com/e/-3 ] > > Did you run rsyslogd as root? As far as I can see, no listeners could > be > activated. Obviously, error reporting needs to be improved, will check > that > out. Sorry, I should have checked that first. The debug log indicates that the error message "imudp: no listeners could be started, input not activated" was generated right in front of the message you quote. Wasn't that present inside your log? Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
