🚀 Welcome to MDriven Learn –  Don’t miss the latest Release Notes.
Turnkey and MDrivenServer logs

MDriven Turnkey and MDriven Server each write their own log files to a logs folder in the application folder. This page shows how to read them – in the browser, in the MDriven Server UI, in Azure, and on the server itself.

Browser Access

If you have the default installation – MDriven Server as __MDrivenServer below Turnkey – you can read the logs directly from a browser like this. With another layout, use each application's own address instead.

Turnkey Server

Portal UI

On the manage page for your application on the MDriven Portal, you will find direct links to the Turnkey log pages.

Direct URL
https://<yourturnkey>/developer/errors 
https://yourturnkey/developer/log

You can add a password parameter if the server is not running in debug mode and you have set the password using ShowDebugInfoPassword in Documentation:TurnkeySettings like this:

https://yourturnkey/developer/log?password=<password>

or

https://<yourturnkey>/logs/TurnkeyServerLogRollingERRORS.txt
https://<yourturnkey>/logs/TurnkeyServerRollingDEBUG.txt

MDrivenServer

Direct URL
https://<yourturnkey>/__MDrivenServer/logs/MDrivenServerRollingDEBUG.txt
https://<yourturnkey>/__MDrivenServer/logs/MDrivenServerLogRollingERRORS.txt
Navigating the MDrivenServer UI

The MDriven Server start page has a link to its log:

If you get an error message and no logs, check that the application pool user can write to the logs folder – see AppPool user.

Using the Azure SCM For Either TurnkeyServer or MDrivenServer

In Azure, there is an admin app for each app called SCM.

https://<yourappname>.scm.azurewebsites.net 

You can log in there using the credentials you find in your publishing profile - or with an account if you have access to the hosting Azure subscription.

If you have this access, you can find logs easily with these two URLs:

https://<yourappname>.scm.azurewebsites.net/api/vfs/site/wwwroot/logs/TurnkeyServerRollingDEBUG.txt
https://<yourappname>.scm.azurewebsites.net/api/vfs/site/wwwroot/__MDrivenServer/logs/MDrivenServerRollingDEBUG.txt
If you're using Chrome, you might like this extension to make the log viewing easier:

https://chrome.google.com/webstore/detail/better-text-viewer/lcaidopdffhfemoefoaadecppnjdknkc

On the Server

You will find the logs folder in the application folder of both Turnkey and MDriven Server, for example C:\inetpub\wwwroot\MyApp\logs and C:\inetpub\wwwroot\MyApp\__MDrivenServer\logs.

The server uses a rolling renaming and cleanup scheme. The current log is the one without an odd extension.

Showing It on the Screen Automatically

To see the logs on the screen, start PowerShell and use the commands:

Get-Content .\*ERRORS.txt -Wait -tail 1
Get-Content .\*DEBUG.txt -Wait -tail 1

When an application does not start (.NET Core builds on IIS)

If the application stops before it can write its own log, IIS has two other places to look:

  • Windows Event Viewer → Windows Logs → Application: errors from the ASP.NET Core Module (IIS AspNetCore Module V2).
  • The startup log: set stdoutLogEnabled="true" on the aspNetCore element in the application's web.config, and the program's console output is written to logs\stdout_*.log. Turn it off again afterwards.

See An application does not start in IIS.

Linux

When MDriven Server and Turnkey run as systemd services, their console output is also in the journal: journalctl -u <service name> -f. See Install on Linux as services.

Windows event log

The .NET Framework build of MDriven Server also writes exceptions to the Windows event log – see Eventlog.