Nut upsuser - Nov 2010 - nut on pclos-2010.7

Greetings people;

The section of drakeconf that pclos uses has two problems.

First is several screens full of complaints about deprecated syntax in
"/etc/udev/rules.d/70-nut-usbups.rules" at each reboot.

So I pulled the current 2.5 svn trunk, then found I was missing quite a few 
build tools needed here that aren't used when building a kernel, currently 
running a 32 bit 2.6.36-PAE on a 2.1Ghz amd quad core phenom.

So I blindly installed autoconf, hoping to get the web pages autoreconf.

And now I am here, not fully grokking what I do next:
[root at coyote trunk]# autoreconf --install
configure.in:10: installing `./config.guess'
configure.in:10: installing `./config.sub'
configure.in:14: installing `./install-sh'
configure.in:14: installing `./missing'
clients/Makefile.am:23: Libtool library used but `LIBTOOL' is undefined
clients/Makefile.am:23:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
clients/Makefile.am:23:   to `configure.in' and run `aclocal' and
`autoconf'
again.
clients/Makefile.am:23:   If `AC_PROG_LIBTOOL' is in `configure.in',
make
sure
clients/Makefile.am:23:   its definition is in aclocal's search path.
clients/Makefile.am: installing `./depcomp'
common/Makefile.am:10: Libtool library used but `LIBTOOL' is undefined
common/Makefile.am:10:   The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
common/Makefile.am:10:   to `configure.in' and run `aclocal' and
`autoconf'
again.
common/Makefile.am:10:   If `AC_PROG_LIBTOOL' is in `configure.in', make
sure
common/Makefile.am:10:   its definition is in aclocal's search path.
autoreconf: automake failed with exit status: 1
[root at coyote trunk]# aclocal
[root at coyote trunk]# autoreconf --install
configure.in:83: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:287: error: possibly undefined macro: AC_DISABLE_STATIC
autoreconf: /usr/bin/autoconf failed with exit status: 1

I have NDI if m4 stuff is needed or even installed, so whats next?

Thanks muchly.


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Wasn't there something about a PASCAL programmer knowing the value of
everything and the Wirth of nothing?

Citeren Gene Heskett <gene.heskett op gmail.com>:
> I have NDI if m4 stuff is needed or even installed, so whats next?
Most likely, you don't have libtool. What does the output of

     libtool --version

show?

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)

On Friday, November 05, 2010 10:15:07 am Arjen de Korte did opine:
> Citeren Gene Heskett <gene.heskett at gmail.com>:
> > I have NDI if m4 stuff is needed or even installed, so whats next?
> 
> Most likely, you don't have libtool. What does the output of
> 
>      libtool --version
> 
> show?
> 
> Best regards, Arjen
command not found...  Doh!  Thanks.

So I installed it, then:

