Topic/Objective
This article lists many of the more common Flex log files.
Scope/Context
Motorola FLEX Servers
Outcome/Recommendation
The following table is a list of Flex log files, where they are located, and the type of information is stored there.
| Log | Type | Linux Location | Windows Location | Notes |
| launcher.log | Client | NA | %LOCALAPPDATA%\Spillman\Spillman\ | This log contains information about the Flex login screen. Check it if the Flex Client silently fails prior to the login screen becoming accessible. |
| log4net | Client | NA | %LOCALAPPDATA%\Spillman\Spillman\[Major Patch Version]\Logs\log4net | This log contains information on the Flex Client. Check this specifically if Mobile Forms, Sentryx IBR, the new call screens, jail screens, or file attachments are not functioning correctly. |
| Mobile.log | Client | NA | %APPDATA%\Spillman\Mobile\Mobile.log | This log contains information about the mobile client. Check it if Mobile / Message Center is not functioning correctly on the client PC. It will not be present unless enabled from within the mobile client. |
| exceptionlog | Client | NA | %LOCALAPPDATA%\Spillman\CommandCentral Jail\[Major Patch Version]\Logs\exceptionlog | This log contains information on Sentryx Jail screens and adminutil. Check this log if the user is getting errors in any associated screens. |
| master.log | Server | /sds/dbs/live.dbs/master.log | This log contains messages from the classic (summit) screens. Be aware that this is a "round robin" log (them most recent log will not always be at the bottom of the log). | |
| Mobile logs | Server | /sds/app/mobile/log | This location will contain both a runtime and an error log for each of the mobile server sydaemons. Check the daemon-specific error log in particular if the daemon is not functioning correctly. | |
| Tomcat logs | Server | /sds/app/tomcat/logs | [Drive letter of Flex install]:\SpillmanServer\app\tomcat\logs | This location contains logs related to the primary tomcat server, the standalone tomcat servers, and all webapps running on the primary tomcat server. Check the logs in this location if you are having issues on jail screens, with Touch2, or with any of the standalone tomcat servers. |
| Interfaces logs | Server | /sds/app/interfaces-server/logs | [Drive letter of Flex install]:\SpillmanServer\app\interfaces-server\logs | This location contains logs for the interfaces server, and all web-apps that are running on the interfaces server e.g. StateLink and DataExchange. Check the logs in this location if you are having any issues with any of the web-apps running on your interfaces server. |
| CTSTATUS.FCS | Server | /sds/dbs/CTSTATUS.FCS | [Drive letter of Flex install]:\SpillmanServer\dbs | This log contains information about ctree (Flex' database engine). Check this log if there is any indication of that the database is not functioning correctly. |
| RHEL System Log | OS | /var/log/messages | NA | This log contains messages about general operating system activity. Check it if a Flex-related service e.g. nginx, ctree, etc. unexpectedly stops or will no longer start correctly, or if you otherwise suspect that the OS is not functioning correctly. |
| Windows Event Viewer | OS | NA | C:\Windows\System32\eventvwr.exe | This is a front-end viewer for aggregated system events. Check this on the client-side if Flex or Mobile silently crashes, or on either side if you suspect that the OS is not functioning correctly. |
| Windows Reliability Monitor | OS | NA | Control Panel\All Control Panel Items\Security and Maintenance\Reliability Monitor | This is a utility that provides a timeline of overall system stability and system updates. Check this client-side if a desired program e.g the Flex Client, stopped functioning correctly following a Windows update, and you would like to identify that update for a potential roll-back. |