Hello,
we have a very high CPU usage from the process Garner, i don't find any information about it, do you know which service is behind it?
Thank you!
This thread was automatically locked due to age.
Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.
Hello,
we have a very high CPU usage from the process Garner, i don't find any information about it, do you know which service is behind it?
Thank you!
Hi Julian Cast : Can you please press 1 ( after PSMON) to get CPU core wise details and confirm output? Please share snapshot for reference again with pressing 1.
Regards,
Vishal Ranpariya
Technical Account Manager | Sophos Technical Support
Sophos Support Videos | Knowledge Base | @SophosSupport | Sign up for SMS Alerts |
If a post solves your question use the 'Verify Answer' link.
Hi Julian Cast : Thanks for sharing the snapshot. Is Device having any syslog configuration ? If yes is it reachable from XG? Can you check garner.log file to see there is any suspected logs there ?
XG Log file guide:
https://support.sophos.com/support/s/article/KB-000038142?language=en_US
Regards,
Vishal Ranpariya
Technical Account Manager | Sophos Technical Support
Sophos Support Videos | Knowledge Base | @SophosSupport | Sign up for SMS Alerts |
If a post solves your question use the 'Verify Answer' link.
Garner is basically the reporting daemon. So it looks like, you have a high volume of reports or a broken database.
Can you check, if your reports (Logviewer / Reporting) on box works?
If there are no reports anymore, check the log size: https://support.sophos.com/support/s/article/KB-000035777?language=en_US
Try to restart the daemon.
__________________________________________________________________________________________________________________
we should know what service needs to be restarted for garner process.
Julian Cast in our case there is a lot of RED logging in the garner.log file. Maybe one device is going banana?
And tail -f the syslog.log file if there is excessive logging happening.
Yes it's work, we will check the log exported and verify if it's not over charged