24.03 servicewatchdog_cron unbound certificate no such file (service won't start)
-
Yes try disabling the watchdog for Unbound and then try to upgrade again.
-
@stephenw10 disabling/removing the watchdog didn't work. It seems I made the mistake of not removing pfblockerng and specifically suricata before i upgraded. when i subsequently removed both packages, the suricata still showed in the installed packages with a red exclamation mark. When I try to reinstall it though, it gets stuck on "installing snort rules", however, if you open a new window and check the status on suricata it shows the rules having been successfully updated
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
So it did upgrade successfully with those packages removed?
-
@stephenw10 still having some issues getting wireguard to start, pfblocker and suricata. but definitely should have removed them before the upgrade i think
-
I wouldn't expect to need to but it will take a lot longer to upgrade with them in place.
-
@stephenw10 looks like may actually be issue with pfblockerng in the new build
ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng_category_edit.php, Line: 391, Message: Uncaught ValueError: range(): Argument #3 ($step) must be greater than 0 for increasing ranges in /usr/local/www/pfblockerng/pfblockerng_category_edit.php:391
Stack trace:
#0 /usr/local/www/pfblockerng/pfblockerng_category_edit.php(391): range()
#1 {main} -
@4o4rh said in 24.03 servicewatchdog_cron unbound certificate no such file (service won't start):
ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng_category_edit.php, Line: 391, Message: Uncaught ValueError: range(): Argument #3 ($step) must be greater than 0 for increasing ranges in /usr/local/www/pfblockerng/pfblockerng_category_edit.php:391
This one ?
-
Yup almost certainly that is generating that error.
But that shouldn't prevent upgrading. Or running pfBlocker in 24.03. It only happens if you try to edit a list.
-
@stephenw10 yep. i was trying to remove one of the failing downloads. how do you add the official patch via system/patches pls?
I tried a couple of methods i get
- does not aply cleanly
- does not revert cleanly
-
The default settings there should work:
-
@stephenw10 got that thanks. seems there are still some issues with dns resolution on the internal network
-
@Gertjan haha
noooo watchdog is like a beefed up junkyard dog that won’t stop barking until you find out what is going on -
@stephenw10 Static DHCP entries are not resolving. Upon checking the ui for DNS Resolver, there is no longer the checkbox for "DHCP Registration" and "Static DHCP"
-
@JonathanLee misdirection. I already posted what the root cause was. everything is working now, except Static DHCP registrations in the DNS Resolver - checkbox is missing now
-
