| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 10/29/13 22:47, Jarry wrote: |
| 5 |
> Hi Gentoo-users, I noticed strange message during boot-up of one of |
| 6 |
> my servers: |
| 7 |
> ______________________________________________________________ |
| 8 |
> |
| 9 |
> * Bringing up interface lo * 127.0.0.1/8 ... |
| 10 |
> [ok] * Adding routes * 127.0.0.0/8 via 127.0.0.1 ... |
| 11 |
> [ok] * Activating additional swap space ... |
| 12 |
> [ok] * setting up tmpfiles.d entries ... |
| 13 |
> [ok] * Initializing random number generator ... |
| 14 |
> [ok] INIT: Entering runlevel: 3 * Starting clamd ... |
| 15 |
> [ok] * Starting freshclam ... |
| 16 |
> [ok] * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) |
| 17 |
> [ok] * Starting syslog-ng... Connection failed; fd='10', |
| 18 |
> server='AF_INET(10.0.0.171:514)', local='AF_INET(0.0.0.0:0)', |
| 19 |
> error='Network is unreachable (101)' Initiating connection failed, |
| 20 |
> reconnecting: time_reopen='60' * Loading iptables state and |
| 21 |
> starting firewall ... [ok] * Bringing up interface enp3s0 * |
| 22 |
> 10.0.0.174 ... [ok] * |
| 23 |
> Adding routes * default via 10.0.0.138 ... |
| 24 |
> [ok] * Starting saslauthd ... |
| 25 |
> [ok] * Starting dovecot ... |
| 26 |
> [ok] * Starting monit ... |
| 27 |
> [ok] |
| 28 |
> ______________________________________________________________ |
| 29 |
> |
| 30 |
> As you see, syslog-ng can not open conection to remote syslog |
| 31 |
> collector. Reason seems to be quite clear: at the time when |
| 32 |
> syslog-ng starts, enp3s0 interface is not up (only loopback). I do |
| 33 |
> not know how this happened, but I think it has something to do with |
| 34 |
> either sendmail, clamav, or dovecot. |
| 35 |
> |
| 36 |
> This is boot-up of my other server (syslog-collector) where neither |
| 37 |
> sendmail nor clamav is installed. As you can see, boot-up order is |
| 38 |
> correct (network interface before syslog-ng): |
| 39 |
> ______________________________________________________________ |
| 40 |
> |
| 41 |
> * Bringing up interface lo * 127.0.0.1/8 ... |
| 42 |
> [ok] * Adding routes * 127.0.0.0/8 via 127.0.0.1 ... |
| 43 |
> [ok] * Activating additional swap space ... |
| 44 |
> [ok] * setting up tmpfiles.d entries ... |
| 45 |
> [ok] * Initializing random number generator ... |
| 46 |
> [ok] INIT: Entering runlevel: 3 * Loading iptables state and |
| 47 |
> starting firewall ... [ok] * Starting monit ... |
| 48 |
> [ok] * Bringing up interface enp3s0 * 10.0.0.171 ... |
| 49 |
> [ok] * Adding routes * default via 10.0.0.138 ... |
| 50 |
> [ok] * Mounting network filesystems ... |
| 51 |
> [ok] * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) |
| 52 |
> [ok] * Starting syslog-ng... |
| 53 |
> [ok] * Starting sshd ... |
| 54 |
> [ok] * Starting vixie-cron ... |
| 55 |
> [ok] |
| 56 |
> ______________________________________________________________ |
| 57 |
> |
| 58 |
> So how can I fix it on the 1st server, so that syslog-ng starts |
| 59 |
> after network interface is up? |
| 60 |
|
| 61 |
init script dependencies and strict requirements? |
| 62 |
|
| 63 |
-----BEGIN PGP SIGNATURE----- |
| 64 |
Version: GnuPG v2.0.20 (GNU/Linux) |
| 65 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 66 |
|
| 67 |
iQEcBAEBAgAGBQJScAOjAAoJEK64IL1uI2han9UH/2YzpEVxxnKDPdQegpqcRlip |
| 68 |
Z4g6fdfHPB8HaYoqJG0L3mPVeNhqFwpAsP/AhT/BLIeDIR6p9G6L19Cx6g5agZ96 |
| 69 |
sgOLL7On+g4OPSH6W81lgIdPaEfitVSXoYHL/BaMshQ2Qq1K47FwcEH9t1U4Zls1 |
| 70 |
5Y2qiu6VcJQN/oKV+apGUofhHD+AiA/CXUbBYpAC3AuHBx5EO8qsq9yMMhlMVonF |
| 71 |
IMQUCPDHlf64NXgsqyxU/8Vlf6XaRNWiq+OZjsw6PckqXl9M3KFZHwbIJ0np2c1M |
| 72 |
U2MPriLkR3DUSESDJw934MSRrj4R//lr42NhbsSc6wB6ifYX6qToNaxiiAy/OSs= |
| 73 |
=dpoP |
| 74 |
-----END PGP SIGNATURE----- |
Archives