ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Policy Server Upgrade Failing With Policy Server is not running Message
Article ID: 127226
Updated On:
Products
CA Single Sign On Secure Proxy Server (SiteMinder)
CA Single Sign On SOA Security Manager (SiteMinder)
CA Single Sign-On
Issue/Introduction
We are in the process of upgrading our 12.51 Policy Server (in-place) on RedHat Linux and we are receiving a failed upgrading message stating that the Policy Server is not running even though the Policy Server is up and running
policy server, failed upgrade.
Getting error:
failed.
COMMAND: sh /tmp/830711.tmp/TestCryptoConfig.sh
COMMAND: sh /tmp/830711.tmp/SetCryptoConfig.sh
EXISTING_VERSION: 12.51.0.905
PRODUCT_VERSION: 12.70.0.1194
INSTALL_TYPE: UPGRADE
The installer requested that the Policy server should be started before
the install can proceed:
Policy Server is not running
----------------------------
The Policy Server must be running to execute UpgradeReadinessCheck
tool.
Please start the Policy Server, before continuing.
[...]
->1- Proceed
2- Back
3- Cancel
ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT
THE
DEFAULT: 3
policy server, failed upgrade.
Getting error:
failed.
COMMAND: sh /tmp/830711.tmp/TestCryptoConfig.sh
COMMAND: sh /tmp/830711.tmp/SetCryptoConfig.sh
EXISTING_VERSION: 12.51.0.905
PRODUCT_VERSION: 12.70.0.1194
INSTALL_TYPE: UPGRADE
The installer requested that the Policy server should be started before
the install can proceed:
Policy Server is not running
----------------------------
The Policy Server must be running to execute UpgradeReadinessCheck
tool.
Please start the Policy Server, before continuing.
[...]
->1- Proceed
2- Back
3- Cancel
ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT
THE
DEFAULT: 3
Cause
There were two instances of the .com.zerog.registry.xml file on the server.
This file contains information about the previous version. It appears that one of the instances was an instance from the previous install and so the installer was detecting the Policy Server as not running.
This file contains information about the previous version. It appears that one of the instances was an instance from the previous install and so the installer was detecting the Policy Server as not running.
Environment
Redhat Linux 6.3 Policy Server R12.51
Resolution
1) Deleted below files from the /tmp directory of the Linux server and then restarted the server:
/tmp: (siteminder files)
GCL-SiteMinder-A.pipe
GCL-SiteMinder-B.pipe
GCL-SiteMinder.sem
snrrpni?{{?pip
2) Ran command to find all instances of the ".com.zerog.registry.xml" file on the server and found 3 instances of the file
/smuser/.com.zerog.registry.xml
/var/.com.zerog.registry.xml
Note:
The third instance was in the Siteminder Policy Server install directory. This instance should be left untouched
3) Renamed the ".com.zerog.registry.xml" under the following directories:
/smuser/.com.zerog.registry.xml_backup
/var/.com.zerog.registry.xml_backup
4) We restarted the server and ran the upgrade again and the current Policy Server install was detected as running.
/tmp: (siteminder files)
GCL-SiteMinder-A.pipe
GCL-SiteMinder-B.pipe
GCL-SiteMinder.sem
snrrpni?{{?pip
2) Ran command to find all instances of the ".com.zerog.registry.xml" file on the server and found 3 instances of the file
/smuser/.com.zerog.registry.xml
/var/.com.zerog.registry.xml
Note:
The third instance was in the Siteminder Policy Server install directory. This instance should be left untouched
3) Renamed the ".com.zerog.registry.xml" under the following directories:
/smuser/.com.zerog.registry.xml_backup
/var/.com.zerog.registry.xml_backup
4) We restarted the server and ran the upgrade again and the current Policy Server install was detected as running.
Feedback
Yes
No
Powered by
