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
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)'
I put in commentary the line PKG_CHECK_MODULES(CPPUNIT, cppunit,
have_cppunit=yes, have_cppunit=no) then # make # make installI 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.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.
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...)
Best regards,
From: hyouko at gmail.com
Sent: Monday, July 29, 2013 1:34 AM
To: James HORLEY
Subject: Re: [Nut-upsuser] infosec e4
You could try voltronic driver
https://github.com/networkupstools/nut/tree/voltronic-driver
/dan
2013/7/29 James HORLEY <farahei14 at mail.pf>
Hi,
Sorry for my poor english but it isn?t my native language.
I?m testing an infosec E4 with nut-2.6.4-2.3 on Proxmox ve 3.0 (based on debian
wheezy). The drivers that match this ups, is blazer_usb.
Btw, I have try nut-2.6.5 with unstable repository from wheezy, but it still
doesn?t fully work.
I can shutdown my computer when battery is low, but unfortunately I can?t
shutdown ups.
Like said on the man blazer :
?Some UPS commands aren?t supported by all models. In most cases, the
driver will send a message to the system log when the user tries to execute an
unsupported command?
I?m wondering if there?s a way I can post some data to help make this ups more
compatible with NUT.
There?s a software advised by the constructor that work on linux
(http://www.power-software-download.com/viewpower.html), unfortunately it?s
heavy (tomcat and java) and I don?t find it as flexible as NUT.
Best regards,
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130731/ecb46ef9/attachment.html>
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-sslIf 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 at gmail
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 at 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 at gmail