I was able to increase the im_ps.log log verbosity by editing the im_ps.conf[1] file and restarting the ProvServer afterwards. You need to see the techdoc[2] in order to see how are willing information you need on the log. You need to fiddle around with it a bit to get the correct verbosity.
You will want to change the loglevel parameter accordingly. For example, if you need "Print out packets sent and received" (16) and "Connection management" (8), you should sum up the values and put it in there. In my case:
Change the conf file, restart PS and see if you can understand what is going on.
Hope it helps.
[1] /opt/CA/IdentityManager/ProvisioningServer/data/im_ps.log - if you do not have the vApp version, you need to find the correspondent file for your deployment (I would expect it to be in the Provisioning Server data folder as stated)
[2]
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-identity-and-access-management/identity-manager/14-2/reference/provisioning-maintenance/view-and-maintain-log-files.html------------------------------
Software Consultant
Gliat Tecnologia da Informação
São Paulo
Brazil
------------------------------
Original Message:
Sent: 12-13-2019 10:59 AM
From: Rakesh Puril
Subject: Prov Server Upgrade IM R14.3 CP1 Issue.
That's the worst part here, there are no logs at all and the only log that's getting created im_ps.log is zero bytes and has no content in it.
Thanks.
Original Message:
Sent: 12-13-2019 10:54 AM
From: SCOTT Owens
Subject: Prov Server Upgrade IM R14.3 CP1 Issue.
Anything in the etatranslog?
------------------------------
Best regards,
Scott Owens
Sr Support Engineer
------------------------------
And, as always Perhaps there are others in the communities who have experience in doing this and we invite them to comment here also.
Another option may be to reach out to our partner HCL Technologies to see in what way they can assist further. The Enterprise Studio team of HCL can be reached at enterprisestudio@hcl.com. https://www.hcltech.com/enterprise-studio
Original Message:
Sent: 12-13-2019 10:51 AM
From: Rakesh Puril
Subject: Prov Server Upgrade IM R14.3 CP1 Issue.
Hello Scott,
Thanks for your reply, Yes we did recycle the Router DSA on the server where IMPS is running and also we recycled the Provisioning Directory ( including User and Policy Store) as well. But no luck.
Thanks
Rakesh
Original Message:
Sent: 12-13-2019 10:37 AM
From: SCOTT Owens
Subject: Prov Server Upgrade IM R14.3 CP1 Issue.
Are the DSA running? Can you run dxserver stop all and dxserver start all. Anything in the etatranslog?
------------------------------
Best regards,
Scott Owens
Sr Support Engineer
------------------------------
And, as always Perhaps there are others in the communities who have experience in doing this and we invite them to comment here also.
Another option may be to reach out to our partner HCL Technologies to see in what way they can assist further. The Enterprise Studio team of HCL can be reached at enterprisestudio@hcl.com. https://www.hcltech.com/enterprise-studio
Original Message:
Sent: 12-12-2019 01:28 PM
From: Rakesh Puril
Subject: Prov Server Upgrade IM R14.3 CP1 Issue.
Hello All,
We are working on upgrading our IM Environment to R 14.3 CP1 and the Identity Manager has been successfully upgraded. We tried to follow the instructions to upgrade the IM Provisioning Server or IMPS as well to this version but the IMPS is not starting. It is juts giving message that im_ps startup failed. There are no logs being updated as well because the imps.log is "zero" bytes so we are not sure where is the problem.
We are running on Redhat Linux 6 with IMPS R 14.3 CP1. Please suggest if you have seen this and how this issue can be fixed. Thanks for your help in advance.
Note: After upgrade the imps command will not work so we changed all occurrences for "/opt" to "/apps" because last installation was done in this directory and the SLAPDUSER was changed as well from default "imps" to "idmuser" that it was running fine before the upgrade.
Instructions from the Support that we followed:
*************************************
INSTRUCTIONS_ON_HOW_TO_DEPLOY:
*************************************
****** on LINUX: --> for "improvisioning.zip":
1. Stop the "Provisioning Server".
2. "linux" folder --> This folder has "improvisioning.zip" --> The "improvisioning.zip" has --> "cp-version.txt",
"bin", "data" & "lib" folders.
3. Copy "improvisioning.zip" to a "tmp" location and extract.
3. Take backup of "bin" & "lib" folders from "<Provisioning Server Installed Location>/".
4. Copy the provided "bin" and "lib" folders to "<Provisioning Server Installed Location>/".
5. Change owner and permissions to the above copied "bin" and "lib" folders.
chown imps:imps bin
chmod 775 bin
&
chown imps:imps lib
chmod 775 lib
6. Take backup of "acfparse.ptt" and "adsparse.ptt" files from "<Provisioning Server Installed Location>/data".
7. Copy the provided "acfparse.ptt" and "adsparse.ptt" to "<Provisioning Server Installed Location>/data".
8. Change owner and permissions to the above copied ".ptt" files.
chown imps:imps *.ptt (Note: change owner to ".ptt" files)
chmod 660 *.ptt (Note: change permission to ".ptt" files)
Thanks