---
schema_version: "1"
id: f2f330db4e0631b367fecb4c74b1a3430571c2e59234fef206ce8c566941e645
title: Troubleshooting Linux Services
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.13/troubleshoot-linux-services.md
canonical_url: https://docs.mulesoft.com/gateway/1.13/troubleshoot-linux-services
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 3b1d517d83f8c4acfdfe070c1c08ae7193f11d22cd632f5b89059f02fc0d6fb7
description: MuleSoft Documentation Site
release: "1.13"
latest: false
---
---
product: Omni Gateway
version: 1.13
---

# Troubleshooting Linux Services

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The following topics provide possible causes for service issues and describe how to troubleshoot:

- [Omni Gateway Service Failed to Run](#flex-gateway-service-failed-to-run)

- [Other Services Failed to Run](#other-services-failed-to-run)

## Omni Gateway Service Failed to Run

The `flex-gateway.service` status displays `failed` after running the
`systemctl list-units flex-gateway*` command.

### Diagnose

To diagnose the service failure, run the following command:

```ssh
journalctl -u flex-gateway
```

#### Error 1: “Panic: could not read platform configuration”

If the output of the `journalctl` command includes this line:

```ssh
flex-agent[3253]: panic: could not read platform configuration: open : no such file or directory
```

The problem can be resolved by running `chmod` on the files created during registration.

## Other Services Failed to Run

If your error does not appear, attempt to restart Omni Gateway:

```ssh
sudo ldconfig
sudo systemctl restart flex-gateway
```

## See Also

- [Known Issues](https://help.salesforce.com/s/issues)