Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 691 views
  • Users 0 members are here
Options
Suggested
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

Log viewer Timer filter not showing all 30 minutes

SGH

We have a XGS2100 (SFOS 18.5.2 MR-2-Build380) 

When I use Log viewer and use a Timer filter (any) it is only showing few minutes and gets in a loop

I think this is a bug?



This thread was automatically locked due to age.
  • 0

    Queries can start with either a table name or the search command. It's a good idea to start with a table name, because it defines a clear scope for the query and improves both query performance and the relevance of the results.

    MIBridges Login

  • 0

    Some more information about the problem I have with Timer filter
    The XGS2100 firewall is in HA

    The other XGS I manage are XGS136 (no HA) and do not have this problem
    XGS136 (SFOS 18.5.2 MR-2-Build380) X131079

    Could this only be with XGS2100 in HA or any HA or any XGS2100?
    The Logviewer is also in a loop when I use Sophos Central.

    Can someone in this community check if they have the same problem?
    Easy to check; start logviewer and use Timer filter; then scroll down; result? loop or no loop?

  • 0 in reply to SGH

    If it is in Central, this means, the syslog Server did in fact report this data. 

    But: logviewer is a connection based method. Means, SFOS is not only showing you the start of the connection, also the End in one entry/connection.

    Check if the entry is actually a loop or unique connections.  

  • +1 in reply to LuCar Toni

    Hi

    it just got solved by itself.

    I did not make any changes and when I just started testing again for a new screenhosts the Timer filter worked as expected.

    Problem solved but not having a clue why.

    The Logviewer had the same issue local and central. I could scroll down forever. (loop)