[SOLVED] Unable to check for Updates

[StP]

Hi!

I have two similar Deciso firewall boxes (OPNsense A10 Quad Core SSD rack OPN20077R) with this installed:

  OPNsense 16.1.5-amd64
  FreeBSD 10.2-RELEASE-p12
  OpenSSL 1.0.2g 1 Mar 2016

When I "Click to check for Updates" on the dashboard I get this on one of the boxes:

  Warning:
  stream_socket_client(): unable to connect to unix:///var/run/configd.socket (Connection refused) in
  /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php on line 93 Connection Error
  Click to retry

Don't know what to do. Retry doesn't help.
The other box is working fine and shows one available update.

Any help welcome...

Best regards
  Stefan

[franco]

Hi Stefan,

Please restart "configd" from the service diagnostics page.

We're investigating this problem at the moment, but it hasn't brought up anything conclusive yet.


Cheers,
Franco

[StP]

Hey Franco,

that did it. Thanks!

Regards
  Stefan

[StP]

I have submitted the related report via the web interface.

Stefan

[franco]

Thanks very much.

[themelon]

I also am unable to check for updates.  I don't get that error though, in the lobby it just tells me my system is up to date but I know it is at 16.1.

In the System>Firmware page all 4 tabs are blank and fetch updates does nothing.

When I try to update from the console I get:

Child process pid=18654 terminated abnormally: Seg fault.

Under Services>Diagnostics all I have are dnsmasq and ntpd.  Any ideas?

[franco]

16.1 did not have configd in the Services Diagnostics. You can, however, drop to the console and issue:

# service configd restart

What kind of hardware is this? The segfault may hint to smaller/older embedded hardware?


Cheers,
Franco

[themelon]

Well, configd was running.  I stopped and restarted it, same thing.

It's running in ESXi 6 on a Xeon X5650, VMXNET3 NIC's, etc.  It seems to pass traffic OK.  Right now it is just a test machine with 3 interfaces on different VLAN's.

I'll install it here a bit later on physical hardware with e1000e NIC's just for giggles.

[franco]

It could also be DNS simply not being properly configured on the box itself.

But in your case, upon rereading, it sounds like the installation is corrupted and the FreeBSD package tool refuses operation. What are your VM parameters in terms of disk space and RAM?

Did you try the cd installer config import->exit -> live cd feature to see if that brings up firmware updates?

[Tikimotel]

Ever since the last update from 16.1.5 to 16.1.6, I too have the backend line 93 error, but only after a reboot of the physical machine.

Code: [Select]

stream_socket_client(): unable to connect to unix:///var/run/configd.socket (Connection refused) in
  /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php on line 93 Connection Error
Then the dashboard is reporting a "crash" and you can report it.
The only thing that is not started after the boot-up has finished is the SSHD service.
But once that service is started manually everything is fine.

It's only on boot-up that this error occurs, that's before the "starting..." of all the services like NTP / DHCPD etc.

I see no difference in rebooting between using DNSmasq or Unbound as my DNS service.

Code: [Select]

[15-Mar-2016 20:05:15 Europe/Amsterdam] PHP Warning:  stream_socket_client(): unable to connect to unix:///var/run/configd.socket (Connection refused) in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php on line 93
[15-Mar-2016 20:05:15 Europe/Amsterdam] PHP Warning:  stream_socket_client(): unable to connect to unix:///var/run/configd.socket (Connection refused) in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php on line 93


[themelon]

Thanks Franco, that did the trick so I reinstalled.  Now it is happily updating.

I appreciate it.

[franco]

Tikimotel, we are removing more oddities from our code with 16.1.7 today, although we do target 16.1.8 for more fixes and also want to issue new images by then. Please let us know if 16.1.7 works better.

[franco]

Is everyone seeing this using the SSH service?