Nut upsuser - Apr 2015 - upssched setup

Roger,
I did and it didnt work.
Hence why I was trying to run just the shell script manually. I am not sure if
this works though with the timer defined in it?
Cheers,
James

Date: Mon, 27 Apr 2015 15:03:44 +0200
From: roger at rogerprice.org
To: nut-upsuser at lists.alioth.debian.org
Subject: Re: [Nut-upsuser] upssched setup

On Mon, 27 Apr 2015, James Hammond wrote:
 
> I am unable to get upssched working correctly as my UPS calls low 
> battery too late and there is no way to change it. I am running Nut 
> 2.7.3 on Ubuntu 14.04 I have made this script, called 
> /sbin/upssched-cmd.sh
> 
> #!/bin/sh
>  case $1 in
>    onbatt)
>      /sbin/upsmon -c fsd;;
>    *)
>      echo "shutdown implemented";;
>  esac
 
Hi, Just wondering, do you have a line in upssched.conf which specifies 
CMDSCRIPT /sbin/upssched-cmd.sh ?
 
Roger

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150427/84198d54/attachment.html>

On Mon, 27 Apr 2015, James Hammond wrote:
> Roger, I did and it didnt work.
Aha!, what does your upssched.conf look like? If you add the lines:

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

to your /sbin/upssched-cmd.sh , what is reported if anything when it 
doesn't work?  Cheers, Roger

Hi Roger,
I get:
Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on batteryApr 27 20:50:05 unifi
upssched[2688]: Timer daemon startedApr 27 20:50:06 unifi upssched[2688]: New
timer: onbatt (20 seconds)Apr 27 20:50:26 unifi upssched[2688]: Event: onbattApr
27 20:50:26 unifi upssched[2688]: exec_cmd(/sbin/upssched-cmd.sh onbatt)
returned 126Apr 27 20:50:41 unifi upssched[2688]: Timer queue empty, exiting

/etc/nut/upssched.conf
CMDSCRIPT /sbin/upssched-cmd.shPIPEFN /etc/nut/upssched/upssched.pipeLOCKFN
/etc/nut/upssched/upssched.lockAT ONBATT * START-TIMER onbatt 20AT ONLINE *
CANCEL-TIMER onbatt
/sbin/upssched-cmd.sh
#!/bin/sh# Debugging: Log all calls to this scriptlogger -t upssched-cmd.sh
Calling upssched-cmd.sh $1 case $1 in   onbatt)     /sbin/upsmon -c fsd;;   *)  
echo "shutdown implemented";; esac
Any help gratefully received as this has got me beat..... Most files have been
chmod to 777 with no difference.
Cheers,
James
> Date: Mon, 27 Apr 2015 16:04:34 +0200
> From: roger at rogerprice.org
> To: nut-upsuser at lists.alioth.debian.org
> Subject: Re: [Nut-upsuser] upssched setup
> 
> On Mon, 27 Apr 2015, James Hammond wrote:
> 
> > Roger, I did and it didnt work.
> 
> Aha!, what does your upssched.conf look like? If you add the lines:
> 
>   # Debugging: Log all calls to this script
>   logger -t upssched-cmd.sh Calling upssched-cmd.sh $1
> 
> to your /sbin/upssched-cmd.sh , what is reported if anything when it 
> doesn't work?  Cheers, Roger
> 
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150427/f568d207/attachment.html>