Sophos XGS 107 with newest firmware temporary not responding over webinterface

Question

Hi, 
 I have the problem that the firewall is temporarily not operable via the web interface and is stuck. The status page doesn't show anything when it comes to performance either. tested across various browsers and systems, including sophos central. what can I do, does anyone have an idea? I've already looked at various logs via SSH, but didn't notice anything unusual. 
 
 Thanks for help.

Mayur Makvana · Answer

Hello Tino Haubner1 , 
 
 Thank you for contacting Sophos Community! 
 This seems affected with NC-137470 or NC-133056 
 The relevant logs as below of tomcat. 
 2024-07-01 15:34:41,68:ERROR:CSC - Exception in sendTCP java.net.SocketTimeoutException: Read timed out at java.base/java.net.SocketInputStream.socketRead0(Native Method) at java.base/java.net.SocketInputStream.socketRead(Unknown Source) at java.base/java.net.SocketInputStream.read(Unknown Source) at java.base/java.net.SocketInputStream.read(Unknown Source) at java.base/java.net.SocketInputStream.read(Unknown Source) at cyberoam.corporate.csc.client.CSCClient.sendTCP(CSCClient.java:538) at cyberoam.corporate.csc.client.CSCClient._send(CSCClient.java:424) at cyberoam.corporate.csc.client.CSCClient.send(CSCClient.java:148) at cyberoam.corporate.csc.client.CSCClient.generateAndSendAjaxEvent(CSCClient.java:712) at cyberoam.corporate.csc.client.CSCClient.generateAndSendAjaxEvent(CSCClient.java:679) at cyberoam.corporate.csc.utilities.CyberoamAjaxHelper.process(CyberoamAjaxHelper.java:2144) at cyberoam.corporate.servlets.CyberoamCommonServlet._doPost(CyberoamCommonServlet.java:487) at cyberoam.corporate.servlets.CyberoamCommonServlet.doPost(CyberoamCommonServlet.java:354) at cyberoam.corporate.servlets.CyberoamCommonServlet.doGet(CyberoamCommonServlet.java:196) at javax.servlet.http.HttpServlet.service(HttpServlet.java:503) at javax.servlet.http.HttpServlet.service(HttpServlet.java:590) at org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1419) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764) at org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1665) at cyberoam.utilities.csrf.CSRFCheckFilter.doFilter(CSRFCheckFilter.java:152) at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:202) at org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1635) at cyberoam.sessionmanagement.SessionCheckHelper.filter(SessionCheckHelper.java:136) at cyberoam.sessionmanagement.SessionCheckFilter.doFilter(SessionCheckFilter.java:57) at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:202) at org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1635) at cyberoam.sessionmanagement.RequestCheckFilter.doFilter(RequestCheckFilter.java:188) at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:210) at org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1635) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:527) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:131) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:578) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:223) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1570) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1383) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:484) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1543) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1305) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:192) at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:51) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122) at org.eclipse.jetty.server.Server.handle(Server.java:563) at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:505) at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100) at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53) at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:416) at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:385) at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:272) at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.lambda$new$0(AdaptiveExecutionStrategy.java:140) at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:411) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:934) at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1078) at java.base/java.lang.Thread.run(Unknown Source)

This will be fixed in version v20 MR 2. The alternate option is to restart the tomcat service using below from the advanced shell: 
 #service tomcat:restart -ds nosync 
 I have appended the information on your case and team shall review for any prefix available.

Erick Jan · Answer

Hi Tino, 
 Thank you for reaching out to Sophos Community. 
 To verify, what version have you upgraded? 
 Can you try to restart the Web services and try again? Also, you may refer to the following KB for reference 
 service apache:restart -ds nosync 
 
 Sophos Firewall: What to do when the Web Admin is not accessible 
 
 If this would not suffice, I would recommend creating a case to Support and kindly share the case ID here.

Sophos XGS 107 with newest firmware temporary not responding over webinterface

Top Replies