From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B4581138542 for ; Tue, 29 Oct 2013 18:51:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A56B9E0A07; Tue, 29 Oct 2013 18:51:32 +0000 (UTC) Received: from smtp33.i.mail.ru (smtp33.i.mail.ru [94.100.177.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5F65AE09EB for ; Tue, 29 Oct 2013 18:51:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=Ie66asrwg4WF2Zx7mL/TKo3chnJA/7UgTeXJmG2Nt5U=; b=IoqO+GttyMXdP/ywUOAV08RKeka4YOxK8ZSequ+sEvkIuS44ulcpjvQmoAKUqE+VELBEiMvlPb/3O4PyuRLM1/7PgEf8+m4WIPXYFIdpn29qFl9YZ4Y4MScBu27RnUyWOtaAfi2XaeQ/E19T9jIxfcHw5d6EDoYPRC4/9xC2JlM=; Received: from [95.221.4.158] (port=48680) by smtp33.i.mail.ru with esmtpa (envelope-from ) id 1VbEO1-0007Bb-2k for gentoo-user@lists.gentoo.org; Tue, 29 Oct 2013 22:51:29 +0400 Message-ID: <527003A4.902@mail.ru> Date: Tue, 29 Oct 2013 22:51:16 +0400 From: the User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130911 Thunderbird/17.0.9 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How can I fix wrong boot order? References: <527002DD.1040509@gmail.com> In-Reply-To: <527002DD.1040509@gmail.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam: Not detected X-Mras: Ok X-Archives-Salt: 375cae0d-d775-48d8-ad79-7dbc4bbc855c X-Archives-Hash: 8715b5df8bee858588e376576b0f77ca -----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-----