From owner-freebsd-questions@FreeBSD.ORG Mon Dec 18 09:07:23 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15E9916A403 for ; Mon, 18 Dec 2006 09:07:23 +0000 (UTC) (envelope-from ml.diespammer@netfence.it) Received: from parrot.aev.net (parrot.aev.net [212.31.247.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD94F43CB5 for ; Mon, 18 Dec 2006 09:07:21 +0000 (GMT) (envelope-from ml.diespammer@netfence.it) Received: from soth.ventu (adsl-ull-245-224.51-151.net24.it [151.51.224.245]) (authenticated bits=128) by parrot.aev.net (8.13.8/8.13.8) with ESMTP id kBI9CucC053964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 18 Dec 2006 10:13:02 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Received: from [10.1.2.18] (alamar.ventu [10.1.2.18]) by soth.ventu (8.13.8/8.13.6) with ESMTP id kBI96lQX058105; Mon, 18 Dec 2006 10:06:47 +0100 (CET) (envelope-from ml.diespammer@netfence.it) Message-ID: <45865A26.2000503@netfence.it> Date: Mon, 18 Dec 2006 10:06:46 +0100 From: Andrea Venturoli User-Agent: Thunderbird 1.5.0.8 (X11/20061115) MIME-Version: 1.0 To: Garrett Cooper References: <45864EAA.8070908@netfence.it> <4586545B.2070907@u.washington.edu> In-Reply-To: <4586545B.2070907@u.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 212.31.247.179 Cc: freebsd-questions@freebsd.org Subject: Re: URGENT: 6.1/amd64 server hangs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 09:07:23 -0000 Garrett Cooper wrote: > Andrea, > Are you running X in some shape or form on the server No, no X server is running. I have X libraries installed and some clients linked against them (e.g. emacs), though, but I don't think this is what you mean. > and what's the last message you receive on the console? I don't have physical access on the console, but from what I'm told there is nothing after the usual "login:" at startup. As for the logs: .... Dec 17 08:29:52 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:56052 192.168.100.101:19999 in via fxp0 Dec 17 08:29:52 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:54673 192.168.100.101:443 in via fxp0 Dec 17 08:29:52 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:54673 192.168.100.101:443 in via fxp0 Dec 17 08:30:00 apocalypse /usr/sbin/cron[33906]: (root) CMD (/usr/local/netfence/bin/flush.sh) Dec 17 08:30:00 apocalypse /usr/sbin/cron[33907]: (root) CMD (/usr/libexec/atrun) Dec 17 08:30:00 apocalypse kernel: ipfw: Accounting cleared. Dec 17 08:30:02 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:57776 192.168.100.101:443 in via fxp0 Dec 17 08:30:02 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:57776 192.168.100.101:443 in via fxp0 Dec 17 08:30:02 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:50596 192.168.100.101:443 in via fxp0 Dec 17 08:30:02 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:50596 192.168.100.101:443 in via fxp0 Dec 17 08:30:17 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:59759 192.168.100.101:19999 in via fxp0 Dec 17 08:30:17 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:59759 192.168.100.101:19999 in via fxp0 Dec 17 08:30:17 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:54663 192.168.100.101:52948 in via fxp0 Dec 17 08:30:17 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:54663 192.168.100.101:52948 in via fxp0 Dec 17 08:30:22 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:49987 192.168.100.101:443 in via fxp0 Dec 17 08:30:22 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:49987 192.168.100.101:443 in via fxp0 Dec 17 08:30:22 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:54663 192.168.100.101:55000 in via fxp0 Dec 17 08:30:22 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:54663 192.168.100.101:55000 in via fxp0 Dec 17 08:30:27 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:52206 192.168.100.101:22 in via fxp0 Dec 17 08:30:27 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:52206 192.168.100.101:22 in via fxp0 Dec 17 08:30:27 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:58384 192.168.100.101:53 in via fxp0 Dec 17 08:30:27 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:58384 192.168.100.101:53 in via fxp0 Dec 17 08:30:32 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:57298 192.168.100.101:22 in via fxp0 Dec 17 08:30:32 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:57298 192.168.100.101:22 in via fxp0 Dec 17 08:30:37 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:49465 192.168.100.101:54663 in via fxp0 Dec 17 08:30:37 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:49465 192.168.100.101:54663 in via fxp0 Dec 17 08:30:37 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:53405 192.168.100.101:19999 in via fxp0 Dec 17 08:30:37 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:53405 192.168.100.101:19999 in via fxp0 Dec 17 08:30:42 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:58705 192.168.100.101:54663 in via fxp0 Dec 17 08:30:42 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:58705 192.168.100.101:54663 in via fxp0 Dec 17 08:30:47 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:59552 192.168.100.101:19999 in via fxp0 Dec 18 08:33:56 apocalypse syslogd: restart Dec 18 08:33:56 apocalypse syslogd: kernel boot file is /boot/kernel/kernel Dec 18 08:33:56 apocalypse kernel: 1:56533 192.168.100.101:443 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:56533 192.168.100.101:443 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:51628 192.168.100.101:53 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:51628 192.168.100.101:53 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:59273 192.168.100.101:53 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:59273 192.168.100.101:53 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:52115 192.168.100.101:443 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:52115 192.168.100.101:443 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:51886 192.168.100.101:22 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:51886 192.168.100.101:22 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:50086 192.168.100.101:19999 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:50086 192.168.100.101:19999 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:56446 192.168.100.101:53 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:56446 192.168.100.101:53 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:49748 192.168.100.101:53 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:49748 192.168.100.101:53 in via fxp0 Dec 18 08:33:56 apocalypse kernel: ipfw: 65534 Deny TCP 192.168.100.201:61136 192.168.100.101:19999 in via fxp0 ..... As can be seen the machine suddenly stops logging and starts over after someone physically resets it. bye & Thanks av.