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

# 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:

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

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

## Flex 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 Flex Gateway:

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

## See Also

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