[Nut-upsuser] Timer Daemon doesn't start

[Stefan Kuhn]

I did it as you said, but I still get only the following log information:
May 23 10:58:07 s-monitor1 upsmon[1674]: UPS usv1 at localhost on battery
May 23 10:58:07 s-monitor1 upssched[16710]: Executing command: ONBATT
May 23 10:58:07 s-monitor1 upssched-cmd: Calling upssched-cmd ONBATT

And now? There are still no information about errors or timers.

Greetings Stefan


-----Ursprüngliche Nachricht-----
Von: nut-upsuser-bounces+kuhn=papier.tu-darmstadt.de at lists.alioth.debian.org [mailto:nut-upsuser-bounces+kuhn=papier.tu-darmstadt.de at lists.alioth.debian.org] Im Auftrag von Roger Price
Gesendet: Mittwoch, 23. Mai 2012 10:36
An: nut-upsuser Mailing List
Betreff: Re: [Nut-upsuser] Timer Daemon doesn't start

On Wed, 23 May 2012, Stefan Kuhn wrote:
> I don't know where to look for the problem.

If you add the lines

  # Debugging: Log all calls to this script
  logger -t upssched-cmd Calling upssched-cmd $1

at the top of the script upssched-cmd, does any message get logged?

If YES: look in the script. If NO: start by looking in upssched.conf for the line

   CMDSCRIPT /<some>/<where>/upssched-cmd

Roger

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser