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.

Sign up for GitHub

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

Jump to bottom

Incomplete OpenNebula service stop #3181

Closed
7 tasks
vholer opened this issue Apr 4, 2019 · 2 comments
Closed
7 tasks

Incomplete OpenNebula service stop #3181

vholer opened this issue Apr 4, 2019 · 2 comments
Assignees
@ospalax @christian7007
Labels
Category: Core & System Category: Packages Status: Accepted Type: Bug
Milestone
Release 6.4.3

Comments

@vholer
Copy link
Contributor

vholer commented Apr 4, 2019

Description
Sometimes it happens that the systemd service is reported as stopped, but oned remains running. This breaks the service start (or, restart) if it's following right after stop:

Apr 04 03:34:57 localhost systemd[1]: Starting OpenNebula Cloud Controller Daemon...
Apr 04 03:35:02 localhost systemd[1]: Started OpenNebula Cloud Controller Daemon.
Apr 04 03:36:20 localhost systemd[1]: Stopping OpenNebula Cloud Controller Daemon...
Apr 04 03:36:21 localhost systemd[1]: Stopped OpenNebula Cloud Controller Daemon.
Apr 04 03:36:21 localhost systemd[1]: opennebula.service: Found left-over process 29180 (oned) in control group while starting unit. Ignoring.
Apr 04 03:36:21 localhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 04 03:36:21 localhost systemd[1]: Starting OpenNebula Cloud Controller Daemon...
Apr 04 03:36:21 localhost systemd[1]: opennebula.service: Found left-over process 29180 (oned) in control group while starting unit. Ignoring.
Apr 04 03:36:21 localhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 04 03:37:55 localhost systemd[1]: opennebula.service: State 'stop-sigterm' timed out. Killing.
Apr 04 03:37:55 localhost systemd[1]: opennebula.service: Killing process 29180 (oned) with signal SIGKILL.
Apr 04 03:37:55 localhost systemd[1]: opennebula.service: Failed with result 'protocol'.
Apr 04 03:37:55 localhost systemd[1]: Failed to start OpenNebula Cloud Controller Daemon.
Apr 04 03:38:01 localhost systemd[1]: opennebula.service: Service RestartSec=5s expired, scheduling restart.
Apr 04 03:38:01 localhost systemd[1]: opennebula.service: Scheduled restart job, restart counter is at 1.
Apr 04 03:38:01 localhost systemd[1]: Stopped OpenNebula Cloud Controller Daemon.
Apr 04 03:38:01 localhost systemd[1]: Starting OpenNebula Cloud Controller Daemon...
Apr 04 03:38:05 localhost systemd[1]: Started OpenNebula Cloud Controller Daemon.

It should be checked why oned isn't terminated, and why the systemd doesn't kill any remaining processes.

Details

  • Affected Component: Core, Packages?
  • Version: 5.8.1

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@vholer vholer modified the milestones: Release 5.10, Release 5.8.2 Apr 4, 2019
@christian7007 christian7007 self-assigned this Apr 8, 2019
@vholer vholer self-assigned this Sep 17, 2019
@tinova tinova modified the milestones: Release 5.10.1, Release 5.10.2 Dec 11, 2019
@tinova tinova modified the milestones: Release 5.10.2, Release 5.10.3 Feb 12, 2020
@vholer vholer modified the milestones: Release 5.10.3, Release 5.12 Feb 17, 2020
@vholer vholer assigned ospalax and unassigned vholer Mar 10, 2020
@ospalax
Copy link
Collaborator

ospalax commented Mar 13, 2020

I would try quickfix: https://www.freedesktop.org/software/systemd/man/systemd.kill.html
explicitly use in the /lib/systemd/system/opennebula.service line: KillMode=control-group I would expect that to be the default but maybe not.

@tinova tinova modified the milestones: Release 5.12, Release 5.12.1 Jun 16, 2020
@tinova tinova modified the milestones: Release 5.12.3, Release 5.12.4 Sep 3, 2020
@tinova tinova modified the milestones: Release 5.12.4, Release 5.12.5 Sep 23, 2020
@tinova tinova modified the milestones: Release 5.12.5, Release 5.12.6 Oct 21, 2020
@tinova tinova modified the milestones: Release 5.12.6, Release 5.12.7 Nov 5, 2020
@tinova tinova modified the milestones: Release 5.12.7, Release 5.12.8 Dec 17, 2020
@tinova tinova modified the milestones: Release 5.12.8, Release 5.12.9 Feb 18, 2021
@vholer vholer modified the milestones: Release 5.12.9, Release 6.2 Mar 10, 2021
@rsmontero rsmontero modified the milestones: Release 6.2, Release 6.2.1 Sep 9, 2021
@paczerny paczerny mentioned this issue Nov 8, 2021
Closed
7 tasks
@tinova tinova modified the milestones: Release 6.2.1, Release 6.2.2 Feb 11, 2022
@tinova tinova modified the milestones: Release 6.2.2, Release 6.2.3 Mar 24, 2022
@tinova tinova modified the milestones: Release 6.2.3, Release 6.4.1 Apr 29, 2022
@tinova tinova modified the milestones: Release 6.4.1, Release 6.4.2 Jul 13, 2022
@tinova tinova modified the milestones: Release 6.4.2, Release 6.4.3 Oct 17, 2022
@rsmontero
Copy link
Member

seems to work for recent releases, we'll open it again if more information or if it happens again

rsmontero pushed a commit that referenced this issue Aug 2, 2024
@jloboescalona2
Fix vmpool (#3181)
e45aedb 
* M #~: makes Vmpool configurable (extended/normal)

* M #~: fix dashboard vmpool request

* M #~: increase of the request time to 2min

* L #~: lint-fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ospalax ospalax

@christian7007 christian7007

Labels
Category: Core & System Category: Packages Status: Accepted Type: Bug
Projects
None yet
Milestone
Release 6.4.3
Development

No branches or pull requests
5 participants
@tinova @vholer @rsmontero @ospalax @christian7007