Netgate 1100 dns stops

Gertjan

@stephenw10 said in Netgate 1100 dns stops:

None of that looks like a problem.

Let me rephrase these logs lines :

Sep 22 21:12:31 unbound 99947 [99947:0] info: start of service (unbound 1.12.0).
Sep 22 21:12:31 unbound 99947 [99947:0] info: start of service (unbound 1.12.0).
Sep 22 21:12:32 unbound 99947 [99947:0] notice: Restart of unbound 1.12.0.
Sep 22 21:12:32 unbound 99947 [99947:0] info: start of service (unbound 1.12.0).
Sep 22 21:12:32 unbound 99947 [99947:0] info: service stopped (unbound 1.12.0).
Sep 22 21:12:32 unbound 99947 [99947:0] notice: Restart of unbound 1.12.0
Sep 22 21:12:32 unbound 99947 [99947:0] info: start of service (unbound 1.12.0).

That's a restart every second !
I think I known all the reasons why unbound would get restarted **.
Still, for a 1100, this is IMHO, far in the danger zone.

Restarting unbound while its already restarting, I don't know how to explain this, but something tells me that there is a big chance that @Freek_Box winds up with a dead unbound process in his pfSense.
And this gives all the effect needed to find himself with that "dns stops".

** is there an interface going up and down every seconds ?
A LAN device is hail storming the SG11000 with DHCP requests ?
Etc.
These two would restart unbound.

SteveITS

@gertjan said in Netgate 1100 dns stops:

would restart unbound

Also a DHCP lease renewal, if DNS registration is enabled.

v1.12 is a few pfSense versions old though...? 22.01 would have 1.13 IIRC. @Freek_Box what pfSense version are you on?

I recall there was one pfSense version that reverted unbound to an earlier version due to stability issues but I can't seem to find that in the release notes.

stephenw10

It's not actually unusual to see that logged multiple times when Unbound is restarted. And that isn't usually a sign of a problem. For example here I restarted manually it on my edge, logs filtered for restarts:

Sep 23 15:57:15 	unbound 	97113 	[97113:0] info: start of service (unbound 1.15.0).
Sep 23 15:57:17 	unbound 	97113 	[97113:0] info: start of service (unbound 1.15.0).
Sep 23 15:57:18 	unbound 	97113 	[97113:0] info: start of service (unbound 1.15.0).
Sep 23 15:57:20 	unbound 	97113 	[97113:0] info: start of service (unbound 1.15.0).
Sep 23 15:57:41 	unbound 	97113 	[97113:0] info: start of service (unbound 1.15.0).
Sep 23 15:57:42 	unbound 	97113 	[97113:0] info: start of service (unbound 1.15.0).

The question of how Unbound is managed is... another question!
But it should not stop t responding normally after that.

Steve

Gertjan

@stephenw10
Manually restarting, because, for example, your editing the config, is normal.

This is a more graphical way to look at my unbound restarts.

and most of these restarts are a result of of my interaction with unbound, directly, or indirectly, like me trying out things with pfBlockerng-devel - like switching between unbound and python mode so I think I can answer something here on the forum after testing it myself

When I'm not at work for a week - then unbound won't restart in that week.
Only pfBlockerng-devel will break that cycle.
For me, unbound 1.15.0, is very stable.

Using 22.05 on a 4100 - and yes, I'm using IPv4 (two third of the traffic) and IPv6 (one third of the traffic).

stephenw10

Yup, it doesn't restart often for me either but when it does it logs several restarts in a row like that.

When OP checks his resolver logs I would expect it to show that as the last thing that happened. If it was showing continuous restarts that would be a much bigger issue.

If the Unbound service just stops a cannot be restarted I expect to see some errors logged either in the Resolver or System log.

Steve

Freek_Box

@gertjan

Running version 21.05.2-RELEASE (arm64)

stephenw10

Any reason you're not running something newer?

Freek_Box

@stephenw10

I asume I'm on the latest version?

SteveITS

@freek_box Nope, that's last year.
https://docs.netgate.com/pfsense/en/latest/releases/index.html#pfsense-plus-software
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

Gertjan

@freek_box said in Netgate 1100 dns stops:

I asume I'm on the latest version?

Add the RSS widget on your dashboard :

https://www.netgate.com/blog/pfsense-plus-software-version-22.05-now-available
so you'll have a double check on what happening and available.

This :

is strange.
The check for available updates succeeded, but the info coming back said "21.05.2-Release", so, you're fine.
As already said above, use the Troubleshooting Upgrades suggestions. You will find 22.05 avaible.

Freek_Box

@steveits

I did the:
Navigate to System > Updates
Set Branch to Previous stable version
Wait a few moments for the upgrade check to complete

But now it shows:

stephenw10

At the command line run:

pkg-static -d update

What error does it return?

Freek_Box

@stephenw10

DBG(1)[40213]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[40213]> PkgRepo: verifying update for pfSense-core
DBG(1)[40213]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[40213]> Request to fetch pkg+https://repo.netgate.com/pkg/pfSense_plus-v21_05_2_aarch64-core/meta.conf
DBG(1)[40213]> opening libfetch fetcher
DBG(1)[40213]> Fetch > libfetch: connecting
DBG(1)[40213]> Fetch: fetching from: https://repo00.atx.netgate.com/pkg/pfSense_plus-v21_05_2_aarch64-core/meta.conf with opts "i"
1082900480:error:141F0006:SSL routines:tls_construct_cert_verify:EVP lib:/var/jenkins/workspace/pfSense-build-release-tarballs/BUILD_NODE/pkg-aarch64/OS_MAJOR_VERSION/freebsd12/PLATFORM/aws/crypto/openssl/ssl/statem/statem_lib.c:283:
DBG(1)[40213]> Fetch: fetching from: https://repo00.atx.netgate.com/pkg/pfSense_plus-v21_05_2_aarch64-core/meta.conf with opts "i"
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/CN=repo00.atx.netgate.com
1082900480:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-build-release-tarballs/BUILD_NODE/pkg-aarch64/OS_MAJOR_VERSION/freebsd12/PLATFORM/aws/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Segmentation fault (core dumped)

Freek_Box

When I do:
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade

I get:
pkg-static: Repository pfSense missing. 'pkg update' required
pkg-static: No package database installed. Nothing to do!
Updating pfSense-core repository catalogue...
1082900480:error:141F0006:SSL routines:tls_construct_cert_verify:EVP lib:/var/jenkins/workspace/pfSense-build-release-tarballs/BUILD_NODE/pkg-aarch64/OS_MAJOR_VERSION/freebsd12/PLATFORM/aws/crypto/openssl/ssl/statem/statem_lib.c:283:
Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/CN=repo01.atx.netgate.com
1082900480:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-build-release-tarballs/BUILD_NODE/pkg-aarch64/OS_MAJOR_VERSION/freebsd12/PLATFORM/aws/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Child process pid=4480 terminated abnormally: Segmentation fault

stephenw10

The segfault like that indicates the crypto chip is in an unreachable state. You need to completely power cycle the device to reset it. So halt the device then remove the power for 10s or so. It should update correctly when rebooted.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#segmentation-fault-in-pkg

Steve

Freek_Box

@stephenw10

I have no possibility to unplug it is that a problem? The device is hours away from me.

SteveITS

@freek_box If you click that doc page URL it's a known issue. It shouldn't affect normal operations but does affect packages and therefore upgrades. I believe it's just a one time fix though. I haven't had it recur on my 2100.

stephenw10

Unfortunately I know of no other way to reset that once it has entered that state. It will not be able to connect to the update repo until the crypto chip is reachable again.

Freek_Box

@stephenw10 only rebooting is not enough?

Gertjan

@freek_box
Noop.
The 'crypto chip' van't be reset using a command.
A 10 seconds power down can bring it back online.

edit : that is : a clean, commanded power down by the GUI or console(SSH),. Some ripping out the power and put it back in again could create other issues like a dirty file system.

So : console or SSH option 6.
Or GUI : Diagnostics > Halt System
Let the system shut down.
Then, remove the power for 10 seconds.
Power back in.
Done.