Errorconfigct error in configd communication Traceback (most recent call last)

Started by mpccert, January 30, 2024, 04:50:04 PM

Previous topic - Next topic
hello everyone,

i've been seeing Error logs on my opnsense installation and my outbound connectivity slows down. Below are the logs and OPNSense versions.

Hope someone can enlighten me on this.

Thank you,

Mike

Logs:
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   
2024-01-30T22:04:01   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   
2024-01-30T22:02:00   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   
2024-01-30T21:04:00   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   
2024-01-30T21:02:00   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

OPNSense versions Installed:
OPNsense 23.7.8_1-amd64
FreeBSD 13.2-RELEASE-p5
OpenSSL 1.1.1w 11 Sep 2023

No replies right? I'm seeing same errors in my log file and really curious if anyone is seeing the same and/or knows the cause

Mine was resolved by removing Zenarmor Free that time. I'm now on a Zenarmor business subscription and I'm no longer seeing that error since then. You might be having a plugins causing the error.

Mike

Quote from: scrensen on July 18, 2024, 09:21:07 PM
No replies right? I'm seeing same errors in my log file and really curious if anyone is seeing the same and/or knows the cause