Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


With help from Canonical I was able to figure out something. The maas-import-pxe-files is getting stuck when downloading ephemeral images from ubuntu. I isolated the following:

wget -v x -O /tmp/aaa.tmp

--2013-10-04 17:12:57--

Resolving (, Connecting to (||:443... failed: Connection timed out.

Connecting to (||:443... failed: Connection timed out.

Despite the fact that I can telnet 80, I can't wget. This is happening because my lab has a proxy. to work around this I had to

export http_proxy= proxy addr

export https_proxy= proxy addr

After that, note that

sudo maas-import-pxe-files

still doesn't work, but

sudo bash maas-import-pxe-files


I'm not sure yet whether this will also fix the problem reported in the MaaS GUI, but will update as soon as the install is complete.

Original question

I've setup MAAS with region and cluster controller in same node. I can log into the GUI, and was able to create the superuser. There are two problems, which might be manifestation of the same issue.

1) The yellow bar on the page is now showing this message:

The region controller does not know whether any boot images have been imported yet.  
If this message does not disappear in 5 minutes, there may be a communication problem between the region worker process and the region controller.  
Check the region worker's logs for signs that it was unable to report to the MAAS API.  

2) When running:

sudo maas-import-pxe-files  

I get this output:

$ sudo /usr/sbin/maas-import-pxe-files
Downloading to temporary location /tmp/tmp.rITlDMoaQl.
/tmp/tmp.rITlDMoaQl /var/log/maas
2013-10-03 11:14:46 URL:x [4965840/4965840] -> "linux" > [1]
2013-10-03 11:14:48 URL:x> amd64/current/images/netboot/ubuntu-installer/amd64//initrd.gz [17446386/17446386] -> "initrd.gz" [1]
2013-10-03 11:14:49 URL:x> amd64/current/images/netboot/ubuntu-installer/amd64//linux [5130968/5130968] -> "linux" > [1]
2013-10-03 11:14:51 URL:x> amd64/current/images/netboot/ubuntu-installer/amd64//initrd.gz [18668122/18668122] -> > > "initrd.gz" [1]
2013-10-03 11:14:52 URL:x> i386/current/images/netboot/ubuntu-installer/i386//linux [5015840/5015840] -> "linux" [1]
2013-10-03 11:14:54 URL:x [15977428/15977428] -> "initrd.gz" [1]
2013-10-03 11:14:55 URL:x [5171760/5171760] -> "linux" [1]
2013-10-03 11:14:57 URL:x [17086667/17086667] -> "initrd.gz" [1]
2013-10-03 11:14:58 URL:x [2978672/2978672] -"vmlinuz" [1]
2013-10-03 11:14:58 URL:x [4958070/4958070] -> "initrd.gz" [1]
2013-10-03 11:14:59 URL:x [3738504/3738504] -> "vmlinuz" [1]
2013-10-03 11:15:00 URL:x [6213909/6213909] -> "initrd.gz" [1]


( I had to prepend an 'x' in front of http in the posting because I'm not allowed to post more than two links)

The command stay stuck at this point without returning the prompt. Note that:

uname -a  

Linux myhost 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux  

I did find bug 1067558 and 1070318 but I can't figure out how to go past this.

Any help is appreciated.

share|improve this question

On Ubuntu Server 14.04

What worked for me on 14.04 was:

1) Configure a static address for the network adapter in /etc/network/interfaces

# Example configuration
auto eth0
iface eth0 inet static

2) Check internet access by pinging an external host, e.g. ping
The entry gateway is essential, as it will establish a route, like sudo route add default gw

3) Reconfigure MAAS to that static address and import PXE images: How to change the MaaS server ip address?

sudo dpkg-reconfigure maas-cluster-controller
sudo dpkg-reconfigure maas-region-controller
  • Delete 'Cluster master' (will be recreated)

4) Import PXE images

sudo maas-import-pxe-files
share|improve this answer

Can you try adding the lines export http_proxy= proxy addr and export https_proxy= proxy addr to /etc/environment and rebooting and see if that does it? I think sudo might not be passing on the proxy settings unless you use the sudo bash command you mentioned.

How do I configure proxies in Ubuntu Server or Minimal (CLI) Ubuntu?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.