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 6F3151381F3 for ; Fri, 19 Jul 2013 09:06:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 46846E0C76; Fri, 19 Jul 2013 09:06:22 +0000 (UTC) Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0A44FE0C2F for ; Fri, 19 Jul 2013 09:06:20 +0000 (UTC) Received: by mail-ee0-f50.google.com with SMTP id d49so2201526eek.37 for ; Fri, 19 Jul 2013 02:06:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=zx/EgLzgEs4fMbH2KNiyABncyI0+lCXf7L5gqRDwPs4=; b=LByz5FvT8P5Sq+IbiZAJ8jmP/StktXX5veZARmV/E+gnwxUQRbvoNnlVwy7uKGTTzq dOEVSlcS6JxbW2XNLuZWxSRS4UDkGTW+/NMCFl8xMSEdsQZTuAzSglaBVx2yDqzd1oVS ZzWZFSYyQl9GrX0Y2xYnMtIvuBlyKzLDju9N33DEifMYYPYYLP+6bDz5pepiZOC9Vd/D sDiQh0rf6Rkc4rNMY1A7blpd9vAf6yGZH/sqEMngxl2Zlzn4FTRKwqjNYMQ1RM4RliYw og+3MvPLgeQqeX7/7YHytZCiphr+HhYSz8W284B2ois9EKNRcsJq0vOjMJIXKOpm0M8V /7Ww== 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 X-Received: by 10.15.100.195 with SMTP id bn43mr14566754eeb.153.1374224779574; Fri, 19 Jul 2013 02:06:19 -0700 (PDT) Received: by 10.14.118.4 with HTTP; Fri, 19 Jul 2013 02:06:19 -0700 (PDT) X-Originating-IP: [217.151.131.12] In-Reply-To: References: <1374187274.26910.2.camel@scurvy.electronsweatshop.com> Date: Fri, 19 Jul 2013 13:06:19 +0400 Message-ID: Subject: Re: [gentoo-user] syslog-ng segfaults From: Alexey Mishustin To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnpcpBt7BuZS5dEmWJg2YLswcqpd6lRP+5ufj1KqRkC/HmPI2VxMbI6FLAHi+o9mE4Wg/sP X-Archives-Salt: a93fdbda-5437-4236-8753-f59ea1bfa21e X-Archives-Hash: d50bc03eb20bb0a6adfe5119de8b8f38 2013/7/19 Adam Carter : >> > syslog-ng[32015]: segfault at 44d8 ip 00007f4f3fa23c83 sp >> > 00007fffb233b940 error 4 in libsyslog-ng.so.0.0.0 (deleted)[7f4f3f9eb000 >> > +67000] >> > >> > Has anybody else seen anything like that? > > > Perhaps you forgot to restart syslog-ng after the update? > > # ldd /usr/sbin/syslog-ng | grep libsyslog-ng > libsyslog-ng-3.4.2.so => /usr/lib64/libsyslog-ng-3.4.2.so > (0x00007fe7dfe5b000) > > If the library was called libsyslog-ng.so.0.0.0 in the previous version, and > if syslog-ng tried to reload it, it would fail after the update which could > cause the segfault. > > 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. > Also, any errors in the config file should not cause segfault. If it does, > that indicates a bug in the input validation/config parsing code. Errors in > the config should result in a graceful termination. -- Regards, Alex