Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-22 Thread vom513 via Nut-upsuser
Shutdown worked as expected ! I did an fsd on the primary and I immediately heard the SS20 furiously clicking away doing a shutdown. ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listi

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-22 Thread vom513 via Nut-upsuser
So I don’t want to get too excited yet - but it actually looks like it’s working. I don’t get any connection errors from startup, I show a local socket, and the remote nut shows the Sun machine as a client ! [root@ss20 ~]# netstat -an | grep ESTAB | grep 3493 192.168.64.31.32789 192.168.64.30.

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-22 Thread vom513 via Nut-upsuser
One other thing I should come clean on. When compiling 2.8.x - it always dies with an error in common.c about left == operand (UINTPTR_MAX) has no value. This seems to be a 32/64 bit check. I know I’m 32 bit, so I’ve been commenting out the below block as shown. Hopefully this isn't biting m

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-22 Thread vom513 via Nut-upsuser
> On Dec 22, 2022, at 10:23 AM, Jim Klimov wrote: > > One thing that popped up in this quest was that Solaris 8 libc does not take > kindly to code similar to: > > printf("%s", NULL); > > ...which ends up dereferencing that NULL to check strlen() - and I suppose > can happen when debug m

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-22 Thread vom513 via Nut-upsuser
On Dec 22, 2022, at 10:17 AM, Jim Klimov wrote: > > Prospective fixes posted to https://github.com/networkupstools/nut/pull/1738 > - hoping the multi-platform CI would survive these changes elsewhere. > Probably a few follow-up fixes will land over time... > > You can try to check out and buil

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-19 Thread vom513 via Nut-upsuser
> On Dec 19, 2022, at 9:25 AM, Jim Klimov wrote: > > Maybe also try strace, truss and the likes to see what syscalls it makes? > e.g. falls on read/select?.. > Yep, it’s not even trying a connect(). Here is upsmon vs. curl: [root@ss20 ~]# LD_LIBRARY_PATH=/usr/local/ups/lib truss -f /usr/lo

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-18 Thread vom513 via Nut-upsuser
On Dec 18, 2022, at 6:06 PM, Sam Varshavchik wrote: > > Signed PGP part > vom513 via Nut-upsuser writes: > >> > Does the built `upsc` client connect? >> >> No - same error “Unknown error”. This is what makes me think there is some >> common code t

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-18 Thread vom513 via Nut-upsuser
Debug doesn’t seem to say much: [root@ss20 ~]# LD_LIBRARY_PATH=/usr/local/ups/lib /usr/local/ups/sbin/upsmon - Network UPS Tools upsmon 2.8.0 0.00 Failed to read pid from /var/run/upsmon.pid 0.008469 Could not parse PID file to see if previous upsmon instance is alr

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-18 Thread vom513 via Nut-upsuser
> On Dec 18, 2022, at 4:34 PM, Jim Klimov wrote: > > Don't have a SPARC machine anymore, but it is regularly tested on illumos > (which is ages newer than Sol8)... wondering if I can get an x86 vm running > with it... > > In the meanwhile, add some `-D` options to the launched program so it i

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-18 Thread vom513 via Nut-upsuser
> On Dec 18, 2022, at 3:00 PM, vom513 wrote: > > So with a bit of hacking and tweaking, I think I’m really close to having the > build finish successfully. I make it to a part with nut-scanner and I get > this: > > Regenerating the USB helper files in SRC dir. > Can't use an undefined value

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-18 Thread vom513 via Nut-upsuser
So with a bit of hacking and tweaking, I think I’m really close to having the build finish successfully. I make it to a part with nut-scanner and I get this: Regenerating the USB helper files in SRC dir. Can't use an undefined value as a symbol reference at ../tools/nut-usbinfo.pl line 237. ***

Re: [Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-18 Thread vom513 via Nut-upsuser
> On Dec 18, 2022, at 11:35 AM, vom513 wrote: > > checking which drivers to build... ./configure: line 13084: syntax error near > unexpected token `(' > ./configure: line 13084: ` get_drvlist() (‘ > Sorry to self reply… got past this by using my sunfreeware / more modern

[Nut-upsuser] Compiling on Solaris 8 sparc - configure errors

2022-12-18 Thread vom513 via Nut-upsuser
Hello, Trying to build from source on Solaris 8/sparc. I grabbed the 2.8.0 release tarball from github. All I really need is upsmon to talk to another nut instance on the network. So I don’t need any kind of drivers built. Here is the error I’m getting: checking which drivers to build... ./

[Nut-upsuser] Cyberpower RMCARD via SNMP - never reports LB

2022-11-21 Thread vom513 via Nut-upsuser
Hello all, Here is all of my version info: - nut 2.7.4 on Debian 11 (default Debian package) - Cyberpower UPS model PR1500RT2U (UPS fw 1.8553) - Cyberpower RMCARD 205 (hw 1.1, fw 1.3.7) - Using snmp-ups driver + cyberpower mibs. snmpv1 So in this configuration, NUT sees the UPS fine, reports a