Hi all,
Shall we start this new thread with the looks and feels of XG v18 MR-3?
community.sophos.com/.../xg-firewall-v18-mr3
This thread was automatically locked due to age.
Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.
Hi all,
Shall we start this new thread with the looks and feels of XG v18 MR-3?
community.sophos.com/.../xg-firewall-v18-mr3
Hi guys, anyone having issues with stability? VPN users reporting connection issues, web admin portal unusable, I even could not restart the router (XG125). So I had to do a hard unplug reset. I was waiting with V18 for at least MR3. Because let's be honest, quality of XG firmwares is going downhill pretty badly. And still v18 MR3 was too soon :-/ If this happens again, I will roll back to v17.
XG was basically dead, no web admin, no ssh, so I cannot provide any more info. Routing, wan connectivity was ok though.
I just had my XG106 MR-3 freeze up where I had to unplug it and plug it back in. It froze in the middle of the night and nothing in the logs that was unusual. I honestly never had to do this before with any of my Sophos firewalls. It's been on MR-3 for a week I think.
Hello Ben,
Do you see any gap in the logs for csc.log, applog.log, syslog.log, networkd.log when this happened?
Also do you see a gap in Memory or CPU graph, when this issue was happening?
Regards,
Hi, I beleive I do have the same issue. As far as I can tell csc, applog have no unusuall gaps, but syslog has 5hours gap the night before the crash.
RAM was at 60% all the time, but the morning before crash I had CPU spikes to 100% which probably caused the web admin not responding.
Thanks for the reply. I wasn't sure what I should check next to determine what happened.
CPU and Memory both flat line at the same times of the outage. Memory had a spike from 52% to 81% at 22:50. My backup is set to run at Sunday at 00:00 and I did receive the backup in an email at 12:02 am.
app.log has a gap
Nov 01 22:45:10 Checking new IPs of fqdn for mta
Nov 02 11:13:20 prepare_virtual_app_setup: Syncing network interface.
csc.log has a gap
MESSAGE Nov 01 22:45:29 [worker:16734]: {"request":{"method":"nopcode","name":"u2d_dr_installer","version":"1.2","type":"text","length":0}}
mount: /_conf/csc: Invalid argument
MESSAGE Nov 02 11:13:15 [csc:992]: Restricted context is initialized successfully
networkd.log has nothing?
INFO ; Oct 27 09:28:43 ; ADMIN ; ND_MAIN ; sending reply: -1;
ERROR ; Nov 02 11:14:47 ; ADMIN ; ND_MAIN ; string is null;
syslog has a gap
Nov 2 23:59:03 (none) user.err kernel: [45963.307650] 774:appdev_release:dev open 0
Nov 3 00:00:04 (none) user.err kernel: [46024.515571] 729:appdev_open:dev open 0 1f
Thanks for the reply. I wasn't sure what I should check next to determine what happened.
CPU and Memory both flat line at the same times of the outage. Memory had a spike from 52% to 81% at 22:50. My backup is set to run at Sunday at 00:00 and I did receive the backup in an email at 12:02 am.
app.log has a gap
Nov 01 22:45:10 Checking new IPs of fqdn for mta
Nov 02 11:13:20 prepare_virtual_app_setup: Syncing network interface.
csc.log has a gap
MESSAGE Nov 01 22:45:29 [worker:16734]: {"request":{"method":"nopcode","name":"u2d_dr_installer","version":"1.2","type":"text","length":0}}
mount: /_conf/csc: Invalid argument
MESSAGE Nov 02 11:13:15 [csc:992]: Restricted context is initialized successfully
networkd.log has nothing?
INFO ; Oct 27 09:28:43 ; ADMIN ; ND_MAIN ; sending reply: -1;
ERROR ; Nov 02 11:14:47 ; ADMIN ; ND_MAIN ; string is null;
syslog has a gap
Nov 2 23:59:03 (none) user.err kernel: [45963.307650] 774:appdev_release:dev open 0
Nov 3 00:00:04 (none) user.err kernel: [46024.515571] 729:appdev_open:dev open 0 1f
Hello Ben,
Thank you for what about the Graphs, do you see any GAP in there?
Regards,