pfSense » pfSense Packages

Since updating NUT to 2.6.5_1 pkg/2.0.4, I'm finding that NUT won't start on a pfSense reboot. Pressing a "restart service" button via the services page won't start NUT nor will the following code:
---
require_once("service-utils.inc");

if (is_service_enabled('nut') && !is_service_running('nut')) {
start_service('nut');
}
---

The NUT status panel will indicate that "nut is enabled but the service is not running" (wording paraphrased from memory).

In order to get NUT to run, again, I need to save the settings (no changes, just resave 'em).

To make matters worse, restarting various other services (e.g., an OpenVPN server) will kill NUT and it won't restart.

Watching things, I can see that a service "stop" is issued for NUT ... and then it's done! Seems that the only way to restart NUT is to save the NUT settings.

This all started when I updated to pfSense 2.1.5 and inherited the current NUT package version. Previously was running pfSense 2.1.4 and (IIRC) a slightly earlier version of the NUT package.

I'm willing to troubleshoot this issue (I done the basics like reboot and reinstalled the package), but could use a more advanced "getting started" pointer (yes, I see the irony of that).

FYI, when they're all running, I have the following services:
---
apinger
avahi
bsnmpd
dhcpd
dnsmasq
ntpd
nut
openvpn
openvpn
openvpn
openvpn
openvpn
racoon
---