KB Article #178709
Copilot failed in Abend 0C4 and cannot be restarted since the 1st Abend occurred​
Problem
Copilot Abend 0C4 at each start attempt. (mvs)
Messages in the sysout:
Copilot server successfully started on port 1866.
Copilot server successfully started on ssl port 1867.
CEE3204S The system detected a protection exception (System Completion Code=0C4).
From entry point CRYPTO_add_lock at statement 633 at compile unit offset +0000010E at entry offset +0000010E at address 2F836216.
Also from the sysout:
20170704 11445116 MSGALL CFTCOPIS38423 Central Governance: sending certificate renewal request Copilot starting...
20170704 11445116 MSGALL CFTCOPIS38423 Central Governance: sending certificate renewal request Copilot starting...
Resolution
The certificate renewal process appears to be the root cause in the reported issue.
As a workaround to restart Copilot, change the renewal period from cg.renewal_period=10 (days) instead of 60days (default)
You can also change the renewal date and time to a farther date value: cg.certificate.governance.renewal_datetime,value
Note: The issue related to the certificate renewal process has been fixed in CG 1.1.2 SP4
Note2: The issue related to Copilot crashing when the certificate is already expired at renewal time is fixed in:
Transfer_CFT_3.2.2-SP1_Patch3 for z/OS.
Transfer_CFT_3.2.2-SP1_Patch5 for Linux and Windows.
Depending of the CFT version registered to your CG, the renewal issue can lead to other symptoms, see KB articles: