Stefan Schumacher via Nut-upsuser writes:
I am considering returning the device to the online shop I bought. As
it is, it's nothing but trouble. Can you recommend a small UPS (1
Server) that is guaranteed to work flawlessly with NUT?
I've had good experience with Cyberpower units, as long as
One more idea, inspired by messages systemd sometimes gives:
* Select to "Copy" the timestamps of when e.g. your `nut-server.service`
stopped/restarted;
* As root(!) run `journalctl -xl` for a detailed log with service state
changes and reasons, and other details, piped into `less` by default
*
> 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
On 19.01.24 18:33, Stefan Schumacher via Nut-upsuser wrote:
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.
afaik they should not be needed with systemd, they still
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
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,
Can you please check what was previous to the signal 15 (graceful
termination)? With `journalctl -lu nut-server` or with longer `systemctl
status -n 50 nut-server` if that works for yours?
Also, check NUT Wiki or other docs about using `debug_min` setting woth
2.8.0+ to bump it and have more
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]:
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
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:
With recent NUT releases, driver disconnections should be contained in its
own `nut-driver@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
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
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
13 matches
Mail list logo
