we have a Sophos XG 106 that now stops working twice.
No web interface, no proxy function. but system is up.
After power off power on the systems it starts working again.
The syslog shows as last entry:
Apr 10 10:00:04 (none) user.err kernel: [2769916.321151] 215:appfiltermap_adt_parser:policy 7 max app order 2 max eac apporder 0Apr 10 10:00:04 (none) user.err kernel: [2769916.321160] 711:appdev_write:count 2004Apr 10 10:00:04 (none) user.err kernel: [2769916.321165] 758:appdev_release:dev open 3Apr 10 10:00:04 (none) user.err kernel: [2769916.321167] 771:appdev_release:counter 7 size 128Apr 10 10:00:04 (none) user.err kernel: [2769916.321169] 774:appdev_release:dev open 0
Thanks for hints
Thanks for reaching out to the Community!
I would suggest you open a support case at support.sophos.com for further investigation.
Set up a console logging, capture the next event, and provide the console logs and csc logs in debugging on your support case.
Note: Though the article explicitly mentioned XG, it’s the same details for UTM
Note: Be sure that the computer in question does not go into Standby or Hibernate while logging
Run the following command to put the csc service in debug:
Community Support Engineer | Sophos Technical SupportSupport Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts If a post solves your question use the 'Verify Answer' button.
Hi, thanks for answer.
Is there also an option to do this via Putty using SSH? There is NO permanent PC at that destination available.
i have the xg106 too.
Can you tell me about the time to see the complete cotrol center pls?.
it takes at least 30 seconds for me to completely display the information on the overview page, is this normal?
Unfortunately, there’s no other way to save the console logging. If you can arrange the console logging, that will help us to identify the issue.
yes. 106 is very slow. We have multiple machines in place. all about 40-60 sec to fully display the control center.
210,330, virtuals are much faster.
106 are set and forget machines. They are extremely slow when making configuration changes.
that is normal, even faster machines the display takes time to complete the update. The GUI performance is why I returned to my e3 in lieu of the j1900.