{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":48099,"path":"servicenow-platform/mid-server/r_MIDServerTroubleshooting.md","title":"Resolving MID Server issues","bundle":null,"doc_type":null,"release":"australia","body":"\n# Resolving MID Server issues\n\nTroubleshoot problems with the MID Server to find solutions. Monitor the MID Server to receive alerts about issues as they occur. Troubleshooting procedures exist to resolve specific problems with the MID Server. The Knowledge Base on Hi contains several articles to help you troubleshoot MID Server issues.\n\n## Monitor the MID Server\n\nMonitoring a MID Server involves verifying entries in log files, confirming network connectivity, and checking MID server status.\n\n-   If the MID Server is on a Windows host, navigate to the Windows Services console, locate the service name that matches the name that appears from the `wrapper-override.conf` file. If the MID Server process is the only Java process running on the host, monitor the memory used by java.exe and alert on less than the maximum configured memory defined in the `~\\agent\\conf\\wrapper-override.conf` folder.\n\n-   Ensure that the `agent0.log.0.lck` file appears in the `~\\agent\\logs` folder to confirm that the MID Server running and logging system activity in the `agent0.log.0` file.\n\n-   Review the following logs for warning, critical, and severe errors: `~\\agent\\logs\\agent0.log.0` `~\\agent\\logs\\wrapper.txt` See [Manage ECC Queue content for a MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/ecc-queue-mid-server.md) to see how to open log entries from the instance.\n\n-   [Test MID Server connectivity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/t_ValidateNetworkConnectivity.md) to confirm that the MID Server host is able to communicate with the instance. Resolve any issues with the network connectivity such as conflicts with firewalls, access control lists, and routing errors.\n\n-   From the MID Server instance, navigate to the **MID Servers** page, and review the status of the MID Server. For additional information, click a **Name**.\n\n-   Set up email, SMS, and push notifications to alert you when issues occur with MID servers. The **MID Server Down** notification is enabled by default. See [Notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/notifications.md) for details.\n\n\n## Java Flight Recorder\n\nJava Flight Recorder \\(JFR\\) uses an articulate data model to analyze Java Virtual Machine \\(JVM\\) internal and application specific memory usage and thread related details. On hosts with Java 14 or later, Event Streaming enables analysis of specific JVM or application events.\n\nThe JFR file actions **Start JFR Recording**, **Stop JFR Recording**, or **Write JFR File**, are accessed on the instance in the MID Server's Related Links. By starting and stopping the JFR recording, you can dump JFR data to the disk on demand. While JFR recording is on, you can write to the JFR file from the MID Server instance page.\n\nThe JFR file is deleted by a scheduler to clean the data after 24 hours. This default behavior can be overridden by adding the following configuration parameter in the **config.xml**: `<parameter name=\"mid.jfr.data.clean.interval\" value=\"<time in milisec>\"/>`\n\nCustom JFR events can be written to JFR file. To disable event writing, add the following configuration parameter to the **config.xml**: `<parameter name=\"mid.jfr.record.aprobe\" value=\"false”/>`\n\n## Troubleshooting procedures\n\nThe following procedures provide information on resolving specific problems with the MID Server. Knowledge Base articles also cover a wide range of issues. If you are encountering problems which are not covered in these procedures, search the Knowledge Base for related articles. For instance, if you are experiencing symptoms such as the MID Server going down or not responding, or CIs being duplicated during discovery, see [KB0597571](https://support.servicenow.com/kb_view.do?sysparm_article=KB0597571) for information and recommended solutions.\n\n-   **[MID Server active issues](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-server-active-issues.md)**\n\n    The ServiceNow® instance has a dedicated table that publishes active issues with MID Servers and alerts administrators when a MID Server is in danger of exceeding its resources.\n\n-   **[Active MID Server post-cloning credential issues](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-post-clone-issue-resolution.md)**\n\n    The system provides automatic processes to detect and notify you of possible MID Server credential issues after instance cloning.\n\n-   **[MID Server resource threshold alerts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-resource-threshold-alerts.md)**\n\n    The instance displays warnings when a MID Server breaches its resource thresholds for CPU and JVM memory usage, enabling users to create email notifications or custom scripts when a breach occurs.\n\n-   **[MID Server user connectivity issues](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-server-connectivity-issues.md)**\n\n    The instance writes issues involving MID Server user logins and network connectivity to the MID Server Issue \\[ecc\\_agent\\_issue\\] table and creates events you can use in custom scripts or to send email notifications.\n\n-   **[Interpreting MID Server user debugging output](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-user-connectivity-debug-output.md)**\n\n    Debugging output from the system log is available in either a summary or detailed view for MID Server user issues, but must be enabled manually.\n\n-   **[MID Server Upgrade History](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-server-upgrade-history.md)**\n\n    Use this module to troubleshoot errors that occur during the MID Server upgrade process. The MID Server Upgrade Histories table contains a record of each instance upgrade. The MID Server Upgrade Stages table shows the status of each MID Server and its upgrade progress, including any errors encountered.\n\n\n-   **[MID Server active issues](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-server-active-issues.md)**  \nThe ServiceNow® instance has a dedicated table that publishes active issues with MID Servers and alerts administrators when a MID Server is in danger of exceeding its resources.\n-   **[MID Server fails to start](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-startup-fails.md)**  \nWhen a newly installed MID Server fails to start or shuts down prematurely, improper configuration could be to blame.\n-   **[Active MID Server post-cloning credential issues](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-post-clone-issue-resolution.md)**  \nThe system provides automatic processes to detect and notify you of possible MID Server credential issues after instance cloning.\n-   **[MID Server resource threshold alerts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-resource-threshold-alerts.md)**  \nThe instance displays warnings when a MID Server breaches its resource thresholds for CPU and JVM memory usage, enabling users to create email notifications or custom scripts when a breach occurs.\n-   **[MID Server user connectivity issues](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-server-connectivity-issues.md)**  \nThe instance writes issues involving MID Server user logins and network connectivity to the MID Server Issue \\[ecc\\_agent\\_issue\\] table and creates events you can use in custom scripts or to send email notifications.\n-   **[Interpreting MID Server user debugging output](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-user-connectivity-debug-output.md)**  \nDebugging output from the system log is available in either a summary or detailed view for MID Server user issues, but must be enabled manually.\n-   **[MID Server Upgrade History](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-server-upgrade-history.md)**  \nUse this module to troubleshoot errors that occur during the MID Server upgrade process. The MID Server Upgrade Histories table contains a record of each instance upgrade. The MID Server Upgrade Stages table shows the status of each MID Server and its upgrade progress, including any errors encountered.\n\n**Parent Topic:**[MID Server reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-server-reference-information.md)\n\n**Related topics**  \n\n\n[MID Server system requirements]()\n\n[MID Server upgrades]()\n\n[MID Server dashboard]()\n\n[MID Server properties]()\n\n[MID Server parameters]()\n\n[MID Server Configuration Parameter settings and priority]()\n\n[MID Server File Cleaner]()\n\n[MID Server protected records and reserved characters]()\n\n[MID Server privileged commands]()\n\n[MIDSystem methods]()\n\n[Manually start, stop, and restart a MID Server]()\n\n[MID Server heartbeat]()\n\n[Set the MID Server JVM memory size]()\n\n[Pause the MID Server]()\n\n"}}