DaemonForums  

Go Back   DaemonForums > FreeBSD > FreeBSD General

FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 28th May 2010
carpman carpman is offline
Shell Scout
 
Join Date: Jul 2008
Posts: 94
Thanked 0 Times in 0 Posts
Default regular server crashes - /proc/ Bad file descriptor

Hello, i have been having issues with my server, it keeps going down every week to two weeks, it becomes unacceptable though sometimes it will respond to a ping but no other service available and hard reboot required by datacenter.

Fist thing i did was visit and do file system check, the raid controller also reports drives ok but while doing a grep of system today looking for something that may give a clue as to why i get output of this.


Code:
grep: /proc/849/mem: Bad address
grep: /proc/849/map: Input/output error
grep: /proc/849/etype: Input/output error
grep: /proc/849/ctl: Bad file descriptor
grep: /proc/849/cmdline: Input/output error
grep: /proc/845/status: Input/output error
grep: /proc/845/rlimit: Input/output error
grep: /proc/845/notepg: Bad file descriptor
grep: /proc/845/note: Bad file descriptor
grep: /proc/845/mem: Bad address
grep: /proc/845/map: Input/output error
grep: /proc/845/etype: Input/output error
grep: /proc/845/ctl: Bad file descriptor
grep: /proc/845/cmdline: Input/output error
grep: /proc/844/status: Input/output error
grep: /proc/844/rlimit: Input/output error
grep: /proc/844/notepg: Bad file descriptor
grep: /proc/844/note: Bad file descriptor
grep: /proc/844/mem: Bad address
grep: /proc/844/map: Input/output error
grep: /proc/844/etype: Input/output error
grep: /proc/844/ctl: Bad file descriptor
grep: /proc/844/cmdline: Input/output error
grep: /proc/787/status: Input/output error
grep: /proc/787/rlimit: Input/output error
grep: /proc/787/notepg: Bad file descriptor
grep: /proc/787/note: Bad file descriptor
grep: /proc/787/mem: Bad address
grep: /proc/787/map: Input/output error
grep: /proc/787/etype: Input/output error
grep: /proc/787/ctl: Bad file descriptor
grep: /proc/787/cmdline: Input/output error
grep: /proc/647/status: Input/output error
grep: /proc/647/rlimit: Input/output error
grep: /proc/647/notepg: Bad file descriptor
grep: /proc/647/note: Bad file descriptor
grep: /proc/647/mem: Bad address
grep: /proc/647/map: Input/output error
grep: /proc/647/etype: Input/output error
grep: /proc/647/ctl: Bad file descriptor
grep: /proc/647/cmdline: Input/output error
grep: /proc/586/status: Input/output error
grep: /proc/586/rlimit: Input/output error
grep: /proc/586/notepg: Bad file descriptor
grep: /proc/586/note: Bad file descriptor
grep: /proc/586/mem: Bad address
grep: /proc/586/map: Input/output error
grep: /proc/586/etype: Input/output error
grep: /proc/586/ctl: Bad file descriptor
grep: /proc/586/cmdline: Input/output error
grep: /proc/432/status: Input/output error
grep: /proc/432/rlimit: Input/output error
grep: /proc/432/notepg: Bad file descriptor
grep: /proc/432/note: Bad file descriptor
grep: /proc/432/mem: Bad address
grep: /proc/432/map: Input/output error
grep: /proc/432/etype: Input/output error
grep: /proc/432/ctl: Bad file descriptor
grep: /proc/432/cmdline: Input/output error
grep: /proc/428/status: Input/output error
grep: /proc/428/rlimit: Input/output error
grep: /proc/428/notepg: Bad file descriptor
grep: /proc/428/note: Bad file descriptor
grep: /proc/428/mem: Bad address
grep: /proc/428/map: Input/output error
grep: /proc/428/etype: Input/output error
grep: /proc/428/ctl: Bad file descriptor
grep: /proc/428/cmdline: Input/output error
grep: /proc/42/status: Input/output error
grep: /proc/42/rlimit: Input/output error
grep: /proc/42/etype: Input/output error
grep: /proc/42/ctl: Bad file descriptor
grep: /proc/42/cmdline: Input/output error
grep: /proc/41/status: Input/output error
grep: /proc/41/rlimit: Input/output error
grep: /proc/41/etype: Input/output error
grep: /proc/41/ctl: Bad file descriptor
grep: /proc/41/cmdline: Input/output error
grep: /proc/40/status: Input/output error
grep: /proc/40/rlimit: Input/output error
grep: /proc/40/etype: Input/output error
grep: /proc/40/ctl: Bad file descriptor
grep: /proc/40/cmdline: Input/output error
grep: /proc/39/status: Input/output error
grep: /proc/39/rlimit: Input/output error
grep: /proc/39/etype: Input/output error
grep: /proc/39/ctl: Bad file descriptor
grep: /proc/39/cmdline: Input/output error
grep: /proc/38/status: Input/output error
grep: /proc/38/rlimit: Input/output error
grep: /proc/38/etype: Input/output error
grep: /proc/38/ctl: Bad file descriptor
grep: /proc/38/cmdline: Input/output error
grep: /proc/37/status: Input/output error
grep: /proc/37/rlimit: Input/output error
grep: /proc/37/etype: Input/output error
grep: /proc/37/ctl: Bad file descriptor
grep: /proc/37/cmdline: Input/output error
grep: /proc/36/status: Input/output error
grep: /proc/36/rlimit: Input/output error
grep: /proc/36/etype: Input/output error
grep: /proc/36/ctl: Bad file descriptor
grep: /proc/36/cmdline: Input/output error
grep: /proc/35/status: Input/output error
grep: /proc/35/rlimit: Input/output error
grep: /proc/35/etype: Input/output error
grep: /proc/35/ctl: Bad file descriptor
grep: /proc/35/cmdline: Input/output error
grep: /proc/34/status: Input/output error
grep: /proc/34/rlimit: Input/output error
grep: /proc/34/etype: Input/output error
grep: /proc/34/ctl: Bad file descriptor
grep: /proc/34/cmdline: Input/output error
grep: /proc/33/status: Input/output error
grep: /proc/33/rlimit: Input/output error
grep: /proc/33/etype: Input/output error
grep: /proc/33/ctl: Bad file descriptor
grep: /proc/33/cmdline: Input/output error
grep: /proc/32/status: Input/output error
grep: /proc/32/rlimit: Input/output error
grep: /proc/32/etype: Input/output error
grep: /proc/32/ctl: Bad file descriptor
grep: /proc/32/cmdline: Input/output error
grep: /proc/31/status: Input/output error
grep: /proc/31/rlimit: Input/output error
grep: /proc/31/etype: Input/output error
grep: /proc/31/ctl: Bad file descriptor
grep: /proc/31/cmdline: Input/output error
grep: /proc/30/status: Input/output error
grep: /proc/30/rlimit: Input/output error
grep: /proc/30/etype: Input/output error
grep: /proc/30/ctl: Bad file descriptor
grep: /proc/30/cmdline: Input/output error
grep: /proc/29/status: Input/output error
grep: /proc/29/rlimit: Input/output error
grep: /proc/29/etype: Input/output error
grep: /proc/29/ctl: Bad file descriptor
grep: /proc/29/cmdline: Input/output error
grep: /proc/28/status: Input/output error
grep: /proc/28/rlimit: Input/output error
grep: /proc/28/etype: Input/output error
grep: /proc/28/ctl: Bad file descriptor
grep: /proc/27/ctl: Bad file descriptor
grep: /proc/26/ctl: Bad file descriptor
grep: /proc/25/ctl: Bad file descriptor
grep: /proc/24/ctl: Bad file descriptor
grep: /proc/23/ctl: Bad file descriptor
grep: /proc/22/ctl: Bad file descriptor
grep: /proc/21/ctl: Bad file descriptor
grep: /proc/20/ctl: Bad file descriptor
grep: /proc/19/ctl: Bad file descriptor
grep: /proc/9/ctl: Bad file descriptor
grep: /proc/8/ctl: Bad file descriptor
grep: /proc/7/ctl: Bad file descriptor
grep: /proc/18/ctl: Bad file descriptor
grep: /proc/6/ctl: Bad file descriptor
grep: /proc/17/ctl: Bad file descriptor
grep: /proc/5/ctl: Bad file descriptor
grep: /proc/16/ctl: Bad file descriptor
grep: /proc/4/ctl: Bad file descriptor
grep: /proc/3/ctl: Bad file descriptor
grep: /proc/2/ctl: Bad file descriptor
grep: /proc/15/ctl: Bad file descriptor
grep: /proc/14/ctl: Bad file descriptor
grep: /proc/13/ctl: Bad file descriptor
grep: /proc/12/ctl: Bad file descriptor
grep: /proc/11/ctl: Bad file descriptor
grep: /proc/1/ctl: Bad file descriptor
grep: /proc/10/ctl: Bad file descriptor
grep: /proc/0/ctl: Bad file descriptor

