[Error] configctl

[tobasium]

Hi,

For some time now I have been finding an error in my log that I cannot finally assign.
The error occurs exactly every hour 0:02, 1:02, 2:02,.....

I have the assumption that Zenarmor has something to do with it but I can't confirm it.

[Error]
error in configd communication Traceback (most recent call last): File "/usr/local/sbin/configctl", line 66, in exec_config_cmd line = sock.recv(65536).decode() socket.timeout: timed out

Can someone help me here?

current opnsense version.

Translated with DeepL.com (free version)

[IHK]

Could you please send all log and configuration files by clicking on the Send Feedback link at the bottom left of the page?

https://www.zenarmor.com/docs/support/reporting-bug#as-of-v114

Best Regards

[tobasium]

hi,

sended all logs.

[mpccert]

Hi, did zenarmor replied to you? I also have the  same error logs. thank you.

OPNsense 23.7.8_1-amd64
FreeBSD 13.2-RELEASE-p5
OpenSSL 1.1.1w 11 Sep 2023
2024-01-30T23:03:11   Error   configctl   error in configd communication Traceback (most recent call last): File "/usr/local/sbin/configctl", line 66, in exec_config_cmd line = sock.recv(65536).decode() socket.timeout: timed out   

[IHK]

We can help you too.

Can you please send all log and configuration files by clicking the Send Feedback link at the bottom left of the page?

https://www.zenarmor.com/docs/support/reporting-bug#as-of-v114

[tobasium]

I might found the issue.

I only have to go to system > settings> general . It turns out there's a checkbox (2nd from bottom) that you need to tick to make OPNSense use your DNS. I think what happens is when you change Unbound's port to make room for AdGuard, OPNSense still does not move over to use AdGuard and tries 'the old way' aka unbound on port 53, first. But unbound isn't listening on 53 anymore, so it hangs.

Since i changed and update opnsense no errors