OPNsense Forum

Archive => 18.7 Legacy Series => Topic started by: nfugal on August 30, 2018, 05:12:57 am

Title: configd failure to start
Post by: nfugal on August 30, 2018, 05:12:57 am
I've poked around and not found anyone with the same problem.

If the answer is already here, please let me know.

I am running version 18.7.1_3 (freshly installed, not an upgrade). I can't get configd to start. I get the following error message:

nfugal@bifrost:~ % service configd status
/usr/local/etc/rc.d/configd: WARNING: cannot read shebang line from /usr/local/opnsense/service/configd.py
configd is not running.


Starting via the WebUI doesn't work either.

I'm happy to post logs or share whatever other info is helpful.

Thanks!
Title: Re: configd failure to start
Post by: mimugmail on August 30, 2018, 09:04:14 am
/var/log/configd.log please
Title: Re: configd failure to start
Post by: nfugal on September 03, 2018, 12:25:02 pm
Here you go. https://drive.google.com/open?id=1suzyvQQZWc47TOVBfbut2uw-5zdZ0ds-

I'm not sure what is going on with the end of the file.

I see that there are a lot of messages regarding NUT in here. I'll try disabling that to see if it makes a difference.

At the very least it should help the log be easier to parse.
Title: Re: configd failure to start
Post by: nfugal on September 03, 2018, 12:59:18 pm
I just noticed that that log file doesn't have anything very recent in it.

I tried clearing it to see if the wonkiness at the end was stopping it from updating, and it has stayed blank thus far.
Title: Re: configd failure to start
Post by: nfugal on September 03, 2018, 01:46:19 pm
Some poking around with a coworker points to a permissions issue.

The permissions were

-rwx------  1 root  wheel   6.6K Aug 29 20:51 /usr/local/opnsense/service/configd.py

After adding permissions for group as well the service can start.

Not sure how/why the permissions would have changed.

Title: Re: configd failure to start
Post by: mimugmail on September 03, 2018, 01:49:28 pm
Permissions are ok, do you now see something in the logs?

You have to "clog /var/log/configd.log" .. no cat or tail or whatever ...
Title: Re: configd failure to start
Post by: nfugal on September 03, 2018, 02:11:07 pm
Here is the output of clog on configd.log:

root@bifrost:/home/nfugal # clog /var/log/configd.log
Segmentation fault (core dumped)


If I check the file with nano or vi, it appears empty.  ls also reports the file as 0 bytes:

root@bifrost:/home/nfugal # ls -alh /var/log/
total 133272
drwxr-xr-x   9 root        wheel        1.5K Sep  3 05:36 .
drwxr-xr-x  32 root        wheel        512B Aug 23 16:43 ..
-rw-------   1 root        wheel          0B Sep  3 04:32 configd.log