You can use the Serverinfo page and application logs to inspect a Turnkey application's current status and diagnose runtime problems; this page is for administrators of Turnkey and MDrivenServer installations.
Use Serverinfo for Turnkey diagnostics
When your Turnkey site has Show Debug Info enabled in the portal, open this address in a browser:
https://<yourSite>/Developer/Serverinfo
Replace <yourSite> with the address of your deployed site. For example, if the site is available at https://example.org, use:
https://example.org/Developer/Serverinfo
The Serverinfo page provides insight into the application's status, including memory-related information.
Enable access
- Open the portal for the Turnkey site.
- Enable Show Debug Info.
- Browse to
/Developer/Serverinfoon that site.
Security: Serverinfo is available when debug information is shown. Enable this setting only for the people and period needed to diagnose the application, because the page exposes application-status information.
Test memory-pruning timing
Serverinfo also lets you temporarily adjust the timing used when the server prunes stale applications and when pruning runs. Use these temporary values when you need faster feedback while investigating memory use; they let you observe the effect of other changes without waiting for the normal intervals.
Do not treat temporary Serverinfo settings as the primary memory-tuning mechanism. For the built-in cleanup behavior, garbage-collection settings, and the trade-offs between memory use, CPU use, and user responsiveness, see Documentation:Memory optimization. For Turnkey client timeout information, see Documentation:Span.TurnkeyTimeoutMinutes.
Find and use logs
Logs record deviations that occur while the application runs. Check the logs alongside Serverinfo when diagnosing an issue: Serverinfo shows current status, while a log file can show what occurred before or during the problem.
| Installation | Where to access logs | Notes |
|---|---|---|
| Turnkey | The Logs folder beneath the application root, when the default configuration is retained.
|
Turnkey writes log files by using log4net. |
| MDrivenServer | The logging facilities in the MDrivenServer UI. | MDrivenServer also uses log4net to produce log files. |
Check Turnkey logs
- Locate the root folder of the deployed Turnkey application.
- Open its
Logsfolder. - Open the relevant log file and compare its timestamps with the time at which the issue occurred.
- If no log file is created, verify that the IIS account running the application has write access to the configured log folder.
For example, when a deployment is using the unchanged logging configuration, an application rooted at C:\Sites\MyTurnkeyApp writes logs below C:\Sites\MyTurnkeyApp\Logs.
Change the log destination or file name
Turnkey and MDrivenServer use log4net. The log4net sections in web.config control where log files are written and what they are called.
- Open the application's
web.config. - Locate the log4net configuration section.
- Change the configured folder or file name as required.
- Ensure that the IIS account running the application has write access to the new location.
- Reproduce or wait for the condition that writes a log entry, then confirm that a log file is created in the configured location.
If you leave web.config unchanged, logs are written under the application's root in Logs. A configuration change alone is not sufficient: without write permission for the IIS application account, logging cannot succeed.
Troubleshooting checklist
- Cannot open
/Developer/Serverinfo: confirm that Show Debug Info is enabled in the portal and that you are using the deployed site's address. - Need to investigate growing memory use: inspect Serverinfo, use its temporary pruning timing only for testing, then follow Documentation:Memory optimization.
- No Turnkey log files: check the configured log location in
web.configand the write permission of the IIS account. - Investigating an MDrivenServer issue: use the logging available in the MDrivenServer UI.