📦
CHI-in-a-box
  • What is CHI-in-a-Box?
  • Before You Begin
    • Assumed Knowledge
    • Hosts and Services
    • Network Overview
    • CC-Ansible
    • The site configuration
      • inventory
      • defaults.yml
      • passwords.yml
      • certificates/
      • node_custom_config/ (optional)
      • post-deploy.yml (optional)
    • How Deployment Works
    • Security considerations
  • Setup Guides
    • Evaluation Site
      • Bring up the Control Plane
    • Production Baremetal
      • Baremetal QuickStart
      • Host Networking Configuration
    • Troubleshooting
      • Networking
    • Verification Checklist
    • Dev-in-a-Box
    • Edge-in-a-Box
  • Reference
    • Chameleon Identity Federation
    • Ironic Flat Networking
    • Ironic Multi-Tenant Networking
    • Glance Image Storage
    • Resource Reservation
      • Default Resource Properties
    • Monitoring
      • IPMI Metrics
      • SNMP Metrics
  • Example Deployments
    • ARM/x86 mixed architecture
    • Edge computing/container testbed
  • Operations
    • Hardware management
    • Certificate management
    • Chameleon tools
      • Hammers 🔨
        • maintenance_reservation
      • Disk image subscription
      • Usage reporting
    • Troubleshooting
      • Known issues
        • Neutron (networking)
        • Nova (KVM)
        • Ironic (bare metal)
      • Instance networking diagnostics
      • Security incident triage
      • Troublesome Hardware
    • Alert runbooks
      • Cron Job No Recent Success
      • Instance Failure
      • Image Cache Space
      • Ironic Node Error State
      • Jupyter Server Launch Failure
      • MySQL Host Down
      • MySQL Replication Error
      • Node Exporter Down
      • Node Network Bridge Down
      • Node Network Bridge Low Traffic
      • Nova Ironic Instance Launch Failure
      • OpenStack API Down
      • PeriodicTask No Recent Success
      • Portal Down
      • Precis Parsed Events Low
      • Provider Conflict
      • Runbook Template
    • User support guide
    • Upgrading to a new Release
  • Development
    • Developing OpenStack Services
    • Dev-in-a-box
Powered by GitBook
On this page
Edit on GitHub
  1. Operations
  2. Alert runbooks

Jupyter Server Launch Failure

Summary: a user's Jupyter server failed to launch on the JupyterHub.

Consequences: the user will not be able to use Jupyter environment. This could also indicate wider issues that may be affecting more users.

Possible causes

Docker unable to map RBD volumes: to avoid storing too much locally on the control node that hosts JupyterHub, we map all user working directories to Ceph RBD volumes.

See if it's possible to create a new Ceph volume.

volname=test-$(date +%Y-%m-%d%H:%M%S)
docker volume create --driver rbd:latest $volname
# Try writing to it
docker run --rm -v $volname:/vol centos:7 touch /vol/test.txt

If that works, then RBD mapping should be working OK. If that doesn't work, then something is wrong.

  1. Clear the Ceph OSD blacklist. It can happen that the Ceph cluster blacklists the client trying to manage the RBD volumes within Docker. Log in to the Ceph monitor node and run ceph osd blacklist clear.

  2. Ensure the rbd kernel module is loaded. This should happen automatically, but the Docker volume driver can't automatically load kernel modules. Run modprobe rbd, and consider adding a file called /etc/modules-load.d/ceph.conf with a single line containing rbd, which will ensure the kernel module is loaded on boot.

PreviousIronic Node Error StateNextMySQL Host Down

Last updated 2 years ago