similar to: 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

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

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

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,

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,

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

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

Hello! I use online UPS MV-1000 LT http://www.230v.ru/catalogue/?id=production/ups-sm/master-vision for the power of my Linux server SLES 10 SP1. I downloaded, compiled and configured diver nut 2.4.1 from this link http://www.networkupstools.org/source/2.4/nut-2.4.1.tar.gz Here are my configuration files: --- srv:/usr/local/ups # cat etc/ups.conf [npower] driver = megatec port = /dev/ttyS0

Hello NUT Team! I continue playing with NUT for Windows and USBHID-UPS driver I've got from Frederic to fix "Data Stale" problem. It seems there is something wrong when Network UPS Tools service is starting with disconnected USB cable. UPSMON is writing "Data Stale" to output and continue do it infinitely, even the cable is connected back. Here is a short log: Network

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

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:

Hi, I have UPS Socomec ITYS 3000 with Netvision card. OS is Centos 6.5 64-bit. NUT installed with yum,. nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64 Why is ups.status empty? Here is upsc output: upsc myups at localhost battery.charge: 97.00 battery.runtime: -60.00 battery.voltage: -0.10 device.mfr: Net Vision v6.01 (SN 0101414290) device.model: ITYS 3 kVA device.serial: 3I14450043

Hi there, i have a problem with the NOTIFYCMD in the upsmon.conf file. My line in the config looks like this: NOTIFYCMD "/etc/nut/upsnotify.sh" Now this ist my "/etc/nut/upsnotify.sh": #!/bin/bash EMAIL='mail at domain.de' SMS1='+49123456789' SMS2='+491987654231' #eMail versenden echo -e "Die USV mit dem Namen '$UPSNAME' hat seinen

Hi, I feel that i'm having a small problem with my upsmon configuration (maybe even simply a permissions problem) since I upgrade today to 2.0.2 I have apcsmart set up and talk to my ups no problem (upsc get answer). I have upsd running no problem! But when I try to start upsmon, it's unable to talk to my upsd. Having try a few option I found that saying RUN_AS_USER=root makes my upsmon

Hello All, I'm trying to establish a MASTER SLAVE configuration of UPS using NUT Driver. I'm able to shutdown the master after UPS is on BATTERY ( POWER BLACKOUT) .However I'm trying to shutdown the other SLAVE MACHINES BEFORE MASTER. But at the remote side ( Slaves ) shutdown after UPS blackout does not happen. My configuration in Master are /usr/etc/upsd.users

On 30.04.2023 10:20, Rowland Penny via samba wrote: > > > On 30/04/2023 09:06, Peter Milesson via samba wrote: >> Hi Yvan, >> >> Thanks for the information, really useful. Essentially, it means I >> need to wait for the official release of Debian Bookworm, and then >> getting the newest Samba packages from Bookworm backports. It's just >> a

30.04.2023 11:20, Rowland Penny via samba ?????: .. > There is a big problem with this, bookworm hasn't been released yet and as far as I can see, there isn't a bookworm-backports yet. > The only mention of Samba 4.18 that I can see in Debian is in experimental, a long way from any backports. No, there's no long way to bookworm-backports. I use experimental just because debian

On 30/04/2023 09:06, Peter Milesson via samba wrote: > Hi Yvan, > > Thanks for the information, really useful. Essentially, it means I need > to wait for the official release of Debian Bookworm, and then getting > the newest Samba packages from Bookworm backports. It's just a little > over a month away, so there is ample time for planning upgrades. > > Best

On 30/04/2023 09:37, Peter Milesson via samba wrote: > > > On 30.04.2023 10:20, Rowland Penny via samba wrote: >> >> >> On 30/04/2023 09:06, Peter Milesson via samba wrote: >>> Hi Yvan, >>> >>> Thanks for the information, really useful. Essentially, it means I >>> need to wait for the official release of Debian Bookworm, and then

On 30-04-2023 10:46, Rowland Penny via samba wrote: > > > On 30/04/2023 09:37, Peter Milesson via samba wrote: >> >> >> On 30.04.2023 10:20, Rowland Penny via samba wrote: >>> >>> >>> On 30/04/2023 09:06, Peter Milesson via samba wrote: >>>> Hi Yvan, >>>> >>>> Thanks for the information, really useful.