Accessing logs


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

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

Verbose output

multipass accepts --verbose (-v for short), which can be repeated to go from the default (error) level through warning, info, debug up to trace. We still have a lot of places where logging could be added, so these will become richer over time.

System Logs

Linux

We’re using systemd-journald on Linux, 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*

macOS

The log files on macOS are stored in /Library/Logs/, where multipassd.log has the daemon messages. You can also see instance logs here - the filename pattern is <instance>-hyperkit.log. You will need sudo to access any of those files by default.

Windows

On Windows, the Event system is used, and Event Viewer lets you access them. Our logs are currently under “Windows Logs/Application”, where you can filter by “Multipass” Event source. You can then export the selected events to a file.

Reporting problems

Now that you have the logs, head on to our GitHub page to report your issue!


Last updated 7 months ago.