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

CSE service on Photon 2 host does not automatically start after reboot #95

Open
bsmr opened this issue Jul 19, 2018 · 2 comments
Open

Comments

@bsmr
Copy link

bsmr commented Jul 19, 2018

I installed the CSE service on a Photon 2 based host. It starts without any problems, when I do this manually (systemctl start cse.service), but it won't automatically start after a reboot.

That's why I also submitted a pull-request (#96) for some small changes to cse.service. But even with those changes, it still doesn't autostart after a reboot.

When I do a systemctl list-dependencies cse.service, it marks systemd-modules-load.service with a red dot. Running systemctl status systemd-modules-load.service gives the following output:

root@vcd-cse01-svc [ ~ ]# systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-07-19 10:18:40 UTC; 1h 9min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
 Main PID: 595 (code=exited, status=1/FAILURE)
      CPU: 3ms

Jul 19 10:18:40 vcd-cse01-svc.adestis.net systemd[1]: Starting Load Kernel Modules...
Jul 19 10:18:40 vcd-cse01-svc.adestis.net systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Jul 19 10:18:40 vcd-cse01-svc.adestis.net systemd[1]: Failed to start Load Kernel Modules.
Jul 19 10:18:40 vcd-cse01-svc.adestis.net systemd[1]: systemd-modules-load.service: Unit entered failed state.
Jul 19 10:18:40 vcd-cse01-svc.adestis.net systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

Issuing systemctrl start cse.service runs it without a problem ... until the next reboot.

Any ideas what this is causing this problem? Or what I should change, please?

@sahithi
Copy link
Collaborator

sahithi commented Sep 5, 2018

I have seen this error in Ubuntu sometime ago. I will add this issue into our internal Jira. I will update again once we get to this issue in our backlog.

@tsugliani
Copy link
Contributor

@sahithi I've tested @bsmr PR, it works well on my setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants