Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Voleg, do you know how to tell what the current setting is without rebooting the server? dmidecode -t bios only tells me the functionality of the BIOS, not any particular setting.
Found it in iLO; set to HP Static Performance. It looks like I can set it to OS Controlled without a reboot, but not sure if the changes will actually take effect. We'll see.
One of our data centers has a Red Hat server, 2.6.32, with a strange and seemingly erratic hanging behavior. Every once in a while, up to 20 times a day, the server will hang while running even common commands such a "who" or "date." Nothing unusual logs to messages. No unusually high resource activity. I have a script that captures the period of time between running instances of the "date" command, with a sleep time of 15 seconds. 99% of the time there is a 15 second delay between the return of "date", but that 1% of the time where it can take 20-30 seconds is a real pain. I've watched top to see if excessive CPU activity is taking place, vmstat to watch for disk activity, free to check swap, ifconfig to look for retransmits, checked the switch for errors, but nothing is bearing fruit. What else should I be checking?
Thanks in advance.
I suspect there might be a hardware issue please check the log in the below given location if it is empty there is no problem with hardware if it shows some error regarding hardware you need look into those parts
Then you faced with something blocking.
This depends on your configuration. Examples may be hard NFS mounts with bad NFS connection,
encryption of something with exhausted enthropy in /dev/random, wrong limits.
Install sysstat and analyze sar reports.
Open service call to RedHat, send them sosreport, they will find the problem. At least you will get something for money you've payed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.