Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
S support requests
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • jupyterhub-paris-saclay
  • support requests
  • Issues
  • #11

Closed
Open
Created Nov 24, 2020 by Nicolas Thiéry@nicolas.thiery1Owner

Zombie jupyter servers

On occasions, we have had zombie Jupyter servers:

The user and admin UI shows the server as running. Yet, clicking on "Stop" triggers an error message "API request failed (400) xxx-at-universite-paris-saclay.fr is not running". And indeed, docker ps shows no container running with that name.

Since one can't Stop the server, one can't Start it either.

Latest occurrence: Monday November 23rd in the morning.

Edited Nov 24, 2020 by Nicolas Thiéry
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking