Skip to main content

Troubleshooting

This page provides solutions to common issues you may encounter while using the EPOS Platform, including the CLI and deployed environments.

CLI (Command Line Interface)​

Common problems and solutions when using the epos-opensource CLI.

Docker/Kubernetes not found​

  • Issue: The CLI reports that Docker or Kubernetes cannot be found.
  • Solution: Ensure that Docker is installed, running, and accessible from your terminal. If you are using Kubernetes, make sure kubectl is installed and configured correctly to connect to your cluster.

Environment or Directory Already Exists​

  • Issue: When creating a new environment, the CLI reports that the environment or directory already exists.
  • Solution: Choose a unique name for your new environment. If you intend to replace an old environment, you must first delete it using the appropriate CLI command before creating a new one with the same name.

Problems with .ttl Files​

  • Issue: The CLI fails to process .ttl (Turtle) files during data population.
  • Solution: Verify that the directory containing the .ttl files exists and that the files are valid. Ensure that the file paths do not contain spaces or special characters that might interfere with processing.

Environment Not Found​

  • Issue: The CLI reports that an environment cannot be found, even though it was created previously.
  • Solution: The CLI stores environment information in a user-level database. Ensure you are running commands as the same user who created the environment. If you switch users, the environment will not be visible.

Docker Environment Not Starting Correctly​

  • Issue: After restarting your machine or the Docker daemon, your EPOS Docker environment does not start up automatically or function as expected.
  • Solution: You can manually trigger a restart and reconciliation of the environment by running the update command. This will check the environment's state and restart any services that are not running correctly. 
    epos-opensource docker update <your-environment-name>

Data Population​

Populated Data Not Appearing​

  • Issue: After populating the system with data, the new information does not appear in the user interface.
  • Solution: This is a known issue that we are working to resolve. In the meantime, you can typically fix this by restarting the resources-service container. You can do this by finding the container ID and using docker restart <container-id>.

Reporting Issues​

If you have tried the solutions on this page and are still experiencing problems, please let us know so we can help.

  • Open a GitHub Issue: The best way to report a bug or request a feature is by opening an issue on our GitHub repository. Please provide as much detail as possible, including steps to reproduce the issue, error messages, and your system configuration.