[Solved] NUT not working with 2.2 RC (amd64)

wishyou

Hi!

I cant get NUT to work with 2.2 RC (amd64).
I just reinstalled (switched from i386) and restored backup, the config is identical, and so is the setup.
I had RC 2.2 i386 installed for a short while and then it was working.

Using local setup with an APC Smart 1400 over serial cable.

Package version: 2.7.2_6 pkg 2.0.4 (Listed as BETA)
I've tried reinstall, reconfig and all the listed ports without any luck.


[2.2-RC][root@xx.xx.net]/root: /usr/local/etc/rc.d/nut.sh start
starting apcsmart
Network UPS Tools - UPS driver controller 2.7.2
Network UPS Tools - APC Smart protocol driver 3.1 (2.7.2)
APC command table version 3.1
unable to detect an APC Smart protocol UPS on port /dev/ttyu0
check the cabling, port name or model name and try again
Driver failed to start (exit status=1)
apcsmart failed to start
[2.2-RC][root@xx.xx.net]/root:

Regards
Lch

hbc

I think it's not due to your upgrade to pfSense 2.2 but it's the package version itself.

I still run pfSense 2.1 and just updated package to current version and NUT does not run any more. Terminates with configuration error.

I compared the config files with the one on my other pfSense that still runs previous NUT version and they are identical in size by byte.

So it's not a configuration problem, at least not with configurations under /usr/local/etc/nut

wishyou

Well, I've figured this one out…

I was doing a full reinstall of 2.2 (to cope with my architecture switch problem), with a complete config.xml on an USB drive. An ingenious way to do it an it works like a charm. However with a full install with config.xml on USB, none of the packages are reinstalled. Installing NUT manually afterwards creates the problem with it not starting. Removing and reinstalling the package does not help, NUT still wont start.

However, after the full install I forced an upgrade with the same version, 2.2 Release AMD64, from an update image. This time the packages are reinstalled properly and NUT works perfectly again, with the old settings present in config.xml, without doing anything.

This process triggered a battery calibration on my SmartUPS 1400 over serial that I cannot explain, but that is another issue.
It works now.