Troubleshooting

If the agent is not reporting data, use these steps to diagnose potential issues.

Is the agent running?

The first step is to determine if the simob agent is actually running on your system. You can do this using the built-in status command:

simob status
  • If running: You should see [✔] simob is running.
  • If not running: You will see an error message indicating that the agent process could not be found.

Linux

If the agent is not running, you can attempt to manage the service using systemctl.

Checking the service status

Check if the systemd service is active or if it failed with an error:

systemctl status simob

Restarting the service

If the service is stopped or failed, attempt to start it:

sudo systemctl start simob

Checking agent logs

If the agent fails to start or remains inactive, the most crucial step is reviewing the logs to identify startup errors, configuration problems, or communication failures.

  • View recent logs:

    sudo journalctl -u simob --since "10 minutes ago"

  • Follow live logs (useful for real-time diagnosis while starting the service):

    sudo journalctl -u simob -f

Windows

On Windows, simob runs as a standard Windows Service.

Checking the service status

Open an Administrator PowerShell and run the following command to see if the service is running:

Get-Service -Name simob

Starting the service

If the status is Stopped, you can start it with:

Start-Service -Name simob

Checking agent logs

If the agent is running but not reporting data, or if it fails to start, check the logs:

  • Event Viewer: The agent logs events and errors to the Windows Event Viewer under Windows Logs > Application. Look for entries with simob as the source.