Hi folks. First off, I want to send a HUGE THANK YOU for this incredible software. I cannot tell you the number of clients I have knocked the socks off of implementing an instance for their sites and various needs.
I do have a question - not necessarily a "bug", but some behavior I am not understanding.
I run the ConsolLabs implementation of OMD and thruk.
https://omd.consol.de/docs/omd/
I have noticed at least in the most recent version (omd-5.70-labs-edition) which includes thruk 3.28, I have an instance running and it spawns a number of chromium processes, on behalf of puppeteer. Totally cool.
Where I'm a bit confused however, is whenever I fully stop the omd/thruk processes, the chromium processes continue to run and seem to be lingering around for days and leaving loads of files in /tmp and never seems to do any cleanup/housekeeping of these old dirs. Is there perhaps a configuration element I am overlooking to ensure that all these processes actually ever stop when the instance gets halted? I haven't (yet) seen any reference to this in the puppeteer docs and will keep reading but figured I would ask in case anyone else had noticed this behavior.
Thank you in advance.
-Chris
Hi folks. First off, I want to send a HUGE THANK YOU for this incredible software. I cannot tell you the number of clients I have knocked the socks off of implementing an instance for their sites and various needs.
I do have a question - not necessarily a "bug", but some behavior I am not understanding.
I run the ConsolLabs implementation of OMD and thruk.
https://omd.consol.de/docs/omd/
I have noticed at least in the most recent version (omd-5.70-labs-edition) which includes thruk 3.28, I have an instance running and it spawns a number of chromium processes, on behalf of puppeteer. Totally cool.
Where I'm a bit confused however, is whenever I fully stop the omd/thruk processes, the chromium processes continue to run and seem to be lingering around for days and leaving loads of files in /tmp and never seems to do any cleanup/housekeeping of these old dirs. Is there perhaps a configuration element I am overlooking to ensure that all these processes actually ever stop when the instance gets halted? I haven't (yet) seen any reference to this in the puppeteer docs and will keep reading but figured I would ask in case anyone else had noticed this behavior.
Thank you in advance.
-Chris