Help Center/
MapReduce Service/
User Guide (Paris Region)/
Troubleshooting/
Using DBService/
DBService Backup Failed Because the Floating IP Address Is Unreachable
Updated on 2022-12-14 GMT+08:00
DBService Backup Failed Because the Floating IP Address Is Unreachable
Symptom
The default DBService backup fails, but backups of NameNode, LdapServer, and OMS are successful.
Cause Analysis
- Check the error information on the DBService backup page:
Clear temporary files at backup checkpoint DBService_test_DBService_DBService_20180326155921 that fialed last time. Temporyary files at backup checkpoint DBService_test_DBService_DBService20180326155921 that failed last time are cleared successfully.
- Check the /var/log/Bigdata/dbservice/scriptlog/backup.log file. It is found that the log printing stops and no related backup information is found.
- Check the /var/log/Bigdata/controller/backupplugin.log file on the active OMS node. The following error information is found:
result error is ssh:connect to host 172.16.4.200 port 22: Connection refused (172.16.4.200 is the floating IP address of DBService) DBService backup failed.
Solution
- Log in to the active DBService node (the Master node bound with the DBService floating IP address).
- Add the DBService floating IP address to ListenAddress or comment out ListenAddress in the /etc/ssh/sshd_config file.
- Run the following command to restart the SSHD service:
service sshd restart
- Check whether the next DBServie backup is successful.
Parent topic: Using DBService
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot