Hi Team
I also installed the resilient circuits on my machine and i attached app.config for your refernece i cant able run resilient-circuits run having the error
C:\temp_dir>resilient-circuits run
2021-02-05 13:04:28,359 INFO [app] Configuration file: C:\Users\Administrator\.resilient\app.config
2021-02-05 13:04:28,360 INFO [app] Resilient server: localhost
2021-02-05 13:04:28,360 INFO [app] Resilient user:
antivirus@indianbank.co.in2021-02-05 13:04:28,361 INFO [app] Resilient org: IBM
2021-02-05 13:04:28,362 INFO [app] Logging Level: INFO
2021-02-05 13:04:30,369 INFO [rest_helper] Retry 1:1 waiting 60 secs for Resilient connection
2021-02-05 13:05:32,382 INFO [filelock] Lock 713066344400 released on C:\Users\Administrator\.resilient\resilient_circuits_lockfile
Unable to lock C:\Users\Administrator\.resilient\resilient_circuits_lockfile: Exceeded retries: 1
appconfig file
[resilient]
# Basic service connection
host=localhost
port=443
# Use (api_key_id, api_key_secret)
# api_key_id=ApiKeyId
# api_key_secret=ApiKeySecret
# Or (email, password)
email=
nitece2012@gmail.compassword=password
org=IBM
# Number of attempts to retry when connecting to Resilient. 0 = unlimited retries
#max_connection_retries=10
# CP4S
# Actions Module connection
# Use stomp_url when configuring an environment for CP4S
#stomp_host=<CP4S stomp URL>
#stomp_port=443
#resource_prefix=/api/respond
#stomp_timeout=120
#stomp_max_retries=3
# Optional parameters for stomp connections.....
# Please refer to IBM Support for additional settings to those outlined below
# format...... stomp_params=<param1=value1>,<,param2=value2>
#stomp_params=startupMaxReconnectAttempts=3,maxReconnectAttempts=10,initialReconnectDelay=20
# Directory containing additional components to load
# componentsdir=components
# Existing directory to write logs to, or set with $APP_LOG_DIR
logdir c:\Users\Administrator\.resilient
#logdir=/tmp
logfile=app.log
loglevel=INFO
# The number of Functions to run concurrently (within the range: 1 <= 50)
num_workers=10
# If your Resilient server uses a self-signed TLS certificate, or some
# other certificate that is not automatically trusted by your machine,
# you need to explicitly tell the Python scripts that it should be trusted.
# If you don't want to use a cert you can set cafile=false.
# To explicitly trust a site, download its certificate to a file, e.g:
# mkdir -p ~/.resilient
# openssl s_client -connect #resilient.example.com:443 -showcerts < /dev/null 2> /dev/null | openssl x509 - outform PEM > ~/.resilient/cert.cer
# then specify the file (remove the '#' from the line below)
cafile=false
------------------------------
Nithiyanantham Palanisamy
------------------------------
Original Message:
Sent: Wed October 28, 2020 06:09 AM
From: John Quirke
Subject: Unable to connect the resilient circuit run
Hi Marc
It looks like your Python environment may not be fully configured.
Can you run the following commands
python --version
python3 --version
pip --version
pip3 --version
I think you may have installed your integration on python3 but you are trying to run in python2 possibly.
Your default Python should point to python3
Could you provide me the contents of /usr/local/bin to confirm.
If I am right I have come across this issue before and it should hopefully be easily resolved.
------------------------------
John Quirke
Original Message:
Sent: Tue October 27, 2020 11:44 PM
From: Marc Lainez
Subject: Unable to connect the resilient circuit run
Hi John.
It is running in azure virtual machine RedHat 7.8. we are using Python 3.6.8. Resilient Integration server is installed same with the machine of Resilient Platform. Please see below command and result
For sudo pip3 list
cachetools (2.1.0)
certifi (2020.6.20)
cffi (1.14.3)
chardet (3.0.4)
circuits (3.2)
cryptography (3.2)
filelock (3.0.12)
idna (2.10)
importlib-metadata (2.0.0)
jeepney (0.4.3)
Jinja2 (2.11.2)
keyring (21.4.0)
MarkupSafe (1.1.1)
pathtools (0.1.2)
pip (9.0.3)
pycparser (2.20)
PySocks (1.7.1)
pytz (2020.1)
rc-phantomcyber (1.0.20)
requests (2.24.0)
requests-mock (1.8.0)
requests-toolbelt (0.9.1)
resilient (38.0.76)
resilient-circuits (38.0.76)
SecretStorage (3.1.2)
setuptools (50.3.2)
six (1.15.0)
stompest (2.3.0)
urllib3 (1.25.11)
watchdog (0.10.3)
wheel (0.35.1)
zipp (3.4.0)
For pip3 list
cachetools (2.1.0)
certifi (2020.6.20)
cffi (1.14.3)
chardet (3.0.4)
circuits (3.2)
cryptography (3.1.1)
filelock (3.0.12)
idna (2.10)
importlib-metadata (2.0.0)
jeepney (0.4.3)
Jinja2 (2.11.2)
keyring (21.4.0)
MarkupSafe (1.1.1)
pathtools (0.1.2)
pip (9.0.3)
pycparser (2.20)
PySocks (1.7.1)
pytz (2020.1)
requests (2.24.0)
requests-mock (1.8.0)
requests-toolbelt (0.9.1)
resilient (38.0.76)
SecretStorage (3.1.2)
setuptools (50.3.2)
six (1.15.0)
stompest (2.3.0)
urllib3 (1.25.11)
watchdog (0.10.3)
zipp (3.3.1)
[integration@hostname ~]$ sudo /usr/local/bin/resilient-circuits list
The following packages and components are installed:
rc-phantomcyber==1.0.20:
PhantomActions
------------------------------
Marc Lainez
Original Message:
Sent: Tue October 27, 2020 12:17 PM
From: John Quirke
Subject: Unable to connect the resilient circuit run
Hi Marc
(sorry for delay in coming back to you)
are you running from locally or inside a virtual environment ?
which version of python are you running ? run which python ?
run pip list and verify python modules installed ?
run resilient-circuits list ? can you share output
------------------------------
John Quirke
Original Message:
Sent: Tue October 27, 2020 07:45 AM
From: Marc Lainez
Subject: Unable to connect the resilient circuit run
Hi John.
Thanks for your help, We already now fixed this one this afternoon, the problem is the hostname is not in the /etc/hosts. Now I have faced another problem.
I was unable to run the "/usr/local/bin/resilient-circuits run" but if i do this one "sudo /usr/local/bin/resilient-circuits run" I was able to run it.
[integration@hostname .resilient]$ /usr/local/bin/resilient-circuits run
Traceback (most recent call last):
File "/usr/local/bin/resilient-circuits", line 7, in <module>
from resilient_circuits.bin.resilient_circuits_cmd import main
ModuleNotFoundError: No module named 'resilient_circuits'
------------------------------
Marc Lainez
Original Message:
Sent: Tue October 27, 2020 05:52 AM
From: John Quirke
Subject: Unable to connect the resilient circuit run
Hi Marc please verify that your resilient server is reachable and can be pinged.
Please enable DEBUG level logging in app.config.
Also not sure is this is your full log message as some detail may be missing.
If you can share your app.config (remove sensitive info) might help us understand why you cant connect.
Also please identify what version of resilient you are using and the user exists on that server ..
------------------------------
John Quirke
Original Message:
Sent: Fri October 23, 2020 09:38 AM
From: Marc Lainez
Subject: Unable to connect the resilient circuit run
Hi All.
We would like to request your assistance on this. We installed Resilient Integration Server to the machine same with Resilient Platform however when running the scrpt resilient-circuits run I encountered below error
2020-10-23 21:23:55,405 WARNING [co3] Unverified HTTPS requests (cafile=false).
2020-10-23 21:23:55,416 INFO [rest_helper] Retry 1:1 waiting 60 secs for Resilient connection
2020-10-23 21:24:55,469 WARNING [co3] Unverified HTTPS requests (cafile=false).
2020-10-23 21:24:55,476 INFO [filelock] Lock 140440841715048 released on /root/.resilient/resilient_circuits_lockfile
Unable to lock /root/.resilient/resilient_circuits_lockfile: Exceeded retries: 1
Thanks.
------------------------------
Marc
------------------------------