ZenArmor issue after 24.7.8

Started by FredsterNL, November 09, 2024, 12:46:32 AM

Previous topic - Next topic
November 09, 2024, 12:46:32 AM Last Edit: November 09, 2024, 12:48:53 AM by FredsterNL
Hi all,

After upgrading yesterday I am getting the following alerts in my email from ZenArmor (paid version)

Time  Priority  Category  Firewall  Title  Message
2024-11-08 23:16:24 UTC  err  IPDRStreamer  MyHost (MyHost.my.domain)  ipdr.(*IPDRDirectoryReader).listen.func2.1  Local Insert Error: ES Return Code 400 local insertion error

Sometimes I get 2 of the same error in the same email

Not exactly inundated by emails (got 3 or 4 now), but....

Anyone an idea what is going? No errors during installation of 24.7.8, kernal update and boot was fine as well. No other changes have been done.

Edit: firewall seems to working normally otherwise, with ZenArmor to be an exception
Running OPNsense on a Deciso DEC750 with upgraded memory (16GB ECC) and active cooling

I'm experiencing the same issue as well. I've been receiving the same emails since upgrading to 24.7.8. Everything appears to be running well with my system.

I'm going to contact Zenarmor support and will report back once I hear back from them.

Thanks, keep us posted pls

there must be more users with this problem...

Do you have a license like I do? possibly only paying customers get the email? Dunno...
Running OPNsense on a Deciso DEC750 with upgraded memory (16GB ECC) and active cooling

Hi there,

There are more affected :), I can confirm I get exactly the same error every few hours (not regularly) since I upgraded to since 24.7.8.

Seems to work tough just fine in general, just get those notifications. So perhaps it's works as designed, we just need to update the notification settings?

Cheers Steff


I got a response back from the Zenarmor team late last night and they're still investigating the issue. They said that the issue isn't affecting Zenarmor operations, which basically confirms our experience. The only issue appears to be the unexpected emails being sent.

Hi,

As I kept getting more emails, I decided to reinstall ZenArmor from scratch.

Several hours ago now, and so far no new emails....

Will check back tomorrow or earlier if mails start again.
Running OPNsense on a Deciso DEC750 with upgraded memory (16GB ECC) and active cooling

November 12, 2024, 04:07:27 PM #6 Last Edit: November 13, 2024, 01:01:44 PM by FredsterNL
After a complete removal and reinstall, I have not received any error emails thusfar, so whatever the cause is, it seems to be solved by reinstalling.

Edit 13 Nov.:

Still no new alert messages after reinstall. No idea if the issue is being investigated by ZenArmor or not, but this could be a workaround it seems.


Running OPNsense on a Deciso DEC750 with upgraded memory (16GB ECC) and active cooling

This does not affect Zenarmor operations.
The team is working on the issue, and it will be resolved shortly.

I haven't heard back from Zenarmor Support, but I just noticed that the email alerts have stopped. I haven't done anything and the last alert I received was on 11/12/2024. I haven't received anything since then.

Quote from: IHK on November 13, 2024, 02:16:39 PM
This does not affect Zenarmor operations.
The team is working on the issue, and it will be resolved shortly.

Good to hear @IHK

Would it be possible to include a description of what went wrong and how it was solved?

The trigger was clear: the upgrade to 24.7.8 started the erors from appearing.

Is this only happening to paying customers or also others using the free version?
Running OPNsense on a Deciso DEC750 with upgraded memory (16GB ECC) and active cooling

I can report that it's an information warning error.

It was not an error related to OPNSense updates. 
It was a situation affecting all customers. An update was made shortly.

You should no longer see the error.


Quote from: FredsterNL on November 16, 2024, 01:42:41 AM
Quote from: IHK on November 13, 2024, 02:16:39 PM
This does not affect Zenarmor operations.
The team is working on the issue, and it will be resolved shortly.

Good to hear @IHK

Would it be possible to include a description of what went wrong and how it was solved?

The trigger was clear: the upgrade to 24.7.8 started the erors from appearing.

Is this only happening to paying customers or also others using the free version?