Jim Klimov
2022-Dec-19 14:25 UTC
[Nut-upsuser] Compiling on Solaris 8 sparc - configure errors
Maybe also try strace, truss and the likes to see what syscalls it makes? e.g. falls on read/select?.. Jim On Sun, Dec 18, 2022, 23:04 vom513 via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote:> Debug doesn?t seem to say much: > > [root at ss20 ~]# LD_LIBRARY_PATH=/usr/local/ups/lib > /usr/local/ups/sbin/upsmon -DDDDDDDDDDDD > Network UPS Tools upsmon 2.8.0 > 0.000000 Failed to read pid from /var/run/upsmon.pid > 0.008469 Could not parse PID file to see if previous upsmon > instance is already running! > > 0.024417 UPS: ups at 192.68.64.30 (secondary) (power value 1) > 0.038074 Using power down flag file /etc/killpower > 0.053368 [D1] debug level is '12' > 0.062147 [D1] debug level is '12' > 0.263514 upsmon parent: read > > It exits immediately as well. > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20221219/edb359b4/attachment.htm>
vom513
2022-Dec-19 16:41 UTC
[Nut-upsuser] Compiling on Solaris 8 sparc - configure errors
> On Dec 19, 2022, at 9:25 AM, Jim Klimov <jimklimov+nut at gmail.com> 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 at ss20 ~]# LD_LIBRARY_PATH=/usr/local/ups/lib truss -f /usr/local/ups/sbin/upsmon 2>&1 | grep -i connect Broadcast Message from nobody (???) on ss20 Mon Dec 19 11:19:26... Communications with UPS ups at 192.68.64.30 lost Broadcast Message from nobody (???) on ss20 Mon Dec 19 11:19:31... UPS ups at 192.68.64.30 is unavailable ^C [root at ss20 ~]# truss curl -I -v http://burn.net 2>&1 | grep -i connect About to connect() to burn.net port 80 (#0) connect(4, 0xEFFFEC98, 32, 1) Err#150 EINPROGRESS connected Connected to burn.net (2001:19f0:5c01:19a3:45:76:18:80) port 80 (#0) Closing connection #0
Harlan Stenn
2022-Dec-20 00:14 UTC
[Nut-upsuser] Compiling on Solaris 8 sparc - configure errors
I remember taking great pains with issues like these for NTP. All of the configure machinations are still in there - if ntp-4.2.8p15 builds and runs, then the configure-related bits should hold the answers. H On 12/19/2022 6:25 AM, Jim Klimov via Nut-upsuser wrote:> Maybe also try strace, truss and the likes to see what syscalls it > makes? e.g. falls on read/select?.. > > Jim > > On Sun, Dec 18, 2022, 23:04 vom513 via Nut-upsuser > <nut-upsuser at alioth-lists.debian.net > <mailto:nut-upsuser at alioth-lists.debian.net>> wrote: > > Debug doesn?t seem to say much: > > [root at ss20 ~]# LD_LIBRARY_PATH=/usr/local/ups/lib > /usr/local/ups/sbin/upsmon -DDDDDDDDDDDD > Network UPS Tools upsmon 2.8.0 > ? ?0.000000? ? ?Failed to read pid from /var/run/upsmon.pid > ? ?0.008469? ? ?Could not parse PID file to see if previous upsmon > instance is already running! > > ? ?0.024417? ? ?UPS: ups at 192.68.64.30 <mailto:ups at 192.68.64.30> > (secondary) (power value 1) > ? ?0.038074? ? ?Using power down flag file /etc/killpower > ? ?0.053368? ? ?[D1] debug level is '12' > ? ?0.062147? ? ?[D1] debug level is '12' > ? ?0.263514? ? ?upsmon parent: read > > It exits immediately as well. > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > <mailto:Nut-upsuser at alioth-lists.debian.net> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser > <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser> > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser