Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 2 subscribers
  • Views 1163 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Update 9.002-12 HA Error

rprengel
This happens trying to install the update (downloaded manually)
1)
What is going wrong
2)
What is 79.125.21.244. 
whois shows Amazon Web Services, Elastic Compute Cloud, EC2, EU

Thanks 

Ralf

2012:09:03-08:54:33 winter-do-1 ha_daemon[3767]: id="38A0" severity="info" sys="System" sub="ha" name="Waiting for 1 nodes to finish up2date process before initiating graceful takeover!"
2012:09:03-08:54:35 winter-do-1 ha_proxy[9152]: Connect (file descriptor 6): node2 [198.19.250.2]
2012:09:03-08:54:35 winter-do-1 ha_proxy[9152]: Request (file descriptor 6): CONNECT 79.125.21.244:443 HTTP/1.0
2012:09:03-08:54:35 winter-do-1 ha_proxy[9152]: No proxy for 79.125.21.244
2012:09:03-08:54:35 winter-do-1 ha_proxy[9152]: Established connection to host "79.125.21.244" using file descriptor 7.
2012:09:03-08:54:35 winter-do-1 ha_proxy[9152]: Not sending client headers to remote machine
2012:09:03-08:54:35 winter-do-1 ha_proxy[9152]: Closed connection between local client (fd:6) and remote client (fd:7)
2012:09:03-08:54:41 winter-do-2 ha_daemon[3797]: id="38A2" severity="error" sys="System" sub="ha" name="Up2date failed!"
2012:09:03-08:54:43 winter-do-1 ha_daemon[3767]: id="38A0" severity="info" sys="System" sub="ha" name="Node 2 changed state: UP2DATE -> UP2DATE-FAILED"
2012:09:03-08:54:43 winter-do-1 ha_daemon[3767]: id="38A3" severity="error" sys="System" sub="ha" name="Up2date failed on Slave node 2, stopping up2date process!"


This thread was automatically locked due to age.
Parents
  • 0
    Hi Ralf,

    I saw the same lines regarding this misterious IP in my ha-log while doing the update. But my installation went through without any problem. I think there must be another reason for the failed update on your node 2.

    I had a similar problem while installing 9.001 and couldn't find a reason. Today I believe I didn't wait long enough after uploading the up2date before clicking the start update button and so the up2date file wasn't completly synced between the nodes. But that's just a guess because I could replicate the problem.

    Stephan
Reply
  • 0
    Hi Ralf,

    I saw the same lines regarding this misterious IP in my ha-log while doing the update. But my installation went through without any problem. I think there must be another reason for the failed update on your node 2.

    I had a similar problem while installing 9.001 and couldn't find a reason. Today I believe I didn't wait long enough after uploading the up2date before clicking the start update button and so the up2date file wasn't completly synced between the nodes. But that's just a guess because I could replicate the problem.

    Stephan
Children
No Data
Cookie Information Banner