Cisco Bug: CSCvi18522 - After ISSU Rollback,Pcrfclient02 Diagnostics gets stuck after startall/stopall or restartall process
Sep 11, 2018
- Cisco Policy Suite for Mobile
Known Affected Releases
During ISSU rollback, if there is any issue for which Rollback is required, the diagnostics takes more time to pass as pcrfclient02 diagnostics gets stuck and after half an hour or more it gets cleared. Symptom: During ISSU rollback, below is seen in pcrfclient02 for which diagnostics gets failed: Retrieving diagnostics from pcrfclient02:9045...[FAIL] Connected to CPS: no diagnostics found. CPS may be still starting up. Ensure CPS service is started (runonone.sh pcrfclient02 /etc/init.d/qns status) and monitor the log for additional errors Conditions: stopall/startall is done after ISSU rollback and the problem is seen in diagnostics.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases