|
Hi everybody!
I've got a RHEL 3.0 server, which is used mainly to open remote Xsessions (using kde), and execute the gui of an application. It has recently crashed several times, using the 100% of the cpu and not allowing remote (or local) connections. The only solution is to stop and start the machine using the power button. I'm not really sure about the cause of these crashes, though I think here may be a problem with de X Sessions. Here are some data I've recolected about 20 minutes before the crash:
- Number of opened kde sessions: 17 - Number of connected users (who | wc -l): 58 - Total number of processes in memory: 561 - Number of user processes: 472 - 7% idle cpu - 1Mb free RAM memory
The /var/adm/messages file shows several errors like this:
<server name> gdm[23933]: gdm_slave_xioerror_handler: Fatal X error - Restarting <ip:0>
It also has some nfs problems (<server name> kernel: nfs: server <server> not responding, timed out).
Can anybody tell me how to tune the machine so that it can handle the remote X Sessions more efficiently? How can I estimate the number of kde sessions that can be opened in the machine? How can I detect crashed kde sessions or bad logouts?
There may have been application errors prior to the crash, but I'm not sure.
Thank you very much.
Carlos Ortega González Iberia Sistemas DS/SP/Unidad Prod. Ordenadores email: iecisa cortegag iberia es Extensión: 4691
-- ---------------------------------------------- Has decidido el mejor precio. Has decidido IBERIA.com You´ve chosen the best price. You´ve chosen IBERIA.com ---------------------------------------------- http://www.iberia.com |