[root at coyote trunk]# autoreconf --install
libtoolize: `config.guess' exists: use `--force' to overwrite
libtoolize: `config.sub' exists: use `--force' to overwrite
[root at coyote trunk]# rm config.guess config.sub
rm: remove regular file `config.guess'? y
rm: remove regular file `config.sub'? y
[root at coyote trunk]# autoreconf --install
libtoolize: `ltmain.sh' exists: use `--force' to overwrite
[root at coyote trunk]# rm ltmain.sh
rm: remove regular file `ltmain.sh'? y
[root at coyote trunk]# autoreconf --install
libtoolize: `config.guess' exists: use `--force' to overwrite
libtoolize: `config.sub' exists: use `--force' to overwrite
[root at coyote trunk]# rm ltmain.sh
rm: remove regular file `ltmain.sh'? y
[root at coyote trunk]# rm config.guess config.sub
rm: remove regular file `config.guess'? y
rm: remove regular file `config.sub'? y
[root at coyote trunk]# autoreconf --install
[root at coyote trunk]# 

looks like I'm good to go for the build.

However, giving ./configure the --with-all option fails, no libgd exists on 
pclos.  I have a libgd2, and just installed some libgda3 libgda4 & devel 
stuffs for them, plus all the pluigins for libdga4.  But that also fails:

checking for tcpd.h... no
checking for library containing yp_get_default_domain... -lnsl
checking for library containing request_init... no
checking whether to enable libwrap (tcp-wrappers) support... no
checking for gd version via gdlib-config... none found
checking for gd include flags... 
checking for gd library flags... -L/usr/X11R6/lib -lgd -lpng -lz -ljpeg -
lfreetype -lm -lXpm -lX11
checking for gd.h... no
checking for gdfontmb.h... no
checking for library containing gdImagePng... no
configure: error: libgd not found, required for CGI build

So where do I go from here?

Many Thanks Arjen.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
* knghtbrd does the ET thing
<knghtbrd> anybody got a speak-n-spell?


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Accordion, n.:
	A bagpipe with pleats.

On Friday, November 05, 2010 02:07:50 pm Arjen de Korte did opine:
> Citeren Gene Heskett <gene.heskett at gmail.com>:
> > However, giving ./configure the --with-all option fails, no libgd
> > exists on pclos.  I have a libgd2, and just installed some libgda3
> > libgda4 & devel stuffs for them, plus all the pluigins for
libdga4.
> 
> You need 'libgd'. On my system, this is provided through the
following
> two packages:
> 
>      gd (provides the actual library)
>      gd-devel (header files for development only)
Which do not seem to be available for pclos.  Darn.  And neither are the 
snmp pieces. libusb-devel I just installed.  Unforch, that didn't get me 
the usb stuff. libusb is actually libusb1.0 here.
 
> So I guess you did not install the right packages.
> 
> > So where do I go from here?
> 
> First to 'docs/configure.txt' so that you can enable only the stuff
> that you want to build. Otherwise you'll probably need to install many
> more packages, since you'll be compiling all the bells-and-whistles
> that NUT offers. Most likely, you won't need that.
I used the --without option after the --with-all to bypass that which pclos 
doesn't have, and wound up with a final configure output of:

Configuration summary:
enable SSL development code: yes
enable libwrap (tcp-wrappers) support: yes
build CGI programs: no
build and install the development files: yes
build serial drivers: yes
build SNMP drivers: no
build USB drivers: yes
enable HAL support: yes
build neon based XML driver: yes
build Powerman PDU client driver: yes

So I should have enough tools to access this turkey.

Now, before I do the make, can I chown this whole tree to myself or does it 
have to be a root only utility?

I was hoping I could just give it a web page since I run a server here 
anyway for my own web pages, but probably not possible without the CGI 
stuff. That can be seen at
<http://gene.homelinux.net:85/gene> if you've half an hour to waste
looking
at what keeps this old fart out of the bars. ;-)

Thanks, Arjen

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Enzymes are things invented by biologists that explain things which
otherwise require harder thinking.
		-- Jerome Lettvin

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
COBOL:
	An exercise in Artificial Inelegance.

On Nov 5, 2010, at 2:42 PM, Gene Heskett wrote:
> Now, before I do the make, can I chown this whole tree to myself or  
> does it
> have to be a root only utility?
You should be able to build it as yourself, then the "make install"  
stage probably needs root privileges.

-- 
Charles Lepple

On Saturday, November 06, 2010 01:04:39 pm Gene Heskett did opine:
> On Saturday, November 06, 2010 11:57:11 am Charles Lepple did opine:
> > On Nov 5, 2010, at 2:42 PM, Gene Heskett wrote:
> > > libusb-devel I just installed.  Unforch, that didn't get me
> > > the usb stuff. libusb is actually libusb1.0 here.
> > 
> > If you do need USB support, check to see if your distribution has
> > libusb-compat or something similar. The 1.0 version of libusb has a
> > compatibility layer that lets programs like NUT use the 0.1 API with
> > the 1.0 library installed. Not all distributions package that up the
> > same way, though.
> 
> It turns out the dynamic version of the -devel stuff wasn't enough, I
> just installed the static versions, then chowned the whole trunk tree
> to me, and it built as me.  Synaptic has now removed the 2.4.1 rpms, so
> now a root make install...  And that seemed successful.  Now, I did
> have it working on mandriva back in the spring, and that drive hasn't
> been re-assigned, so if I can find all the stuff on that drive and move
> it, maybe it will work.  But first use synaptic to install the K
> interface.  Humm, that was a kde3 piece, and seems not to have made the
> trip to kde4.5.x yet, darn.
> 
> Anyway its installed, now to find the old configs.  Thanks Charles.
> 
> One thing that keeps biting me, this list has no List-Header:, so when I
> click on reply to mail-list, I get no To: line and have to copy paste
> the recipients, you and the list.  Is this intentional?

PS, progress of sorts:
I have followed along on the web page's install & configure, editing to
fix
changes in the syntax according to the warnings returned, untill I get to 
the upsd start(which has to be done as root), and its returning this:
[root at coyote etc]# /usr/local/ups/sbin/upsd
Network UPS Tools upsd 2.4.3-2672
/usr/local/ups/etc/upsd.conf is world readable
upsd.conf: invalid directive LISTEN: all
listening on localhost port 3493
getaddrinfo: Servname not supported for ai_socktype

Now I'd assume the chmod 0640 applies to everything, and that the whole 
REJECT line is a no-op now.

That now gets me this:
[root at coyote etc]# /usr/local/ups/sbin/upsd
Network UPS Tools upsd 2.4.3-2672
listening on localhost port 3493
getaddrinfo: Servname not supported for ai_socktype
[root at coyote etc]# /usr/local/ups/sbin/upsd -c stop
Network UPS Tools upsd 2.4.3-2672
fopen /var/state/ups/upsd.pid: No such file or directory

So obviously it is not running, however, when I used the web page sample 
'ACL' etc, it warned but ran ok (I think):

[root at coyote etc]# /usr/local/ups/sbin/upsd
Network UPS Tools upsd 2.4.3-2672
ACL in upsd.conf is no longer supported - switch to LISTEN
ACL in upsd.conf is no longer supported - switch to LISTEN
ACCEPT in upsd.conf is no longer supported - switch to LISTEN
REJECT in upsd.conf is no longer supported - switch to LISTEN
listening on 127.0.0.1 port 3493
listening on ::1 port 3493
Connected to UPS [coyotes-ups]: usbhid-ups-coyotes-ups

And:

[root at coyote etc]# /usr/local/ups/bin/upsc coyotes-ups at localhost
ups.status
OL CHRG

Then the whole list:

[root at coyote etc]# /usr/local/ups/bin/upsc coyotes-ups at localhost
battery.charge: 100
battery.charge.low: 30
battery.charge.warning: 30
battery.runtime: 120
battery.type: PbAc
battery.voltage: 27.8
battery.voltage.nominal: 24
device.mfr: Belkin 
device.model: Belkin UPS
device.serial:             
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/hidraw2
driver.version: 2.4.3-2672
driver.version.data: Belkin HID 0.12
driver.version.internal: 0.35
input.frequency: 60.0
input.frequency.nominal: 60
input.transfer.high: 140
input.transfer.high.max: 144
input.transfer.high.min: 140
input.transfer.low: 88
input.transfer.low.max: 88
input.transfer.low.min: 84
input.voltage: 125.9
input.voltage.nominal: 120
output.frequency: 60.0
output.voltage: 126.5
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.firmware: 1
ups.load: 30
ups.mfr: Belkin 
ups.model: Belkin UPS
ups.power.nominal: 1500
ups.productid: 0751
ups.serial:             
ups.status: OL CHRG
ups.test.result: Done and passed
ups.timer.shutdown: 0
ups.timer.start: 0
ups.type: offline
ups.vendorid: 050d

So, whats next, reload the web page in a few hours? Or just ignore the 
warnings? ;-)

Well, I thought I was fixing upsmon.conf correctly, but:
[root at coyote etc]# /usr/local/ups/sbin/upsmon
Network UPS Tools upsmon 2.4.3-2672
Unable to use old-style MONITOR line without a username
Convert it and add a username to upsd.users - see the documentation
Fatal error: unusable configuration

Sigh...

Thanks Charles (no CC this time, just the list)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some of the things that live the longest in peoples' memories never
really happened.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
You will have a long and unpleasant discussion with your supervisor.

On Nov 6, 2010, at 1:47 PM, Gene Heskett wrote:
> So, whats next, reload the web page in a few hours? Or just ignore the
> warnings? ;-)
Which web page does the Web Page Doctor need to visit? :-)

In your case, it sounds like upsd is listening on localhost, which  
should work unless the web server is separate from the NUT server.

-- 
Charles Lepple

On Sunday, November 07, 2010 11:00:17 am Gene Heskett did opine:
> On Saturday, November 06, 2010 06:39:36 pm Charles Lepple did opine:
> > On Nov 6, 2010, at 1:47 PM, Gene Heskett wrote:
> > > So, whats next, reload the web page in a few hours? Or just
ignore
> > > the warnings? ;-)
> > 
> > Which web page does the Web Page Doctor need to visit? :-)
> > 
> > In your case, it sounds like upsd is listening on localhost, which
> > should work unless the web server is separate from the NUT server.
> 
> It turned out that I wasn't fully grokking the web page, and once I had
> that figured out, it looks like its working.
> 
> I was following the recipe at
> <http://www.networkupstools.org/doc/2.2.0/INSTALL.html>
> and got confused a bit when editing the upsmon.conf file.  Looking at
> the example got me squared away after reading it the 3rd or so time.
> 
> The error message didn't point to the error, claiming the username was
> wrong, when what I had actually done was to leave the "master"
off the
> end of the string.  Dumb. :(
The continuing saga of making nut work.  It seems no matter what I do, I 
cannot seem to get a passwordless execution of the daemon in my rc.local 
file which execs before anyone is logged in.  I tried syntax that I use to 
start fetchmail, but no permission is the order of the day.  I ran into 
that rebooting because kde was updated to 4.5.3 this morning.

Does anyone have a linux nut starter/stopper that can be put in 
/etc/init.d, and linked to the various runlevels rcx.d's?


Thanks all;

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
San Francisco isn't what it used to be, and it never was.
		-- Herb Caen

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If you are too busy to read, then you are too busy.