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

XG 18 MR3 crashing

I have an XG that I upgraded from 17.5.14-1 to 18.0.3 and twice now during the business day it crashes. This is the first time in my few years working with the XG that it crashed and restarts. Has anyone else experienced this? I have a case open and the engineer had me make the changes below. I made the changes on Tuesday and it just crashed again on me today on Thursday.

1. From GUI of XG, Please go to Protect-> web->general Settings->  Do not scan files larger than-> Set as 1 mb
Scanning mode: Change to Real-time
 
Please go to system services-> Log settings-> Disable logging for Invalid Traffic. 
Also disable logging for the feature which you are not using. 
 
2.
Get the device console access:
Main Menu-> Option 4
 
console>system auto-reboot-on-hang show
Auto reboot system when kernel gets into a hang state is disabled
 
If you see it is disabled then please enable it. 
 
console>system auto-reboot-on-hang enable
 
3.
console>system firewall-acceleration show
Firewall Acceleration is Enabled.
 
If you see it is enabled then disable it. 
 
console>system Firewall-acceleration disable 

Its an SFV6C8, 6 core with 8GB RAM running on Hyper-V. There have always been bugs in the XG but its always been stable.



This thread was automatically locked due to age.
Parents
  • Do you see a abnormal usage in the Report section for your hardware. Something like a Mem leak? 

  • Hi LuCar, not really. I mean when it first happened I had a bunch of "SWAP memory Usage reached 99% exceeding the threshold of 95%" in the SYSTEM log for a few hours leading up to the reset however, after making the listed changes from the engineer there were no more of those leading up to this next crash. As far as I could tell everything was working normally. The system log only shows normal signature updates periodically and then the next entries are the interfaces coming back online.

Reply
  • Hi LuCar, not really. I mean when it first happened I had a bunch of "SWAP memory Usage reached 99% exceeding the threshold of 95%" in the SYSTEM log for a few hours leading up to the reset however, after making the listed changes from the engineer there were no more of those leading up to this next crash. As far as I could tell everything was working normally. The system log only shows normal signature updates periodically and then the next entries are the interfaces coming back online.

Children
No Data