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 D85421381F3 for ; Fri, 19 Jul 2013 21:03:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3F9F5E0933; Fri, 19 Jul 2013 21:03:40 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by pigeon.gentoo.org (Postfix) with ESMTP id 00DE2E08ED for ; Fri, 19 Jul 2013 21:03:38 +0000 (UTC) Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r6JL3bF7000515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 19 Jul 2013 17:03:37 -0400 Received: from where.rdu.redhat.com (dhcp129-155.rdu.redhat.com [10.13.129.155]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r6JL3a7C012226 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Fri, 19 Jul 2013 17:03:37 -0400 Message-ID: <51E9A9A8.3020908@electronsweatshop.com> Date: Fri, 19 Jul 2013 17:03:36 -0400 From: Randy Barlow User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17.1 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] syslog-ng segfaults References: <1374187274.26910.2.camel@scurvy.electronsweatshop.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 X-Archives-Salt: bd4b58b7-d52f-4c3a-8725-492e072941bd X-Archives-Hash: 723685498768faee67952a804c667fd9 Alexey Mishustin wrote: >> So, restarting syslog-ng should be all that's required to fix it - reboot is >> >overkill. > As for me, first I updated syslog-ng, then I issued > '/etc/init.d/syslog-ng reload' (by mistake, instead of 'restart'), and > then 'restart' as I should. Then, just when syslog-ng was restarting, > the segfault happened. I also noted that restarting syslog didn't seem to solve the problem. I do think Adam's reasoning makes sense, but there must be something else that needed to be restarted as well. -- R