![]() Select User or Phone to specify whether you want to view logs by user or device.To remove existing log entries from the log view window and view only new log entries: If you close the log view window and then re-open it, the displayed window shows only log entries made since you closed the window. The most recent log entries are at the top. The window scrolls dynamically as Core adds entries to the log. MobileIron System Backup process (see System backup)Ĭlick the link for the log you want to view. Searchable device logs (search by mobile number or user) MobileIron Configuration Service (i.e., the service that supports System Manager) The following table lists the available logs: Table 1. The Troubleshooting screen enables you to view the contents of debug logs directly from the console. Set the log level to OFF (turns off all logging for the selected package)Ĭlearing logs enables you to discard information for previous events, making it easier to isolate the information you need.Remove the package from the list (sets lowest level of logging).To disable debugging for MIFS packages under Troubleshooting > Logs: Clear the checkbox next to each module you want to remove from debug mode.Disabling debugging for MICS or the employee portal For MIFS packages, clicking this button sets the log level to Info for all selected packages. To disable all debugging, which stops MobileIron Core from writing detailed information to all logs, click Stop All Debugging under Troubleshooting > Logs. You can disable all debugging or you can select the modules for which you want to disable debugging. Click the + icon to add additional packages and log levels.Use the Log level drop-down to select the level of detail you want to include.In the MIFS Debugging section, use the Package drop-down to select an area to include in the log.MobileIron File Service (the service that supports the rest of MobileIron Core)įor MIFS (MobileIron File Service), which represents the rest of MobileIron Core, select: MobileIron Configuration Service (the service that supports System Manager) Under Troubleshooting > Logs, select the check boxes for the modules you want to place in debug mode: Placing a module in debug mode causes more detailed messages to be recorded in the corresponding log. You can specify which MobileIron modules you want to place in debug mode. When the maximum is exceeded, Core deletes the oldest file.Įnabling debugging for MobileIron modules Core maintains up to 5 100MB files for each of the log files in /var/log/httpd. NOTE:Ĭhanging the log level to Debug or Trace causes many events to be logged. MobileIron recommends that you contact MobileIron Technical Support before changing the log level. Typically, you do not need to change the httpd log level. These logs are captured in the files in /var/log/httpd/https_error_log and /var/log/httpd/portal_error_log. In Troubleshooting > Logs, in the section Stunnel/HTTPD Log Management, you can set the log level for events related to incoming HTTP/HTTPS requests. Typically, you do not need to change the Stunnel log level. These logs are captured in the /var/log/mi_messages file. Stunnel is a library that MobileIron Core uses for TLS encryption. In Troubleshooting > Logs, in the section Stunnel/HTTPD Log Management, you can set the log level for Stunnel. Setting the log level for Stunnel and HTTPD logs Setting the Stunnel log level Disable debugging for MobileIron modules.Enable debugging for MobileIron modules.Set log levels for Stunnel and HTTPD logs.Use the Troubleshooting > Logs options to:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |