search for: lempi

...ecified directly that it was an error situation. My server code looped in a thread hogging CPU. When I modified the code to treat 0 bytes read as an error, everything worked fine. Best regards, Kari From: Jim Klimov <jimklimov+nut at gmail.com> Date: Tuesday, 13. June 2023 at 18.36 To: Kari Lempi?inen <kari.lempiainen at summerday.net> Cc: Arnaud Quette via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>, nut-upsdev <nut-upsdev at alioth-lists.debian.net>, Dimitris Economou <dimitris.s.economou at gmail.com> Subject: Re: [Nut-upsuser] Upssched 100% CPU after upd...

...ecified directly that it was an error situation. My server code looped in a thread hogging CPU. When I modified the code to treat 0 bytes read as an error, everything worked fine. Best regards, Kari From: Jim Klimov <jimklimov+nut at gmail.com> Date: Tuesday, 13. June 2023 at 18.36 To: Kari Lempi?inen <kari.lempiainen at summerday.net> Cc: Arnaud Quette via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>, nut-upsdev <nut-upsdev at alioth-lists.debian.net>, Dimitris Economou <dimitris.s.economou at gmail.com> Subject: Re: [Nut-upsuser] Upssched 100% CPU after upd...

...lhost' we were launched to process? 0.000096 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'heartbeat at localhost' UPSNAME we were launched to process 0.000104 [D1] parse_at: processing START-TIMER $ Jim On Tue, Jun 13, 2023 at 1:58?PM Kari Lempi?inen < kari.lempiainen at summerday.net> wrote: > Hi, > > Thanks Jim! Here is more system information from the commands you > mentioned. > > Kari > > root at fricka:~# lsof -p 1716171 > lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs...

...lhost' we were launched to process? 0.000096 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'heartbeat at localhost' UPSNAME we were launched to process 0.000104 [D1] parse_at: processing START-TIMER $ Jim On Tue, Jun 13, 2023 at 1:58?PM Kari Lempi?inen < kari.lempiainen at summerday.net> wrote: > Hi, > > Thanks Jim! Here is more system information from the commands you > mentioned. > > Kari > > root at fricka:~# lsof -p 1716171 > lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs...

...t:[16426351]' lrwx------ 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 <jimklimov+nut at gmail.com> Sent: Tuesday, June 13, 2023 14:17 To: Kari Lempi?inen <kari.lempiainen at summerday.net> Cc: Arnaud Quette via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>; nut-upsdev <nut-upsdev at alioth-lists.debian.net>; Dimitris Economou <dimitris.s.economou at gmail.com> Subject: Re: [Nut-upsuser] Upssched 100% CPU after upd...

...t:[16426351]' lrwx------ 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 <jimklimov+nut at gmail.com> Sent: Tuesday, June 13, 2023 14:17 To: Kari Lempi?inen <kari.lempiainen at summerday.net> Cc: Arnaud Quette via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>; nut-upsdev <nut-upsdev at alioth-lists.debian.net>; Dimitris Economou <dimitris.s.economou at gmail.com> Subject: Re: [Nut-upsuser] Upssched 100% CPU after upd...

...0.000096 [D1] parse_at: 'heartbeat at localhost' in AT command > matched the 'heartbeat at localhost' UPSNAME we were launched to process > 0.000104 [D1] parse_at: processing START-TIMER > > $ > > Jim > > > On Tue, Jun 13, 2023 at 1:58?PM Kari Lempi?inen < > kari.lempiainen at summerday.net> wrote: > >> Hi, >> >> Thanks Jim! Here is more system information from the commands you >> mentioned. >> >> Kari >> >> root at fricka:~# lsof -p 1716171 >> lsof: WARNING: can't stat() fu...

...0.000096 [D1] parse_at: 'heartbeat at localhost' in AT command > matched the 'heartbeat at localhost' UPSNAME we were launched to process > 0.000104 [D1] parse_at: processing START-TIMER > > $ > > Jim > > > On Tue, Jun 13, 2023 at 1:58?PM Kari Lempi?inen < > kari.lempiainen at summerday.net> wrote: > >> Hi, >> >> Thanks Jim! Here is more system information from the commands you >> mentioned. >> >> Kari >> >> root at fricka:~# lsof -p 1716171 >> lsof: WARNING: can't stat() fu...

