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

[Arnaud Quette]

2010/12/17 Zachary LaCelle <lacelle at roboticresearch.com>

> > 2010/12/16 Zach La Celle <lacelle at 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 R&D - 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101217/ae8cf30c/attachment.htm>