Re: [Nut-upsuser] upsdrvctl doesn't seem to start with init.d

2010-12-17 Thread Zachary LaCelle
 2010/12/16 Zach La Celle lace...@roboticresearch.com

 I can run upsdrvctl start and it starts fine.  On computer boot,
 however,
 it doesn't start properly.

 I'm trying to find the logs which would give more detail, but I'm not
 sure
 where they are.  I see no logs in /etc/nut or /var/log.


 try running directly your driver in debug mode (as root), ie:
 $ /path/to/apcsmart -DDD -a upsname

 and send us back the output.

 have you also verified device privileges? (ie ls -l /dev/ttyS0 or
 something like that)

 cheers,
 Arnaud
 --
 Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
 Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
 Debian Developer - http://www.debian.org
 Free Software Developer - http://arnaud.quette.free.fr/


Permission settings were as follows:
ups.conf, upsd.conf, upsd.users, upsmon.conf, upssched.conf: 640, root.nut
hosts.conf, nut.conf, upsset.conf, upsstats.conf, upsstats-single.html:
644, root.root

I tried changing them all to root.nut and 644.

It's hard to know what works and what doesn't, because when I start the
process manually it seems to work fine.


The output of /lib/nut/apcsmart -DDD -a rack3ups when run as root is:
Network UPS Tools - APC Smart protocol driver 2.03 (2.4.3)
APC command table version 2.1
   0.00 debug level is '3'
   0.046913 Attempting firmware lookup
   0.133912 Not found in table - trying normal method
   0.133922 APC - Attempting to find command set
   0.705908 APC - Parsing out command set
   0.705925 UPS supports variable [ups.model]
   0.849914 UPS supports command [load.on]
   0.849925 UPS supports variable [input.quality]
   0.893910 UPS supports variable [battery.packs]
   0.949928 UPS supports command [test.panel.start]
   0.949943 UPS supports variable [battery.voltage]
   1.025917 UPS supports variable [ups.temperature]
   1.097916 UPS supports command [calibrate.start]
   1.097927 UPS supports command [calibrate.stop]
   1.097936 UPS supports variable [ups.test.interval]
   1.149916 UPS supports variable [input.frequency]
   1.221911 UPS supports variable [input.transfer.reason]
   1.257912 UPS supports command [shutdown.stayoff]
   1.257922 UPS supports variable [input.voltage]
   1.333914 UPS supports variable [input.voltage.maximum]
   1.405916 UPS supports variable [input.voltage.minimum]
   1.481917 UPS supports variable [output.voltage]
   1.559161 UPS supports variable [ups.load]
   1.629912 UPS supports command [shutdown.return]
   1.629923 UPS supports command [test.failure.start]
   1.629933 protocol_verify: 0x56 [V] unrecognized
   1.629940 UPS supports command [test.battery.start]
   1.629947 UPS supports command [test.battery.stop]
   1.629955 UPS supports variable [ups.test.result]
   1.673913 UPS supports command [load.off]
   1.673925 UPS supports variable [ups.firmware]
   1.757914 UPS supports variable [ups.id]
   1.849918 UPS supports variable [battery.charge.restart]
   1.890663 UPS supports variable [battery.charge]
   1.965911 UPS supports variable [battery.voltage.nominal]
   2.013911 UPS supports variable [battery.runtime]
   2.089915 UPS supports variable [battery.alarm.threshold]
   2.121912 UPS supports variable [input.transfer.low]
   2.173914 UPS supports variable [ups.mfr.date]
   2.265911 UPS supports variable [ups.serial]
   2.405916 UPS supports variable [output.voltage.nominal]
   2.457913 UPS supports variable [ups.delay.shutdown]
   2.505911 UPS supports variable [battery.runtime.low]
   2.549915 UPS supports variable [ups.delay.start]
   2.597914 UPS supports variable [input.sensitivity]
   2.633914 UPS supports variable [input.transfer.high]
   2.681913 UPS supports variable [battery.date]
   2.773917 APC - About to get capabilities string
   4.913922 Supported capability: 75 (D) - input.transfer.high
   4.914006 Supported capability: 6c (D) - input.transfer.low
   4.914061 Supported capability: 65 (4) - battery.charge.restart
   4.914090 Supported capability: 6f (D) - output.voltage.nominal
   4.914105 Supported capability: 73 (4) - input.sensitivity
   4.914125 Supported capability: 71 (4) - battery.runtime.low
   4.914147 Supported capability: 70 (4) - ups.delay.shutdown
   4.914166 Supported capability: 6b (4) - battery.alarm.threshold
   4.914184 Supported capability: 72 (4) - ups.delay.start
   4.914202 Supported capability: 45 (4) - ups.test.interval
   4.914219 APC - UPS capabilities determined
Detected SMART-UPS 2200 [YS0234212126] on /dev/ttyUSB0
   4.957916 update_info_all: starting
   7.027656 update_info_all: done
   7.027694 dstate_init: sock /var/run/nut/apcsmart-rack3ups open on fd 5
   7.067659 update_info_normal: starting
   7.935414 update_info_normal: done
   8.877741 new connection on 

Re: [Nut-upsuser] upsdrvctl doesn't seem to start with init.d

2010-12-17 Thread Arnaud Quette
2010/12/17 Zachary LaCelle lace...@roboticresearch.com

  2010/12/16 Zach La Celle lace...@roboticresearch.com
 
  I can run upsdrvctl start and it starts fine.  On computer boot,
  however,
  it doesn't start properly.
 
  I'm trying to find the logs which would give more detail, but I'm not
  sure
  where they are.  I see no logs in /etc/nut or /var/log.
 
 
  try running directly your driver in debug mode (as root), ie:
  $ /path/to/apcsmart -DDD -a upsname
 
  and send us back the output.
 
  have you also verified device privileges? (ie ls -l /dev/ttyS0 or
  something like that)
 
  cheers,
  Arnaud
  --
  Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
  Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
  Debian Developer - http://www.debian.org
  Free Software Developer - http://arnaud.quette.free.fr/
 

 Permission settings were as follows:
 ups.conf, upsd.conf, upsd.users, upsmon.conf, upssched.conf: 640, root.nut
 hosts.conf, nut.conf, upsset.conf, upsstats.conf, upsstats-single.html:
 644, root.root

 I tried changing them all to root.nut and 644.


have you also verified *device* privileges? (ie ls -l /dev/ttyS0 or
something like that)
and how are you setting these (ie using udev, rc.local, ...)


 It's hard to know what works and what doesn't, because when I start the
 process manually it seems to work fine.


if the boot time problem still occurs, check around device privileges, udev
startup (before NUT) if used to set *device* privileges.

cheers
Arno
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] upsdrvctl doesn't seem to start with init.d

2010-12-17 Thread Arjen de Korte

Citeren Zachary LaCelle lace...@roboticresearch.com:


It's hard to know what works and what doesn't, because when I start the
process manually it seems to work fine.


Have a look at this bug report and check if this might be the problem:

https://bugzilla.redhat.com/show_bug.cgi?id=544121

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


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


[Nut-upsuser] upsdrvctl doesn't seem to start with init.d

2010-12-16 Thread Zach La Celle
I can run upsdrvctl start and it starts fine.  On computer boot, 
however, it doesn't start properly.


I'm trying to find the logs which would give more detail, but I'm not 
sure where they are.  I see no logs in /etc/nut or /var/log.


I don't know if this helps, but it looks like there's a problem with the 
PID file generation: when I run upsdrvctl stop I get an error about a 
missing PID file.


My UPS driver is the apcsmart driver.

Thank you for your help.

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


Re: [Nut-upsuser] upsdrvctl doesn't seem to start with init.d

2010-12-16 Thread Arnaud Quette
2010/12/16 Zach La Celle lace...@roboticresearch.com

 I can run upsdrvctl start and it starts fine.  On computer boot, however,
 it doesn't start properly.

 I'm trying to find the logs which would give more detail, but I'm not sure
 where they are.  I see no logs in /etc/nut or /var/log.


try running directly your driver in debug mode (as root), ie:
$ /path/to/apcsmart -DDD -a upsname

and send us back the output.

have you also verified device privileges? (ie ls -l /dev/ttyS0 or
something like that)

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser