Hi,
Thanks Jim! Here is more system information from the commands you mentioned.
Kari
root@fricka:~# lsof -p 1716171
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
upssched 1716171 root cwd DIR 8,2 4096 2 /
upssched 1716171 root rtd DIR 8,2 4096 2 /
upssched 1716171 root txt REG 8,2 39240 21762148
/usr/sbin/upssched
upssched 1716171 root mem REG 8,2 1922136 21764230
/usr/lib/x86_64-linux-gnu/libc.so.6
upssched 1716171 root mem REG 8,2 210968 21764476
/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
upssched 1716171 root 0u CHR 1,3 0t0 4 /dev/null
upssched 1716171 root 1u CHR 1,3 0t0 4 /dev/null
upssched 1716171 root 2u CHR 1,3 0t0 4 /dev/null
upssched 1716171 root 3u unix 0x00000000eeb52825 0t0 16427010
type=DGRAM (CONNECTED)
upssched 1716171 root 4r REG 8,2 545 39847858
/etc/nut/upssched.conf
upssched 1716171 root 5u unix 0x00000000a035b466 0t0 16426351
type=STREAM (UNCONNECTED)
upssched 1716171 root 6u unix 0x0000000050820b2b 0t0 16426352
type=STREAM (UNCONNECTED)
upssched 1716171 root 7u unix 0x00000000447aac0e 0t0 16424724
/var/run/nut/upssched.pipe type=STREAM (CONNECTED)
upssched 1716171 root 10u unix 0x00000000d7bd8088 0t0 16424722
/var/run/nut/upssched.pipe type=STREAM (LISTEN)
root@fricka:~# ps -ef|grep ups
root 1425 1 0 Jun11 ? 00:00:00 sshd: /usr/sbin/sshd -D
[listener] 0 of 10-100 startups
root 1156722 1 0 00:00 ? 00:00:00 /usr/sbin/cupsd -l
root 1156723 1 0 00:00 ? 00:00:00 /usr/sbin/cups-browsed
lp 1156748 1156722 0 00:00 ? 00:00:00 /usr/lib/cups/notifier/dbus
dbus://
nut 1713117 1 0 14:30 ? 00:00:00 /lib/nut/dummy-ups -a
heartbeat
nut 1713154 1 0 14:30 ? 00:00:00 /lib/nut/usbhid-ups -a
eaton5s
nut 1713155 1 0 14:30 ? 00:00:00 /lib/nut/upsd -F
root 1713156 1 0 14:30 ? 00:00:00 /lib/nut/upsmon -F
root 1713157 1713156 0 14:30 ? 00:00:00 /lib/nut/upsmon -F
root 1716171 1 99 14:35 ? 00:05:10 /sbin/upssched UPS
heartbeat@localhost: On battery.
root 1719510 1550505 0 14:40 pts/2 00:00:00 grep ups
root@fricka:~# fuser /var/run/nut/upssched.pipe
/run/nut/upssched.pipe: 1716171
root@fricka:/proc/1716171/fd# ls -la
total 0
dr-x------ 2 root root 0 Jun 13 14:36 .
dr-xr-xr-x 9 root root 0 Jun 13 14:35 ..
lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null
lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null
lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]'
lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null
lrwx------ 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]'
lrwx------ 1 root root 64 Jun 13 14:36 7 -> 'socket:[16424724]'
________________________________
From: Jim Klimov <[email protected]>
Sent: Tuesday, June 13, 2023 14:17
To: Kari Lempiäinen <[email protected]>
Cc: Arnaud Quette via Nut-upsuser <[email protected]>;
nut-upsdev <[email protected]>; Dimitris Economou
<[email protected]>
Subject: Re: [Nut-upsuser] Upssched 100% CPU after updating Debian 12
FWIW, cross-posted the issue to NUT GitHub tracker:
https://github.com/networkupstools/nut/issues/1964
Jim
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
