> For the complete documentation index, see [llms.txt](https://docs.invariant.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.invariant.io/troubleshooting/service-troubleshooting.md).

# Service Troubleshooting

Invariant ptovides a number of background services which provide a variety of functions such as - transforms data or serve requests. Unlike interactive apps, you may have to review logs and trace files to figure out the root cause of the error.

#### Review Logs <a href="#review_logs" id="review_logs"></a>

Invariant products are designed Linux servers and the logs are usually written out to /var/log folders

#### Check the service status <a href="#check_the_service_status" id="check_the_service_status"></a>

A service can have any of the following statuses:

* `start`: The service has started.
* `stop`: The service has stopped running.
* `restart`: The service is rebooting and will start after the process is complete.

#### Find port conflicts <a href="#find_port_conflicts" id="find_port_conflicts"></a>

Many times, you may have another service listening on the port, which may prevent the service from starting. To find out what’s listening, use the `netstat` command.