Help Center/
MapReduce Service/
Troubleshooting/
Using Hive/
WebHCat Fails to Be Started After the Hostname Is Changed
Updated on 2023-11-30 GMT+08:00
WebHCat Fails to Be Started After the Hostname Is Changed
Symptom
WebHCat fails to be started after the hostname is changed.
The following error is reported in the WebHCat startup log (/var/log/Bigdata/hive/webhcat/hive.log) of the corresponding node.
Cause Analysis
- The server account of the MRS WebHCat role contains the hostname. If you change the hostname after the cluster installation, WebHCat fails to start.
- The one-to-many or many-to-one association between IP addresses and hostnames is configured in the /etc/hosts file. As a result, the IP address and hostname cannot be obtained correctly after the hostname and hostname -i commands are executed.
Solution
- Change the hostname of the modified node to the initial hostname of the cluster.
- Check whether the /etc/hosts of the node where WebHCat is located is correctly configured.
- Restart WebHCat.
Parent topic: Using Hive
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