On 14/05/18 09:47, senor wrote: > Hi All, > > I had to change a monitor script to use squidclient ping instead of > 'squid -k check' because the check would succeed even if all workers had > died except for the coordinator and disker. Obviously, the real problem > is that the workers are dying but what I'm looking for ATM is a way to > restart individual workers. It seems a complete restart is necessary > once the coordinator gives up after a few attempts. I'd like to trigger > the coordinator to retry or something similar. Anything possible? As you said; the coordinator already did retry many times before it gave up. That is pretty clear evidence that coordinator retrying is not working. > > Bonus question: Where, if anywhere, is the cache manager use of "kid=N" > documented? I haven't gone to the source code yet and would like not to. Cache manager is a REST web API. So parameters like that are passed as query-string in the URLs. Support for parameters is report-specific and most of the reports are undocumented. It is mentioned in the SMP pages somewhere IIRC, but only as a mention that it exists. In regards to your problem. The cachemgr reports are executed by workers, not the coordinator. So that API in its current form is highly unlikely to help with restarting of a single worker. But if you find a report that pays attention to that parameter it might be useful to see if any workers are running. Ultimately watching the cache.log for worker death and restart messages will be your best source of info about the deaths. You should even find the reason the workers are dying in there. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
