From owner-freebsd-questions@FreeBSD.ORG Tue Nov 25 18:17:23 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F13081065672 for ; Tue, 25 Nov 2008 18:17:23 +0000 (UTC) (envelope-from bsd@todoo.biz) Received: from newmail.rmm.fr (newmail.rmm.fr [87.98.206.99]) by mx1.freebsd.org (Postfix) with ESMTP id 8FF768FC27 for ; Tue, 25 Nov 2008 18:17:23 +0000 (UTC) (envelope-from bsd@todoo.biz) Received: from localhost (localhost [127.0.0.1]) by newmail.rmm.fr (Postfix) with ESMTP id F2DB928D13 for ; Tue, 25 Nov 2008 19:17:22 +0100 (CET) X-Virus-Scanned: amavisd-new 2.6.1 (20080629) at rmm.fr Received: from newmail.rmm.fr ([127.0.0.1]) by localhost (newmail.rmm.fr [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 7QWGN3VFbnKI for ; Tue, 25 Nov 2008 19:17:22 +0100 (CET) Received: from [192.168.0.201] (me.todoo.biz [82.66.93.242]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: grego03) by newmail.rmm.fr (Postfix) with ESMTPSA id 8ABC428D12 for ; Tue, 25 Nov 2008 19:17:22 +0100 (CET) Message-Id: From: bsd To: Liste FreeBSD In-Reply-To: <6ECF7CD4-BE6A-4F37-8083-9403621F4C85@todoo.biz> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v929.2) Date: Tue, 25 Nov 2008 19:17:22 +0100 References: <6ECF7CD4-BE6A-4F37-8083-9403621F4C85@todoo.biz> X-Mailer: Apple Mail (2.929.2) Subject: Re: 7.0-RELEASE-p6 problem amd64 daemonology X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2008 18:17:24 -0000 Hello, I think you all deserve a clear information about what has been going =20= on today. After the update of all servers to P-6 - the server could not be =20 booted normaly - in fact they did boot but after that they didn't get =20= back with the prompt=85 So I ended up in a "dead end". As I was working last weeks with the engineers that helped me setup =20 the hardware (and as Intel didn't have a right guideline specifying =20 that TCP ports needed to be opened) - I have ended up mofidying a =20 little parameter in /boot/loader.conf that was aimed to redirect the =20 console to "vidconsole" & "comconsole". This little parameter seems to have caused a conflict with the KVM of =20= intel which probably uses the same redirect or blocked us from =20 receiving the output (even from ssh). It took me quite a long time to figure out what was going on as I =20 suspected other problems to have happened. This has all the symptoms =20 of a system freeze, but services were launched (at least some of them)=85 I have found the solution by booting using a low level prompt that has =20= allowed me to pass the parameter "set console=3Dcomconsole" and all went = =20 back to normal. Quite firghtening, but finaly armless. Le 25 nov. 08 =E0 16:27, bsd a =E9crit : > Hello I have updated my server (Intel Modular server) using the =20 > classical > > # freebsd-update install > > > And I am now facing very weired issues only on amd64 servers I am =20 > maintaining. > Servers boots and then freezes when It launch "ipfilter". This is =20 > not a low level freeze, simply all access to the server are disabled. > > - Single user boot does not work. > - SSH access does not work either. > > > These servers were working perfectly before this update=85 > > --- > > What would you suggest to get out of this situation=85 > > 1. Rollback to the 7.0-RELEASE-p5 which was stable and worked well. > --> If so how can I access the server knowing that single user mode =20= > does not work? > --> Can you describe me the stages I would have to go through - I am =20= > not very used to this kind of situations. > > 2. Deactivate ipfilter (is there a way to do that at boot time =20 > without editing /etc/rc.conf ) ? > > 3. Deactivate all services at boot time (is there a way of bypassing =20= > at boot time the rc.conf file) ? > > > Thanks for your support. > > > =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF > Gregober ---> PGP ID --> 0x1BA3C2FD > bsd @at@ todoo.biz > =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF > > P "Please consider your environmental responsibility before printing =20= > this e-mail" > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org=20 > " =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF Gregober ---> PGP ID --> 0x1BA3C2FD bsd @at@ todoo.biz =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF P "Please consider your environmental responsibility before printing =20 this e-mail"