/etc/init.d/gdrcopy fails to start on SLES

Open
  • Is something wrong?
#215 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
linux, shell
Domain
devops, operating-systems

Research direction

Inspect the RPM-installed /etc/init.d/gdrcopy script, especially lines 17 and 95, and compare its init functions with SLES 15 SP1 conventions. Reproduce the boot or systemctl failure; done means the gdrcopy service starts without missing-function errors or a failed systemd state.

Written by the indexing model from the issue text.

Description

bug enhancement

Greetings,

on a SLES 15 SP1 system with gdrcopy installed via RPM, one observes the following during boot:

Oct 15 19:34:26 localhost systemd[1]: Starting LSB: Startup/shutdown script for GDRcopy kernel-mode driver...
Oct 15 19:34:26 localhost gdrcopy[6233]: /etc/init.d/gdrcopy: line 17: /etc/rc.d/init.d/functions: No such file or directory
Oct 15 19:34:26 localhost gdrcopy[6233]: Checking required modules: /etc/init.d/gdrcopy: line 95: success: command not found
Oct 15 19:34:26 localhost gdrcopy[6233]: /etc/init.d/gdrcopy: line 95: failure: command not found
Oct 15 19:34:26 localhost systemd[1]: gdrcopy.service: Control process exited, code=exited status=127
Oct 15 19:34:26 localhost systemd[1]: Failed to start LSB: Startup/shutdown script for GDRcopy kernel-mode driver.
Oct 15 19:34:26 localhost systemd[1]: gdrcopy.service: Unit entered failed state.
Oct 15 19:34:26 localhost systemd[1]: gdrcopy.service: Failed with result 'exit-code'.

which leads to this entry in systemctl --failed:

localhost:~ # systemctl --failed
  UNIT                         LOAD   ACTIVE SUB    DESCRIPTION
● gdrcopy.service              loaded failed failed LSB: Startup/shutdown script for GDRcopy kernel-mode driver

The problem is that the gdrcopy service is trying to read /etc/rc.d/init.d/functions, which I believe is part of RHEL but not SLES.

This error appears to be functionally harmless, and can be worked around (one can simply delete the /etc/init.d/gdrcopy file), but I wonder if it might be possible to adjust the gdrcopy init.d configuration to work on SLES, or at least to avoid this constantly failed process.

Thanks very much.

Dominant language
C
Stars
1.4k
Forks
198
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/gdrcopy

All issues in NVIDIA/gdrcopy

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.