Troubleshooting Assistance Contents General Troubleshooting Contact the WRC This section contains advice and suggestions that may come in handy when trying to identify an issue. General Troubleshooting This section contains advice and steps to follow in any troubleshooting scenario. Pinpoint where and when the issue originated. What time did the issue start? Where did the problem first appear? In complex systems with multiple instances, it may be difficult to figure out when the problem started. Review the logs for warnings, errors, and alerts. The following logs may contain useful information about the issue. Look for warnings, errors, or alerts around the time that the issue began. Check messages.log.Opens in a new tab Check Production Event Log.Opens in a new tab Review Application Error Log.Opens in a new tab Review Web Gateway Error Log.Opens in a new tab Review Web Server Error Log.Opens in a new tab Check whether the instance has access to enough storage space. Check whether the file system is out of space.Opens in a new tab Check database space.Opens in a new tab Check whether Temp DB is full.Opens in a new tab Check journal space.Opens in a new tab Review CPU activity. Is the server load within the typical range? Monitor CPU UtilizationOpens in a new tab; is CPU usage steady, or are there spikes? Are the spikes an increase or decrease in activity? Is the CPU often waiting on I/O? (On systems with sysstat installed, you can look at iostat.) Review open transactions and locks. Are there issues with open transactions?Opens in a new tab Evaluate Lock Table Size.Opens in a new tab Check whether all processes are running as expected. Monitor Total Processes.Opens in a new tab Are any processes stuck, or looping? Go to Management Portal > System Operations > Process > Details (on far right) of a process ID for information about specific processes. Check the Mirror Monitor and Mirror Status Monitor. Monitor Mirror Health.Opens in a new tab Is journaling caught up? Monitor for Mirror Differences.Opens in a new tab Ensure the InterSystems IRIS license is valid and current. Monitor License Usage.Opens in a new tab Monitor License Status.Opens in a new tab Contact the WRC Even if you are unable to identify and resolve the issue, the InterSystems Worldwide Response Center (WRC)Opens in a new tab is available to help diagnose and resolve any issues that may arise. Any information you have about the issue can help the WRC quickly identify what is causing the issue. The following are steps you can perform to provide the WRC with as much information as possible. Summarize the issue. Can the issue be reproduced? Does it occur consistently? Has anything changed on the system recently that may have caused the issue? Record the version information for InterSystems IRIS and its operating system. The $ZVERSIONOpens in a new tab variable contains this useful information. Run monitoring utilities. Run Diagnostic Report in Management Portal.Opens in a new tab Identify resource-intensive lines of code for a particular routine using ^%SYS.MONLBL.Opens in a new tab Determine resource-intensive routines and drill down to find where resources are used most with ^PROFILE.Opens in a new tab If the system is in a hung state, run IRISHung.Opens in a new tab Create System Performance Report using ^SystemPerformance.Opens in a new tab Get in touch with the WRC Go to the InterSystems Worldwide Response Center (WRC)Opens in a new tab website for assistance with any problems you have with InterSystems IRIS.