From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-151891-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id B9DAD138547
	for <garchives@archives.gentoo.org>; Tue, 29 Oct 2013 19:31:24 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 88FD0E0A45;
	Tue, 29 Oct 2013 19:31:14 +0000 (UTC)
Received: from mail.persimplex.net (mail.persimplex.net [64.22.124.52])
	(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 967BDE0A03
	for <gentoo-user@lists.gentoo.org>; Tue, 29 Oct 2013 19:31:13 +0000 (UTC)
Message-ID: <52700CFE.4010703@persimplex.net>
Date: Tue, 29 Oct 2013 23:31:10 +0400
From: victor romanchuk <rom@persimplex.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
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.5.2
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
X-Authenticated-At: persimplex.net/0
X-Archives-Salt: 05006b90-9d2c-447a-b8e1-101df859fbc8
X-Archives-Hash: e19e327480238227f853b1ff39fe9916

On 10/29/2013 10:47 PM, Jarry wrote:
> Hi Gentoo-users,
> I noticed strange message during boot-up of one of my servers:
> ______________________________________________________________
>

[snip]

>
> 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.
>

[snip]

> ______________________________________________________________
>
> So how can I fix it on the 1st server, so that syslog-ng starts
> after network interface is up?
>
> Jarry
>

disable explicit syslog-ng service startup from the runlevel (one would start anyway as a dependency)

rc-update del syslog-ng

does the trick

victor