From owner-freebsd-questions@FreeBSD.ORG  Fri Aug 29 05:38:34 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 0E8D116A4BF
	for <freebsd-questions@freebsd.org>;
	Fri, 29 Aug 2003 05:38:34 -0700 (PDT)
Received: from exchange.wan.no (exchange.wan.no [80.86.128.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C520243FD7
	for <freebsd-questions@freebsd.org>;
	Fri, 29 Aug 2003 05:38:32 -0700 (PDT)
	(envelope-from sten.daniel.sorsdal@wan.no)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Aug 2003 14:36:01 +0200
Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F07DF27@exchange.wanglobal.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Syslogd dying often on different hardware - hackers?
Thread-Index: AcNuKmfTcAZvjCvBTXWFZQJgU59NzQ==
From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= <sten.daniel.sorsdal@wan.no>
To: <freebsd-questions@freebsd.org>
Subject: 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 <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Aug 2003 12:38:34 -0000


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:

pid 17263 (syslogd), uid 0: exited on signal 11
pid 87264 (syslogd), uid 0: exited on signal 11

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

The command lines are either;	-nccvvs -ccvvs (but mostly) -vvs

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.


When i ran syslogd -dvvs in 'screen' it started logging to remote =
'loghost'.=20
For a -long- time it kept repeating "Host is down" and tried to log to =
'loghost'=20
'loghost' is a local alias.

I'm finding it hard to reproduce.

-- Sten