Commands

The Miru Agent is managed with the operating system’s service tools: systemd on Linux and the Windows service manager on Windows. The Miru CLI is only for managing Miru resources from your development machine’s terminal. Please do not attempt to use the miru command to manage the agent.

Version

To check the version of the agent, run the following command on the device:

Linux
Windows

miru-agent --version

PowerShell

& "$env:ProgramW6432\Miru\Agent\miru-agent.exe" --version

Logs

Linux
Windows

The Miru Agent logs are accessible via journalctl, the standard tool for viewing systemd service logs.View allBy default, journalctl truncates each line’s output to the size of the terminal window. We recommend using the --no-pager flag to view the full log output for each line.

journalctl -u miru --no-pager

Tail in real-timeTail the logs and watch new entries as they appear.

journalctl -u miru -f --no-pager

Recent logsView only the most recent log entries (e.g., the last 100 lines).

journalctl -u miru -n 100 --no-pager

Filter by timeView logs from a specific time period.

# Logs from the last hour
journalctl -u miru --since "1 hour ago" --no-pager

# Logs from today
journalctl -u miru --since today --no-pager

# Logs from a specific date/time range
journalctl -u miru --since "2024-01-15 09:00:00" --until "2024-01-15 12:00:00" --no-pager

Filter by priorityView only logs of a specific priority level (e.g., errors).

# Show only errors and above
journalctl -u miru -p err --no-pager

# Show warnings and above
journalctl -u miru -p warning --no-pager

Combine flags for more targeted output. For example, journalctl -u miru -f -n 50 --no-pager will tail the last 50 lines and then follow new entries in real-time.

The agent writes logs to files in %ProgramData%\Miru\Agent\logs, one file per hour (miru.log.YYYY-MM-DD-HH). Logs are not written to the Windows Event Log.Tail in real-timeFrom PowerShell opened as administrator, tail the most recent log file and watch new entries as they appear. The command follows a single hourly file, so re-run it after the log rotates.

PowerShell

Get-ChildItem "$env:ProgramData\Miru\Agent\logs" -Filter 'miru.log.*' | Sort-Object LastWriteTime | Select-Object -Last 1 | Get-Content -Wait -Tail 100

Service management

Linux
Windows

The Miru Agent runs as a systemd service named miru, allowing you to manage the service using standard systemctl commands.You can find the agent’s systemd service files on your file system at the following paths:

/lib/systemd/system/miru.service
/lib/systemd/system/miru.socket

The Miru Agent runs as a Windows service named miru-agent (display name “Miru Agent”). The service runs as the virtual account NT SERVICE\miru-agent.Run the service management commands below from PowerShell opened as administrator.

Status

Linux
Windows

To check the status of the agent, use the status command.

systemctl status miru

The service is active (running) when the agent is running as expected and inactive (dead) when it is not running.

To check the status of the agent, use Get-Service.

PowerShell

Get-Service miru-agent

The Status column shows Running when the agent is running as expected and Stopped when it is not running.

Restart

Restarting the agent stops and starts the agent, giving it a fresh start. If you’re experiencing unexpected behavior, restarting the agent is a good place to begin.

Linux
Windows

systemctl restart miru

PowerShell

Restart-Service miru-agent

If the agent is not running, restarting it will start it.

Stop

stop stops the agent while leaving its state intact. Stopping the agent does not disable the agent—it will still automatically start on next system boot. Note that stopping the agent will prevent any new deployments from reaching the device until the agent is started again.

Linux
Windows

systemctl stop miru

PowerShell

Stop-Service miru-agent

If the agent is not running, stopping it does nothing.

Start

start starts the agent if it has been stopped.

Linux
Windows

systemctl start miru

PowerShell

Start-Service miru-agent

If the agent is already running, starting it does nothing.

Disable

Disabling the agent prevents it from starting automatically on boot. This does not immediately stop the agent—it will still run if it is currently running. However, it will not be able to start on next system boot.

Linux
Windows

systemctl disable miru

PowerShell

Set-Service miru-agent -StartupType Disabled

Enable

Enabling the agent allows it to start automatically on boot. This is the default behavior after installation and only needs to be done if the agent has been disabled. Enabling the agent will not immediately start it—it will still need to be started manually.

Linux
Windows

systemctl enable miru

PowerShell

Set-Service miru-agent -StartupType Automatic

Provisioning status

To check whether the machine is provisioned, run provision --check.

Linux
Windows

sudo -u miru /usr/sbin/miru-agent provision --check

From PowerShell opened as administrator:

PowerShell

& "$env:ProgramW6432\Miru\Agent\miru-agent.exe" provision --check

The command exits with 0 if the machine is provisioned, 3 if it is not provisioned, and 1 on error.

Welcome

Fleet

Config Management

Data Uploads

Developers

Administration

Version

Logs

Service management

Status

Restart

Stop

Start

Disable

Enable

Provisioning status

​Version

​Logs

​Service management

​Status

​Restart

​Stop

​Start

​Disable

​Enable

​Provisioning status

Version

Logs

Service management

Status

Restart

Stop

Start

Disable

Enable

Provisioning status