From owner-freebsd-questions@FreeBSD.ORG Fri Aug 29 06:24:05 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CD0116A4BF for ; Fri, 29 Aug 2003 06:24:05 -0700 (PDT) Received: from smtp.infracaninophile.co.uk (happy-idiot-talk.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3954143F3F for ; Fri, 29 Aug 2003 06:23:55 -0700 (PDT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost [127.0.0.1]) h7TDMVLa001605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Aug 2003 14:23:40 +0100 (BST) (envelope-from matthew@happy-idiot-talk.infracaninophile.co.uk) Received: (from matthew@localhost)h7TDMVFk001604; Fri, 29 Aug 2003 14:22:31 +0100 (BST) (envelope-from matthew) Date: Fri, 29 Aug 2003 14:22:31 +0100 From: Matthew Seaman To: Sten Daniel =?iso-8859-1?Q?S=F8rsdal?= Message-ID: <20030829132231.GA1325@happy-idiot-talk.infracaninophile.co.uk> Mail-Followup-To: Matthew Seaman , Sten Daniel =?iso-8859-1?Q?S=F8rsdal?= , freebsd-questions@freebsd.org References: <0AF1BBDF1218F14E9B4CCE414744E70F07DF27@exchange.wanglobal.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <0AF1BBDF1218F14E9B4CCE414744E70F07DF27@exchange.wanglobal.net> User-Agent: Mutt/1.5.4i X-Spam-Status: No, hits=-10.2 required=5.0 tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2, QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_MUTT autolearn=ham version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-questions@freebsd.org Subject: Re: Syslogd dying often on different hardware - hackers? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2003 13:24:05 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 29, 2003 at 02:36:01PM +0200, Sten Daniel S=F8rsdal wrote: >=20 > Many of my servers tend to have their syslogd die on them. > In dmesg i could see the signal number on one of them; 11 > But kill -l doesnt reveal which that is: >=20 > pid 17263 (syslogd), uid 0: exited on signal 11 > pid 87264 (syslogd), uid 0: exited on signal 11 See /usr/include/sys/signal.h --- signal 11 is SIGSEGV, segmentation violation. Most of the time that it's mentioned on this list it's due to memory hardware errors causing crashes. However, in this case as the problem is localized to syslogd then I think you've found a bug. > /var/log has lots of space, newsyslog does it's job regularly. > The versions vary from 4.7 to 4.9-prerelease. Lots of memory available. > Hardware ranges from 1ghz celerons, 400mhz p3's, 1.6ghz p4's. >=20 > The command lines are either; -nccvvs -ccvvs (but mostly) -vvs >=20 > They log to remote host that is currently unavailable.=20 > (router emites destination host unreachable). > The reason i mention this is that many types of software misbehave=20 > when they receive this message. >=20 >=20 > When i ran syslogd -dvvs in 'screen' it started logging to remote 'loghos= t'.=20 > For a -long- time it kept repeating "Host is down" and tried to log to 'l= oghost'=20 > 'loghost' is a local alias. >=20 > I'm finding it hard to reproduce. Did you compile the system with a higher optimization level than the recommended -O? If so, then a) try recompiling using the recommend optimization levels, which should cure your crashing problem and b) you've found a bug in the system C compiler, which may or may not get fixed, seeing as gcc-2.95.4 is quite a lot older that the current 3.3.x version as seen in FreeBSD 5.x. Does this happen often enough that you can tell if it's happening on all your machines or not? Perhaps you are using CPUTYPE specific optimizations -- again, try compiling without and see if the problem goes away. If, on the other hand, you haven't used excessive levels of optimization, then there's something special about your environment that has tickled a bug in syslogd. Is this the same bug as PR bin/51253? This should certainly be reported through send-pr(1), and all extra information you can supply that may lead someone to be able to reproduce the problem would be really useful. Have you got a core dump from syslogd? If so, keep hold of it, and the corresponding syslogd binary from /usr/obj (which should not have hat debug symbols stripped out) as anyone working on this is likely to ask you for a backtrace. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/T1OXdtESqEQa7a0RAiKhAJ9Ul2FLmsYLxHGgUS2QTzoFtBiRiACfTVxD +HR4anUvL9L/2UhKyaLyitA= =imqi -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/--