Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
bcfriesen opened this issue Oct 28, 2021 · 5 comments
Open

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

bcfriesen opened this issue Oct 28, 2021 · 5 comments

Comments

@bcfriesen
Copy link

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.

@pakmarkthub
Copy link
Collaborator

Hi @bcfriesen,

Thank you for reporting this issue.

Currently, SLES is not in our support matrix. Thus, we have never QA'd it on that platform. Nevertheless, let's me put this in our request list.

@drossetti
Copy link
Member

@bcfriesen has this been fixed?

@bcfriesen
Copy link
Author

@bcfriesen has this been fixed?

Hi @drossetti - thanks for the heads up! Sorry I missed the MR that went in back in November that fixed this. I'll try this on our test system in the near future and let you know if it works.

@FlorianDeconinck
Copy link

Hello,

Looking to also build GDR_COPY on SLES (12 or 15). @bcfriesen did you get the chance to test the fix?

Still no official support for SLES @drossetti ?

Thank you.

@cponder
Copy link

cponder commented Mar 29, 2023

It's been almost 2 years since the last official release.
Could you tag a release-candidate with SLES support?

@drossetti drossetti added this to the v2.4 milestone May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants