I have been seeing a
git status -s showing up in
top every 30 seconds and can't figure out what's calling this command. It's showing 20%–60% CPU (on a busy 24gb production Linode running Debian 8.1) so I'd like to eliminate this from happening.
Any thoughts on how to track down the source of this? I have no cronjobs that call git, nor any that run that often.
8332 myusername 20 0 177936 5564 4940 R 17.9 0.0 0:00.54 git status -s ... 30sec later 8395 myusername 20 0 177936 5616 4992 R 21.6 0.0 0:00.65 git status -s ... 30sec later 8444 myusername 20 0 177936 5508 4880 R 23.2 0.0 0:00.70 git status -s ... etc
I'm guessing there's a way to watch for a command to be run and capture information on it to track the source. The PID changes on each call, so it's not a long-running process, and it's only there for a second or two, making it difficult to dig deeper.
Any help much is appreciated!
UPDATE: Turns out it's somehow pm2 related, see: https://github.com/Unitech/PM2/issues/924
I have a simple node app that connects to redis and socket.io and broadcasts live notifications to users.
My app is not showing any restarts in
pm2 monit and I've updated all node modules and pm2 to the latest version, and I'm still seeing that
git status -s showing up in top every 30 seconds.