Troubleshooting and FAQs for IBM Spectrum Conductor
Learn how to isolate and resolve problems with IBM® Spectrum Conductor.
- Troubleshooting cluster startup
Follow this high-level troubleshooting process to verify if your cluster has started up. - Logs
Log files are an essential troubleshooting tool during production and testing. IBM Spectrum Conductor includes three sets of log files: Use the EGO logs to troubleshoot EGO daemons and system events. Use the ascd logs to troubleshoot Spark instance group-related issues. Use the egodeploy log to troubleshoot deployment issues. - Events
Events can be monitored for and used to trigger actions automatically. - Traces
Traces enable an administrator to turn logging on for information specific to an object in EGO. - Troubleshooting SSL-related issues in the IBM Spectrum Conductor cluster management console
By default, the cluster management console in IBM Spectrum Conductor is SSL-enabled. However, over time, changes such as installing new browsers, clearing browser certificates, or network related configurations on management hosts might stop browsers from accessing IBM Spectrum Conductor services due to SSL-related issues. - Troubleshooting host factory
To isolate and resolve issues with cloud bursting, use the host factory logs. The log files provide important runtime information about the general health of the HostFactory service, requestor and provider plug-ins, and system events. - FAQs
Read frequently asked questions about IBM Spectrum Conductor.
Parent topic: Troubleshooting, FAQs, and support