Installer hangs and service cannot be restarted

[nsercproject]

Describe the bug

The installer hangs while building on new Orin NX-based systems, using ConnetcTech's Photon carrier board (NGX020), L4T r35.4.1 BSP, Ubuntu 20.04, JP 5.1.2

To Reproduce

Steps to reproduce the behaviour:

1. Run the following at the terminal: sudo pip3 install -U jetson-stats
2. The process hangs while the output to the terminal is: Building wheel for jetson-stats (setup.py) ... -
3. Try installing with a fresh download: sudo pip3 install --no-cache-dir -v -U jetson-stats
4. The process hangs while printing: INFO:jtop.service: - ENABLE jtop.service
5. In both cases running jtop gives the following:
   The jtop.service is not active. Please run:
sudo systemctl restart jtop.service
6. Running the last line hangs. The service is enabled but inactive and can't be restarted.
7. Rebooting does not change the results of running all or some of the above commands

Screenshots

Expected behaviour

The installation should complete as it used to in previous systems using the same Photon board but the TX2 NX SoM. Actually this was working a month or so ago.

Additional context

The installer for jtop has worked well in two more units, but the behaviour has been inconsistent. In one it worked straight out of the box, in a second it worked after a few reboots. I cannot make the current one work. Even if it starts working tomorrow, what is it getting in the way of the installation? jtop is an excellent tool, however, installing it has been a hit or miss in this release of L4T. Hopefully, it will get more attention as more people run into it or am I the only one?

Board

Output from jetson_release -v:

• jetson-stats version: 4.2.8
• P-Number: p3767-0000
• Module: NVIDIA Jetson Orin NX (16GB ram)
• Jetpack: 5.1.2-b104
• L4T: R35 (release), REVISION: 4.1

Log from jtop.service

Attach here the output from: journalctl -u jtop.service -n 100 --no-pager

$ journalctl -u jtop.service -n 100 --no-pager
-- Logs begin at Tue 2023-11-21 14:10:21 MST, end at Thu 2024-08-15 17:55:01 MDT. --
Aug 15 17:05:42 orin-4 systemd[1]: Failed to start jtop.service.
Aug 15 17:06:47 orin-4 systemd[1]: Failed to start jtop.service.
Aug 15 17:18:35 orin-4 systemd[1]: Failed to start jtop.service.
Aug 15 17:21:02 orin-4 systemd[1]: Failed to start jtop.service.

Log from jetson-stats installation

Attach here the output from: sudo -H pip3 install --no-cache-dir -v -U jetson-stats

sudo_H_install__no_cache_jetson_stats.txt

RAW Data

File from jtop --error-log attached

[vladmosoiu98]

I am currently having the same software setup (only using the Orin Nano DevKit) and encountered the exact same issue.

Digging around the issues on this topic, I found a solution.
Basically when the install process is stuck at INFO:jtop.service: - ENABLE jtop.service in a separate terminal edit the jtop.service file that was just copied by the installer in /etc/systemd/system/ and remove After=multi-user.target

Save it, then reload the systemd services with systemctl daemon-reload and restart the jtop.service

Now it should properly start and the installation to be finished.

I am still currently investigating why this happens, since the After=multi-user.target is a check has been added for almost a year and did not cause problems so far. Some users suggested it might be due to some issues related to the GUI coloring, but I am not sure.

The main source for this fix was this issue if it helps in any case: #428 (comment)

Hopefully this might provide some insights for @rbonghi for a quickfix 😄

[rbonghi]

Hi all!
Thank you for your posts! I will do it soon this week!

Quite exceptional busy this week at work and I didn't have time to work on jetson-stats

[vladmosoiu98]

No worries, thanks for checking it.

After further inspection, it seems that multi-user.target depends to the time-sync.target which in my case had some configuration issue due to my chrony setup for a clock sync between multiple Orins.

So the quickfix I mentioned might not truly be universal, you should first check the target services status with systemctl list-units --type=target to make sure is related to this or not.

[nsercproject]

[like] Pablo Adames reacted to your message:

…

________________________________ From: Vlad Mosoiu ***@***.***> Sent: Wednesday, August 21, 2024 11:54:27 AM To: rbonghi/jetson_stats ***@***.***> Cc: Pablo Adames ***@***.***>; Author ***@***.***> Subject: Re: [rbonghi/jetson_stats] Installer hangs and service cannot be restarted (Issue #563) I am currently having the same setup and encountered the exact same issue. Digging around the issues on this topic, I found a solution. Basically when the install process is stuck at INFO:jtop.service: - ENABLE jtop.service in a separate terminal edit the jtop.service file that was just copied by the installer in /etc/systemd/system/ and remove After=multi-user.target Save it, then reload the systemd services with systemctl daemon-reload and restart the jtop.service Now it should properly start and the installation to be finished. I am still currently investigating why this happens, since the After=multi-user.target is a check has been added for almost a year and did not cause problems so far. Some users suggested it might be due to some issues related to the GUI coloring, but I am not sure. The main source for this fix was this issue if it helps in any case: #428 (comment)<#428 (comment)> Hopefully this might provide some insights for @rbonghi<https://github.com/rbonghi> for a quickfix 😄 — Reply to this email directly, view it on GitHub<#563 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5KQZ7EUBHQ2EP7DMFMI63TZSR5XHAVCNFSM6AAAAABMTDUJWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBRHA3DOOBQHA>. You are receiving this because you authored the thread.Message ID: ***@***.***>