Hello, I have been encountering this exact issue since version 1.6.0.
Rather than restarting the entire service, I terminate only the threads that are consuming excessive CPU resources. This way, I can avoid interrupting service for my users.
I would be happy to provide any necessary details to help move the troubleshooting process forward :)
Antoine Le 01/12/2025 à 15:29, radmal a écrit :
Hi,We have issues with the *guacd* process. After a certain period of time, the guacd process starts consuming 100% CPU, and multiple processes keep stacking up until we restart the service. After the restart everything if fine again, but the same problem repeats. In practice, we have to restart it at least once a month.Is there anything we can extract from the existing processes (as shown in the screenshot below) before we kill/restart them or from the logs that could help you analyze why this is happening?Thank you. image.png best regards, Radenko
--
Antoine Roux - Qualitative WYSIWYG Maker (QWM)
ooo ooo
d888b d888b
ooo 88W88 88I88 ooo
d888b Y88P Y88P d888b
88S88 '` `' 88X88
Y8P' .od888bo. 'Y8P
.od888888888bo.
d888888888888888b
88888888888888888
Y8888888888888P
`Y888P"Y888P'
OpenPGP_0x85A3680AA48F12F5.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
