search for: upcl

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

...5T15:06:02.573252-05:00 malaysia systemd[1]: nut-driver at malaysia.service: Control process exited, code=exited, status=1/FAILURE 2023-07-05T15:06:02.573390-05:00 malaysia systemd[1]: nut-driver at malaysia.service: Failed with result 'exit-code'. Not enough time to fail from not finding UPCL This seems like this might be a timing issue - something is running before something else is ready? Debug would slow something down? I hooked it up to cutecom connected and I seem to get a list of supported commands back if I ask for UPCL UPSS UPDS UPDV UPTP UPSN UPPN UPSD UPCD UPPC UPPU UP...

Ah, I thought you missed in my earlier reply the part about a bug with debug printouts in 2.8.0 (fixed on master since), did not comment on that when you replied with quoting... So, for now options are to bump debugging to 3+ or to build your own in one of many ways possible :\ On Wed, Jul 5, 2023, 06:23 Karl 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 On Wed, Jul 5, 2023, 02:29 Karl 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

..."Shutdown called, but UPS does not support it"); } } The problem is that the if(can_upsd && can_uppc) check was added between SVN 408 and SVN 743. Those variables can_upsd and can_uppc get set to 0 (zero) when upscode2 starts and then based on the output of the UPCL command to the UPS, they get set to a one if the UPS supports those commands. However, if you call the driver with the -k option to force a shutdown, which my shutdown scripts do, it fails because those variables are never set, because the routine upsc_commandlist is never called. That is...

...2001-2002 H??vard Lygre, <hklygre@online.no> Copyright (C) 2004 Niels Baggesen <niels@baggesen.net> Warning: This is an experimental driver. Some features may not function correctly. Bad response to UPTP "": Bad response to UPTP "": Bad response to UPSN 0: Missing UPCL after UPCL Communications with UPS lost: Empty string from UPS for UPDS! I thought the USB/serial dongle or serial port might be bad, so I dual booted into Windows and ran Powerware's Lanware 5.x software and it found the UPS properly on COM3. Any other suggestions? :-P ken ______________...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Has anyone gotten it working at all with Linux :) I picked one up for thiry bucks and would love to monitor it! Liz - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD/5fEIACpLcG4dhwRAmeCAJ9+8FGXqKoOlZdkw/KFXb9n0PEemwCdHaoD NVnv7JjmBAjNsExK6WzAdnA= =pcPX - -----END PGP