Random crashes after upgrade to 16.6.2 from 16.5.2

[a1vdu]

Hi there, my untangle started crashing randomly after the upgrade to 16.6.2. I can't find any reason in the logs I've checked. Is there anything I can enable to have more debug info in the logs? I suspect it may be an hardware compability issue with the new debian version. It's installed on a PC with 16gb of ram and and Intel Core i3-4130 CPU. Never had any crash before this.

Thanks in advance and sorry if this isn't the right place to post this.

[bcarmichael]

I am sorry to hear that you are having stability issues with the latest release. Please reach out to our support team so we can identify what is causing the issue. https://support.untangle.com/hc/en-us/requests/new

[DCROK]

Seeing the same issue. Random reboots. Have been happily running 16.5.2 for a long time without any issues and now with the latest update it reboots randomly. As a Home Protect Plus subscriber (running on Protectli) my request ticket just got closed without any further help because I'm not eligible to support. If only the released software would thoroughly tested and reliable we wouldn't need any support. Pretty disappointed. Looking into other products.

[donhwyo]

You can look at /var/log/syslog. It may give some clues. There are a lot of ipv6 errors on mine but I don't think they are to blame. I don't think it is debian either. If it was there would probably be lots of complaints on debian forums. Plus they would be fixed quickly not ignored or deleted. LOL

[sky-knight]

Dont waste your time, that's an OS huge upgrade. If you have a problem, pull a backup and nuke the machine from orbit. These OS level updates have always had gremlins attached, and you can either pull your hair out, or start fresh and fix it.

[donhwyo]

Good advice if you upgraded. Unfortunately it is happening with clean installs too. But it is not there hardware so no problem. LOL

[DCROK]

fyi - I turned off Intrusion Prevention app and system has been running without random reboots for 5 days now. No real solution but at least we know what's the problem.

[sky-knight]

Intrusion Prevention is very memory and disk intense. It indicates the hardware is either buckling under the strain, or the new kernel has an "updated" driver that isn't handling the strain. Specifically, it would be a chipset or storage problem. Could be memory too, but that's a stretch.

[DCROK]

Intrusion Prevention is very memory and disk intense. It indicates the hardware is either buckling under the strain, or the new kernel has an "updated" driver that isn't handling the strain. Specifically, it would be a chipset or storage problem. Could be memory too, but that's a stretch.

Well, when looking at these system stats, they don't show any strain at crash/reboot time. FWIW Hardware is Protectli Vault FW4B - 4 Port, Intel Quad Core, 8GB RAM, 120GB mSATA SSD

[sky-knight]

Well, when looking at these system stats, they don't show any strain at crash/reboot time. FWIW Hardware is Protectli Vault FW4B - 4 Port, Intel Quad Core, 8GB RAM, 120GB mSATA SSD

That platform? that mSATA is dying... they love doing that. One of the many reasons I refuse to sell China junk like Protecli does. Here, you can import them yourself: https://www.alibaba.com/trade/search...rity+appliance

If you're going to buy garbage, you may as well get it cheap. The recent upgrade just pushed that garbage drive over it's wear endurance level, because it's basically that of a Micro SD card.

[road hazard]

Experienced the same thing. Fresh install of 16.6.2 and had a random crash. Made a post about it over here: https://forums.edge.arista.com/forum...taenous-reboot

When v17 drops, I'm going to run it in ESXi and see how it goes.

[sky-knight]

Experienced the same thing. Fresh install of 16.6.2 and had a random crash. Made a post about it over here: https://forums.edge.arista.com/forum...taenous-reboot

When v17 drops, I'm going to run it in ESXi and see how it goes.

Your situation is completely different, your hardware is fine just the drivers are suspect because Dell meets Debian, that's just the way it goes. You can fix your hardware AND be supported by using VMWare. The OP here has Protectli junk and most likely his SSD gave out during upgrade, because that's what they do.

Hang around Debian long enough, doesn't matter who's product uses it, and you'll see these same patterns.

[road hazard]

Your situation is completely different, your hardware is fine just the drivers are suspect because Dell meets Debian, that's just the way it goes. You can fix your hardware AND be supported by using VMWare. The OP here has Protectli junk and most likely his SSD gave out during upgrade, because that's what they do.

Hang around Debian long enough, doesn't matter who's product uses it, and you'll see these same patterns.

Good point (regarding the different hardware in use).

I put ESXi on my server a few days ago and testing things out with spinning up Linux and Windows workstations and so far so good. Been doing some disk intensive bench-marking in the Windows VM and after a bit over 48 hours, no spontaneous reboots. Still keeping a watchful eye out for v17 .

[agit8or]

I made a post about this and it was censored. We have multiple boxes randomly rebooting and UT blames it on the hardware, yet they have zero issues before the upgrade. Tech support has gone downhill.

[agit8or]

After spending a week with tech support (Which is now almost worthless) blaming it on hardware, we tried disabling IDS on 4 higher traffic boxes we were constantly having issues with. That was 5 days ago, zero crashes. Do better for your partners Arista.