# Service Operations

- Link: https://ubient.dscloud.biz/docs/ubient-software/rtmn/service-operations/
- Published: 2026-10-13T01:29:54+09:00
- Author: Ubient

`rtmn` runs as a systemd service.

## Single-Instance Service

Check status:

    ```ubient-docs-code
    Bashsudo systemctl status rtmn --no-pager
    ```

Restart:

    ```ubient-docs-code
    Bashsudo systemctl restart rtmn
    ```

Stop:

    ```ubient-docs-code
    Bashsudo systemctl stop rtmn
    ```

Follow logs:

    ```ubient-docs-code
    Bashsudo journalctl -u rtmn -f
    ```

Show recent logs:

    ```ubient-docs-code
    Bashsudo journalctl -u rtmn -n 100 --no-pager
    ```

## Account-Isolated Services

In account-isolated installations, service names use the `rtmn-<instance>.service`
format.

Check status:

    ```ubient-docs-code
    Bashsudo systemctl status "rtmn-$INSTANCE.service" --no-pager
    ```

Restart:

    ```ubient-docs-code
    Bashsudo systemctl restart "rtmn-$INSTANCE.service"
    ```

Stop:

    ```ubient-docs-code
    Bashsudo systemctl stop "rtmn-$INSTANCE.service"
    ```

Follow logs:

    ```ubient-docs-code
    Bashsudo journalctl -u "rtmn-$INSTANCE.service" -f
    ```

Show recent logs:

    ```ubient-docs-code
    Bashsudo journalctl -u "rtmn-$INSTANCE.service" -n 100 --no-pager
    ```

## Confirm a Healthy Start

A healthy service start sends a startup notification to the allowed Telegram chats.

Check these items:

 * The systemd service is `active (running)`.
 * The journal has no configuration errors.
 * The startup notification arrived in every allowlisted Telegram chat.
 * The audit log path is writable by the service account.