MaxTo's log files provide insights when something goes wrong.
Advanced topic
You would normally only need to look in the log files if something goes wrong or you are reporting an issue to us.
MaxTo produces quite a bit of log data when it is installed and running. These are the locations where you can expect to find useful information should you experience a crash or unexpected behavior.
Runtime logs
This runtime logs contains entries about what MaxTo is doing at specific points in time, including any crashes that
MaxTo experience. You will find the files in %AppData%\MaxTo. In this folder you will
find files named something like maxto20210613.log (representing today). Old log files are
automatically deleted.
Note on file paths
You can see the file paths we specify contain special variables (such as %AppData%). These
expand into full paths on your machine, but can be different from computer to computer.
To quickly open the log file, hit R on your keyboard, and copy in the path to the file. Then press OK, and the file should open in your default text editor (usually Notepad).
Each line in this file is timestamped; and the file can grow quite large. If you can reliably reproduce your issue, it could be helpful to delete the log file before trying to reproduce the issue — that way there will be less data for us to read when we try to figure out what is going on.
Here is an excerpt from the log file:
2020-10-05 07:51:10 [[email protected]] [Information] [] Logger setup (online logging: True, process #1656) 2020-10-05 07:51:10 [[email protected]] [Information] [MaxTo.Core.Settings.DefaultConfigurationLocation] Found no specified configuration location file, using default settings location "C:\Users\vegar\AppData\Roaming\MaxTo" 2020-10-05 07:51:21 [[email protected]] [Information] [] Logger setup (online logging: True, process #29972) 2020-10-05 07:51:21 [[email protected]] [Information] [MaxTo.Core.Settings.DefaultConfigurationLocation] Found no specified configuration location file, using default settings location "C:\Users\vegar\AppData\Roaming\MaxTo" 2020-10-05 07:51:22 [[email protected]] [Information] [MaxTo.Core.RestartService] Restarting MaxTo with arguments "--waitforexit 284" 2020-10-05 07:51:22 [[email protected]] [Information] [MaxTo.Server.ServerApplicationContext] Received exit message. Exiting in 250ms... 2020-10-05 07:51:22 [[email protected]] [Information] [] Deactivated "MaxTo.UI.ViewModels.NotificationIconViewModel". Closed: True
Let us take a closer look at a single log line.
2020-10-02 13:10:23 [[email protected]] [Information] [MaxTo.Core.Settings.DefaultConfigurationLocation] Found no specified configuration location file, using default settings location "C:\Users\vegar\AppData\Roaming\MaxTo"
| Part | Description |
|---|---|
| Date and time | When did this event occur? |
| Executable | Which MaxTo executable caused this line? |
| Version | The version number of MaxTo that is running. This is the file version, and does not correspond exactly to the published version numbers (meaning it won't contain any alpha or beta labels). |
| Log level | How severe is the event considered to be? |
| Source | Where in the source code did this event originate? Useful for the developers. |
| Message | The text of the event, describing what actually happened. |
Each line has a log level, which indicates the severity of what is being reported. The log levels are, in order from least to most important:
| Level | Description |
|---|---|
| Debug | Trivial events that specify in intricate detail what is being done. |
| Information | Events that carry information about normal program behavior. |
| Warning | Events that may indicate that something is wrong; but may be trivial. |
| Error | Events that indicate that something couldn't be done in the way you wanted. You'll get feedback from the program when this happens. |
| Fatal | Events that the program couldn't recover from. You'll get a notification the next time you start MaxTo. |
You can change the log level, which affects only what goes in the log files. However, there is no user interface for changing it, so you will have to manually edit the configuration file to do so.
Installation logs
If you use the normal installer, it generates a log file during installation in %LocalAppData%\SquirrelTemp\SquirrelSetup.log.
Look in this file if you are experiencing issues with the MaxTo installer.
Note that the installation log may also contain information about other programs on your machine; as other program may use the same installer as MaxTo does.