search for: debug_min

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their `addvar`'ed options handling (as a separate effort from users/maintainers of those drivers). Live testing and other forms of review would be welcome :) Jim -------------- next part ----...

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their `addvar`'ed options handling (as a separate effort from users/maintainers of those drivers). Live testing and other forms of review would be welcome :) Jim -------------- next part ----...

...-driver-enumerator (NDE) script had a regression which caused it to not reload nut-driver instances (systemd, SMF) when `ups.conf` edits happened. * on a related note, it may be possible that "live" driver reloading (at least on master branch) does not reduce debug verbosity to zero when `debug_min 0` is active in its `ups.conf` section. Increasing verbosity and decreasing to non-zero (e.g. 1) works. These are currently being investigated. Jim Klimov On Tue, Apr 2, 2024 at 1:06?AM Jim Klimov <jimklimov+nut at gmail.com> wrote: > Hello all, > > After a prolonged labour w...

...-driver-enumerator (NDE) script had a regression which caused it to not reload nut-driver instances (systemd, SMF) when `ups.conf` edits happened. * on a related note, it may be possible that "live" driver reloading (at least on master branch) does not reduce debug verbosity to zero when `debug_min 0` is active in its `ups.conf` section. Increasing verbosity and decreasing to non-zero (e.g. 1) works. These are currently being investigated. Jim Klimov On Tue, Apr 2, 2024 at 1:06?AM Jim Klimov <jimklimov+nut at gmail.com> wrote: > Hello all, > > After a prolonged labour w...

...tor brought everything to life. Charles' reply below had the seed of the answer when he mentioned how the UPS will appear in the /dev/ directory. I had been looking at every other file except ups.conf and so the bus number was not top of mind. The documentation linked by Jim says that the DEBUG_MIN setting is supported in all of the .conf files. I changed it in upsd.conf, then went looking in other files. That is when I noticed the bus number in ups.conf. A very big DOH slap was promptly administered! I think the messages about permissions were the result of not having bus number 6 at...

