> ## Documentation Index
> Fetch the complete documentation index at: https://comis-feature-skill-archive-import.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# pm2
> Running Comis with the pm2 process manager
pm2 is a process manager that keeps Comis running in the background, restarts it
if it crashes, and provides easy log viewing. It works on both Linux and macOS,
making it the recommended choice for most users.
## Prerequisites
Before setting up pm2, make sure you have:
* **Node.js 22 or newer** installed
* **Comis built** -- run `pnpm build` in the Comis directory
* **pm2 installed globally:**
```bash theme={null}
npm install -g pm2
```
## Setup
Run the setup command to generate the pm2 ecosystem config:
```bash theme={null}
node packages/cli/dist/cli.js pm2 setup
```
Expected output:
```
✔ Ecosystem file written to /home/user/.comis/ecosystem.config.js
ℹ Start with: comis pm2 start
```
This creates `~/.comis/ecosystem.config.js` with the correct paths to your
daemon binary and configuration file. You do not need to edit this file.
The generated ecosystem config automatically sets `COMIS_CONFIG_PATHS` so you
do not need to manage environment variables manually. This avoids the common
pitfall of environment variables not propagating to background processes.
Start the daemon through pm2:
```bash theme={null}
node packages/cli/dist/cli.js pm2 start
```
Expected output:
```
✔ Daemon started via pm2
```
Check the process status:
```bash theme={null}
pm2 status comis
```
You should see a table with `status: online`:
```
┌────┬──────┬────────┬───┬─────┬───────────┐
│ id │ name │ status │ ↺ │ cpu │ memory │
├────┼──────┼────────┼───┼─────┼───────────┤
│ 0 │ comis│ online │ 0 │ 0% │ 120.0 MB │
└────┴──────┴────────┴───┴─────┴───────────┘
```
Then check the logs to confirm the daemon started successfully:
```bash theme={null}
pm2 logs comis --lines 10 --nostream
```
Look for `"Comis daemon started"` in the output.
## Common commands
| Command | What it does |
| ------------------------------------------- | ----------------------------------- |
| `node packages/cli/dist/cli.js pm2 start` | Start the daemon |
| `node packages/cli/dist/cli.js pm2 stop` | Stop the daemon |
| `node packages/cli/dist/cli.js pm2 restart` | Restart the daemon |
| `pm2 status comis` | Check if the daemon is running |
| `pm2 logs comis` | View live logs (streaming) |
| `pm2 logs comis --lines 50 --nostream` | View the last 50 log lines and exit |
After rebuilding Comis (`pnpm build`), always restart the daemon to pick up the
new code:
```bash theme={null}
pm2 restart comis
```
## Auto-start on boot
By default, pm2 processes stop when the server reboots. To make Comis start
automatically on boot:
**1. Generate the startup script:**
```bash theme={null}
pm2 startup
```
This prints a command that you need to run with `sudo`. Copy and run the
exact command it shows you. For example:
```
[PM2] To setup the Startup Script, copy/paste the following command:
sudo env PATH=$PATH:/usr/bin pm2 startup systemd -u youruser --hp /home/youruser
```
**2. Save the current process list:**
```bash theme={null}
pm2 save
```
Now pm2 will restore the Comis process automatically on every reboot.
## Ecosystem config
The `pm2 setup` command generates a config file at `~/.comis/ecosystem.config.js`.
Here is what it contains:
```javascript theme={null}
module.exports = {
apps: [{
name: "comis",
script: "/path/to/packages/daemon/dist/daemon.js",
env: {
COMIS_CONFIG_PATHS: "~/.comis/config.yaml",
},
restart_delay: 2000,
kill_timeout: 10000,
max_restarts: 10,
autorestart: true,
}],
};
```
Here is what each field does:
| Field | Value | What it means |
| -------------------- | ----------------- | ------------------------------------------------------------- |
| `name` | `"comis"` | The process name used in all pm2 commands |
| `script` | Path to daemon.js | The Node.js file to run |
| `COMIS_CONFIG_PATHS` | Config file path | Tells the daemon where to find config.yaml |
| `restart_delay` | `2000` | Wait 2 seconds between restart attempts |
| `kill_timeout` | `10000` | Wait 10 seconds for the daemon to shut down gracefully |
| `max_restarts` | `10` | Give up after 10 consecutive crashes (prevents restart loops) |
| `autorestart` | `true` | Automatically restart if the daemon crashes |
## Log management
pm2 stores its logs in `~/.pm2/logs/`, not in `~/.comis/`. You will find two files:
* `comis-out.log` -- standard output (normal log messages)
* `comis-error.log` -- standard error (error messages)
**Clear old logs:**
```bash theme={null}
pm2 flush comis
```
**Set up automatic log rotation:**
```bash theme={null}
pm2 install pm2-logrotate
```
This prevents log files from growing indefinitely. The default rotation keeps
logs under 10 MB per file.
The daemon also supports its own file logging with rotation. See
[Logging](/operations/logging) for details on configuring the daemon's built-in
log rotation.
Do **not** use `export COMIS_CONFIG_PATHS=...` separately from the start command.
The ecosystem config handles this for you. Setting it separately may not propagate
to the background process, causing a "Config file not found" error.
## Related pages
How the daemon starts, runs, and shuts down.
Run Comis as a systemd service on Linux.
Run Comis in a Docker container.
Configure log levels, rotation, and structured output.
Solutions to common issues.