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 ABD47138CC5 for ; Tue, 24 Mar 2015 09:14:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 446B4E0979; Tue, 24 Mar 2015 09:14:16 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) by pigeon.gentoo.org (Postfix) with ESMTP id 10481E086E for ; Tue, 24 Mar 2015 09:14:15 +0000 (UTC) Received: from [142.196.200.180] ([142.196.200.180:37034] helo=navi.localnet) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id B3/7B-09217-6EA21155; Tue, 24 Mar 2015 09:14:14 +0000 From: Fernando Rodriguez To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] syslog-ng: reporting no space though there's plenty Date: Tue, 24 Mar 2015 05:13:41 -0400 Message-ID: <2520750.BR9qhanJsz@navi> User-Agent: KMail/4.14.3 (Linux/3.19.1; KDE/4.14.3; x86_64; ; ) In-Reply-To: <55110BD1.30207@gmail.com> References: <55104148.8060803@gartencenter-vaehning.de> <55110BD1.30207@gmail.com> 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 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 X-Archives-Salt: e8a3d54d-b658-44d8-a64c-4ccd95b80add X-Archives-Hash: e36d2ec7b05218144a3127675100240a On Tuesday, March 24, 2015 9:01:37 AM Alan McKinnon wrote: > On 23/03/2015 18:37, hw wrote: > > > > Hi, > > > > syslog-ng keeps reporting: > > > > > > Mar 23 17:34:41 sunflo-mx syslog-ng[27532]: Error suspend timeout has > > elapsed, attempting to write again; fd='15' > > Mar 23 17:34:41 sunflo-mx syslog-ng[27532]: Suspending write operation > > because of an I/O error; fd='15', time_reopen='60' > > > > > > while there's plenty of disk space available. Restarting it didn't > > help. This is from an LXC container --- could there be some disk limit > > in effect by default which I don't know about? > > > > > You are on the wrong track. That error message does not say there is no > space available. > > It says the disk is not available, something very different. Check dmesg. > > It just says that a write failed. It could be anything. -- Fernando Rodriguez