From owner-freebsd-stable@FreeBSD.ORG Thu Sep 16 19:33:03 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8EF71065670 for ; Thu, 16 Sep 2010 19:33:03 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 824248FC08 for ; Thu, 16 Sep 2010 19:33:03 +0000 (UTC) Received: by vws7 with SMTP id 7so1335374vws.13 for ; Thu, 16 Sep 2010 12:33:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=h1+qJTebXqHWt7SjniFff0XZNCdubl6hzw0v8f7q+lQ=; b=lOZPNrl9v4cog8rzOKpWTKzDzdQp0YdETLQ02ZtyejdZY3TV2Ypm1A0f5nUwNlwnMh G8WkKPz60ZPXqz+0IaAQvLES2ZwGuMkMl2FS6H5gKlt5WHHIyKfMgEr7xdgdZ1FLOIZw 2SInQgnFavOsEn0VpxoZBCrStOeO9l7YMBKL0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=s66/kT0jjKrDVJsy8EQPoEe8omurEYJqY2sP2bQn8RczMlFJnog57Q0i18xlu9zi1U +4K3teLFZ/9IWOWKrRczNaFI6LuxOUCYzv1UIPh/7zVItF+23a+EFH0Zh7Xo9g/Zo5OP KgmQEb6mrpx910JqAqthK3fo2NSIz20NbjAnY= MIME-Version: 1.0 Received: by 10.220.71.136 with SMTP id h8mr2431373vcj.275.1284665582548; Thu, 16 Sep 2010 12:33:02 -0700 (PDT) Received: by 10.220.180.71 with HTTP; Thu, 16 Sep 2010 12:33:02 -0700 (PDT) In-Reply-To: <20100916164930.GA31869@icarus.home.lan> References: <20100916164930.GA31869@icarus.home.lan> Date: Thu, 16 Sep 2010 23:33:02 +0400 Message-ID: From: Michael BlackHeart To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 8.1 Stable Unreasanoble Rebooting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2010 19:33:04 -0000 2010/9/16 Jeremy Chadwick : > On Thu, Sep 16, 2010 at 08:37:29PM +0400, Michael BlackHeart wrote: >> Today I've got a pretty strange event. It looks like a reboot but >> unreasonable as far as I see. Before server's uptime was over month, >> it's sometimes have to reboot for kernel updates or somethings like >> that. I've digen all logs and didn't find a reason, so here they all. >> >> auth.log >> Sep 16 13:59:58 diablo sshd[2284]: Received signal 15; terminating. >> Sep 16 14:04:26 diablo sshd[2290]: Server listening on 0.0.0.0 port 2244= 2. >> >> cron - nothing >> debug.log - nothing >> dmesg - nothing >> >> messages >> Sep 16 13:44:55 diablo transmission-daemon[7965]: Couldn't create >> socket: Protocol not supported (fdlimit.c:651) >> Sep 16 13:45:31 diablo last message repeated 5 times >> Sep 16 13:47:23 diablo last message repeated 13 times >> Sep 16 13:57:40 diablo last message repeated 51 times >> Sep 16 13:59:48 diablo last message repeated 12 times >> Sep 16 14:00:18 diablo named[1575]: stopping command channel on 127.0.0.= 1#953 >> Sep 16 14:00:18 diablo named[1575]: exiting >> Sep 16 14:00:18 diablo syslogd: exiting on signal 15 >> Sep 16 14:02:31 diablo syslogd: kernel boot file is /boot/kernel/kernel >> Sep 16 14:02:31 diablo kernel: Copyright (c) 1992-2010 The FreeBSD Proje= ct. >> {...} > > This sure looks like a legitimate reboot to me (e.g. shutdown -r now); > note how your system daemons (named, syslogd) are being shut down with > SIGTERM. =A0You can check with "last" (shutdown/reboot vs. crash). > > > I would highly recommend taking this machine offline and reinstalling > the OS, in addition to newfs'ing all existing filesystems (restore from > last known good backup). =A0buildworld/installworld and > buildkernel/installkernel may not be enough depending on what the > individual did. =A0It's likely the machine could be compromised in some > way, especially if there's any service on it which is public-facing, > regardless of authentication mechanisms you've deployed in front of it. > > > -- > | Jeremy Chadwick =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 jdc@parodius.com | > | Parodius Networking =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://= www.parodius.com/ | > | UNIX Systems Administrator =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Mountain = View, CA, USA | > | Making life hard for others since 1977. =A0 =A0 =A0 =A0 =A0 =A0 =A0PGP:= 4BD6C0CB | > > That looks reasonable last says: reboot ~ th 16 sen 14:04 reboot ~ th 16 sen 14:03 shutdown ~ th 16 sen 13:59 and it's pretty good syncs with logs but there's no anybody access to physical console 'cos it's not even plugged in. That's for the first. Next, I've got, I believe, pretty strong passwords, and also root can't log in directly, but wheel user also is in operators so he also can reboot or shutdown, but there's no any attempts or successful logins. All potentialy dangerous services run under their own unprerileged users, and so on. Crontabs also doesn't contain scripts, I prefer periodic system, and there's no anyway anything that cause reboot. Thing that worries me it that there were multiple reboots and shutdown that goes up by itself without anyone pressing a button. And in messages log there's fsck segment that indicates to unnormal shutdown or reboot. It looks like it started to shutting down but was in some case interrupted and after powering up it few times reboots itself. But commonly FreeBSD doesn't reboot by it's own will. The same hardware worked over a half a year under 8.0 stables without such a problem. I just would like to understand from where this problem comes up. This machine doesn't contain any critical info so I'll wait for a bit. Also I'd like to notice that recently I've tuned hdd's spindown exept system hdd by atacontrol port, powerd and CPU frequency lowering in idle, maybe something of this could cause this problem? And where could I check this out?