Package: syslog-ng
Version: 3.3.4.dfsg-2
Severity: normal
User: [email protected]
Usertags: wheezy
syslog-ng in unstable does not start if it cannot resolve its loghosts:
henze:~# service syslog-ng start
| Starting system logging: syslog-ngError resolving hostname;
host='heininen.debian.org'
| Error initializing dest driver; dest='loghost-heininen',
id='loghost-heininen#0'
| Error initializing message pipeline;
| failed!
During boot name services are not yet available, so it cannot resolve
these hosts. (Unbound's start depends on a syslog, so syslog-ng
naturally gets started first)
This is a regression from squeeze, where this worked without problems:
| root@schuetz:~# service syslog-ng start
| Starting system logging: syslog-ngError resolving hostname;
host='heininen.debian.org'
| Initiating connection failed, reconnecting; time_reopen='10'
| Error resolving hostname; host='lotti.debian.org'
| Initiating connection failed, reconnecting; time_reopen='10'
| .
| root@schuetz:~# ps xauf | grep -i sysl
| root 14776 0.0 0.0 112312 808 pts/0 S+ 17:58 0:00
\_ grep -i sysl
| root 14768 0.0 0.0 43224 736 ? S 17:58 0:00 supervising
syslog-ng
| root 14769 0.2 0.3 59484 3332 ? Ss 17:58 0:00 \_
/usr/sbin/syslog-ng -p /var/run/syslog-ng.pid
Cheers,
weasel
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