...blocks, 128 in each of them). Nothing else in the strace log, just read and pselect lines for the short time I let strace to run. Any help from this? Best regards, Kari ________________________________ From: Jim Klimov <jimklimov+nut at gmail.com> Sent: Tuesday, June 13, 2023 00:35 To: Kari Lempi?inen <kari.lempiainen at summerday.net> Cc: Arnaud Quette via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> Subject: Re: [Nut-upsuser] Upssched 100% CPU after updating Debian 12 Hello, Thank you for the report and I don't recall any similar issues. Unfortunately, upssc...

...blocks, 128 in each of them). Nothing else in the strace log, just read and pselect lines for the short time I let strace to run. Any help from this? Best regards, Kari ________________________________ From: Jim Klimov <jimklimov+nut at gmail.com> Sent: Tuesday, June 13, 2023 00:35 To: Kari Lempi?inen <kari.lempiainen at summerday.net> Cc: Arnaud Quette via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> Subject: Re: [Nut-upsuser] Upssched 100% CPU after updating Debian 12 Hello, Thank you for the report and I don't recall any similar issues. Unfortunately, upssc...

...> conn_add(pipefd) or sock_read(conn) with short-lived child processes (command-line launched from `upsmon`) parsing the configuration to pick the part relevant to them per envvars, and talk to the daemon (fork one if needed) to start/cancel the timers. Jim On Tue, Jun 13, 2023 at 8:33?AM Kari Lempi?inen < kari.lempiainen at summerday.net> wrote: > Hi, > > I ran the strace command while upssched was 100% CPU hungry. This is what > I got: > > 1686633611.702798 read(7, "", 1) = 0 <0.000004> > 1686633611.702816 read(7, "", 1) = 0...

...> conn_add(pipefd) or sock_read(conn) with short-lived child processes (command-line launched from `upsmon`) parsing the configuration to pick the part relevant to them per envvars, and talk to the daemon (fork one if needed) to start/cancel the timers. Jim On Tue, Jun 13, 2023 at 8:33?AM Kari Lempi?inen < kari.lempiainen at summerday.net> wrote: > Hi, > > I ran the strace command while upssched was 100% CPU hungry. This is what > I got: > > 1686633611.702798 read(7, "", 1) = 0 <0.000004> > 1686633611.702816 read(7, "", 1) = 0...

...d(conn) > with short-lived child processes (command-line launched from `upsmon`) > parsing the configuration to pick the part relevant to them per envvars, > and talk to the daemon (fork one if needed) to start/cancel the timers. > > Jim > > On Tue, Jun 13, 2023 at 8:33?AM Kari Lempi?inen < > kari.lempiainen at summerday.net> wrote: > >> Hi, >> >> I ran the strace command while upssched was 100% CPU hungry. This is what >> I got: >> >> 1686633611.702798 read(7, "", 1) = 0 <0.000004> >> 1686633611.70281...

...d(conn) > with short-lived child processes (command-line launched from `upsmon`) > parsing the configuration to pick the part relevant to them per envvars, > and talk to the daemon (fork one if needed) to start/cancel the timers. > > Jim > > On Tue, Jun 13, 2023 at 8:33?AM Kari Lempi?inen < > kari.lempiainen at summerday.net> wrote: > >> Hi, >> >> I ran the strace command while upssched was 100% CPU hungry. This is what >> I got: >> >> 1686633611.702798 read(7, "", 1) = 0 <0.000004> >> 1686633611.70281...

...eartbeat at localhost' in AT command >> matched the 'heartbeat at localhost' UPSNAME we were launched to process >> 0.000104 [D1] parse_at: processing START-TIMER >> >> $ >> >> Jim >> >> >> On Tue, Jun 13, 2023 at 1:58?PM Kari Lempi?inen < >> kari.lempiainen at summerday.net> wrote: >> >>> Hi, >>> >>> Thanks Jim! Here is more system information from the commands you >>> mentioned. >>> >>> Kari >>> >>> root at fricka:~# lsof -p 1716171 &gt...

...eartbeat at localhost' in AT command >> matched the 'heartbeat at localhost' UPSNAME we were launched to process >> 0.000104 [D1] parse_at: processing START-TIMER >> >> $ >> >> Jim >> >> >> On Tue, Jun 13, 2023 at 1:58?PM Kari Lempi?inen < >> kari.lempiainen at summerday.net> wrote: >> >>> Hi, >>> >>> Thanks Jim! Here is more system information from the commands you >>> mentioned. >>> >>> Kari >>> >>> root at fricka:~# lsof -p 1716171 &gt...

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 changes to configuration file formats with nut upgrade and only differences I noticed were a terminology