This article explains how to launch Mari with verbose logging, either from the command line or a desktop shortcut.
It is helpful for the Support team to review output from Mari when an issue occurs in the application. Without verbose mode, the Mari console is not present to capture this information. Although there is a MariLog.txt file created in a specific location, if for some reason the MariLog.txt file is unable to be created (due to permissions or other networking conflicts), launching in verbose mode will allow the console to be displayed, and Mari’s output to be copied to a text file for further inspection.
The user can also view verbose output while working to understand how their actions affect Mari, keeping an eye on it to analyse specific processes and errors that may appear.
NOTE: The verbose output and MariLog.txt file are nearly identical, except for the licensing checkouts which are only shown in verbose mode.
From the Command Line:
Please do the following to launch Mari with verbose logging from the command line, based on whichever platform is used. These examples assume the default installation directory and that you are launching Mari 6.0v2 (or 4.7v7 on macOS). Please replace all instances of the version number to launch other Mari releases:
"C:\Program Files\Mari6.0v2\Bundle\bin\Mari6.0v2.exe" --verbose
From a Desktop Shortcut:
Unfortunately, the desktop shortcut icons with verbose mode are not created on macOS or Linux platforms during installation. However, they are created when installing the application on Windows, and can be accessed by using the Windows Search bar.
In the Windows Start menu or Search Bar, please type “Mari 6.0v2 (Verbose Output)”, then press Enter to launch the application.
Alternatively, you can launch Mari with verbose logging from a desktop application icon (assuming the default installation path):
- In the File Explorer, navigate to: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\The Foundry\Mari 6.0v2
- Locate the Mari 6.0v1 (Verbose Output) application icon, and double-click it to launch the software.
NOTE: The ProgramData directory is generally hidden by default. To display and access hidden items on Windows, enable the "Hidden items" option in the View tab of File Explorer, as shown in the screenshot below:
This icon unfortunately needs to be created manually due to the installation package not including pre-registered desktop shortcut icons. Please review the following article for creating one, and append --verbose to the application path:
Q100521: Creating a desktop shortcut on Linux operating systems
Unfortunately, macOS does not automatically generate a verbose output Mari shortcut, and will need to be generated manually. Please do the following to create a Mari icon with verbose output through the Terminal:
Open a text editor and create a new empty file.
Add the following code into the empty file. The second line consists of the full path to the Mari application, with the --verbose flag appended:
Save the file to your desktop with an appropriate name and the extension ".command", for example:
NOTE: If you save the file with a .command extension, Mari will open with a Terminal window and print the verbose output of the application while in use. If you save the file with an .app extension, although Mari still logs the information, it will not be visible in a terminal window.
Open a new Terminal window, and change directory to your desktop, using the command:
Run the following command in the Terminal window, changing "Mari4.7v7(Verbose Output)" for the name of your shortcut:
chmod 744 "Mari4.7v7(Verbose Output)"
When double-clicking the desktop shortcut, Mari 4.7v7 should open with verbose output in the Terminal.
- Additional troubleshooting options in Mari:
Q100253: Troubleshooting Mari performance issues
- Information about where the MariLog.txt file is located can be found in the following article:
Q100020: Default Mari directory paths for config and log files
If you are still having trouble launching Mari with verbose logging after performing the steps outlined in this article, then please create a support ticket and provide us with the information requested in this article:
Q100090: Reporting a Mari issue
For more information on how to open a support request, please refer to this article:
Q100064: How to raise a support ticket
We're sorry to hear thatPlease tell us why