| 1 |
Hi Gentoo-users, |
| 2 |
I noticed strange message during boot-up of one of my servers: |
| 3 |
______________________________________________________________ |
| 4 |
|
| 5 |
* Bringing up interface lo |
| 6 |
* 127.0.0.1/8 ... [ok] |
| 7 |
* Adding routes |
| 8 |
* 127.0.0.0/8 via 127.0.0.1 ... [ok] |
| 9 |
* Activating additional swap space ... [ok] |
| 10 |
* setting up tmpfiles.d entries ... [ok] |
| 11 |
* Initializing random number generator ... [ok] |
| 12 |
INIT: Entering runlevel: 3 |
| 13 |
* Starting clamd ... [ok] |
| 14 |
* Starting freshclam ... [ok] |
| 15 |
* Checking your configfile (/etc/syslog-ng/syslog-ng.conf) [ok] |
| 16 |
* Starting syslog-ng... |
| 17 |
Connection failed; fd='10', server='AF_INET(10.0.0.171:514)', |
| 18 |
local='AF_INET(0.0.0.0:0)', error='Network is unreachable (101)' |
| 19 |
Initiating connection failed, reconnecting: time_reopen='60' |
| 20 |
* Loading iptables state and starting firewall ... [ok] |
| 21 |
* Bringing up interface enp3s0 |
| 22 |
* 10.0.0.174 ... [ok] |
| 23 |
* Adding routes |
| 24 |
* default via 10.0.0.138 ... [ok] |
| 25 |
* Starting saslauthd ... [ok] |
| 26 |
* Starting dovecot ... [ok] |
| 27 |
* Starting monit ... [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). |
| 33 |
I do not know how this happened, but I think it has something |
| 34 |
to do with either sendmail, clamav, or dovecot. |
| 35 |
|
| 36 |
This is boot-up of my other server (syslog-collector) where |
| 37 |
neither sendmail nor clamav is installed. As you can see, |
| 38 |
boot-up order is correct (network interface before syslog-ng): |
| 39 |
______________________________________________________________ |
| 40 |
|
| 41 |
* Bringing up interface lo |
| 42 |
* 127.0.0.1/8 ... [ok] |
| 43 |
* Adding routes |
| 44 |
* 127.0.0.0/8 via 127.0.0.1 ... [ok] |
| 45 |
* Activating additional swap space ... [ok] |
| 46 |
* setting up tmpfiles.d entries ... [ok] |
| 47 |
* Initializing random number generator ... [ok] |
| 48 |
INIT: Entering runlevel: 3 |
| 49 |
* Loading iptables state and starting firewall ... [ok] |
| 50 |
* Starting monit ... [ok] |
| 51 |
* Bringing up interface enp3s0 |
| 52 |
* 10.0.0.171 ... [ok] |
| 53 |
* Adding routes |
| 54 |
* default via 10.0.0.138 ... [ok] |
| 55 |
* Mounting network filesystems ... [ok] |
| 56 |
* Checking your configfile (/etc/syslog-ng/syslog-ng.conf) [ok] |
| 57 |
* Starting syslog-ng... [ok] |
| 58 |
* Starting sshd ... [ok] |
| 59 |
* Starting vixie-cron ... [ok] |
| 60 |
______________________________________________________________ |
| 61 |
|
| 62 |
So how can I fix it on the 1st server, so that syslog-ng starts |
| 63 |
after network interface is up? |
| 64 |
|
| 65 |
Jarry |
| 66 |
|
| 67 |
-- |
| 68 |
_______________________________________________________________ |
| 69 |
This mailbox accepts e-mails only from selected mailing-lists! |
| 70 |
Everything else is considered to be spam and therefore deleted. |
Archives