0

I have a problem with MAAS node deployment. I commission the node and it all goes well, node shuts down and node is in ready status. I start the node it goes to Deploying state and when it starts to download root-tgz file it get's to 34% and I get the message Connection reset by the peer.

The message looks like:

Read error at byte 110815170/328093608 (Connection reset by peer). Retrying.

--2015-10-15 11:39:00-- (try: 2) http://10.0.0.1/MAAS/static/images/ubuntu/amd64/generic/trusty/release/root-tgz Connection to 10.0.0.1:80 failed.Connection refused.

gzip stdin: unexpected end of file

tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Unexpected error while running command. Command: [\'sh\', \'-cf\', \'wget "$1" --progress=dot:mega -0 - |tar -C "$2" --xattrs --xattrs -include=* -Sxpzf - --numeric-owner\', \'--\', \'http://10.0.0.1/MAAS/static/images/ubuntu/amd64/generic/trusty/release/root-tgz\', \'/tmp/tmp70Ffz8/target\'] Exit code: 2

Improve this question
10
  • Anyone experienced this problem?
    – Von Goofy
    Oct 15, 2015 at 12:27
  • Sounds a bit like a network error. Have you tried a second time? You can always save the Ethernet MAC address, delete the node, create the node again using the same MAC address and watch it go through the motions again.
    – Michael Blankenship
    Oct 15, 2015 at 20:06
  • I have tried multiple times and it's always stuck at the same percentage. I can wget the file from other nodes that are deployed without any error. So it's only happening to nodes that are deploying which is strange.
    – Von Goofy
    Oct 16, 2015 at 10:17
  • Assuming that you could begin a pull of the root-tgz download from another node using that URL (acknowledging that 10.0.0.1 is listening on port 80 and the path is valid) then if it were me I'd ssh to the problem node and see if I could then manually (as the ubuntu user) also try to pull from that URL. And then finally, I think I would delete the node, erase the hard disk manually, recreate it using a new node name and give that a try (on the assumption that the DHCP/DNS has re-issued the same IP address to two different nodes).
    – Michael Blankenship
    Oct 17, 2015 at 21:26
  • Done all of that and nothing. Also you cant ssh to the node that is in deployment since there is no root directory there. I wish I could do that because it would be easier to debug the situation.
    – Von Goofy
    Oct 19, 2015 at 9:52

1 Answer 1

Reset to default
0

I'm answering my question since I have discovered that fast installer probably has a bug and debian installer goes through the process of installation without a problem.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .