01-20-2006
Turns out the server has a bad processor. Maybe this information will help someone one day.
*** UPDATE ***
It also had a bad root disk.
Last edited by biznatch; 01-22-2006 at 12:42 PM..
10 More Discussions You Might Find Interesting
1. IP Networking
I installed sco unix v 5.0.5 in the hp server lc 2000 HD size
27gb & ram 256 , used micro focus cobol for unix , aplication
system bank , the problem is the system hung 2 or 3 times a day
will you pls. give me the solution.
thanks
talib alsaadi
:( (2 Replies)
Discussion started by: talib alsaadi
2 Replies
2. HP-UX
Here's a difficult one for you.
I am on HPUX 11.0. I have a hung port, it is stuck in FIN_WAIT_2. Short of rebooting, how can I terminate the connection the system thinks still exists? I found a script online that uses adb but have not been able to get it to work. I am still open to using... (6 Replies)
Discussion started by: TioTony
6 Replies
3. UNIX for Advanced & Expert Users
Hi Guys,
Just wondering if anyone of you have been in a situation where you end up having around 100 close_wait connections and seems to me those connections are locking up resources/processes in the server so unless the server is rebooted those processes won't be released by the close_wait... (3 Replies)
Discussion started by: hariza
3 Replies
4. Shell Programming and Scripting
A coworker has a shell script that runs from a scheduler at the 3am. The shell script runs sqlplus passing in a sql statement, which generate a file. This is done 21 times for 21 different sql statements. Recently, one of the sqlplus processes got hung.
Is there a way to monitor how long the... (2 Replies)
Discussion started by: prismtx
2 Replies
5. Programming
Hi friends
I am Administrator for a system works with uinx OS but, many times I get messages from server console inform me about Subroutine is Hanging
so what can I do to reset this Subroutine?
Note: always when I got that I restart the server but I think that is not professional solution. (3 Replies)
Discussion started by: bintaleb
3 Replies
6. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
7. SuSE
Hi all
We've had an issue over the weekend when one of the SUSE Linux Enterprise Server 11 hung and had to be rebooted. The thing is that I got the ticket alert for a FS exceeding its usage at about 22:41:49 PM on 23 March. I checked the dmesg, the messages log and the boot.msg but all I found... (1 Reply)
Discussion started by: hedkandi
1 Replies
8. Linux
Hi everyone,
Our Red Hat server hung yesterday, and I managed to log into the console and see the following message:
RIP: 0010: mwait_idle_with_hints+0x66/
0x67
RSP: 0018:ffffffff80457f40 EFLAGS: 00000046
RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001
RDX:... (6 Replies)
Discussion started by: badoshi
6 Replies
9. Shell Programming and Scripting
I wish to monitor if my Tomcat process if Running, Hung, or Shutdown.
I cannot use any third party monitoring tools so i decided to use one of these to test if the tomcat server is responding or not .
1. nslookup
2. telnet
3. ps
The reason I do not use wget / curl is because it will... (2 Replies)
Discussion started by: mohtashims
2 Replies
10. Infrastructure Monitoring
Hi,
We have Solaris-10 running on VMware (x86). It is being monitored by HP Openview. Sometimes when this server hungs, while ping still works, HPOpenview can't alert that server is down (which is actually unresponsive).
First symptom we see is, login failure. It will ask user name and after... (7 Replies)
Discussion started by: solaris_1977
7 Replies
BADSECT(8) System Manager's Manual BADSECT(8)
NAME
badsect - create files to contain bad sectors
SYNOPSIS
/sbin/badsect sector ...
DESCRIPTION
Badsect makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a for-
warding table for bad sectors to the driver; see bad144(8) for details. If a driver supports the bad blocking standard it is much prefer-
able to use that method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be
copied with dd(1). The technique used by this program is also less general than bad block forwarding, as badsect can't make amends for bad
blocks in the i-list of file systems or in swap areas.
Adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter, as UNIX does
not supply formatters. Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect
may be used to good effect.
Badsect is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make a direc-
tory BAD there and change into it. Run badsect giving as argument all the bad sectors you wish to add. (The sector numbers should be
given as physical disk sectors relative to the beginning of the file system, exactly as the system reports the sector numbers in its con-
sole error messages.) Then change back to the root directory, unmount the file system and run fsck(8) on the file system. The bad sectors
should show up in two files or in the bad sector files and the free list. Have fsck remove files containing the offending bad sectors, but
do not have it remove the BAD/nnnnn files. This will leave the bad sectors in only the BAD files.
Badsect works by giving the specified sector numbers in a mknod(2) system call (after taking into account the filesystem's block size),
creating a regular file whose first block address is the block containing bad sector and whose name is the bad sector number. The file has
0 length, but the check programs will still consider it to contain the block containing the sector. This has the pleasant effect that the
sector is completely inaccessible to the containing file system since it is not available by accessing the file.
SEE ALSO
mknod(2), bad144(8), fsck(8)
BUGS
If both sectors which comprise a (1024 byte) disk block are bad, you should specify only one of them to badsect, as the blocks in the bad
sector files actually cover both (bad) disk sectors.
On the PDP-11, only sector number less than 131072 may be specified on 1024-byte block filesystems, 65536 on 512-byte block filesystems.
This is because only a short int is passed to the system from mknod.
3rd Berkeley Distribution BADSECT(8)