10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We observe below logs from switch - the database servers rebooted becaause they couldn't do I/O on vfiler -Any pointers looking at below logs please?
2016 Apr 30 07:41:16.729 EAG-ECOM-POD111GPU-SWF1 %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet152/1/8 is down (Link... (0 Replies)
Discussion started by: admin_db
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/
RSP: 0018:ffffffff80457f40 EFLAGS: 00000046
RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001
RDX:... (6 Replies)
Discussion started by: badoshi
3. Red Hat
when system is hung state due to swap, we will reboot it through ILO.
i want to know which process caused system hung. (1 Reply)
Discussion started by: Naveen.6025
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
5. Shell Programming and Scripting
Now i want write a shell to get the state of weblogic server,and when the Managed Server's state is not ok, after 3 times checking, i will send msg to the system administrator by sms.
BTW, my environment is :
Linux ,Redhat 5.4 64bit
weblogic version: 10.3.3
the count number... (1 Reply)
Discussion started by: wangsk
Good Day all
i have a solaris 8 server and i want the procedure for how to install HPOV
becuse dont have any small info about solaris . (1 Reply)
Discussion started by: thecobra151
Can any one of you suggest me the method to get apache server in online from maintenance mode. I tried in the following way, but couldn't get that service to online.
bash-3.00# svcs -a | grep apache
legacy_run 9:51:55 lrc:/etc/rc3_d/S50apache
offline 9:51:22... (3 Replies)
Discussion started by: Sesha
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
9. UNIX for Advanced & Expert Users
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
So my server was hung when I came in this morning. It was responding to pings, but the console and telnet sessions would not respond. There was no disk activity. The display said FA1F which I discovered that the "A" represents a high CPU load. I tired several things to get it going but was forced... (6 Replies)
Discussion started by: biznatch
lockd - network lock daemon
/usr/etc/lockd [ -t timeout ] [ -g graceperiod ]
The daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking service
makes this advisory locking support possible by using the system call and the subroutine. The daemon forwards lock requests for remote
data to the server site's lock daemon. The daemon then requests the status monitor daemon, for monitor service. The reply to the lock
request is not sent to the kernel until the status daemon and the server site's lock daemon have replied.
If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.
When a server recovers, it waits for a grace period for all client site daemons to submit reclaim requests. Client site daemons are noti-
fied by of the server recovery and promptly resubmit previously granted lock requests. If a client site's daemon fails to secure previ-
ously granted locks at the server site, the daemon sends the signal SIGLOST to all the processes that were previously holding locks and
cannot reclaim them.
-t timeout The daemon uses timeout (in seconds) as the interval instead of the default value of 15 seconds to retransmit a lock
request to the remote server.
-g graceperiod The daemon uses graceperiod (in seconds) as the grace period duration instead of the default value of 45 seconds.
fcntl(2), lockf(3), signal(3), statd(8c)