Re: Error 400007: `stats_z1/0' is not running after update

Home Messages Hashtags Subgroups

iamflying #1917 It does not help. I always see the "collector" process bouncing between "running" and "does not exit" when I use "monit summary" in a while loop. Who knows how to get the real error when the "collector" process is not failed? Thanks. toggle quoted message Show quoted text On Wed, Sep 23, 2015 at 4:11 PM, Tony <Tonyl(a)fast.au.fujitsu.com> wrote: My approach is to login on the stats vm and sudo, then run "monit status" and restart the failed processes or simply restart all processes by running "monit restart all" wait for a while(5~10 minutes at most) If there is still some failed process, e.g. collector then run ps -ef \| grep collector and kill the processes in the list(may be you need to run kill -9 sometimes) then "monit restart all" Normally, it will fix the issue "Failed: `XXX' is not running after update" -- View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Error-400007-stats-z1-0-is-not-running-after-update-tp1901p1902.html Sent from the CF Dev mailing list archive at Nabble.com. attachment.html attachment.html
More All Messages By This Member

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.