Thread Info
  • State Verified Answer
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 35 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 42758 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

XG210 crashed today

VikenNajarian

Hello,

The XG210 of my Custommer crashed today at 8:50AM, we were not able to ping the LAN IP or the WAN IP.

The firmware version is 17.1 GA.

It came back after a manual reboot.

Once online again I saw in the "performance" tab that we had an anormal high number of sessions at 8h50 which I guess it's the cause why the firewall crashed.

I don't really know what can cause such a high number of sessions, in normal use the sessions number is between 300 and 600 on this firewall...

Any advice ?


I opened a case with the number: 8183274

 

Viken



This thread was automatically locked due to age.
Parents
  • 0

    I had a similar experience.

    My XG 230 running 17.1 GA hot a Load Average of above 15 which made the CPU get stuck at 98+%

     

    I had to pull the plug and reboot it to get it back. It too reports high CPU. Only since 17.1 was loaded though.

    Sophos XG 450 (SFOS 18.5.1 MR-1)

    Sophos R.E.D 50 x 2

    Always configuring new stuff.....

  • 0 in reply to M8ey

    Hello,

    Mine did not crashed since my post.

    Hope that it won't anymore.

    Viken

    XG Certified Architect

    Sophos Gold Partner - Reseller from Lyon, France

  • 0 in reply to VikenNajarian

    Mine hasn't either.

     

    I had the Sophos Support team jump in and run through the logs. We can see when I rebooted it but for 30 min before - when CPU was high there were no logs showing anything bad.

    The XG just went nuts for no reason.

    Sophos XG 450 (SFOS 18.5.1 MR-1)

    Sophos R.E.D 50 x 2

    Always configuring new stuff.....

  • 0 in reply to M8ey

    The Sophos support just called me back today to connect on the XG and have a look on this crash.

    They told me they will escalate the case at the lvl 3 because they couldn't find anything in the logs.

    Viken

    XG Certified Architect

    Sophos Gold Partner - Reseller from Lyon, France

  • 0 in reply to VikenNajarian

    All I got from support was to perform Hardware, Memory, and Disc checks.

    Sophos XG 450 (SFOS 18.5.1 MR-1)

    Sophos R.E.D 50 x 2

    Always configuring new stuff.....

  • 0 in reply to VikenNajarian

    Sadly mine crashed yet again - this time no CPU load etc - just stopped and died.

    Sophos XG 450 (SFOS 18.5.1 MR-1)

    Sophos R.E.D 50 x 2

    Always configuring new stuff.....

  • 0 in reply to M8ey

    Sad...

    Mine did not crash since the initial crash and lvl 3 engineers are still investing on the issue.

    Viken

    XG Certified Architect

    Sophos Gold Partner - Reseller from Lyon, France

  • 0 in reply to VikenNajarian

    Mine crashed yet again today.

     

    Logging etc was fine until the crash when it just stopped - no errors etc.

    Sophos are now RMA me a new one as they think it might be a Hardware failure due to the way logs just stop.

    Sophos XG 450 (SFOS 18.5.1 MR-1)

    Sophos R.E.D 50 x 2

    Always configuring new stuff.....

  • 0 in reply to M8ey

    We have had one of our XG210s (lightly loaded) crash yesterday about 15:45, with 17.1.1 MR-1, hard rebooted today as even ssh terminal will not log in, GUI died 1hr or so later, ssh cannot login as well so downgraded to 17.0.8 MR-8

    It had been running 17.1.1 MR-1 for over a week with no issues so I think an update sent yesterday has caused this.

Reply
  • 0 in reply to M8ey

    We have had one of our XG210s (lightly loaded) crash yesterday about 15:45, with 17.1.1 MR-1, hard rebooted today as even ssh terminal will not log in, GUI died 1hr or so later, ssh cannot login as well so downgraded to 17.0.8 MR-8

    It had been running 17.1.1 MR-1 for over a week with no issues so I think an update sent yesterday has caused this.

Children
No Data
Cookie Information Banner