Skip to content

Troubleshooting

Service not starting

If the Dracal device service fails to start:

  1. Check service status — see Service Status
  2. Review log files for error messages:
    • Windows: %PROGRAMDATA%\Dracal\
    • Ubuntu: /var/log/dracal/
  3. Check configuration file for JSON syntax errors
  4. Reset configuration by deleting the config file — it will be recreated with defaults
  5. Verify installation by reinstalling from dracal.com

Devices not detected

If your Dracal devices are not being detected:

  1. Verify USB connection — ensure devices are properly connected
  2. Restart the service — see Service Management
  3. Try a different USB port — some ports may have connectivity issues
  4. Review log files for error messages:
    • Windows: %PROGRAMDATA%\Dracal\
    • Ubuntu: /var/log/dracal/
  5. Enable debug logging in the configuration file for more detailed diagnostics

Configuration issues

If you're experiencing configuration problems:

  1. Verify configuration file syntax (.json file) in:
    • Windows: %PROGRAMDATA%\Dracal\
    • Ubuntu: /etc/dracal/
  2. Use a JSON validator to check for syntax errors
  3. Restart the service after making configuration changes
  4. Check log files for configuration-related error messages
  5. Reset to defaults by deleting the configuration file — it will be recreated automatically on restart

API connection errors

If you cannot connect to the REST JSON API:

  1. Verify service is running — check Service Status
  2. Check configured port — verify the port in the configuration file (default: 11395)
  3. Test the endpoint — use curl http://localhost:<port>/dracal-service-info
  4. Review firewall settings — ensure the port is not blocked (though the service only accepts local connections)
  5. Check log files for HTTP server errors

Port conflict errors

If you see errors about the port being in use:

  1. Check for other services using the same port
  2. Change the HTTP port in the configuration file to an unused port (e.g., 12000)
  3. Restart the service after changing the port
  4. Update your client code to use the new port