As this on proc it looks to me like some bad memory?

anyone confirm this?


Memtest86 does not work on this dell server as reports bad memory all the time, have used the dell mem test on this memory when install and was ok but will try again to make sure it has not gone bad.

I would try memtester on live system but does appear to be in ports?

cheers
Reply With Quote
  #2   (View Single Post)  
Old 30th May 2010
Android1's Avatar
Android1 Android1 is offline
Fdisk Soldier
 
Join Date: Mar 2009
Posts: 60
Thanked 1 Time in 1 Post
Default

Memtest86 and its cousin, memtest86+, are known to be pretty reliable. If one of them says your memory is bad, it probably is.

Another good way to find bad memory is mprime's "Blend" torture test. Mprime can be found in the FreeBSD ports tree in the math section.
Reply With Quote
  #3   (View Single Post)  
Old 1st June 2010
carpman carpman is offline
Shell Scout
 
Join Date: Jul 2008
Posts: 94
Thanked 0 Times in 0 Posts
Default

Thanks i will try Mprime.

Fact is memtest86 or memtest86+ do not work on some dell servers.

http://en.community.dell.com/support.../14097094.aspx
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Microsoft warns of IE flaw, turns PC into public file server J65nko News 0 4th February 2010 11:21 PM
cant see screensaver or proceses in proc manager whispersGhost FreeBSD Installation and Upgrading 2 22nd January 2009 08:30 PM
Advice needed: File server for VPN - samba, NFS? sim FreeBSD General 11 4th November 2008 10:48 PM
What's the deal with /proc? JMJ_coder NetBSD General 17 11th July 2008 10:12 PM
Remote Access to File Server Oko OpenBSD Security 7 23rd June 2008 05:17 PM


All times are GMT. The time now is 07:24 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick