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

[6.303] Very unstable since update, 5 crashes in 24 hours

Since updating to 6.303 (not the reloaded one) we have one firewall which has crashed 5 times in the past 24 hours since the update.

I don't have the exact error message (the fw is not next to me so I have to have the message relayed), but the screen will say something like "not synchronizing" and "fatal error".

The machine has 2 e1000 nics, 2 8129 nics and an e100 nic.

Anyone else seeing something like this? I've seen plenty of other problems with 6.303, but nothing quite like this. Out of 5 firewalls running 6.303 (not the reload) this is the only one with problems so far...

In the mean time we are going to try putting a switch between the external nic/router and if that doesn't work luckily we have spare hardware we can load a backup onto.

This thread was automatically locked due to age.

Parents

0 drees over 19 years ago
After closer analysis of the logs, it appears to be the PPTP crash problem mentioned in this thread https://community.sophos.com/products/unified-threat-management/astaroorg/f/52/t/25758

2006:09:15-09:41:48 (none) pptpd[24922]: CTRL: Received PPTP Control Message (type: 15)
2006:09:15-09:41:48 (none) pptpd[24922]: CTRL: Got a SET LINK INFO packet with standard ACCMs
2006:09:15-09:41:48 (none) pppd-pptp[24923]: rcvd [LCP TermReq id=0x8 "}\37777777744m\37777777666\000

That's the last thing I see in the logs, then the thing gets hung.

So how can I install the new 6.303 so I don't have to swap out hardware and reinstall from scratch?
Cancel
Vote Up 0 Vote Down

Cancel
0 drees over 19 years ago in reply to drees

I reinstalled 6.303 and it looks OK now.

But the kernel did oops when shutting down for the update, see the attachment.
Cancel
Vote Up 0 Vote Down

Cancel
0 Basty777 over 19 years ago in reply to drees

i got big Problems too. I have ASG 220 and it crashes all the time, too!
Cancel
Vote Up 0 Vote Down

Cancel
0 drees over 19 years ago in reply to drees

Just FYI, I used yoshiki's tip to get 6.303 reloaded.

Edit /etc/version from 6.303 to 6.302.
Run normal update process as if you were running 6.302.
Cancel
Vote Up 0 Vote Down

Cancel
0 RFCat_vk_01 over 19 years ago in reply to drees

My home machine keeps locking up. I rebuilt it this morning and I thought I was using the re-loaded version of 6.303. If it fails again I will have to rebuild it and only update to 6.302.
Cancel
Vote Up 0 Vote Down

Cancel
0 VelvetFog over 19 years ago in reply to RFCat_vk_01

We installed the 6.303 patch on our office firewall around 4 pm Thursday.
Friday morning around 8 am the firewall crashed, and had to be restarted.
This is the first crash we have had since installing this machine a year ago.
I can not find anything in the logs to tell me what actually happened.
Cancel
Vote Up 0 Vote Down

Cancel
0 drees over 19 years ago in reply to VelvetFog

Do you know if you got the original 6.303 or the re-rolled one?
Cancel
Vote Up 0 Vote Down

Cancel
0 VelvetFog over 19 years ago in reply to drees

Do you know if you got the original 6.303 or the re-rolled one?
I am not sure. The firewall notified me that the new patch was available, and I installed it.

This is the very first time that I have had problems after installing an Astaro patch.
Cancel
Vote Up 0 Vote Down

Cancel
0 RFCat_vk_01 over 19 years ago in reply to VelvetFog

I rebuilt mine with what I thought was the reloaded version, but not sure how to tell.

I examined all the logs after yesterdays crash eg the system didn't really stop, just didn't record anything and access that didn't use the proxies continued. I couldn't log onto it to investigate what was happening. About the latest entry I can find was a virus update and then nothing until I restarted it.
Cancel
Vote Up 0 Vote Down

Cancel
0 drees over 19 years ago in reply to VelvetFog

You can tell if you are running the reloaded version by looking at the kernel version number.

Log into the console and run `uname -a`. If the version is 2.6.10-57 you are running the original 6.303. If the version is 2.6.10-58 you are running the reloaded version.

Example:
[FONT="Fixedsys"]Linux firewall.example.com 2.6.10-57-smp #1 SMP Mon Sep 4 09:29:26 UTC 2006 i686 i686 i386 GNU/Linux
Linux firewall.example.com 2.6.10-58-smp #1 SMP Thu Sep 14 16:09:00 UTC 2006 i686 i686 i386 GNU/Linux[/FONT]
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 drees over 19 years ago in reply to VelvetFog

You can tell if you are running the reloaded version by looking at the kernel version number.

Log into the console and run `uname -a`. If the version is 2.6.10-57 you are running the original 6.303. If the version is 2.6.10-58 you are running the reloaded version.

Example:
[FONT="Fixedsys"]Linux firewall.example.com 2.6.10-57-smp #1 SMP Mon Sep 4 09:29:26 UTC 2006 i686 i686 i386 GNU/Linux
Linux firewall.example.com 2.6.10-58-smp #1 SMP Thu Sep 14 16:09:00 UTC 2006 i686 i686 i386 GNU/Linux[/FONT]
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 RFCat_vk_01 over 19 years ago in reply to drees

Just did what was suggested in an esrlier post on this thread and the system behaved in a very similar way to the original upgrade in that it stopped part the way through the reboot cycle and had to be manually rebooted.

Something that I think has only started since 6.303 was installed is this in the kernel log. It doesn't show up during the build until after 6.303 is installed

2006:09:16-10:24:30 (none) kernel: HTB init, kernel part version 3.17
2006:09:16-10:24:30 (none) kernel: HTB: quantum of class 20001 is big. Consider r2q change.
2006:09:16-10:24:30 (none) kernel: HTB: quantum of class 20008 is big. Consider r2q change.
2006:09:16-10:24:30 (none) kernel: HTB: quantum of class 20003 is big. Consider r2q change.
2006:09:16-10:24:30 (none) kernel: HTB: quantum of class 20005 is big. Consider r2q change.
2006:09:16-10:24:30 (none) kernel: Ingress scheduler: Classifier actions prefered over netfilter

I am running the 2.6.10-58-default version.
Cancel
Vote Up 0 Vote Down

Cancel
0 drees over 19 years ago in reply to RFCat_vk_01

When the fw fails to reboot, do you see anything on the console?
Cancel
Vote Up 0 Vote Down

Cancel
0 RFCat_vk_01 over 19 years ago in reply to drees

Yes, it gets as far as checking the drives or disks can't remember which it is in blue.
System stopped about an hour ago, stopped processing anything using the virus/proxies. I couldn't logon via the console to find out what is happening.

Rebooted, looked in the logs and the only thing I can find is this in up2date report that might be relevant. I have the full set of virus/spam updates active (paid for).

2006:09:16-12:32:45 (none) pattern_install[8746]: Pattern Up2Date failed: Kaspersky Virus Protection Pattern chroot is missing
2006:09:16-12:32:45 (none) pattern_install[8746]: Pattern Up2Date: type='', status='failed'
2006:09:16-12:32:46 (none) pattern_install[8746]: Pattern Up2Date exiting:

2 of my eth cards are e1000.

This time I have root logged on running "top" to see if I can catch what ever it is.

Looks like tomorows job is re-build it back to 6.302

Ian M
Cancel
Vote Up 0 Vote Down

Cancel
0 drees over 19 years ago in reply to RFCat_vk_01

Sounds like your system is seriously borked.
Cancel
Vote Up 0 Vote Down

Cancel
0 RFCat_vk_01 over 19 years ago in reply to drees

That is after a fresh install from 6.300 iso and add each update. The current install is only a day old. This has only happened since 6.303 was installed.

Looks like the cure is worse than the disease.

Ian M
Cancel
Vote Up 0 Vote Down

Cancel