I'm trying to use a Nas4Free storage system. This same hardware worked fine on Freenas 0.7.2. O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. UPS is an APC Back UPS RS 800. USB interface. Driver : usbhid-ups Port: auto my NAS is communicating with the UPS, but in testing power failures, I'm not getting the shutdown to be handled properly. When I pull the AC plug on the UPS, the NAS recognizes that event, but doesn't send out the email and doesn't start the shutdown sequence even though the 30 sec time limit has passed. The log shows errors. I've posted them below. The restoring of power is also recognized by the NAS. Jul 14 06:14:41 nas4free upsmon[1813]: UPS Back-UPS-RS-800 at localhost on battery Jul 14 06:14:42 nas4free upssched[2334]: read confirmation got [ERR UNKNOWN own" "30"] Jul 14 06:14:43 nas4free last message repeated 24 times Jul 14 06:14:43 nas4free upssched[2334]: Unable to connect to daemon and unable to start daemon Jul 14 06:17:01 nas4free upsmon[1813]: UPS Back-UPS-RS-800 at localhost on line power Jul 14 06:17:01 nas4free upssched-cmd: UPS Back-UPS-RS-800 at localhost - Running on line power. Shutdown cancelled. Jul 14 06:17:03 nas4free msmtp: host=smtp.gmail.com tls=on auth=on user=xyz at gmail.com <mailto:user=xyz at gmail.com> from=xyz at gmail.com <mailto:from=xyz at gmail.com> recipients=xyz at gmail.com <mailto:recipients=xyz at gmail.com> mailsize=244 smtpstatus=250 smtpmsg='250 2.0.0 OK 1342261023 y66sm18956640yhi.10' exitcode=EX_OK more information in the daemon log file: Jul 14 08:35:17 nas4free upsmon[6990]: UPS ups at localhost on battery Jul 14 08:35:17 nas4free upssched[7010]: Timer daemon started Jul 14 08:35:17 nas4free upssched[7010]: Unknown command on socket: Jul 14 08:35:17 nas4free upssched[7010]: arg 0: 30START Jul 14 08:35:17 nas4free upssched[7010]: arg 1: shutdown Jul 14 08:35:17 nas4free upssched[7010]: arg 2: 30 Jul 14 08:35:17 nas4free upssched[7009]: read confirmation got [ERR UNKNOWN own" "30"] Jim A -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120723/7c4ed87c/attachment.html>
FredericBohe at Eaton.com
2012-Jul-24 07:18 UTC
[Nut-upsuser] getting nut 2.6.4 working in Nas4Free
Hello Jim, Can you send your configuration files please (hide your password). Regards, Fred -- Eaton Opensource Team - http://opensource.eaton.com ________________________________ ________________________________ ________________________________ From: nut-upsuser-bounces+fredericbohe=eaton.com at lists.alioth.debian.org [nut-upsuser-bounces+fredericbohe=eaton.com at lists.alioth.debian.org] on behalf of Jim Abernathy [jfabernathy at gmail.com] Sent: Monday, July 23, 2012 9:51 PM To: nut-upsuser at lists.alioth.debian.org Subject: [Nut-upsuser] getting nut 2.6.4 working in Nas4Free I'm trying to use a Nas4Free storage system. This same hardware worked fine on Freenas 0.7.2. O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. UPS is an APC Back UPS RS 800. USB interface. Driver : usbhid-ups Port: auto my NAS is communicating with the UPS, but in testing power failures, I'm not getting the shutdown to be handled properly. When I pull the AC plug on the UPS, the NAS recognizes that event, but doesn't send out the email and doesn't start the shutdown sequence even though the 30 sec time limit has passed. The log shows errors. I've posted them below. The restoring of power is also recognized by the NAS. Jul 14 06:14:41 nas4free upsmon[1813]: UPS Back-UPS-RS-800 at localhost on battery Jul 14 06:14:42 nas4free upssched[2334]: read confirmation got [ERR UNKNOWN own" "30"] Jul 14 06:14:43 nas4free last message repeated 24 times Jul 14 06:14:43 nas4free upssched[2334]: Unable to connect to daemon and unable to start daemon Jul 14 06:17:01 nas4free upsmon[1813]: UPS Back-UPS-RS-800 at localhost on line power Jul 14 06:17:01 nas4free upssched-cmd: UPS Back-UPS-RS-800 at localhost - Running on line power. Shutdown cancelled. Jul 14 06:17:03 nas4free msmtp: host=smtp.gmail.com tls=on auth=on user=xyz at gmail.com<mailto:user=xyz at gmail.com> from=xyz at gmail.com<mailto:from=xyz at gmail.com> recipients=xyz at gmail.com<mailto:recipients=xyz at gmail.com> mailsize=244 smtpstatus=250 smtpmsg='250 2.0.0 OK 1342261023 y66sm18956640yhi.10' exitcode=EX_OK more information in the daemon log file: Jul 14 08:35:17 nas4free upsmon[6990]: UPS ups at localhost on battery Jul 14 08:35:17 nas4free upssched[7010]: Timer daemon started Jul 14 08:35:17 nas4free upssched[7010]: Unknown command on socket: Jul 14 08:35:17 nas4free upssched[7010]: arg 0: 30START Jul 14 08:35:17 nas4free upssched[7010]: arg 1: shutdown Jul 14 08:35:17 nas4free upssched[7010]: arg 2: 30 Jul 14 08:35:17 nas4free upssched[7009]: read confirmation got [ERR UNKNOWN own" "30"] Jim A -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120724/2a36db1e/attachment.html>
Hi Jim 2012/7/23 Jim Abernathy <jfabernathy at gmail.com>> I'm trying to use a Nas4Free storage system. This same hardware worked > fine on Freenas 0.7.2. > > O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. > > UPS is an APC Back UPS RS 800. USB interface. > > Driver : usbhid-ups > Port: auto > > my NAS is communicating with the UPS, but in testing power failures, I'm > not getting the shutdown to be handled properly. > > When I pull the AC plug on the UPS, the NAS recognizes that event, but > doesn't send out the email and doesn't start the shutdown sequence even > though the 30 sec time limit has passed. The log shows errors. I've posted > them below. The restoring of power is also recognized by the NAS. > > Jul 14 06:14:41 nas4free upsmon[1813]: UPS Back-UPS-RS-800 at localhost on > battery > > Jul 14 06:14:42 nas4free upssched[2334]: read confirmation got [ERR > UNKNOWN own" "30"] > Jul 14 06:14:43 nas4free last message repeated 24 times > Jul 14 06:14:43 nas4free upssched[2334]: Unable to connect to daemon and > unable to start daemon > (...) >you're sadly running into a regression, that happened in 2.6.4. sorry! 2.6.5 is scheduled, but I won't commit on this week (I'm enjoying holidays with my kids). so, for now, either downgrade nut to 2.6.3, or apply the following patch to the source code: http://trac.networkupstools.org/projects/nut/changeset/3670 cheers, Arno -- Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120724/96254549/attachment.html>