Skip to content

Login node fails to bootstrap

Login node bootstrap logs are written to the shared filesystem, so you can read them from the controller without connecting to the login node.

Read the shared logs

cd /apps/edh/<EDH_CLUSTER_ID>/shared/logs/bootstrap/login_node/<HOST>/
grep -riE "error|fatal|critical" .

To open a single file, list the folder first, then print or scroll through the file you want:

# List everything in the login node's logs folder
ls -l /apps/edh/<EDH_CLUSTER_ID>/shared/logs/bootstrap/login_node/<HOST>/

# Print the first-boot user-data log
cat /apps/edh/<EDH_CLUSTER_ID>/shared/logs/bootstrap/login_node/<HOST>/01_user_data.sh.log

# Scroll through a long log page by page (press q to quit)
less /apps/edh/<EDH_CLUSTER_ID>/shared/logs/bootstrap/login_node/<HOST>/01_user_data.sh.log

If the shared logs are missing

If the node failed before /apps was mounted, the shared logs will not exist. Connect to the login node itself and read the local logs instead:

cd /root/edh_bootstrap_<INSTANCE_ID>/logs
grep -riE "error|fatal|critical" .

# List the files, then open one
ls -l /root/edh_bootstrap_<INSTANCE_ID>/logs/
cat /root/edh_bootstrap_<INSTANCE_ID>/logs/01_user_data.sh.log

Placeholders

  • <EDH_CLUSTER_ID> is your EDH cluster ID (for example, edh-abc123).
  • <HOST> is the node's short hostname.
  • <INSTANCE_ID> is the EC2 instance ID. The folder name uses an underscore, edh_bootstrap_, not a dash.