[BUG] sudo systemctl restart nv_nvsciipc_init.service failed without modifying any content of nvsciipc.cfg

Required Info:

  • Software Version
    DRIVE OS 6.0.8.1
  • Target OS
    Linux
  • SDK Manager Version
    1.9.2.10884
  • Host Machine Version
    native Ubuntu Linux 20.04 Host installed with DRIVE OS DOCKER Containers

Describe the bug

according to the doc of cgf Compute Graph Framework SDK Reference: Demo Pipeline Introduction we need to reinit the nvsciipc when the nvsciipc.cfg file is updated.

Please make sure there are 32 slots allocated inside the nvsciipc.cfg file. After the file has been updated, it is necessary to reboot the system for changes to take effect. To make sure the changes has been properly applied, please check with the following command:
sudo service nv_nvsciipc_init status should print message below:
‍nv_nvsciipc_init.service - NvSciIpc initialization
Loaded: loaded (/lib/systemd/system/nv_nvsciipc_init.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2021-06-16 20:36:43 UTC; 52min ago
Process: 758 ExecStart=/bin/sh /etc/systemd/scripts/nv_nvsciipc_init.sh (code=exited, status=0/SUCCESS)
Main PID: 758 (code=exited, status=0/SUCCESS)
If not, please double check your nvsciipc.cfg file.

we found that /etc/systemd/scripts/nv_nvsciipc_init.sh always return error.

To Reproduce

sudo service nv_nvsciipc_init status
# good

sudo systemctl restart nv_nvsciipc_init.service
# report error
Job for nv_nvsciipc_init.service failed because the control process exited with error code.
See "systemctl status nv_nvsciipc_init.service" and "journalctl -xe" for details.

Expected behavior

sudo systemctl restart nv_nvsciipc_init.service should works well.

Actual behavior

the service report failed after manual restarting the service

systemctl is-failed nv_nvsciipc_init.service
failed

Additional context

reboot the machine should fix the failure

Dear @lizhensheng,
I can reproduce the issue. I will check internally and get back to you.

1 Like

Dear @lizhensheng,
I can see the recommendation is to reboot the system after file update in documentation. Are you asking why reboot is needed instead of restarting the service?

Yes, I report the issue to the forum.