June 3, 20206 yr Hello, since a week ago I started to have an issue regarding circusd process. It is using one whole cpu. top - 09:17:51 up 21:36, 1 user, load average: 1.16, 1.28, 1.39 Tasks: 386 total, 2 running, 384 sleeping, 0 stopped, 0 zombie %Cpu(s): 10.1 us, 3.3 sy, 0.0 ni, 85.8 id, 0.7 wa, 0.0 hi, 0.1 si, 0.0 st MiB Mem : 32195.9 total, 9696.9 free, 3399.8 used, 19099.2 buff/cache top - 09:27:35 up 21:46, 1 user, load average: 1.56, 1.41, 1.39 Tasks: 375 total, 2 running, 373 sleeping, 0 stopped, 0 zombie %Cpu(s): 10.3 us, 3.6 sy, 0.0 ni, 84.3 id, 1.5 wa, 0.0 hi, 0.3 si, 0.0 st MiB Mem : 32195.9 total, 10366.5 free, 1979.0 used, 19850.4 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 29067.6 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 24329 2001 20 0 214416 27752 8252 R 100.3 0.1 1181:40 circusd 6785 root 20 0 1223916 185748 1200 S 0.7 0.6 46:39.19 shfs 6930 root 0 -20 0 0 0 S 0.7 0.0 5:25.81 loop2 12188 root 20 0 109104 12876 4736 S 0.7 0.0 4:47.88 containerd-shim 24343 2001 20 0 214992 29648 11764 S 0.7 0.1 15:05.83 python3 16 root 20 0 0 0 0 S 0.3 0.0 0:00.92 ksoftirqd/1 1432 root 39 19 0 0 0 S 0.3 0.0 0:05.45 kipmi0 Help please. Best regards André Rung.
June 3, 20206 yr I suspect that circus is coming from a container or you've installed it via NerdPack or something. You're going to have to figure out which and then diagnose and/or post in the appropriate application's support thread for more help.
June 3, 20206 yr Author Hi Squid, I've just checked NerdPack and it's not there... when you say container, do you mean docker container? I have stopped VM manager and docker... circusd went away... after restart I got this: root@Tower:/usr/bin# ps -ef | grep -i circus root 3563 28913 0 11:40 pts/1 00:00:00 grep -i circus 2001 14556 4817 4 11:00 ? 00:01:54 /home/fermentrack/venv/bin/python3 /home/fermentrack/venv/bin/circusd --daemon /home/fermentrack/fermentrack/circus.ini 2001 14566 14556 1 11:00 ? 00:00:41 /home/fermentrack/venv/bin/python3 -c from circus import stats; stats.main() --endpoint tcp://127.0.0.1:5555 --pubsub tcp://127.0.0.1:5556 --statspoint tcp://127.0.0.1:5557 --log-level ERROR --log-output /home/fermentrack/fermentrack/log/circusd.log But circusd is not at 100% now... so... you was right, something inside Fermentrack container... I'll keep an eye on it. Thanks, André Rung Edited June 3, 20206 yr by Gnur
Archived
This topic is now archived and is closed to further replies.