From owner-freebsd-questions@FreeBSD.ORG Tue Nov 25 05:56:34 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 0A5DB16A4CF for ; Tue, 25 Nov 2003 05:56:34 -0800 (PST) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ED8343FF7 for ; Tue, 25 Nov 2003 05:56:31 -0800 (PST) (envelope-from fbsd_user@a1poweruser.com) Received: from barbish ([68.169.105.3]) by mta11.adelphia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20031125135634.UCJF1464.mta11.adelphia.net@barbish>; Tue, 25 Nov 2003 08:56:34 -0500 From: "fbsd_user" To: "Antonio Lupher" , Date: Tue, 25 Nov 2003 08:56:29 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: RE: "Device not configured" after every command, crashing X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: fbsd_user@a1poweruser.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2003 13:56:34 -0000 X-List-Received-Date: Tue, 25 Nov 2003 13:56:34 -0000 Sounds like hardware problems caused by overheating. Open the PC cover and blow out all the dust. Leave cover off and see if problem reoccurs. The PC's power supply may be going bad, replace. FBSD 4.4 is real old you should install 4.9 to separate HD with out any ports to see if problem is bad HD. -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Antonio Lupher Sent: Tuesday, November 25, 2003 12:34 AM To: freebsd-questions@freebsd.org Subject: "Device not configured" after every command, crashing I'm a newbie running FreeBSD (I believe it's 4.4... am at the moment unable to check, as the computer is down) to host some of my websites. I sent a query to this mailing list before about receiving some errors when trying to access my website, after which, ssh would stop logging me into the server ("Connection closed by [server ip]"), and all web pages would bring up a "Forbidden" error. After this, the server would go down completely... or at least I was unable to ping it, access it through http, or anything else that I tried... This has been happening regularly, about every 3-7 hours after the computer is rebooted. However, while the computer is running, I can distinguish nothing out of the ordinary. However, tonight, it "crashed" while i was logged in through ssh. Suddenly, almost every command that I issued or program I tried to run came back as "Device not configured." e.g.: # reboot /sbin/reboot : Device not configured Some things work... (lynx, ping, ps -- all seem to work fine) but many other commands just return the "Device not configured" or "Segmentation fault" errors. Also very odd: ls, cd, pwd, etc. seem to work fine, but when I ls any directory, no files come up. It is completely blank.... Anyway, I'm very scared and at my wit's end. The system will appear normal once it's rebooted, but the same thing will happen within a few hours... Any suggestions on what to look for? Are there certain log files that may contain information on this? I think the most recent thing I did to the server was several weeks ago, when I installed "wusage" to analyze web logs... i had since deleted it. Maybe something went wrong there? Hmmm.... Thanks! -antonio >I have also noticed two processes running that I hadn't seen before: > > 6 con Is+ 0:00.11 sh /etc/rc autoboot >447 con I+ 0:00.00 sh /etc/rc autoboot > Errors when trying to access a php/mysql driven website.... >>>Warning: open(/tmp/sess_4a23ba911863d07812e9cdf99656586f, O_RDWR) >>>failed: Device not configured (6) in >> >>>Warning: open(/tmp/sess_4a23ba911863d07812e9cdf99656586f, O_RDWR) >>>failed: Device not configured (6) in Unknown on line 0 >>> Warning: Failed to write session data (files). Please verify that the >>>current setting of session.save_path is correct (/tmp) in Unknown on line >>>0 >>>======================================================= >>> >>>I then try to login via ssh... but I get "Connection closed by [my ip]". >> >>It seems to me there is something wrong with your /tmp filesystem, causing >>both php and apache to be unable to write temp files, and also causes >>problems for several other daemons. _________________________________________________________________ Groove on the latest from the hot new rock groups! Get downloads, videos, and more here. http://special.msn.com/entertainment/wiredformusic.armx _______________________________________________ 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"