error in configd communication Traceback

[dstr]

2021-03-25T14:00:15   configctl[98023]   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

After that the interface configuration and only the interface configuration got defaulted. ipsec and openvpn still complete and active.

Its the third time in a row now and only happens on 1 out of 3, other 2 are fine.

Is it software related and could maybe be fixed with an complete factory reset?


hardware used:
Model Name   JBC390F541AA-1900-B
Part Number   HBJC390F541AA19B
Motherboard Specification
CPU   Intel® Celeron J1900, 2.0GHz Quad-Core SoC, 10W, Bay Trail
Memory   1 * 204-pin DDR3L-1333 SO-DIMM up to 8GB (1.35V required)
Graphics   Intel HD Graphics
LAN   10 * Intel i211AT Gigabit LAN
Audio   Realtek ALC662 HD Audio
Storage   1 * 2.5" SATA2 3Gb/s drive bay for HDD or SSD
1 * mSATA/mini-PCI Express shared slot (Full-size)
Wireless / Mini-PCIE Slot   1 * Mini-PCI Express slot (Full-size)
USB / SIM   Embedded 1 * USB 3.0 and 3 * USB 2.0, 1 * SIM card socket

[dcol]

I would like to restart this thread. What causes this error? It has just started and disabled my firewall three times yesterday. Had to reboot to get firewall to function again.
I do not have netflow enabled or Sensei installed. Using 21.7.3, Just updated to 27.7.3_1

2021-09-25T11:22:00   configctl[25255]   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

Please help me track down this error.
Thanks

[Greelan]

I’ve had this previously, but it was Sensei: https://forum.opnsense.org/index.php?topic=23120

Any other errors in the logs that might indicate the cause?

[dinguz]

I have had this as well (always 2 messages exactly at 3:00am), and eventually found out it was related to Sensei. Probably some internally scheduled housekeeping task, as I don't have cron jobs running at that time.

What fixed it in my case was:
- backup Sensei config
- uninstall Sensei completely
- reinstall Sensei
- restore config, but don't do a full restore, only restore 'policy and rules'

[dcol]

I do not have Sensei installed on this firewall, but I haven't seen this issue since I updated to 21.7.3_1 from 21.7.3
The logs showed no other useful info.

What I would like to know is what does this error mean? Then maybe I can track it down if it happens again.