Hello everyone, I have a problem on my ML server as it's flooding /var/log/messages with the following errors:
MarkLogic: Failed to update hostname on server localhost MarkLogic: Failed renaming my host via localhost MarkLogic: [/opt/MarkLogic/mlcmd/scripts/initialize-node.xsh line: 59] MarkLogic: Failed renaming my host to all online cluster hosts - waiting MarkLogic: [/opt/MarkLogic/mlcmd/scripts/initialize-node.xsh line: 62] MarkLogic: Failed to update hostname - waiting to retry MarkLogic: [/opt/MarkLogic/mlcmd/scripts/initialize-node.xsh line: 139] MarkLogic: Sleeping for 17 seconds MarkLogic: [/opt/MarkLogic/mlcmd/scripts/initialize-node.xsh line: 140] MarkLogic: State is valid-name MarkLogic: Original host name <HOSTNAME-FROM-SMALLER-INSTANCE> does not match our new host name <NEW-HOSTNAME-AFTER-INCREASE> MarkLogic: [/opt/MarkLogic/mlcmd/scripts/initialize-node.xsh line: 38] MarkLogic: Attempting to rename on the following hosts: localhost MarkLogic: [/opt/MarkLogic/mlcmd/scripts/initialize-node.xsh line: 49] MarkLogic: Attempting to contact localhost to rename my hostid 4182996195802625515 to host <NEW-HOSTNAME-AFTER-INCREASE> MarkLogic: [/opt/MarkLogic/mlcmd/scripts/initialize-node.xsh line: 51] MarkLogic: Renaming host to <NEW-HOSTNAME-AFTER-INCREASE> on localhost MarkLogic: Rename request returns 401 MarkLogic: <error xmlns="http://marklogic.com/manage";>#012 <status-code>401</status-code>#012 <status>Unauthorized</status>#012 <message-code/>#012 <message>Not authorized.</message>#012</error> MarkLogic: Error 401 renaming host MarkLogic: <error xmlns="http://marklogic.com/manage";>#012 <status-code>401</status-code>#012 <status>Unauthorized</status>#012 <message-code/>#012 <message>Not authorized.</message>#012</error> I'm running MarkLogic 7.0-5.4 on ec2 under ASG using CloudFormation template that was provided by MarkLogic. In our development environment we're using just 1 instance under ASG, which is fine for now. I had to increase the size of the ec2 and below are the steps that I took: - Update size in cfn template, - Added change request in CloudFormation: o Launch configuration was replaced (great) o But nothing happened, meaning current instance was not replaced ( that's not a problem but I was looking for different result) o Waited 10 minutes and terminated current instance o ASG provided new larger instance and after few minutes ML was back online (great, almost) Everything seems to be working on the front end but above errors are just looping and flooding the log. It seems like ML application doesn't know how to update new hostname that is provided with new ec2. Is that a bug or there are some steps that we could take to prevent this issue from happening when new instance is provisioned by ASG? Thank you, Ernest Gulik
_______________________________________________ General mailing list General@developer.marklogic.com Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
