No edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
[[MDrivenServer log]] | [[MDrivenServer log]] | ||
=== Using the Azure SCM for either TurnkeyServer or MDrivenServer === | ==== Using the Azure SCM for either TurnkeyServer or MDrivenServer ==== | ||
In Azure there is admin app for each app called scm. | In Azure there is admin app for each app called scm. | ||
https://<yourappname>.scm.azurewebsites.net | https://<yourappname>.scm.azurewebsites.net | ||
| Line 32: | Line 32: | ||
https://<yourappname>.scm.azurewebsites.net/api/vfs/site/wwwroot/__MDrivenServer/logs/MDrivenServerRollingDEBUG.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 log viewing easier ==== | ===== If you're using Chrome, you might like this extension to make log viewing easier ===== | ||
https://chrome.google.com/webstore/detail/better-text-viewer/lcaidopdffhfemoefoaadecppnjdknkc | https://chrome.google.com/webstore/detail/better-text-viewer/lcaidopdffhfemoefoaadecppnjdknkc | ||
=== Command line on the server === | |||
You will find the "logs"-folder on both Turnkey and MDrivenServer. | |||
The server uses a rolling renaming and cleanup scheme. The current log is the one without odd extension. | |||
===== Showing it on screen automatically ===== | |||
To see the logs on screen, start powershell and use the command | |||
Get-Content .\MDrivenServerLogRollingERRORS.txt -Wait -tail 1 | |||
__FORCETOC__ | __FORCETOC__ | ||
Revision as of 15:35, 16 February 2021
Browser access
If you have the default installation of the TurnkeyServer and MDrivenServer you can access their logs directly like this from a browser0
Turnkey Server
Portal UI
On the manage page for you 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
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
Using the Azure SCM for either TurnkeyServer or MDrivenServer
In Azure there is 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 easy 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 log viewing easier
https://chrome.google.com/webstore/detail/better-text-viewer/lcaidopdffhfemoefoaadecppnjdknkc
Command line on the server
You will find the "logs"-folder on both Turnkey and MDrivenServer.
The server uses a rolling renaming and cleanup scheme. The current log is the one without odd extension.
Showing it on screen automatically
To see the logs on screen, start powershell and use the command
Get-Content .\MDrivenServerLogRollingERRORS.txt -Wait -tail 1