Trouble with jtop Service on Xavier NX 8GB Devkit

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hello,

I’ve been encountering an issue with the jtop service on my Xavier NX 8GB Devkit device. Despite restarting it whenever it stops, it continues to do so intermittently. Whenever I attempt to run jtop when it stops, I receive the following message:

The jtop.service is not active. Please run: sudo systemctl restart jtop.service

I suspect that high CPU usage might be the reason, causing the service to stop due to insufficient resources. The Jetpack version I’m using is 5.0.2, and jtop version is 4.2.6. How can I prevent the jtop service from stopping?

Looking forward to your suggestions and insights.

Best regards,
Ugur

3

Hi ugur4,

It seems you are using Xavier NX devkit with JP5.0.2.
Could you update to the latest JP5.1.3(R35.5.0) to verify?

What are you running on the board to cause high CPU usage?
Could you share the detailed steps how do you reproduce the issue?

4

Thank you for your quick response.
Unfortunately, upgrading to the latest jetpack does not help me since I need to test my software in this version.
I use an intelligent video analytics (IVA) software that causes high CPU usage.
Steps to reproduce:

  1. I log in to my account.
  2. Start my IVA software and start an inference job
  3. The software also displays the metrics of the device such as CPU, GPU usage, temperature etc. I can see the live metrics change
  4. After a while, which I can describe as minutes, the metrics freezes, and when I type jtop command on terminal to see the jtop results on terminal, I get the warning
The jtop.service is not active.
Please run: sudo systemctl restart jtop.service

Best.

5

Please run the following command to check the status of jtop.service.

$ sudo systemctl status jtop.service
6

Here is the output:

● jtop.service - jtop service
     Loaded: loaded (/etc/systemd/system/jtop.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Mon 2024-05-13 07:05:15 +03; 4h 22min ago
    Process: 2726 ExecStart=/usr/local/bin/jtop --force (code=exited, status=0/SUCCESS)
   Main PID: 2726 (code=exited, status=0/SUCCESS)

May 13 07:05:14 openzeka-desktop jtop[2759]:     table = [self.get_process_info(prc[0], prc[3], prc[2], uptime) for prc in table]
May 13 07:05:14 openzeka-desktop jtop[2759]:   File "/usr/local/lib/python3.8/dist-packages/jtop/core/processes.py", line 136, in <listcomp>
May 13 07:05:14 openzeka-desktop jtop[2759]:     table = [self.get_process_info(prc[0], prc[3], prc[2], uptime) for prc in table]
May 13 07:05:14 openzeka-desktop jtop[2759]:   File "/usr/local/lib/python3.8/dist-packages/jtop/core/processes.py", line 92, in get_process_info
May 13 07:05:14 openzeka-desktop jtop[2759]:     stat = cat(os.path.join('/proc', pid, 'stat')).split()
May 13 07:05:14 openzeka-desktop jtop[2759]:   File "/usr/local/lib/python3.8/dist-packages/jtop/core/common.py", line 109, in cat
May 13 07:05:14 openzeka-desktop jtop[2759]:     with open(path, 'r') as f:
May 13 07:05:14 openzeka-desktop jtop[2759]: FileNotFoundError: [Errno 2] No such file or directory: '/proc/10814/stat'
May 13 07:05:15 openzeka-desktop jtop[2726]: [INFO] jtop.service - Service closed
May 13 07:05:15 openzeka-desktop systemd[1]: jtop.service: Succeeded.

Best,
Ugur

7

It seems your jtop.service is not working.

Do you mean that jtop could work as expected after reboot, but it will stop working after you run your application with high CPU usage?

8

Hi @ugur4

Thank you for your message. I’m the creator and maintainer.

Looking at your error seems to be an error in decoding the process info.

This error is happening only in your specific use case or always?

BTW: I will fix it for the next release

Best,
Raffaello

Hint: if you are working with jtop open a new github issue, help me to track these bugs

1 Like
9

Unfortunately I often encounter this problem, but more often when I am using my IVA software. Thank you for taking this problem into your plans for next release.
Best,
Ugur

1 Like
11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.