Re: [p4] p4 monitor terminate never seems to work

Posted on behalf of forum user 'Matt Janulewicz'.



[https://forums.perforce.com/index.php?app=forums&module=forums&section=findpost&pid=22500]
Mailman Sync, on 2017/10/16 20:30:03 UTC, said:
>     Originally posted to the perforce-user mailing list by: Michael Mirman
>   
>   
>   
>   
>   I can't explain this with Ctl-C. Presumably, the p4d process *should* go away (at least eventually) if the client does Ctl-C.
>   The p4d log often says "Partner exited unexpectedly", and at least in some cases it could be traced back to Ctrl-C.
>   
>   However, there are often cases when p4d leaks processes. Sometimes they are shown in "p4 monitor", sometimes they aren't.
>   In our case, there is almost always an edge server and a broker in the chain, and that possibly plays an important role in leaking.
>   
>   We have a script, which runs as a cron job, looking for leaked and/or hung processes, and either kills them or it can report them for an investigation.
>   Our latest bane is leaking "login" processes ("p4 login -s", "p4 login", "p4 login -a").
>   Users never complain - this is purely the problem on the server side. We get about a dozen of those processes on a good day, and several dozen processes on a bad day.
>   
>     

Yeah, edge servers. We have them.

We do the 'optimized db swap-into-production' mambo once a week, which
requires each service to be restarted, so that clears up the rogues quite
nicely. I realize that's the 'Did you try turning it off and back
on?' solution but it works well for us.



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/3581-p4-monitor-terminate-never-seems-to-work
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user