Can you try starting the driver with higher debug verbosity to see more details, e.g. add `debug_min = 6` to the `ups.conf` section, or stop the auto-starting driver attempts and run the driver program with CLI options? * https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity With `upsdrvctl` driven attempts, you may also be in conflict with a generated `nut-driver at cy...

...osity mode, it historically defaults to staying foregrounded for easier Ctrl+C etc. NUT 2.8.0 should include -F/-B explicit options for some daemons (though not upsdrvctl wrapper - that was added/fixed on master recently), so you can e.g. run drivers backgrounded and verbose. It also includes "debug_min" settings via ups.conf global or per-device sections, and via some other daemon configs. With raised verbosity, you would see lines about setting dstate entries with readings at least. I think you interrupted the sent log too early, it might have completed the initialization a few seconds lat...

...osity mode, it historically defaults to staying foregrounded for easier Ctrl+C etc. NUT 2.8.0 should include -F/-B explicit options for some daemons (though not upsdrvctl wrapper - that was added/fixed on master recently), so you can e.g. run drivers backgrounded and verbose. It also includes "debug_min" settings via ups.conf global or per-device sections, and via some other daemon configs. With raised verbosity, you would see lines about setting dstate entries with readings at least. I think you interrupted the sent log too early, it might have completed the initialization a few seconds...

...life. > > Charles' reply below had the seed of the answer when he mentioned how > the UPS will appear in the /dev/ directory. I had been looking at every > other file except ups.conf and so the bus number was not top of mind. > > The documentation linked by Jim says that the DEBUG_MIN setting is > supported in all of the .conf files. I changed it in upsd.conf, then > went looking in other files. That is when I noticed the bus number in > ups.conf. A very big DOH slap was promptly administered! > > I think the messages about permissions were the result of not ha...

Normally yes - enable and start the target and the particular services relevant to your setup. For the binary you have from packaging (if not rebuilt as suggested earlier), set debug_min=3 in ups.conf section for upscode2, to currently trade driver viability for some storage traffic with more logs :\ Sorry about that, Jim On Wed, Jul 5, 2023, 02:29 Karl Schmidt <karl at lrak.net> wrote: > Ok - I'm wondering is this is a systemd config bit? > > systemctl restar...

On 7/4/23 10:01PM, Jim Klimov wrote: > Normally yes - enable and start the target and the particular services relevant to your setup. > > For the binary you have from packaging (if not rebuilt as suggested earlier), set debug_min=3 in ups.conf section for > upscode2, to currently trade driver viability for some storage traffic with more logs :\ > > Sorry about?that, > Jim OK - this is strange . If I run it WITH the debug - it works - WITHOUT - it fails. Put debug back in and it works again.. With debug I ca...

Hello all, After a prolonged labour with a few re-issues of the tag and many pushes during the day, NUT v2.8.2 was found in a strange egg by a bunny hopping away from the April fools. All that - blessed under the shine of Polar lights in the middle of the icy North Ocean. A python module was released but slipped away with an earlier commit. Other artifacts should follow shortly. Jim Klimov

Hello all, After a prolonged labour with a few re-issues of the tag and many pushes during the day, NUT v2.8.2 was found in a strange egg by a bunny hopping away from the April fools. All that - blessed under the shine of Polar lights in the middle of the icy North Ocean. A python module was released but slipped away with an earlier commit. Other artifacts should follow shortly. Jim Klimov

...Schmidt <karl at lrak.net> wrote: > On 7/4/23 10:01PM, Jim Klimov wrote: > > Normally yes - enable and start the target and the particular services > relevant to your setup. > > > > For the binary you have from packaging (if not rebuilt as suggested > earlier), set debug_min=3 in ups.conf section for > > upscode2, to currently trade driver viability for some storage traffic > with more logs :\ > > > > Sorry about that, > > Jim > > OK - this is strange . If I run it WITH the debug - it works - WITHOUT - > it fails. Put debug back in...

...the memory lane with another device with Richcomm-based hardware, and ultimately nutdrv_qx driver happened to support that one: https://github.com/networkupstools/nut/issues/2395 Some key take-aways were: * try starting the driver with bumped debug verbosity (e.g. from command line, or using a `debug_min` setting with NUT v2.8.0 and newer) to know better what it probes and how it fails; * if the device uses a serial port connection (maybe over a USB link, but with a chip that presents as a serial port for the OS) be sure to specify the appropriate `port=/dev/...` line in the NUT driver configuratio...

...e # set in a UPS section. This value controls how long # upsdrvctl will wait for the driver to finish starting. # This keeps your system from getting stuck due to a # broken driver or UPS. # The default is 45 seconds. # # debug_min: OPTIONAL. Specify a minimum debug level for all driver daemons # (when specified at global level), or for this driver daemon # (when specified in a driver section), e.g. for troubleshooting # a deployment. This does not directly impact the foreground or #...

Heya, first time posting to a mailing list so please excuse me if I do something wrong :) I'm new to NUT and trying to get things working on my TrueNAS, I have a "Vultech 1500VA" UPS which comes with the software "PowerManager II" and it seems to be using the "richcomm_usb" driver. There are 5 devices in the compatibility list and I tried all of them, sadly to

I also am wondering if the message about libusb driver missing might be the real problem. Checking my system, I see this: =================== [root at mythtv dev]# ll /dev/bus/usb/001 total 0 crw-rw-r--+ 1 root root 189, 0 Nov 9 08:21 001 crw-rw-r--+ 1 root root 189, 1 Nov 9 08:21 002 crw-rw-r--+ 1 root root 189, 2 Nov 9 08:21 003 crw-rw-r--+ 1 root dialout 189, 3 Nov 10 09:43 004

...t lrak.net>> wrote: > > On 7/4/23 10:01PM, Jim Klimov wrote: > > Normally yes - enable and start the target and the particular services relevant to your setup. > > > > For the binary you have from packaging (if not rebuilt as suggested earlier), set debug_min=3 in ups.conf section > for > > upscode2, to currently trade driver viability for some storage traffic with more logs :\ > > > > Sorry about?that, > > Jim > > OK - this is strange . If I run it WITH the debug - it works - WITHOUT - it fa...

Ok - I'm wondering is this is a systemd config bit? systemctl restart nut-driver at malaysia.service Job for nut-driver at malaysia.service failed because the control process exited with error code. See "systemctl status nut-driver at malaysia.service" and "journalctl -xeu nut-driver at malaysia.service" for details. root at malaysia:~# systemctl status nut-driver at