dt4acc-container-troubleshooting

Diagnose dt4acc container startup failures from missing MongoDB lattice data.

4|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/arm2arm/AstroAgentAssistant --skill dt4acc-container-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt4acc-container-troubleshooting
Source: https://github.com/arm2arm/AstroAgentAssistant/tree/main/science/dt4acc-container-troubleshooting
Command: npx skills add https://github.com/arm2arm/AstroAgentAssistant --skill dt4acc-container-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and resolve dt4acc container startup failures caused by missing accelerator lattice data in MongoDB.

Core Features & Use Cases

  • Prerequisite awareness: highlights essential startup prerequisites (MongoDB, BESSY II data, EPICS vs Tango twins) and common failure modes.
  • Step-by-step troubleshooting: provides reproducible checks for container health, MongoDB readiness, and latency data imports.
  • Use Case: You are debugging a failed dt4acc-twin startup due to missing lattice data; apply this skill to verify prerequisites and restore a working environment.

Quick Start

Run the quick-start diagnostics to confirm MongoDB readiness, lattice data presence, and container startup health.

Frequently Asked Questions about dt4acc-container-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot dt4acc container startup failures?

To troubleshoot dt4acc container startup failures, run diagnostics to verify container health, MongoDB readiness, and accelerator lattice data presence across Docker and Apptainer workflows.

Why does my EPICS or Tango twin container fail to start?

EPICS or Tango twin containers fail to start when missing BESSY II accelerator lattice data in MongoDB prevents initialization, requiring data import checks and environment verification.

Do I need MongoDB running before starting a dt4acc container?

Yes, MongoDB must be running and ready before starting a dt4acc container, as the startup validation checks for required accelerator lattice data stored within the MongoDB instance.

Does this container troubleshooting process work with Apptainer?

Yes, the troubleshooting process works with Apptainer and Docker deployments, providing reproducible environment verification and configuration path checks for HIFIS pre-built deployments.

What is the best way to verify missing lattice data in MongoDB?

The best way to verify missing lattice data in MongoDB is to run quick-start diagnostics that confirm database readiness and validate the presence of required BESSY II imports.

What to do when dt4acc container startup is not working?

When dt4acc container startup is not working, enforce startup prerequisites, validate container health, and apply step-by-step reproducible checks to restore the environment.