0 bytes
> read as an error, everything worked fine.
>
>
>
> Best regards,
>
> Kari
>
>
>
> *From: *Jim Klimov
> *Date: *Tuesday, 13. June 2023 at 18.36
> *To: *Kari Lempiäinen
> *Cc: *Arnaud Quette via Nut-upsuser ,
> nut-upsdev , Dimitris Economo
Any help from this?
Best regards,
Kari
________________
From: Jim Klimov
Sent: Tuesday, June 13, 2023 00:35
To: Kari Lempiäinen
Cc: Arnaud Quette via Nut-upsuser
Subject: Re: [Nut-upsuser] Upssched 100% CPU after updating Debian 12
Hello,
Thank you for the report and I
rwx-- 1 root root 64 Jun 13 14:36 3 -> 'socket:[16427010]'
>> lr-x-- 1 root root 64 Jun 13 14:36 4 -> /etc/nut/upssched.conf
>> lrwx-- 1 root root 64 Jun 13 14:36 5 -> 'socket:[16426351]'
>> lrwx-- 1 root root 64 Jun 13 14:36 6 -> 'socket:[16426352]'
>> lr
- 1 root root 64 Jun 13 14:36 6 -> 'socket:[16426352]'
> lrwx-- 1 root root 64 Jun 13 14:36 7 -> 'socket:[16424724]'
>
>
>
> ----------
> *From:* Jim Klimov
> *Sent:* Tuesday, June 13, 2023 14:17
> *To:* Kari Lempiäinen
> *Cc:* Ar
'
lrwx-- 1 root root 64 Jun 13 14:36 7 -> 'socket:[16424724]'
From: Jim Klimov
Sent: Tuesday, June 13, 2023 14:17
To: Kari Lempiäinen
Cc: Arnaud Quette via Nut-upsuser ;
nut-upsdev ; Dimitris Economou
Subject: Re: [Nut-upsuser] Upssched 100% CPU aft
FWIW, cross-posted the issue to NUT GitHub tracker:
https://github.com/networkupstools/nut/issues/1964
Jim
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
FWIW, I wonder if this is a fallout of PR #1274 :
https://github.com/networkupstools/nut/pull/1274/files
and specifically
https://github.com/networkupstools/nut/commit/550064930e369fb3a322c3b288b4acf53532
which added a `sock_read()` loop continuation effectively if `pconf_char()`
returned 0.
Thanks for the interesting puzzle to crunch!
Looking at these few bread-crumbs, I wager an educated guess that this
loops in `sendcmd()` (where CLI child processes talk to a daemonized copy
which tracks the timers for events), around here:
Hello,
Thank you for the report and I don't recall any similar issues.
Unfortunately, upssched did not have any "native" enablement of debug
verbosity in 2.8.0 and older releases (some added with
https://github.com/networkupstools/nut/pull/1864 recently), so maybe the
best way to get more
Hi,
I have been running nut successfully for a long time with my Debian 11 server.
I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13
to 2.8.0-7. I noticed that after upgrade there was a upssched process running
and taking 100% cpu time.
I checked if there were any
10 matches
Mail list logo
