Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - tracker

#1
I am having the same issue, can't really pinpoint the source script (each time is a different one, PHP, Bash, CShell, different length of time since reboot, no errors other than the lockup).

I even put a healthcheck call on each script to know when it stops, and still cannot understand why.

Any good ideas for troubleshooting?

How do you monitor and recover from this if the problem is with the tool that is supposed to do that???

thanks
#2
Zenarmor (Sensei) / Re: Getting Ready for Zenarmor 1.16
December 19, 2023, 05:32:29 AM
Thank you for moving a bunch of Essential Security Items in the policy (free) to the Advanced Security policy (paid).
That was a low move, removing functionality that everybody had forever, heavy push do cripple the free version, isn't it?
Has the enshitification finally reached ZenArmor too?
#3
23.7 Legacy Series / WireGuard issues on 23.7.6
October 23, 2023, 05:02:50 PM
hello everyone.

Is anyone else seeing issues with wireguard connections failing between 23.7.6 upon reboot? I have a site-to-site link with a older opnsense router that's on 23.1.11_2 and a roadwarrior tunnel and I'm finding that ever since I did the upgrade, the wireguard connections won't re-establish on reboot. I have to uncheck the peer, hit apply, recheck it and hit apply every time the router is rebooted.

I've noticed the following: on the 23.7.6 side, upon reboot, when I check the new WireGuard Diagnostics page, the tunnels have (none) under the public key heading and the wrong port listed in the table, up until I uncheck/recheck the peer and hit apply. Once I do that, the tunnels behave properly until the next reboot. No changes have to be made on the roadwarrior client side and no changes have to be made on the 23.1.11_2 side for the tunnels to re-establish.

I am positive it was working on 23.7.5 and no configurations changes were made.

thanks!
#4
Perhaps I am misunderstanding the command, but I am trying to create a monit alarm for CPU temperatures, and the number I am retrieving from sysctl is not matching the dashboard by a large margin!

Is there any kind of math I need to do to get the real temp in a script?
Thanks
F
#5
Zenarmor (Sensei) / Re: Reports age
November 24, 2021, 08:07:54 PM
I was following this post as I thought something was amiss with Sensei on a couple of boxes I control.

All of a sudden, data would be missing. Instead of the configured 30 days, I would just have a couple of days of data, both on the dashboards and the drilldown.

Thinking that some corruption happened on the databases after the upgrade to 21.7 (as I noticed it just a couple of days after), I erased all the reporting data on 3 boxes and made a note of the day/time.

At the same time, I have also scheduled a weekly reboot Sunday morning to clear the nasty use of the swap that Sensei has developed in the last versions.

Today, I checked again, and to my surprise instead of having data since the erase, I only have data since the reboot, and made me realize that the problem was not the upgrade, but the reboot.

This problem might predate the 21.7 upgrade, but I never associated it to a reboot.

Does that make sense? Am I doing something wrong?

How can I help troubleshoot this?
(Bug Report sent from all three boxes)
#6
Well, problem is fixed, at least on the offending machine. Some PHP bug that got squashed by SunnyValley awesome support! You guys rock!

Thanks for the quick response!
#7
Unfortunately, they are! I went through every option for the interface configuration between the box that works and the one that doesn't...

The interesting part is that the LAGG interface, despite being active, doesn't show up on the list of interfaces (on the box that works), but the individual ports do!
#8
I have a couple of installs of Sensei where it protects the LAGG interface by adding the individual interfaces that are part of the team to the Protected interfaces:

In this case, igb2 and igb3, and it works as expected, handles the VLANS on the LAGG interface, etc...

New install, hardware is slightly different (6 ports instead of 4). Same configuration for the LAGG and interfaces, but the adapters that are part of the LAGG interface do not show up on the available interfaces list to be selected:


Ideas? Suggestions?