apcupsd - FreeNAS as slave

[JohnnyBeGood]

Hello,

I have apcupsd on Ubuntu. On Win 10 I have apcupsd installed as slave it connects and works correctly.
When I enable it on FreeNAS using same settings as on Win 10 I get bellow errors. Obviously, there is no username/password setting on Win 10 but I even tried entering default, root and regular user with no luck.
I'm on FreeNAS v11. and I can ping 192.168.1.119 just fine.
Any help would be much appreciated.

TIA!

Code:

Dec  7 00:00:00 freenas newsyslog[28922]: logfile turned over due to size>200K
Dec  7 00:00:00 freenas syslog-ng[1840]: Configuration reload request received, reloading configuration;
Dec  7 00:00:00 freenas syslog-ng[1840]: Configuration reload finished;
Dec  7 03:45:00 freenas ZFS: vdev state changed, pool_guid=9178103228728611311 vdev_guid=4807192679957107605
Dec  8 00:00:00 freenas syslog-ng[1840]: Configuration reload request received, reloading configuration;
Dec  8 00:00:00 freenas syslog-ng[1840]: Configuration reload finished;
Dec  8 08:46:18 freenas root: /usr/local/etc/rc.d/nut: WARNING: /usr/local/etc/nut/ups.conf is not readable.
Dec  8 08:46:18 freenas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Dec  8 08:46:18 freenas upsmon[81911]: Set username on [FreeNASups@192.168.1.119:3551] failed: Write error: Broken pipe
Dec  8 08:46:23 freenas upsmon[81911]: Poll UPS [FreeNASups@192.168.1.119:3551] failed - Driver not connected
Dec  8 08:46:23 freenas upsmon[81911]: Communications with UPS FreeNASups@192.168.1.119:3551 lost
Dec  8 08:46:28 freenas upsmon[81911]: Set username on [FreeNASups@192.168.1.119:3551] failed: Write error: Broken pipe
Dec  8 08:46:33 freenas upsmon[81911]: Poll UPS [FreeNASups@192.168.1.119:3551] failed - Driver not connected
Dec  8 08:46:33 freenas upsmon[81911]: UPS FreeNASups@192.168.1.119:3551 is unavailable
undefinedundefinedDec  8 08:46:38 freenas upsmon[81911]: Set username on [FreeNASups@192.168.1.119:3551] failed: Write error: Broken pipe
Dec  8 08:46:43 freenas upsmon[81911]: Poll UPS [FreeNASups@192.168.1.119:3551] failed - Driver not connected
Dec  8 08:46:48 freenas upsmon[81911]: Set username on [FreeNASups@192.168.1.119:3551] failed: Write error: Broken pipe
Dec  8 08:46:53 freenas upsmon[81911]: Poll UPS [FreeNASups@192.168.1.119:3551] failed - Driver not connected

 

[dlavigne]

Please create a report at bugs.freenas.org and post the issue number here.

 

[rogerh]

This has been raised before. NUT can only work as a network slave to apcupsd with a special driver, which does not appear to work. Bug #9256 applies, which has been closed as outside the scope of FreeNAS.
Edit: my workaround is to run NUT on the relevant Linux server, but depending on your UPS this may not be as easy to use as apcupsd. Particularly, if your UPS does not accept a shutdown delay command NUT does not have as good a scheme for safely turning off the UPS at the end of the shutdown process.

 

[JohnnyBeGood]

This has been raised before. NUT can only work as a network slave to apcupsd with a special driver, which does not appear to work. Bug #9256 applies, which has been closed as outside the scope of FreeNAS.
Edit: my workaround is to run NUT on the relevant Linux server, but depending on your UPS this may not be as easy to use as apcupsd. Particularly, if your UPS does not accept a shutdown delay command NUT does not have as good a scheme for safely turning off the UPS at the end of the shutdown process.

Thanks for this info! I have apcupsd working with everything else windows and linux and I guess for FreeNAS I have to accept the fact that it does not work and never will.

 

[rogerh]

Thanks for this info! I have apcupsd working with everything else windows and linux and I guess for FreeNAS I have to accept the fact that it does not work and never will.

I did consider using an 'expect' script started in the apcupsd shutdown process on a linux server to log into FreeNAS via SSH and shut it down, but this is probably a bit clunky and unreliable.