search for: danpower2023

Displaying 20 results from an estimated 22 matches for "danpower2023".

2024 Mar 06
2
Upssched 100% CPU
...prerelease source version of NUT 2.8.1, built and installed it. Evidently there was an issue with upssched consuming 100% CPU. I downloaded the current release and the issue has been resolved. Updating all 3 systems. Dan ________________________________ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on behalf of Andy Smith via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> Sent: Tuesday, March 5, 2024 6:43 AM To: nut-upsuser at alioth-lists.debian.net <nut-upsuser at alioth-lists.debian.net> Subject: Re: [Nut-upsuser] Upssched 100% C...
2024 Mar 06
1
Upssched 100% CPU
...ad downloaded a prerelease source version of NUT 2.8.1, built and installed it. Evidently there was an issue with upssched consuming 100% CPU. I downloaded the current release and the issue has been resolved. Updating all 3 systems. Dan _____ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net <mailto:nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net > > on behalf of Andy Smith via Nut-upsuser <nut-upsuser at alioth-lists.debian.net <mailto:nut-upsuser at alioth-lists.debian.net> > Sent: Tuesday, March 5, 2...
2024 Mar 05
1
Upssched 100% CPU
Hi, On Tue, Mar 05, 2024 at 08:37:32AM +0000, Dan Grostick via Nut-upsuser wrote: > My Raspberry PI 3B was overheating - 70 degrees C. I used Top and > it turns out that upssched is taking 100% CPU. Debian 11 (PI Os). > I have two others running the same configuration, 2.8.1 with no > problems. I have no first hand knowledge of this issue, but in the change log for the 2.8.1
2024 Mar 29
1
Heartbeat timer failure 15 minutes after startup
It is consistently happening 14-15 minutes after starting. Please see attached upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary upssched is used. Dan ________________________________ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on behalf of Roger Price via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> Sent: Thursday, March 28, 2024 12:29 PM To: Dan Grostick via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> Subject: Re: [Nut-upsuser] Heartbeat timer failu...
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
2024 Mar 08
1
NUT 2.8.1 (source build) Pi OS bookworm 32 bit - nut-monitor trying to connect to UPS - Connection Refused
On Mar 8, 2024, at 8:22?AM, Dan Grostick via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian 12) with success. > > When I take that same configuration to a PI 3B running bookworm 32 bit, compile from source, use the same files from /etc/nut, I get a 'nut-monitor ups at
2024 Mar 28
2
Heartbeat timer failure 15 minutes after startup
On Thu, 28 Mar 2024, Dan Grostick via Nut-upsuser wrote: > All three systems have a heartbeat-timer failure approximately 15 minutes > after starting NUT. No subsequent failures. Any ideas on what is happening? I've seen the timers: heartbeat.conf has two 300 sec timers, upssched.cmd looks like what is often called upssched.conf and has a 660 sec timer. So it looks as if the
2024 Mar 03
2
NUT 2.8.1 build from source - upssched missing
PI OS - Debian12 - Raspberry PI 5 NUT 2.8.1 I'm building from source just downloaded from GITHUB. The error when starting NUT: nut-monitor: /usr/sbin/upssched not found I did a 'find / ' and upssched is not in the filesystem. I've done a make clean, make uninstall. then autogen.sh, make, make install 1. is there an option to make that completely removes everything? In
2024 Feb 16
1
Stopping dummy ups from broadcasting messages
Is there any way to stop dummy ups from continuously broadcasting status? (onbatt) I want to keep the broadcasts from the ups itself. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240216/b43de97f/attachment.htm>
2024 Feb 19
1
msmtp not running in upssched-cmd
Msmtp is not sending messages when invoked from upssched-cmd. I can manually invoke it from the command line. There is a 's' instead of an 'x' in the ls -l. Might this be some sort of permission problem? upsmon.conf has run user as root. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:
2024 Mar 03
0
Makefile: SBINDIR=/usr/local/ups/sbin - can't change it....
Building 2.8.1 from source. I have --sbindir=/usr in the 'newconfigure' file, but Makefile contains SBINDIR = /usr/local/ups/sbin and that's where the files go. I run autogen.sh and then bash newconfigure. I don't know how to get Makefile SBINDIR to be /usr. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:
2024 Mar 05
1
Upssched 100% CPU
My Raspberry PI 3B was overheating - 70 degrees C. I used Top and it turns out that upssched is taking 100% CPU. Debian 11 (PI Os). I have two others running the same configuration, 2.8.1 with no problems. If I kill upssched, it soon reestablishes the 100% CPU usage. Any ideas on how to diagnose the issue? Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:
2024 Mar 28
1
Heartbeat timer failure 15 minutes after startup
I have 3 Raspberry Pi NUT 2.8.1 systems running PI OS. (Debian 11 and 12) All three systems have a heartbeat-timer failure approximately 15 minutes after starting NUT. No subsequent failures. Any ideas on what is happening? Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:
2024 Apr 07
0
NUT v2.8.2 sucesses!
I updated 3 Pi OS systems with v2.8.2. So far all are running without error. Raspberry PI 2, Pi 3 and Pi 5. Debian 12 (bookworm). Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240407/74832090/attachment-0001.htm>
2024 Apr 11
0
Solaris ?
Why are scripts being generated for Solaris on a Debian based build? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240411/bb002ba9/attachment.htm>
2024 Apr 19
0
UPS ups@localhost: administratively OFF or asleep
NUT 2.8.2 I received two broadcasts: UPS ups at localhost: administratively OFF or asleep What does this mean? Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240419/cf000f7a/attachment.htm>
2023 Jun 14
1
Accessing: upsstats.cgi Error: no hosts to monitor (check hosts.conf)
For some reason I?m no longer able to access the upsstats.cgi (http://192.168.123.49/cgi-bin/nut/upsstats.cgi) I get the error: Error: no hosts to monitor (check hosts.conf) When Apache starts is complains about not finding the fully qualified domain name. In the past, upsstats.cgi would just load. I didn?t have to do any Apache2 configuration. I don?t know what has changed. I?ve build NUT
2024 Mar 08
1
NUT 2.8.1 (source build) Pi OS bookworm 32 bit - nut-monitor trying to connect to UPS - Connection Refused
I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian 12) with success. When I take that same configuration to a PI 3B running bookworm 32 bit, compile from source, use the same files from /etc/nut, I get a 'nut-monitor ups at localhost Connection refused. usbhid-ups and dummy-ups are running at the time. What should I be looking for? Dan -------------- next
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 Jun 16
1
Dummy-ups cycles between online and onbatt every 5 minutes. (Nut 2.8.0)
Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5 minutes between OL and OB (probably when the 300 second timer expires). The UPS state stays online. Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS