How To
Summary
This article provides advice on how to troubleshoot the IBM Resilient Circuits service and gather required logs when it fails to start.
Steps
If IBM Resilient Circuits is set up to run as a service that uses systemd and the service and thus IBM Resilient Circuits does not start you can use this document as a guide.
Try restarting IBM Resilient Circuits and capture the output from journalctl.
sudo systemctl restart resilient_circuits
sudo journalctl -xe > /tmp/journal.txt
sudo journalctl -xe > /tmp/journal.txt
Take a look at /var/log/messages for further details. The cause of the problem might be obvious. The example below shows "No section: 'email_module'" which indicates that a section in the app.config is not present.
Apr 16 18:15:04 server resilient-circuits: File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2434, in load
Apr 16 18:15:04 server resilient-circuits: return self.resolve()
Apr 16 18:15:04 server resilient-circuits: File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2440, in resolve
Apr 16 18:15:04 server resilient-circuits: module = __import__(self.module_name, fromlist=['__name__'], level=0)
Apr 16 18:15:04 server resilient-circuits: File "/crypt/integration/functions/send_emails/send_emails/components/funct_send_emails.py", line 6, in <module>
Apr 16 18:15:04 server resilient-circuits: import send_emails.util.email_module as email
Apr 16 18:15:04 server resilient-circuits: File "/crypt/integration/functions/send_emails/send_emails/util/email_module.py", line 30, in <module>
Apr 16 18:15:04 server resilient-circuits: email_server = Config.get("email_module", "email_server")
Apr 16 18:15:04 server resilient-circuits: File "/usr/lib/python2.7/site-packages/backports/configparser/__init__.py", line 784, in get
Apr 16 18:15:04 server resilient-circuits: d = self._unify_values(section, vars)
Apr 16 18:15:04 server resilient-circuits: File "/usr/lib/python2.7/site-packages/backports/configparser/__init__.py", line 1160, in _unify_values
Apr 16 18:15:04 server resilient-circuits: raise NoSectionError(section)
Apr 16 18:15:04 server resilient-circuits: backports.configparser.NoSectionError: No section: 'email_module'
Apr 16 18:15:04 server systemd: resilient_circuits_int-mna.service: main process exited, code=exited, status=1/FAILURE
Apr 16 18:15:04 server systemd: Unit resilient_circuits_int-mna.service entered failed state.
Apr 16 18:15:04 server systemd: resilient_circuits_int-mna.service failed.
Apr 16 18:15:04 server systemd: resilient_circuits_int-mna.service holdoff time over, scheduling restart.
Apr 16 18:15:04 server systemd: Stopped Resilient-Circuits Service.
If you cannot resolve the problem, then log a support case at https://www.ibm.com/mysupport/ and provide the following information and files.
- Enable debug and collect the logs mentioned in Collecting logs for IBM Resilient Circuits after reproducing the failure
- /tmp/journal.txt
- /etc/systemd/system/resilient_circuits.service
- Output of pip freeze (use sudo if installed with sudo)
- app.config
- app.log
- /var/log/messages
Read Collecting logs for IBM Resilient Circuits for supplemental information on gathering data on IBM Resilient Circuits.
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSIP9Q","label":"IBM Security SOAR"},"ARM Category":[{"code":"a8m0z0000008ZtGAAU","label":"Integrations->Resilient Circuits"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
19 April 2021
UID
ibm16194223