Nucleus frontend and dispatcher pod logs are usually helpful starting points to troubleshoot various connections, latency, and miscellaneous issues.
The following example shows how to find the Domino Nucleus pod name.
<user-id>$ prod-field % kubectl get pods -n domino-platform | grep -i nucleus
nucleus-create-db-2cwf9 0/1 Completed 0 20d
nucleus-dispatcher-cbc564d96-r9whr 2/2 Running 0 20h
nucleus-frontend-7dd78879f7-bsm6b 2/2 Running 0 20h
nucleus-frontend-7dd78879f7-vnqps 2/2 Running 0 20h
nucleus-keycloak-realm-migrations-lrdbp 0/1 Completed 0 20d
nucleus-mongodb-migrations-d55ch 0/1 Completed 0 20d
nucleus-secret-migrations-mkk9j 0/1 Completed 0 20d
nucleus-seed-central-config-defaults-rwbbr 0/1 Completed 0 20d
nucleus-train-588c78cfb5-xnq8c 2/2 Running 0 20h
nucleus-workspace-volume-snapshot-cleaner-65f567bd8b-nfvlz 2/2 Running 0 20hThe following shows how to view the Nucleus logs.
<user-id>$ prod-field % kubectl logs nucleus-frontend-7dd78879f7-bsm6b -n domino-platform -c nucleus-nginx | grep '"status": "500"'
<snip>
{ "time": "2023-06-15T17:39:25+00:00", "remote_addr": "10.0.84.117", "real_addr": "202.164.132.175", "remote_user": "-", "body_bytes_sent": "57", "request_time": "0.006", "status": "500", "request": "GET /v4/users/notifications/unreadStatus HTTP/1.1", "request_method": "GET", "http_referrer": "https://prod-field.cs.domino.tech/loggedout", "http_user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36" }The following sections provide useful steps to troubleshoot: - Basic Domino health - Workspaces and Jobs issues - Compute environment build issues - Domino endpoint issues - Distributed model monitoring issues - Data sources issues