Displaying 20 results from an estimated 2000 matches similar to: "Timer doesn't appear to start"
2020 Jan 28
0
Timer doesn't appear to start
One last update. I needed to log out and in to get the group add of my user
nutmon to be recognized. My permissions are now root:nut on upssched.conf
and it works.
On Tue, Jan 28, 2020 at 7:00 AM <nut-upsuser-request at alioth-lists.debian.net>
wrote:
> Send Nut-upsuser mailing list submissions to
> nut-upsuser at alioth-lists.debian.net
>
> To subscribe or unsubscribe
2020 Jan 28
1
Timer doesn't appear to start
The time and upssched-cmd are now working.
Here are the issues I had:
1) Did not define NOTIFYCMD in upsmon.conf Added NOTIFYCMD /sbin/upssched
2) Added +EXEC to NOTIFYMSG rules I am using
3) Change ownership of upssched.conf to my nut user nutmom. I had added
nutmon to the group nut but it didn't work.
Thanks again for all your guidance
On Tue, Jan 28, 2020 at 7:00 AM
2020 Jan 27
1
Timer doesn't appear to start
Here is the output
root at nutpi:/etc/nut# ps -elf | grep -E '[n]ut|ups[dms]'
4 S avahi 246 1 0 80 0 - 1472 poll_s Jan26 ? 00:00:31
avahi-daemon: running [nutpi.local]
1 S nut 451 1 0 80 0 - 678 poll_s Jan26 ? 00:03:41
/lib/nut/upscode2 -a deltec-PRA1500
1 S nut 454 1 0 80 0 - 1173 poll_s Jan26 ? 00:00:28
/lib/nut/upsd
1
2020 Jan 26
1
Timer doesn't appear to start
I have a Raspberry PI that I have connected to a Deltec UPS via serial
(upscode2 driver). I had an older version of Rasbian running. The nut
configuration worked fine but I had mail issues I couldn't resolve when
gmail changed how it handled MTAs. Plus it was running an old version of
Deb that is no longer supported. It was broken enough I could not upgrade
to a never version so I started from
2020 Jan 27
0
Timer doesn't appear to start
I only pasted a subset of my upsmon.conf. NOTIFYCMD is in my upsmon.conf
AFA nutmon user. I was trying different things I had the directory as
nutmon nut but changed it to nutmon nutmon to see if that worked. It didn't
make a difference.
Sorry about the digest this. I needed to hit a line in gmail web client to
see the subject line. Know I know. Thanks for the heads up..
[root at donner
2020 Jan 27
3
Nut-upsuser Digest, Vol 175, Issue 32
Here are my permissions and user info. Let me know if there is anything
else I should check
pi at nutpi:~ $ ls -alt /etc/nut
total 56
drwxr-xr-x 87 root root 4096 Jan 26 15:22 ..
drwxr-xr-x 2 root nut 4096 Jan 26 13:53 .
-rw-r----- 1 root nut 4719 Jan 26 13:15 upssched.conf
-rw-r----- 1 root nut 15347 Jan 26 11:25 upsmon.conf
-rw-r----- 1 root nut 1543 Jan 26 10:02 nut.conf
-rw-r-----
2020 Jan 27
1
Nut-upsuser Digest, Vol 175, Issue 30
Roger,
here is my output of ps -elf |grep upssched
root at nutpi:~# ps -elf |grep upssched
0 S root 1242 1191 0 80 0 - 1834 pipe_w 05:23 pts/0 00:00:00
grep upssched
No timer, just the grep of upssched..
On Mon, Jan 27, 2020 at 4:27 AM <nut-upsuser-request at alioth-lists.debian.net>
wrote:
> Send Nut-upsuser mailing list submissions to
>
2010 Nov 16
2
Shutdown script does not trigger
Dear nut users,
I am fighting to configure a smooth server shutdown with an ubuntu
server and a dell usb ups using nut.
It seems that the drivers connect properly (upsc gives very coherent
outputs).
However I can't get anything to happen when the ups goes on battery.
How can I be sure the the UPS status is really monitored ?
Is there a particular log file where I upsmon reports problems
2005 Dec 29
1
Deltec PRA1500 UPS and FC4
I recently bought new batteries for this old "Compaq"
Deltec PRA 1500 ups and downloaded LanSafe3 and
haven't had much luck communicating with the UPS via a
serial cable. Does anyone out there have a manual on
this UPS? Or has anyone else gotten this to work with
LanSafe3 and/or upsd?
Any help would be greatly appreciated!
Jon Moss
__________________________________
2016 Jul 11
0
Proposal for technique to stop a timer at any moment
Here is patch 2 of 2. Roger
diff -rup -x '*.html' -x '*.8' -x '*.5' nut-2.7.4.orig/docs/man/upsd.txt nut-2.7.4.dev/docs/man/upsd.txt
--- nut-2.7.4.orig/docs/man/upsd.txt 2015-12-29 09:42:34.000000000 +0100
+++ nut-2.7.4.dev/docs/man/upsd.txt 2016-07-07 10:08:51.939354892 +0200
@@ -119,6 +119,16 @@ administrative functions like SET and IN
controlled in
2006 Feb 14
3
Master privileges unavailable on UPS
Hello all,
I'm having problems with what I'm told should be a straightforward
issue.
The message in /var/log/daemon is:
<quote>
Feb 13 10:37:57 lupin upsmon[31324]: Master privileges unavailable on
UPS [lupin1500AVR@localhost]
2007 Jan 17
1
NOTIFYCMD not running
I have the nut package installed and running - everything perfect (or so I
thought). My syslog shows everything looks great, and pulling the UPS plug
for a few seconds triggers a WALL event, but not my notifycmd (which should
write a test message to syslog).
Can someone offer insight/ideas as to why my NOTIFYCMD is not running?
Thanks,
Michelle
-----------------------
Extract from messages
2006 Jun 07
1
RPM spec file
Hi,
To to build an RPM from the nut 2.0.3 source I've corrected the old
nut.spec.in file. Please find a copy of the slightly updated spec file
attached. The changes are documented at the bottom of the spec file.
Regards,
Will
-------------- next part --------------
# don't know how different I can do this
%define majorver 2.0
%define version 2.0.3
%define relver 1
%define nutuser
2015 Oct 29
0
The system doesn't shutdown
On Thu, 29 Oct 2015, George Anchev wrote:
> Today I experienced something weird. As I was working, the system
> started a shutdown and did shut down, then the UPS got powered off and
> then back on - an expected behavior for a power fail situation. However
> there was no power failure!
...
> Oct 29 10:46:46 i7 upsmon[2239]: UPS myups at localhost battery is low
> Oct 29
2015 Sep 22
2
NOTIFYCMD shell script problem driving me NUTS
Either I am missing something or I am really STUPID.
1. I have added a user, named nutmon, to the nut group.
2. In upsmon.conf I have set RUN_AS_USER nutmon .
3. I have NOTIFYCMD /etc/nut/notifyme.sh and it is set as 755, so should be
executable by everyone.
4. I have the NOTIFYFLAG set as SYSLOG+WALL+EXEC, so the shell should
execute.
This is the shell script :
#!/bin/bash
#
# NUT NOTIFYCMD
2018 Sep 20
3
Upssched not getting called from UPSMON
Hi, I cant seem to get my upssched to get called by upsmon. Upsmon -c fsd just shuts down without the message I set or the one in upssched-cmd
/etc/ups/upsmon.conf:
MONITOR ups6 at localhost 1 <user> <pass> master
MONITOR ups8 at localhost 1 <user> <pass> master
SHUTDOWNCMD "/sbin/shutdown -h +0"
NOTIFYCMD /usr/sbin/upssched
NOTIFYMSG
2017 Oct 31
0
Email Alerts for Multiple UPSs with upssched
I'm running a single "nut-server" that monitors seven ups units.
In upsmon.conf:
MONITOR ups-1 0 <User> <Pw> master
MONITOR ups-2 0 <User> <Pw> master
MONITOR ups-3 0 <User> <Pw> master
MONITOR ups-4 0 <User> <Pw> master
MONITOR ups-5 1 <User> <Pw> master
MONITOR ups-6 1 <User> <Pw> master
MONITOR
2013 Mar 08
0
HowTo use upssched right.
Hi,
I want to test the events off my UPS.
I define
In upsmon.conf:
RUN_AS_USER root
NOTIFYCMD /sbin/upssched
NOTIFYMSG ONLINE "UPS %s on line power"
NOTIFYMSG ONBATT "UPS %s on battery"
NOTIFYMSG LOWBATT "UPS %s battery is low"
# NOTIFYMSG FSD "UPS %s: forced shutdown in progress"
NOTIFYMSG COMMOK "Communications with UPS %s established"
2017 Oct 31
0
Email Alerts for Multiple UPSs with upssched
There's supposedly another way with a custom upsmon.conf:
NOTIFYMSG type message
upsmon comes with a set of stock messages for various events. You can change them if you like.
NOTIFYMSG ONLINE "UPS %s is getting line power"
NOTIFYMSG ONBATT "Someone pulled the plug on %s"
Note that %s is replaced with the identifier of the UPS in question.
The message must be one
2023 Jun 10
1
Fopen upsmon.pid - no such file or directory - Nut 2.8.0 built from source
I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath.
Is there something I am missing?
Please see attached.
Dan
-------------- next part --------------
An HTML attachment was