-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to start Replication Manager installed from tar ball (Failed to start replication-manager open source, replication-manager.service failed) #428
Comments
Do you mean to say that you don't have new packages for RPM? |
Yes. Kindly suggest, aarch RPM generated by Replication Manager, will it support for x86_64 ? Link Reference: Latest Binary: https://ci.signal18.io/mrm/builds/tags/v2.2.20/ |
Tried in my PC (x86_64), with aarch64 RPM. But its not happening. sudo yum install replication-manager-osc-2.2.20-1.aarch64.rpm From version v2.2.17 on wards purposely x86_64 RPM support is removed ? |
No, it's an error, thanks for reporting. We will restore it and keep you posted PS: aarch64 is for ARM CPU, you cannot use it on x86 architecture ;) |
@tanji Thanks for your prompt response. Once done, please update. |
The repositories have been updated. |
Thanks @tanji for your quick response & fix. |
Reference Link : https://ci.signal18.io/mrm/builds/tags/v2.2.20/replication-manager-osc-2.2.20-1.x86_64.rpm Now able to install & able to start the replication-manager service.
|
NOTE: Upto version 2.2.16 x86_64 RPM package available. It was worked without any problem.
Team,
Followed below steps for replication installation from Tar ball. Not able to start the service. Kindly share the proper steps.
Reference: https://docs.signal18.io/installation/setup-instructions
Downloaded Binary Reference: https://ci.signal18.io/mrm/builds/tags/v2.2.20/replication-manager-osc-2.2.20.tar.gz
Steps Followed:
systemctl status replication-manager.service
sudo systemctl start replication-manager.service
sudo systemctl status replication-manager.service
The text was updated successfully, but these errors were encountered: