Skip to main content

How to trace short lived suspecious-processes

Comments

4 comments

  • cPanelLauren
    The nobody user is apache's default user, I'd suggest opening a ticket for this as it's actually pretty difficult to diagnose this without access to the server and that strace output you obtained is actually not very helpful.
    0
  • oah
    The nobody user is apache's default user, I'd suggest opening a ticket for this as it's actually pretty difficult to diagnose this without access to the server and that strace output you obtained is actually not very helpful.

    I solved it for the time being by removing the setting the permission to 750 on php-cgi binary and everything went to normal again. Let me see how can we arrange access for you guys. just one quick question though, I thought you need to strace the process while it is running so how do you plan on stracing if it is bursty? Thx again.
    0
  • cPanelLauren
    That makes it more difficult to strace but it is also possible to see the configuration on the server and understand what is causing the behavior in some cases.
    0
  • oah
    That makes it more difficult to strace but it is also possible to see the configuration on the server and understand what is causing the behavior in some cases.

    I get your point. Thank you guys for the support. For the time being feel free to mark the thread as solved :) It will be really great if you can think of some method to catch such bursty processes (if you find any feel free to post it here as a reply). I mean there gotta be a way to set up a filter/log and tell it whenever the user "nobody" calls the php-cgi binary just log it (long the whole command along with as much information as possible). Thx
    0

Please sign in to leave a comment.