Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-25 Thread gene heskett
On 4/25/23 18:11, Jim Klimov wrote: ups.load:8 is 8% right? just the RPi or more serious load? At lower values, the gauge might not be precise, maybe... 8 is max, depending on the mood its in it might show 0% for hours at a time, that particular outlet, checked with a kil-a-watt is below what

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-25 Thread Jim Klimov via Nut-upsuser
ups.load:8 is 8% right? just the RPi or more serious load? At lower values, the gauge might not be precise, maybe... Wondering why the shell froze - could be systemd waiting for startup to complete (driver and other daemonware signalling it is forked and ready), which might take time. The `journal

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-25 Thread gene heskett
On 4/24/23 20:11, gene heskett wrote: sudo systemctl restart nut-driver-enumerator.service nut-monitor nut-server Got to the last line, but shell is hung now. Except it finally completed after several minutes, and upsc myups output looks normal. Strange. pi@rpi4:/media/pi/workspace/nut $ upsc

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-25 Thread gene heskett
On 4/25/23 13:44, Jim Klimov wrote: That's odd - a name like this is not default I think, so either you passed it to configure script options, or in-place config mode deduced it from packaging remnants?.. I went back in the shells history and looked. I gave no arguments to ./configure except -

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-25 Thread Jim Klimov via Nut-upsuser
That's odd - a name like this is not default I think, so either you passed it to configure script options, or in-place config mode deduced it from packaging remnants?.. Either way, better than running as root or nobody, so useradd (maybe also groupadd) are your friends here :) Ideally, NUT driver

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-25 Thread gene heskett
On 4/24/23 19:54, Jim Klimov wrote: sudo systemd-tmpfiles --create [/usr/lib/tmpfiles.d/nut-common-tmpfiles.conf:3] Unknown user 'nutmon'. [/usr/lib/tmpfiles.d/nut-common-tmpfiles.conf:5] Unknown user 'nutmon'. so how, on a pi running buster, do I create this missing user? Thanks Jim. Cheers,