Logs

If you are having problems with running Pareto Desktop on your Linux system, we might ask you to send over “logs” so we can investigate the issue.

Using the CLI

You can get logs directly from the command line application:

Get status information

paretosecurity status

Verbose logging

paretosecurity check --verbose

This might be overwhelming, so it makes sense to tell paretosecurity to run just the check you are interested in.

First, run paretosecurity state to see which checks are failing, and what is their UUID:

paretosecurity state

Then use the UUID to run the specific check with verbose logging:

paretosecurity check --verbose --only <check-uuid>

Using systemctl

An alternative way to get logs is using systemctl to view the service logs:

# View current logs
sudo journalctl -u paretosecurity --no-pager

# View logs with follow mode (real-time)
sudo journalctl -u paretosecurity -f

# View logs from the last hour
sudo journalctl -u paretosecurity --since "1 hour ago"

# View user service logs
journalctl --user -u paretosecurity-user --no-pager

Tray Application Logs

The tray application logs can be found by running:

# View tray logs in real-time
journalctl --user -u paretosecurity-trayicon -f