OPNsense Forum

English Forums => Zenarmor (Sensei) => Topic started by: Greelan on May 17, 2021, 02:50:33 pm

Title: [SOLVED] Error in configd communication
Post by: Greelan on May 17, 2021, 02:50:33 pm

I've just started seeing the following error in my OPNsense logs. It repeats 2 times (close together) every hour:

Code: [Select]

configctl[2077] error in configd communication Traceback (most recent call last): File "/usr/local/opnsense/service/configd_ctl.py", line 68, in exec_config_cmd line = sock.recv(65536).decode() socket.timeout: timed out
Any ideas as to cause and cure?

Title: Re: Error in configd communication
Post by: Greelan on May 22, 2021, 01:38:32 pm

Nobody?

I can't see anything else in the logs around the same time that seems connected.

Title: Re: Error in configd communication
Post by: mihak on May 23, 2021, 12:32:46 am

It seems like a timeout when Python code in Configd_ctl waits for something...
What OPN version, what plugins, when was the last reboot of the FW... We need more info to help you triage.

Title: Re: Error in configd communication
Post by: Greelan on May 23, 2021, 02:07:03 am

Fair.  :)

Versions:

Code: [Select]

OPNsense 21.1.5-amd64
FreeBSD 12.1-RELEASE-p16-HBSD
OpenSSL 1.1.1k 25 Mar 2021
Plugins:

Code: [Select]

os-postfix
os-sensei
os-sensei-updater
os-smart
os-speedtest-community
os-sunnyvalley
os-theme-cicada
os-theme-rebellion
os-udpbroadcastrelay
os-wireguard
(Although Sensei is currently completely stopped.)

Uptime:

Code: [Select]

8 days 04:04:48
Currently have two WG interfaces, one for various road warrior clients, and one for a tunnel to a commercial VPN provider.

Happy to post any more info that might be relevant.

Title: Re: Error in configd communication
Post by: Greelan on May 23, 2021, 02:14:27 am

Just also noticed these errors:

Code: [Select]

configd.py[40730] unable to sendback response [OK ] for [sensei][datastore-retire][['ES']] {aefea11b-8826-4552-bf56-f4171f34e92c}, message was Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 202, in run self.connection.sendall(('%s\n' % result).encode()) BrokenPipeError: [Errno 32] Broken pipe
configd.py[40730] unable to sendback response [OK ] for [sensei][periodicals][None] {7896f46a-3830-440d-a63a-a7c686559c90}, message was Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 202, in run self.connection.sendall(('%s\n' % result).encode()) BrokenPipeError: [Errno 32] Broken pipe
Again, twice per hour near the start of the hour. The first one close to the other error, the second maybe 2 or 3 minutes later.

I will uninstall Sensei entirely and see whether anything changes. If this is Sensei, it will be the third time that it has caused some weird router behaviour over the last few months. First it caused interfaces to drop/restart every 48 hours, resulting in IPv6 failing, and then it borked DNS resolution on OPNsense. Seems a pretty broken plugin imo.

Title: Re: Error in configd communication
Post by: Greelan on May 23, 2021, 03:32:24 am

Yep, errors have stopped after uninstalling Sensei. It is always bloody Sensei

Title: Re: [SOLVED] Error in configd communication
Post by: franco on May 24, 2021, 07:27:48 pm

Looks like it tries to poll a service that is not running without checking if it should be running at all. Should be an easy fix for them. I'll move it to Sensei forum.


Cheers,
Franco

Title: Re: [SOLVED] Error in configd communication
Post by: jclendineng on December 24, 2021, 06:25:59 pm

Same issue here sorry to re open. I’m out of town and this error was tied to my unbound shutting down. Has the sensei team fixed? I can’t have my dns randomly shutting down. Thank you!

Title: Re: [SOLVED] Error in configd communication
Post by: eponymous on December 26, 2021, 08:18:17 pm

This is also reported here (along with many other posts I found searching this forum):

https://forum.opnsense.org/index.php?topic=23758.0 (https://forum.opnsense.org/index.php?topic=23758.0)

I'm seeing the issue as well.

Note: I don't think this post should be marked as [SOLVED] as uninstalling Sensei is just working around the issue, not solving the underlying problem.