how do we stop nobody httpd

979485 nobody 20 0 83276 10m 1992 S 0.3 0.1 0:00.12 httpd 979488 nobody 20 0 83352 10m 2004 S 0.3 0.1 0:00.07 httpd 979510 nobody 20 0 83400 10m 2004 S 0.3 0.1 0:00.12 httpd 979511 nobody 20 0 83408 10m 1980 S 0.3 0.1 0:00.11 httpd 979549 nobody 20 0 83552 10m 2000 S 0.3 0.1 0:00.11 httpd 979550 nobody 20 0 83316 10m 1988 S 0.3 0.1 0:00.09 httpd 979554 nobody 20 0 83108 9976 1876 S 0.3 0.1 0:00.12 httpd 979584 nobody 20 0 83344 10m 1984 S 0.3 0.1 0:00.08 httpd 979603 nobody 20 0 83400 10m 2000 S 0.3 0.1 0:00.10 httpd 979616 nobody 20 0 83416 10m 2000 S 0.3 0.1 0:00.12 httpd 979655 nobody 20 0 83400 9m 1928 S 0.3 0.1 0:00.10 httpd 979726 nobody 20 0 83352 10m 1988 S 0.3 0.1 0:00.07 httpd 979774 nobody 20 0 83352 10m 1984 S 0.3 0.1 0:00.11 httpd 979808 nobody 20 0 83364 10m 2004 S 0.3 0.1 0:00.09 httpd 979828 nobody 20 0 83412 10m 1996 S 0.3 0.1 0:00.10 httpd 979880 nobody 20 0 83400 10m 2000 S 0.3 0.1 0:00.10 httpd

Sreejit

January 22, 2014 11:31

Those are core apache process and it will run under nobody only. The php sub-process will run under their respective user if your php handler is suphp or fcgi

cPanelMichael

January 22, 2014 12:33

Hello :) It's normal to see "httpd" processes running under the "nobody" username. Are you experiencing an issue with your server load or responsiveness? Thank you.

mojamoi

January 22, 2014 14:52

it showed apache socket timeout error in nagios [COLOR="silver">- - - Updated - - - also showed this, but datacaenter said there were no ddos attacks on the server # netstat -n -p|grep SYN_REC | wc -l 109 websites on the server were very slow

January 22, 2014 15:13

The following thread may be of help to you: Troubleshooting High Loads On Linux Servers It's primary purpose is for troubleshooting high loads, but some of the referenced log files and commands could help you troubleshoot the issue. Thank you.

how do we stop nobody httpd

Comments

Didn't find what you were looking for?