Sophos XG firmware 18.0 MR4 Internal Server Error

Hi Nilesh R Lad :  This issue with V18 MR4 is getting observed if "Refreshing the packet capture page with wrap buffer on"  over GUI packet capture. This is known to Sophos team with ID NC-64984 and as of now this issue fixed version taken in V18 MR-5. 

Without restarting appliance, TOMCAT service ( GUI service) restart will fix the issue.

TOMCAT service restart command:

For Single device ( or Non HA setup): 

#service tomcat:restart -ds nosync

If device in HA

#service tomcat:restart -ds sync

Hi Nilesh R Lad :  This issue with V18 MR4 is getting observed if "Refreshing the packet capture page with wrap buffer on"  over GUI packet capture. This is known to Sophos team with ID NC-64984 and as of now this issue fixed version taken in V18 MR-5. 

Without restarting appliance, TOMCAT service ( GUI service) restart will fix the issue.

TOMCAT service restart command:

For Single device ( or Non HA setup): 

#service tomcat:restart -ds nosync

If device in HA

#service tomcat:restart -ds sync

Thank you for the simpler restart. Using packet capture is painful in MR-4.

Hi GaryChancellor : Sorry for the trouble however as per my last comment team has already identified this issue and fixed is taken in V18 MR-5 and time being above is the work around without restart of firewall.

Hello GaryChancellor,

In addition, you can also check the packet flow using the command line interface.

Please find below link for more information on "How to monitor packet flow using the CLI"

support.sophos.com/.../KB-000035939

other details on this can be found here:

community.sophos.com/.../v18-mr4---webadmin-tomcat-crashes-500-internal-server-error

Is there already an ETA for 18.0MR5 for software installations? 

Should be ready. There will be no ISO. So use V18.0 MR4 and update to V18.0 MR5 via up2Date. 

Na, my VM is running with 18.0.4.506 and shows no new version

MR5 is in a soft release. You have to pick up the firmware as a SIG file in the mysophos portal and manually upload it. 

I ran the command "service tomcat:restart -ds nosync" but it didn't work. the shell shows "503 service failed" error. 

Hi Kafu Hacin,

Request to share the output of tomcat.log

Login to SSH > 4. Device Console > 5. Device Management

# tail -f /log/tomcat.log

In another SSH session, run the command to restart tomcat service.

# service tomcat:restart -ds nosync