Nut upsdev - Mar 2006 - Problem after reboot

Hello all,

Rebooted my server by mistake (don't ask...) - everything was working OK 
before the reboot, but after the reboot, NUT stopped working - so had a 
look and I found I couldn't track the exact problem - I'm quite stumped 
as there's nothing indicating that there's a problem, but it just 
doesn't work...

In a nutshell....

destiny:/usr/local/ups/bin# ./upsdrvctl start
Network UPS Tools - UPS driver controller 2.0.2
Network UPS Tools (version 2.0.2) - APC Smart protocol driver
         Driver version 1.99.7, command table version 2.0
getpwnam(nut): Success
Driver failed to start (exit status=1)
destiny:/usr/local/ups/bin#

I see a "Success" and then a "Failed" notice.  Which is
which?  And what
has failed?  And how?

I tried running the driver on its own:

destiny:/usr/local/ups/bin# ./apcsmart /dev/ttyS0 -x cable=940-0024C
Network UPS Tools (version 2.0.2) - APC Smart protocol driver
         Driver version 1.99.7, command table version 2.0
getpwnam(nut): Success
destiny:/usr/local/ups/bin#

which points to me there's a problem with upsdrvctl somehow.

Am running an APC Smart UPS V/S 1400 with a home made serial cable.  My 
ups.conf contains:

[ups]
         driver=apcsmart
         port=/dev/ttyS0
         cable=940-0024C
         desc="UPS"

and nothing else.

Any ideas how I can fix this problem?

Thanks very much for your help in advance!

Cheers - Piers

> Hello all,
>
> Rebooted my server by mistake (don't ask...) - everything was working
OK
> before the reboot, but after the reboot, NUT stopped working - so had a
> look and I found I couldn't track the exact problem - I'm quite
stumped
> as there's nothing indicating that there's a problem, but it just
> doesn't work...
>
> In a nutshell....
>
> destiny:/usr/local/ups/bin# ./upsdrvctl start
> Network UPS Tools - UPS driver controller 2.0.2
> Network UPS Tools (version 2.0.2) - APC Smart protocol driver
>          Driver version 1.99.7, command table version 2.0
> getpwnam(nut): Success
> Driver failed to start (exit status=1)
> destiny:/usr/local/ups/bin#
>
> I see a "Success" and then a "Failed" notice.  Which is
which?  And what
> has failed?  And how?
>
> I tried running the driver on its own:
>
> destiny:/usr/local/ups/bin# ./apcsmart /dev/ttyS0 -x cable=940-0024C
> Network UPS Tools (version 2.0.2) - APC Smart protocol driver
>          Driver version 1.99.7, command table version 2.0
> getpwnam(nut): Success
> destiny:/usr/local/ups/bin#
>
> which points to me there's a problem with upsdrvctl somehow.
No. The 'getpwnam(nut): Success' should not be displayed by the driver
as
far as I can tell. Throughout the sources, the word 'getpwnam' is only
used to display a fatal error when NUT isn't able to locate a userid, in
this case for 'nut'. Where this 'Success' is coming from, is
beyond me.

My guess would be that the user 'nut' doesn't exist. Try if adding
'-u
root' to the list of commandline parameters solves this (temporarily).
Sometimes 'id nut' may be helpful too.
> Am running an APC Smart UPS V/S 1400 with a home made serial cable.  My
> ups.conf contains:
>
> [ups]
>          driver=apcsmart
>          port=/dev/ttyS0
>          cable=940-0024C
>          desc="UPS"
>
> and nothing else.
>
> Any ideas how I can fix this problem?
>
> Thanks very much for your help in advance!
>
> Cheers - Piers
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
>
>