Files
werewulf/hpcod/image/desktop
ilkerandClaude Opus 5 f8a9d658e5 hpcod: the desktop opens
Six things were wrong, one behind the other, and every one of them let
the session get further before dying.

  The per-user server never restarted. "nginx_stage pun -s stop" prints a
  path and does nothing; the process serving my requests was 42 minutes
  old, so none of the configuration I was changing had any effect. Every
  conclusion drawn before finding this was drawn against a stale process.
  "nginx -u USER -s stop" actually stops it.

  The cluster config named its own cluster, so every sbatch passed
  --cluster, which Slurm can only resolve through slurmdbd. There is no
  accounting database here: "'c001' can't be reached now". The key is for
  federated Slurm. Removed, and the job queued and ran.

  TigerVNC is not TurboVNC. OnDemand's template runs "vncserver -log
  ... -noxstartup" and both are TurboVNC options; EL9's TigerVNC rejects
  -log outright. The container carries TurboVNC from the project's own
  release now, pinned.

  TurboVNC's vncserver is a Perl script and the container had no perl.
  It installed cleanly, sat on PATH, and died with "env: 'perl': No such
  file or directory". The build now runs perl -c against it.

  --bind /opt mounted the host's /opt over the container's own and hid
  /opt/TurboVNC, so vncserver was "command not found" inside an image
  that demonstrably contained it. Only /opt/apps is bound. --cleanenv
  also drops the image's PATH, so the wrapper states it.

  websockify_cmd defaults to /opt/websockify/run. With everything else
  fixed the session came all the way up - Xvnc running, XFCE started,
  connection details written - and stopped at "[websockify]: failed to
  launch!".

  And ood_portal.yml had no node_uri or rnode_uri, so Apache never
  created the proxy locations: the browser got 404 on the websocket for a
  session that was healthy from every other angle.

Verified end to end: connection.yml written with host c001-node1 display
1 websocket 15927, the sessions page offering noVNC, and a real WebSocket
handshake through the public name answering 101 Switching Protocols -
browser to control plane to Apache to websockify to Xvnc.

Two smaller things on the way. A YAML anchor shared between the basic and
vnc wrappers parsed fine and stopped the dashboard from starting at all,
so they are written out. And the cluster user now gets an SSH key of its
own at first boot rather than at image build - baked into the template it
would be one key shared by every cluster - which is what the portal's
terminal needs, and what MPI needs to start ranks over SSH.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-21 22:08:51 +02:00
..
2026-09-21 22:08:51 +02:00