Two reboot commands needed to reboot opnsense (WebUI)

[iamperson347]

Hi All,

I'm running into an odd issue where my install of opnsense will not reboot through the WebUI the first time. The dialog pops up that the reboot is happening, and the "shutdown chime" plays on the physical machine, but after a few seconds I get sent back to the dashboard. If I go to the reboot screen and select to reboot again, the system then properly reboots.

This also appears to affect reboots required/triggered by upgrades.

However, using "reboot" command via ssh shell session works fine.

I was trying to look through logs to see if I could determine what is going on but the system log doesn't really show anything at the time the issue occurs. The configd.log says "rebooting system" (or something to that effect), but that is it.

Any ideas on where else I can look to determine what might be holding things up?

[iamperson347]

It seems this may be related to ntopng and redis. When I manually ran /usr/local/etc/rc.reboot, it appears redis gets shutdown before ntopng. This causes ntopng to hang while shutting down.

I'll have to look into changing the order to see if that will fix the issue. I tried modifying the ntopng rc script to REQUIRE redis, but that didn't seem to help.

[franco]

It's been reported previously. We would suggest taking this to ntopng since we can't do much about it.


Cheers,
Franco

[iamperson347]

It looks like someone reported it. We will see what ntopng devs have to say.

https://github.com/ntop/ntopng/issues/5127

Does the opnsense plugins build process generate the rc scripts, or does it come from the upstream package?

[chemlud]

Hmmm, will it take longer than 2 hours before "Closed" because not an official package installed and apparently related to BSD script? ;-)

[iamperson347]

It's been reported previously. We would suggest taking this to ntopng since we can't do much about it.


Cheers,
Franco

Hi Franco,

Is it possible that something like this would help?

https://github.com/iamperson347/core/commit/cb75a0003389d6181403c0d10ef425423b6ce12f

I tested it on my machine and it seems to fix the issue. I don't know if this would have any ill effects, but shutting things down in the reverse of rcorder seems logical when the rc.freebsd file is called with "stop."

What do you think?

[franco]

Yes, looks promising at first glance. Can you open an official PR on GitHub to discuss?


Thanks,
Franco

[tswalker]

hi, i made the report over  on ntopng about it... not sure they are able to address this.  regardless, i'm interested in a workaround too and though perhaps a service ordering for shutdown might work as ntopng has that dependency on redis.

i have no clue how to make that happen though

[iamperson347]

I think this issue should be resolved for opnsense via this commit (not in a released version yet).

https://github.com/opnsense/core/commit/7316071974b790b6262b65465649df61aa55c500

[franco]

Yep, to apply from console:

# opnsense-patch 7316071


Cheers,
Franco

[tswalker]

Yep, to apply from console:

# opnsense-patch 7316071


Cheers,
Franco

confirmed as resolved.  i closed the ntopng issue.  thanks you all!!!

[franco]

Ok, I'll add it to 21.1.5 for next week. :)


Thanks,
Franco