This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos XG Firewall 17.5: Logs are not updating on the GUI "Log Viewer"

Sophos XG firewall is offering on Device Reporting and logs, which is a good feature for all SMBs. There is another module "Sophos iView" available for logs and reporting but it is good for some critical organization or big data Center who need a lot of logs, reports, and backup of all those.   

Recently, I faced an issue as there is no log showing on the GUI "Log Viewer" but you will see all logs through the command line or some new logs on the auxiliary device but not on the primary devices (new logs not updating). This issue is reported on a virtual and hardware firewall as well. Today I am going to share how to handle this issue without book a ticket with the NOC team.

 

Issue Reported:

Logs are not updating on the GUI "Log Viewer" application of the Sophos XG firewall. 

Troubleshooting Steps:

Please read a full blog post at:

http://www.routexp.com/2019/04/sophos-xg-firewall-175-logs-are-not.html



This thread was automatically locked due to age.
Parents
  • Just facing this issue today, thank, it saves me a lot of time. 

    after executing the command line: service garner:restart -ds nosync log viewer updated new data. 

    I'm using XG310 (SFOS 17.5.5 MR-5) , hope Sophos soon release the new firmware to get it fixed. 

    Thanks guys

  • Ok.  But you have an idea what "service garner:restart -ds nosync" really does ? I mean, beyond the title ?

    I'm always scratching my head when Sophos' development is "on something".  What kind of codes Sophos' developers are facing ?  We already know XG is mostly a collection of open-source codes.  Nothing that unknown.  Here, we are taking about a "reporting" bug.  Corecting this is not something that's supposed to change the behavior of XG.  It does not input anything back into XG's database.  And yet, this post is two month old.  That bug is known since even further.  And no fix on the radar yet.  For god's sake, why each and everything takes an eternity to fix at Sophos ?

    Paul Jr

Reply
  • Ok.  But you have an idea what "service garner:restart -ds nosync" really does ? I mean, beyond the title ?

    I'm always scratching my head when Sophos' development is "on something".  What kind of codes Sophos' developers are facing ?  We already know XG is mostly a collection of open-source codes.  Nothing that unknown.  Here, we are taking about a "reporting" bug.  Corecting this is not something that's supposed to change the behavior of XG.  It does not input anything back into XG's database.  And yet, this post is two month old.  That bug is known since even further.  And no fix on the radar yet.  For god's sake, why each and everything takes an eternity to fix at Sophos ?

    Paul Jr

Children
No Data