Displaying 20 results from an estimated 20000 matches similar to: "NUT and Eaton UPS produce a lot of error messages"
2024 Jan 19
1
NUT and Eaton UPS produce a lot of error messages
Well, from your logs it seems that at 05:17:03 your nut-server (upsd)
restarted, so an upsmon reconnection attempt at 05:17:09 had an issue with
that (config not all applied? strange a bit) but since 05:17:14 it is okay.
Maybe a few too many banners shown from upsmon, while its same uptime seems
to continue. Maybe someone should check on that, seems like a good and easy
newcomer issue to learn
2024 Jan 19
1
NUT and Eaton UPS produce a lot of error messages
On 19.01.24 09:00, Jim Klimov via Nut-upsuser wrote:
>Well, from your logs it seems that at 05:17:03 your nut-server (upsd)
>restarted, so an upsmon reconnection attempt at 05:17:09 had an issue with
>that (config not all applied? strange a bit) but since 05:17:14 it is okay.
>
>Maybe a few too many banners shown from upsmon, while its same uptime seems
>to continue. Maybe
2024 Jan 19
1
NUT and Eaton UPS produce a lot of error messages
With recent NUT releases, driver disconnections should be contained in its
own `nut-driver at eaton` instance (the `@upsname` part is derived from the
`ups.conf` section name). One of the drivers failing and restarting is not
a proper cause for the data server to recycle.
Also, nowadays some (maybe not all) USB-capable drivers should try to
reconnect without restarting. Note however, that in some
2024 Jan 19
2
NUT and Eaton UPS produce a lot of error messages
Hello and thanks for all the replies.
This morning at 9:50 the server stopped working unexpectedly - I was
still sleeping until 10:00, so no user intervention took place.
Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call
Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting
Jan 19 05:50:17 mars nut-server[1303]: Network UPS Tools upsd 2.8.0
Jan 19 05:50:17 mars
2024 Jan 19
1
NUT and Eaton UPS produce a lot of error messages
On 19.01.24 16:20, Stefan Schumacher via Nut-upsuser wrote:
>This morning at 9:50 the server stopped working unexpectedly - I was
>still sleeping until 10:00, so no user intervention took place.
>
>Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call
>Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting
>Jan 19 05:50:17 mars nut-server[1303]: Network UPS
2024 Jan 19
2
NUT and Eaton UPS produce a lot of error messages
Jan 19 05:50:13 mars nut-monitor[849]: Signal 15: exiting
Jan 19 05:50:13 mars nut-monitor[849]: Network UPS Tools upsmon 2.8.0
Jan 19 05:50:13 mars systemd[1]: Stopping nut-monitor.service -
Network UPS Tools - power device monitor and shutdown controller...
Jan 19 05:50:13 mars systemd[1]: nut-monitor.service: Deactivated successfully.
Jan 19 05:50:13 mars systemd[1]: Stopped nut-monitor.service
2024 Jan 19
2
NUT and Eaton UPS produce a lot of error messages
I still have two questions:
1) How do I make the nut-server and nut-monitor find the right pid
files? They are there but it seems they can't be opened. Permissions
are nut/nut.
2) What do these error messages mean?
Jan 19 16:14:52 mars nut-monitor[3781]: Init SSL without certificate database
Jan 19 16:14:52 mars nut-monitor[3781]: Login on UPS [Eaton at localhost]
failed - got [ERR
2024 Jan 19
1
NUT and Eaton UPS produce a lot of error messages
> 1) How do I make the nut-server and nut-monitor find the right pid files?
They are there but it seems they can't be opened. Permissions are nut/nut.
Actually, if the preceding lifetime of the service was a graceful stop, the
exiting daemon should have removed its PID files. Then the newly starting
one would check and not find them - as I wrote before - to make sure there
is no hung old
2010 Sep 30
1
Getting "Error: No such host" and [ERR ACCESS-DENIED]
I'm using NUT 2.4.1 with openSUSE 11.2, my UPS is an MGE/Eaton
Ellipse ASR 1500 USBS. The set-up is as described at
http://rogerprice.org/NUT.html.
Since NUT uses TCP wrappers, I have the /etc/hosts.allow entry
upsd : 10.0.0/24, localhost, LOCAL, 127.0.0.1 : ALLOW
When I pull the plug from the wall to test my setup, I get the
sequence of KDE notifications and finally a
2016 May 02
2
New UPS Support: Eaton 5S 1000
Hi,
Thank you for taking a look at this. This is 13.10. I realize Saucy is no
longer supported. This system is slated for replacement, but in the
meantime I'm responsible for it.
The repo version of nut was 2.6.4-2.3ubuntu2. Installing it was useful as
it gave me the nut user and group. The compiled version errors out whether
or not the repo version is installed.
I just did strace.
2011 Apr 03
3
Multi UPS on Debian
Hello,
i have a server which supposed to control three Eaton UPS connected by USB cables. Each UPS is Eaton NV 2000H. (eaton_1, eaton_2, eaton_3)
The connection is fine with each UPS, if it is configured alone.
If i configure two or all three, the connections broke up.
After nut started, tried to start upsdrv manually (eaton_1.
The log:
Apr 4 00:43:46 mail blazer_usb[10799]: Startup
2009 Sep 14
3
Eaton NV 1000H in nut's hardware compatibility list
Le samedi 12 septembre 2009 ? 01:59 -0300, Vitor Choi Feitosa a ?crit :
> Hi Arnaud,
Hi Vitor,
> I found your email on the contact page and since you seem to work for
> Eaton and is involved in the NUT community I think you're the right
> person to contact.
>
> I've got an Eaton NV 1000H and just installed it here. Before NUT
> configuration I've checked the HCL
2016 Apr 26
3
New UPS Support: Eaton 5S 1000
I've used NUT successfully for monitoring many different brands of UPS, but
this one has me stumped. It has the same manufacturer ID and Product ID as
older supported MGE-type Eaton UPS's, but has trouble talking. I tried
Ubuntu's repo NUT, and it logs a Connecting to UPS message every few
seconds forever, but never really succeeds (or says it fails). Different
failure mode after
2013 Jun 20
3
Cannot connect to a Eaton Ellipse Pulsar ASR/6000VA usbs [solved] but new problem surfaces.
Hi Charles, thank you for your answer.
This was indeed the core of the problem. I have amended the configuration
files.
It means now the communication works as required. Alas I now have another
problem.
Just for the record here is the configuration after the changes.
The configuration is as follows.
#nut.conf
MODE=standalone
#ups.conf
[eaton]
driver = usbhid-ups
port = auto
2024 Jan 19
2
NUT and Eaton UPS produce a lot of error messages
On 19.01.24 17:02, Stefan Schumacher via Nut-upsuser wrote:
>Jan 19 05:50:13 mars nut-monitor[849]: Signal 15: exiting
>Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting
this looks like someone repeatedly killed nut server. This not a problem of
UPS.
--
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this
2012 May 12
2
NUT for Windows + Eaton/PW 5110
Nut for Windows 2.6.3-3 + Eaton/PW 5110 (103004256-5591).
I had to manually install libusb driver and I'm using bcmxcp_usb.
upsd.exe is reporting to me "Out of memory". It will run, but once
anything connects to the daemon, it dies with that message.
I don't have much experience with NUT yet so I'm not sure what the next
course of action is. I do have NUT for Windows
2011 Jun 08
2
Misconfiguration of Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port
Hello.
I've tried to configure Windows (complete port, Beta): Windows MSI installer
2.6.0-1 with my Powerware 5115 connected via USB port but have no luck.
Here is my config files:
*nut.conf:*
MODE = netserver
*ups.conf:*
[PW5115]
driver = bcmxcp_usb
port = notUsed
desc = "PowerWare 5115"
*upsd.conf:*
LISTEN 192.168.1.12 3493
*upsd.users:*
[monuser]
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
2014 Jun 05
2
Question about voltage threshold setting in NUT
Hello Charles,
Thank you so much for your help. Just run upsc and it is possible that
input.transfer.low is the one because we used power regulator to bring down
the power around 84v and then the ups sent the power loss message to PC. Do
you think some others may take effect for the low voltage? Just have the
upsc result attached.
Then I retried input.transfer.low, default.input.transfer.low,
2010 Dec 20
1
Power Walker VI 2000 LCD
Hello,
there's a recent thread about this or very similar model but without much info:
http://lists.alioth.debian.org/pipermail/nut-upsdev/2010-October/004968.html
I have this UPS and I'm trying to use it with nut-2.4.3 and megatec_usb driver:
The ups id iin ups.conf is powewalker. /var/log/messages says:
Dec 20 22:22:16 kvm-dom0 upsd[1666]: listening on 127.0.0.1 port 3493
Dec 20