
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Merge conflicts while upgrading the Replicate server on Linux for files: repctl.cfg and repctl.cfg.rpmnew
Apr 22, 2021 4:22:53 AM
May 11, 2020 8:47:36 AM
Merge conflicts can occur for files repctl.cfg and repctl.cfg.rpmnew during a Replicate upgrade on a Linux server. The upgrade will stop abruptly and will not continue with
replicate file creation in the /etc/init.d/areplicate and symbolic link in replicate bin directory.
The files will have to be manually changed. An example of the Replicate upgrade Verbose snippet is shown underneath.
Environment:
Resolution:
Replicate upgrade Verbose snippet:
Updating / installing... 1:areplicate-6.6.0-177 warning: /cdctools/attunity/replicate/bin/repctl.cfg created as /cdctools/attunity/replicate/bin/repctl.cfg.rpmnew ################################# [ 50%] post install ... changing ownership of /cdctools/attunity/replicate to cdcadm:ocdcprd There is a new configuration file to replace /cdctools/attunity/replicate/bin/repctl.cfg You will have to merge your old configuration with the new file The service is not being restarted See documentation for instructions warning: %post(areplicate-6.6.0-177.x86_64) scriptlet failed, exit status 7 pre uninstall ... Cleaning up / removing... 2:areplicate-6.4.0-425 warning: file /cdctools/attunity/replicate/lib/libarepteradata.img: remove failed: No such file or directory ################################# [100%] post uninstall ... ^^^^^^^^^^^^^^^^^^^ Post upgrade - Missing areplicate file ^^^^^^^^^^^^^^^^^^^
Resolution:
Work around:
To manually correct these conflicts with the files by adding additional details from repctl.cfg.rpmnew to repctl.cfg and create the service using :
pass=server_password iport=number rport=number data=data-directory [runservice=false] ./arep.sh install instancename(instancename is areplicate).
Note:
In the case of using any automation tool(ansible) to upgrade all the Linux replicate servers, they will end up doing this activity manually.
Note:
If a situation is reached the uninstall script wont run (instead of doing the workaround) use the rpm switch, --noscripts, that will remove Replicate. There are two dashes before noscripts:
Example of script:
verbose=true rpm -e areplicate