similar to: nut client config?

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

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

Marcus, I did try to do that several days ago, got the email, confirmed my desire to unsubscribe, and wad told that my "request would soon be acted upon" Yet I continue to get these messages. I'd love to have just a way to receive only message chains where I either started the question or am contributing. I don't need to see ALL the comms on the list, however this old-school

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

Hello, I have noticed that (apparensly) since Debian 12 upgrade the WALL commands for upsmon.conf don's seem to work. To test I have configured upsmon-dummy.conf to debug this: NOTIFYCMD /usr/sbin/upssched NOTIFYFLAG ONBATT SYSLOG+EXEC+WALL NOTIFYFLAG ONLINE SYSLOG+EXEC+WALL the /usr/sbin/upssched gets called: /lib/nut/upsmon -D -D -D -D -f /etc/nut/upsmon-dummy.conf and I

Maybe...ish - I haven't seen those for a while, but had few outages either. Can you check if the updated (root) user profile or default profile(s) under /etc mention `mesg n` or similar means of limiting broadcasts? In your manual `wall` executions, do you see them in the same terminal that sent the message, or on all terminals (GUI, SSH sessions)? As root or as any user (as recipient and as

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

On Jun 3, 2013, at 12:21 PM, Matus UHLAR - fantomas wrote: > It would be easier to configure UPSes for upsc, upsmon and nut-monitor with > client config file. > Maybe ups.conf ? If you are looking for a simpler way to set up NUT in general, there is the nut-scanner tool. I don't use it, but others on the list might be able to help. The separation between clients and server is to

> 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

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

Hello, I have tried setting umask 0027 for tftpd, so files are created with permissions 0640. However, tftpd-hpa refused uploading a file with error "must have global write permissions". Looking at the source, I could avoid this issue by using "-p" option. However, it also seems that the umask is not applied when the "-p" option is used. Can anyone explain this

>> On Sun, 23 Feb 2014 19:39:02 +0100, Josu Lazkano <josu.lazkano at gmail.com> wrote: >>> # dmesg >>> ... >>> [181041.636190] usb 4-4: new low-speed USB device number 2 using ohci_hcd >2014-02-25 10:12 GMT+01:00 Virgo P?rna <virgo.parna at mail.ee>: >> I recently read about openwrt (for one of the routers I own). And there was a >>

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

Hello, when I have UPS connected to NUT server, does it matter if the NUT client (running a different version) supports that UPS? In other words, does the NUT protocol require the UPS being supported by the client in addition to the server? ...I guess the answer is 'no' but I'd like to know if there is anything good to know. -- Matus UHLAR - fantomas, uhlar at fantomas.sk ;

>>gene heskett <gheskett at shentel.net> writes: >>>Which file in the nut I pulled a month ago, should I start with to get >>>the new version actually running? I still get - -V=2.7.4 >On 5/22/23 07:13, Greg Troxel wrote: >>It is likely that you have built new nut but old nut is still on your >>system. I do a 'sudo make install' to write over

On 20.03.22 16:02, Roger Price wrote: >I received the following comment from the Independent Submissions Editor (ISE): > > The command VER is hazardous because it encourages exploiting of > implementation peculiarities that are not well documented in a > protocol.? The best example of such a failure is the browser version > field in HTTP.? A complete disaster.? You should warn

On Mon, 2023-05-22 at 15:54:51 +0200, Matus UHLAR - fantomas wrote: > > > gene heskett <gheskett at shentel.net> writes: > > > > Which file in the nut I pulled a month ago, should I start with to get > > > > the new version actually running? I still get - -V=2.7.4 > > > On 5/22/23 07:13, Greg Troxel wrote: > > > It is likely that you have

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

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

Hello, I run TP-Link WR2543ND router with openwrt installed. versions: kernel - 3.8.3-1-eef5f2649dd28f8ed1d4fd9b737acdc7 kmod-hid - 3.8.3-1 libusb-1.0 - 1.0.9-1 libusb-compat - 0.1.4-1 nut-driver-usbhid-ups - 2.6.5-2 I have installed NUT but it can not find the UPS while lsusb can: root at gw:~# lsusb Bus 001 Device 003: ID 0463:ffff MGE UPS Systems UPS Bus 001 Device 001: ID 1d6b:0002 Linux