-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/29/13 22:47, Jarry wrote: > Hi Gentoo-users, I noticed strange message during boot-up of one of > my servers: > ______________________________________________________________ > > * Bringing up interface lo * 127.0.0.1/8 ... > [ok] * Adding routes * 127.0.0.0/8 via 127.0.0.1 ... > [ok] * Activating additional swap space ... > [ok] * setting up tmpfiles.d entries ... > [ok] * Initializing random number generator ... > [ok] INIT: Entering runlevel: 3 * Starting clamd ... > [ok] * Starting freshclam ... > [ok] * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) > [ok] * Starting syslog-ng... Connection failed; fd='10', > server='AF_INET(10.0.0.171:514)', local='AF_INET(0.0.0.0:0)', > error='Network is unreachable (101)' Initiating connection failed, > reconnecting: time_reopen='60' * Loading iptables state and > starting firewall ... [ok] * Bringing up interface enp3s0 * > 10.0.0.174 ... [ok] * > Adding routes * default via 10.0.0.138 ... > [ok] * Starting saslauthd ... > [ok] * Starting dovecot ... > [ok] * Starting monit ... > [ok] > ______________________________________________________________ > > As you see, syslog-ng can not open conection to remote syslog > collector. Reason seems to be quite clear: at the time when > syslog-ng starts, enp3s0 interface is not up (only loopback). I do > not know how this happened, but I think it has something to do with > either sendmail, clamav, or dovecot. > > This is boot-up of my other server (syslog-collector) where neither > sendmail nor clamav is installed. As you can see, boot-up order is > correct (network interface before syslog-ng): > ______________________________________________________________ > > * Bringing up interface lo * 127.0.0.1/8 ... > [ok] * Adding routes * 127.0.0.0/8 via 127.0.0.1 ... > [ok] * Activating additional swap space ... > [ok] * setting up tmpfiles.d entries ... > [ok] * Initializing random number generator ... > [ok] INIT: Entering runlevel: 3 * Loading iptables state and > starting firewall ... [ok] * Starting monit ... > [ok] * Bringing up interface enp3s0 * 10.0.0.171 ... > [ok] * Adding routes * default via 10.0.0.138 ... > [ok] * Mounting network filesystems ... > [ok] * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) > [ok] * Starting syslog-ng... > [ok] * Starting sshd ... > [ok] * Starting vixie-cron ... > [ok] > ______________________________________________________________ > > So how can I fix it on the 1st server, so that syslog-ng starts > after network interface is up?
init script dependencies and strict requirements? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJScAOjAAoJEK64IL1uI2han9UH/2YzpEVxxnKDPdQegpqcRlip Z4g6fdfHPB8HaYoqJG0L3mPVeNhqFwpAsP/AhT/BLIeDIR6p9G6L19Cx6g5agZ96 sgOLL7On+g4OPSH6W81lgIdPaEfitVSXoYHL/BaMshQ2Qq1K47FwcEH9t1U4Zls1 5Y2qiu6VcJQN/oKV+apGUofhHD+AiA/CXUbBYpAC3AuHBx5EO8qsq9yMMhlMVonF IMQUCPDHlf64NXgsqyxU/8Vlf6XaRNWiq+OZjsw6PckqXl9M3KFZHwbIJ0np2c1M U2MPriLkR3DUSESDJw934MSRrj4R//lr42NhbsSc6wB6ifYX6qToNaxiiAy/OSs= =dpoP -----END PGP SIGNATURE-----
