Non-existent User (1000) endlessly restarting high cpu consuming app

[HamishMacEwan]

Describe the bug 1000 15319 0.1 0.9 63544404 35988 ? Sl Jun26 81:21 node --unhandled-rejections=strict /home/node/app/accounts/index.js

This is one instance of a task that sits at the top of btop. It then stops/crashes and is replaced by another instance.

Expected behavior The user has no name, there is no /home/node/ directory

It is expected not to exist.

Desktop (please complete the following information):

• Browser Chrome
• Version 103.0.5060.134 (Official Build) (64-bit)

MyNode hardware (please complete the following information):

• Device: Raspi400
• Version 0.2.57

Additional context

uname -a
Linux flat6 5.10.103-v8+ #1529 SMP PREEMPT Tue Mar 8 12:26:46 GMT 2022 aarch64 GNU/Linux

Other tasks running under user id 1000

ps -U 1000 -u 1000 u
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
1000      4358  0.0  0.0   2556  1140 ?        Ss   Jun26  34:48 /bin/bash /home/node/app/restart.sh
1000      5770 76.0  1.3 10791588 53088 ?      Rl   16:47   0:01 node --unhandled-rejections=strict /home/node/app/track
1000      5781  0.0  0.0   1648     4 ?        S    16:47   0:00 sleep 1
1000     10194  0.0  0.2 302804  7920 ?        Ssl  Jun26   1:21 /usr/local/bin/node /usr/local/lib/node_modules/forever
1000     10270  0.0  0.1 302896  7448 ?        Ssl  Jun26   1:20 /usr/local/bin/node /usr/local/lib/node_modules/forever
1000     10310  0.0  0.1 303024  7864 ?        Ssl  Jun26   1:31 /usr/local/bin/node /usr/local/lib/node_modules/forever
1000     10473  0.3  0.7 309728 30648 ?        Ssl  Jun26 167:05 /usr/local/bin/node /usr/local/lib/node_modules/forever
1000     15317  0.0  0.8 21291012 34184 ?      Sl   Jun26   5:33 node --unhandled-rejections=strict /home/node/app/pusht
1000     15318  0.0  0.9 21292508 35904 ?      Sl   Jun26   4:54 node --unhandled-rejections=strict /home/node/app/pusht
1000     15319  0.1  0.9 63544404 36236 ?      Sl   Jun26  81:22 node --unhandled-rejections=strict /home/node/app/accou

[tehelsper]

It could be a docker container. Can you run docker stats to see if anything sticks out?

[HamishMacEwan]

Here's a snapshot. Not quite sure what I'm looking for but the CPU% on nodejsis often much higher than this figure:

CONTAINER ID   NAME      CPU %     MEM USAGE / LIMIT   MEM %     NET I/O           BLOCK I/O         PIDS
eb8b06163de4   webssh2   0.00%     0B / 0B             0.00%     1.98MB / 28.6kB   50.4MB / 16.4kB   18
f7a2e6ff24ea   nginx     0.00%     0B / 0B             0.00%     20.3kB / 27.4kB   5.45MB / 0B       5
8b1286e13526   nodejs    190.52%   0B / 0B             0.00%     3.22GB / 2.73GB   8.23GB / 27.1GB   98
32d3048e9c19   tor       0.05%     0B / 0B             0.00%     516MB / 416MB     8.69GB / 1.36GB   2
c065a9574054   db        0.03%     0B / 0B             0.00%     644MB / 493MB     2.28GB / 16.4kB   10

[tehelsper]

So, nodejs is Dojo. Is that enabled? It sounds like it may be doing something or have an issue. Can you disable Dojo to see if it gets better?

[HamishMacEwan]

Sorry I didn't get back to this sooner.

Never had Dojo enabled ever.