Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

How to access logs

Logs are our first go-to when something goes wrong. Multipass is comprised of a daemon process (service) and the CLI and GUI clients, each of them reporting on their own health.

The multipass command accepts the --verbose option (-v for short), which can be repeated to go from the default (error) level through warning, info, debug up to trace.

We use the underlying platform’s logging facilities to ensure you get the familiar behaviour wherever you are.

On Linux, systemd-journald is used, integrating with the de-facto standard for this on modern Linux systems.

To access the daemon (and its child processes’) logs:

journalctl --unit 'snap.multipass*'

The Multipass GUI produces its own logs, that can be found under ~/snap/multipass/current/data/multipass_gui/multipass_gui.log


Errors or typos? Topics missing? Hard to read? Let us know or open an issue on GitHub.

Last updated 3 months ago. Help improve this document in the forum.