Displaying 20 results from an estimated 1000 matches similar to: "Dummy-ups cycles between online and onbatt every 5 minutes. (Nut 2.8.0)"
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
2024 Feb 23
0
Getting two notifications of nocomm-timer expired when USB cable is pulled from the UPS
NUT 2.8.01
When I pull the USB cable from the UPS, I get two notifications of the nocomm-timer expired. The first notification is in the proper sequence, the second notification occurs after 'commok' occurs. Seems somehow that upssched-cmd is getting a second nocomm-timer expired delayed.
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2023 May 27
2
unable to connect to APC UPS Connection Refused
I've not been able to connect to my ups using NUT 2.7.4 or NUT 2.8.0.
2.7.4 was installed as a package, 2.8.O was compiled from source.
I've messed with permissons, everything is root:root and has the approprate read/execute permissons. I've tried two differnt UPS(es) APC & CyperPower. I'm running PI OS (Raspbian) on a Raspberry Pi3 model B. The port 3493 is open (UFW). I can
2023 Jun 11
1
Upssched 100% CPU after updating Debian 12
Hi,
I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time.
I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
Hi,
I ran the strace command while upssched was 100% CPU hungry. This is what I got:
1686633611.702798 read(7, "", 1) = 0 <0.000004>
1686633611.702816 read(7, "", 1) = 0 <0.000004>
1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006>
1686633611.702862 read(7,
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
Hi,
I ran the strace command while upssched was 100% CPU hungry. This is what I got:
1686633611.702798 read(7, "", 1) = 0 <0.000004>
1686633611.702816 read(7, "", 1) = 0 <0.000004>
1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006>
1686633611.702862 read(7,
2006 Feb 04
2
[PATCH] allow user to update changed key in known_hosts
Hi list,
I use ssh a lot and I often need to connect to hosts whose host key has
changed. If a host key of the remote host changes ssh terminates and the
user has to manually delete the offending host key from known_hosts. I
had to do this so many times that I no longer like the idea ;-)
I would really like ssh to ask me if the new host key is OK and if I
want to add it to known_hosts.
I talked
2004 Oct 03
0
[patch] tell user about hosts with same key
The attached patch implements a feature that would make my interaction
with ssh somewhat more secure. When connecting to a host whose key is
not in the known_hosts file, this patch makes ssh tell the user about any
other hosts in the known_hosts file that have the same key.
For example, if I have host A in my known_hosts file, and try to connect
to host B which is an alias for A, ssh will tell
2020 Jun 21
2
Server did not shut down
2015 Oct 27
0
The system doesn't shutdown
On Tue, 27 Oct 2015, George Anchev wrote:
> Yes, that was the power off test. However the upssched-cmd script gave
> absolutely no signs of activity. Even it's logger lines don't show up in
> journalctl. No any permission error messages - nothing. Only the 2
> messages from upsmon - on battery and then on line power.
>
> Here is the nut-report:
>
2010 Jan 09
2
problem with mailing (nut 2.4.1 and a powermust650 -> megatec_usb)
Hello guys
Yesterday i started do configure my Mustek Powermust650 with nut using
the megatec_usb driver. Everything works fine except for the mailing
when something happens. My upsmon looks like this:
MONITOR powermust650 at localhost 1 local controller master
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h +0"
NOTIFYCMD /root/upsmailer
POLLFREQ 10
POLLFREQALERT 5
HOSTSYNC 15
2015 Jul 15
3
No messages
Charles,
This is how I have the upsmon.conf set up. ?The only time I get a message is if the?NUT Monitor gui is running. ?I open LXterminal, pull the wall plug, and I get no messagesin the terminal.
?MONITOR Asium_p700 at localhost 1 upsmon jsamcr master?MINSUPPLIES 1?SHUTDOWNCMD "/sbin/shutdown -h +0"?NOTIFYCMD /sbin/upssched?POLLFREQ 5?POLLFREQALERT 5?HOSTSYNC 15?DEADTIME
2020 Mar 10
2
Fwd: Windows upssched does not work
Hi,
I have problem with upssched on windows. Upssched is not executed. I
have 2 scripts, 1 for notification in upsmon and second for scheduling
in upssched. Monitoring is working fine, script write to log. I'm
using binary windows installer 2.6.5-6 from NUT.
Here are my configs:
--- nut.conf
MODE=netclient
--- upsmon.conf
MONITOR ups_1000 at 192.168.3.95 1 <user> <password> slave
2024 Feb 19
1
msmtp not running in upssched-cmd
On 19.02.24 14:48, Dan Grostick via Nut-upsuser wrote:
>Msmtp is not sending messages when invoked from upssched-cmd.
>I can manually invoke it from the command line.
where is its config file?
>There is a 's' instead of an 'x' in the ls -l. Might this be some sort of
>permission problem?
Should not be the case.
>upsmon.conf has run user as root.
msmtp may use
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
2012 Jan 28
2
No shutdown on empty battery
Hello,
I set up a FreeBSD 8.2 system with nut 2.6.1 and a Powerware 5115
connected by RS-232. I expected this setup to shut down before running
out of battery power, but I either missed some important configuration
or something else went wrong:
The syslog says:
Jan 9 05:03:42 b1 upsmon[67752]: UPS upsb1 at localhost on battery
Jan 9 05:04:42 b1 upsmon[67752]: UPS upsb1 at localhost on line
2024 Jul 27
1
Fedora 40 nut-server not starting at boot
Hi folks, I'm having an issue with getting nut-server to start at boot on a
freshly installed Fedora 40 desktop. Seems once the machine is up, I can
manually start with systemctl start nut-server and everythings fine.
dnf info nut
Last metadata expiration check: 2:08:11 ago on Sat 27 Jul 2024 03:48:13 PM
EDT.
Installed Packages
Name : nut
Version : 2.8.2
Release : 1.fc40
2017 Oct 18
2
debian 8 "jessie" nut 2.7.2 slaves not shutting down
MASTER SYSTEM
nut.conf
MODE=netserver
ups.conf
[TOPAPC]
driver = usbhid-ups
port = auto
pollonly
serial = "IS1309002707"
desc = "TOPAPC"
[MIDAPC]
driver = usbhid-ups
port = auto
pollonly
serial = "IS1309001233"
desc = "MIDAPC"
[BOTAPC]
driver = usbhid-ups
port = auto
2017 Jun 09
0
Apple Mac slave
On Fri, 9 Jun 2017, Robbie van der Walle wrote:
> # NOTIFYMSG - change messages sent by upsmon when certain events occur
> #
> # You can change the default messages to something else if you like.
> #
> # NOTIFYMSG <notify type> "message"
> #
> # NOTIFYMSG ONLINE "UPS %s on line power"
> # NOTIFYMSG ONBATT "UPS %s on battery"
> #
2020 Apr 28
2
Tripp-Lite SMART1500LCD: powers off with /etc/killpower...then powers back on...
Hi Everyone,
I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine,
connected via a USB cable. I installed Nut 2.7.4 from the Mint package
repository via sudo apt update && sudo apt install nut. Everything works
great: NUT issues low battery warning when it reaches the set low
battery point and then issues shutdown commands...computer shuts
down..then the UPS shuts