automation-api-quickstart icon indicating copy to clipboard operation
automation-api-quickstart copied to clipboard

bmc_api is not tiggerring the job resource in the cntrlm server has context menu

Open Abhishek-Control-M opened this issue 1 year ago • 0 comments

We encountered an error while using the Control-M API with the following curl command.

curl -H "Content-Type: application/json" -X POST -d "{"username":"$user","password":"$passwd"}" "$endpoint/session/login"

curl: (35) SSL received a record that exceeded the maximum permissible length. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (35) SSL received a record that exceeded the maximum permissible length. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (35) SSL received a record that exceeded the maximum permissible length. % Total % Received % Xferd Average Speed Time Time Time Current

During our troubleshooting, we changed the protocol from HTTPS to HTTP:

After making these changes, we ran the job again. This time, there was no SSL error, but the Control-M API still isn't triggering job resources. I tried and see everything but not sure why Control-M API still isn't triggering job resources.

Abhishek-Control-M avatar Oct 30 '24 09:10 Abhishek-Control-M