I've download again nut source today from "https://github.com/networkupstools/nut/tree/voltronic-driver"; and try compiliing the voltronic-driver. The drivers is working fine (ie computer is shutting down) except for the shutdown of the ups. I can shutdown the ups by sending the command "shutdown.return" but standard shutdown doesn't work.

upsmon -K return:
kill: No such process
UPS: myups@localhost (master) (power value 1)
Using power down flag file /etc/killpower
Power down flag is not set

Is there a way I can help nut developpers by send debug output or anything else?

Best regards,

-----Message d'origine----- From: James HORLEY
Sent: Thursday, August 01, 2013 4:40 PM
To: nut-upsuser list
Subject: Re: [Nut-upsuser] infosec e4

I'm pretty sure, I've install pkg-config, but I will check it monday after
my holliday.

This is my test steps:
- Shutting down nut-client (upsmon)
- Only nut-server (driver + upsd) is running
- upsmon.conf have been revert to normal shutdown, no upssched
- upsc myups return ups stats

then: upsmon -K -DDDDD, here is the output:
       kill: No such process
       UPS: myups@localhost (master) (power value 1)
       Using power down flag file /etc/killpower
       Power down flag is not set

Best regards,


-----Message d'origine----- From: Charles Lepple
Sent: Thursday, August 01, 2013 2:25 AM
To: James HORLEY
Cc: nut-upsuser list
Subject: Re: [Nut-upsuser] infosec e4

On Jul 31, 2013, at 9:07 AM, James HORLEY wrote:

I’m wondering if what I have done is good :
    # get the source from github on my computer
    # autogen.sh
    # name=nut
# ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man
--libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name
--with-statepath=/var/run/nut --with-altpidpath=/var/run/nut
--with-drvpath=/lib/nut --with-pidpath=/var/run/$name
--with-user=$name –with-group=$name --without-ssl

If these are the same parameters as are used to build the .deb, then that
should owrk.

There was an error :
    ./configure: line 7079: syntax error near unexpected token `CPPUNIT,'
    ./configure: line 7079: `PKG_CHECK_MODULES(CPPUNIT, cppunit,
    have_cppunit=yes, have_cppunit=no)'

Do you have pkg-config installed?

I put in commentary the line PKG_CHECK_MODULES(CPPUNIT, cppunit, have_cppunit=yes, have_cppunit=no) then
  # make
  # make install
I took the driver voltronic_ser then from my workstation put it in the server, change the ups.conf and try it. The command “upscmd –u admin myups shutdown.return” now work (shutting down server then ups). Unfortunately, when I do “shutdown –h +0”, the ups is never shut down. After a little research, it appears that the line “upsmon –K >/dev/null 2>&1” in ups-monitor always return 1 so the line “exec /etc/init.d/nut-server poweroff” is never execute.

For initial shutdown testing, I would recommend using a dummy load (such as
a lamp) and plug the server into another UPS or directly to line power.

Then, you can remove power from the UPS and run "upsmon -K" from the command
line (without redirection) to see why it is failing.

I’m ussing upssched in upsmon.conf, do I need to create the flag with my script before calling the shutdown –h +0? How (it’s supposed to be set automaticaly)? or maybe I’m missing something.

I don't recommend configuring upssched until basic shutdowns work.

Did I do the right thing by getting only the driver from my computer and put it on the server? Or should I do a package of the whole nut (binary, conf etc...)

This is not guaranteed to work, but when the version numbers are close
enough (2.6.4, 2.6.5, 2.7.1/master), it usually does work. The network
protocol is more stable than the upsd/driver interface.

--
Charles Lepple
clepple@gmail



_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to