Troubleshooting¶
This page lists common issues and how to recover from them.
oqtopus: command not found¶
The install directory may not be on your PATH.
By default, oqtopus is installed to:
Add that directory to your shell PATH, then restart your shell.
.metadata not found¶
Backend commands must be run from inside a backend environment created by:
Change into the environment root before running backend commands:
Current Directory Does Not Match env_root¶
The current directory must match the env_root recorded in .metadata.
This can happen if the environment directory was moved after creation. Create a new environment or move the directory back to its recorded path.
Docker Is Required For Engine Install¶
Installing engine builds the sse_runtime Docker image.
If Docker is not installed or not running, commands such as these fail:
Install and start Docker, then run the command again.
If you need to finish installation before Docker is available, use
--skip-sse-build and build the image later:
uv Is Required¶
Backend and cloud-local components are synchronized and launched with uv.
Install uv before installing or starting components.
git Is Required For Branch Install (Backend)¶
Installing a backend component from a branch requires git.
If git is not installed, the following command fails:
Install git, then run the command again.
Branch Name Not Found (Backend)¶
If the specified branch does not exist in the remote repository, the clone
fails with an error from git.
Check that the branch name is correct, then run the command again with the correct branch name:
Backend: Component Version Is Not Bound¶
If a service is started before its component is installed, start fails.
Install the required components:
Then start services again:
Service Appears Already Running¶
If a PID file exists and the recorded process is alive, start skips that
service and logs a message such as:
This means start all is safe to run at any time: services already running
are skipped and the rest are started normally.
If another start command is already launching the same service, start fails
before creating a duplicate process.
Check status:
Stop the service if needed:
Stop Times Out¶
stop sends TERM and waits up to 5 seconds. If the process is still running
after that, stop exits with an error.
Inspect the process and stop it manually if required.
Logs Are Missing¶
OQTOPUS CLI creates log directories, but it does not create log files.
For backend environments, log files appear only after the backend applications
write them according to the logging.yaml files under config/.
For cloud-local environments, runtime stdout and stderr are written to
$ENV_ROOT/logs/<service>/service.log for each service started in background
mode.
git Is Required For Branch Install (Cloud-Local)¶
Installing a cloud-local component from a branch requires git:
Install git, then run the command again.
Docker Compose Is Required For Cloud-Local DB¶
The db service in a cloud-local environment uses Docker Compose:
If Docker or Docker Compose is not installed or not running, this command fails. Install and start Docker, then run the command again.
Cloud-Local DB Container Name Conflict¶
If docker compose up fails with a container name conflict, a container from
a previous run may still exist. Remove it with:
Then run oqtopus cloud-local start db again. To avoid conflicts, the
compose.yaml in the cloud component should not use fixed container_name
values.