default linux
label linux
kernel boot/Ubuntu-12.04-x86_64-linux
append initrd=boot/Ubuntu-12.04-x86_64-initrd.gz interface=auto preseed/url=http://192.168.1.111/unattended/provision ramdisk_size=10800 root=/dev/rd/0 rw auto hostname=unassigned-hostname locale=en_US console-setup/ask_detect=false consol
After launching the installation, the client met an error: the debconf
could not retrieved from
preseed/url=http://192.168.1.90/unattended/provision, anything wrong with
it?
After copied the content of provision to a test file, the installation was
running, but failed in the last step(exit 1):
d-i preseed/late_command string wget <%= foreman_url("finish") %> -O
/target/tmp/finish.sh && in-target chmod +x /tmp/finish.sh && in-target
/tmp/finish.sh
···
On Monday, September 24, 2012 3:03:12 PM UTC+8, gm wrote:
>
> Hi All,
>
> I plan to use Preseed default PXElinux, Preseed Default,
> Preseed DefaultFinish to provision Ubuntu, the content of pxelinux.cfg/mac file is:
>
> default linux
> label linux
> kernel boot/Ubuntu-12.04-x86_64-linux
> append initrd=boot/Ubuntu-12.04-x86_64-initrd.gz interface=auto preseed/url=http://192.168.1.111/unattended/provision ramdisk_size=10800 root=/dev/rd/0 rw auto hostname=unassigned-hostname locale=en_US console-setup/ask_detect=false consol
>
>
> After launching the installation, the client met an error: the debconf
> could not retrieved from preseed/url=
> http://192.168.1.90/unattended/provision, anything wrong with it?
>
> Thanks,
>
>
> Hi All,
>
> I plan to use Preseed default PXElinux, Preseed Default<https://192.168.1.90/config_templates/Preseed%20Default/edit>,
> Preseed Default<https://192.168.1.90/config_templates/Preseed%20Default/edit>Finish to provision Ubuntu, the content of pxelinux.cfg/mac file is:
>
> default linux
> label linux
> kernel boot/Ubuntu-12.04-x86_64-linux
> append initrd=boot/Ubuntu-12.04-x86_64-initrd.gz interface=auto preseed/url=http://192.168.1.111/unattended/provision ramdisk_size=10800 root=/dev/rd/0 rw auto hostname=unassigned-hostname locale=en_US console-setup/ask_detect=false consol
>
>
> After launching the installation, the client met an error: the debconf
> could not retrieved from preseed/url=
> http://192.168.1.111/unattended/provision<http://192.168.1.90/unattended/provision>,
> anything wrong with it?
>
> Thanks,
>
···
On Monday, September 24, 2012 3:03:12 PM UTC+8, gm wrote:
> Hello,
>
> I'm having the same problem. I think that there is an error in the
> command because the wget command download the finish file at *
> /target/tmp/finish.sh* and after, this is /tmp/finish.sh that is used
> instead of /target/tmp/finish.sh
>
This is correct - the command is run in the /target chroot, so the path is
actually /tmp/finish.sh
> Anyway, I modified it and I've still the error. The things that is really
> strange is that when I run the same command from a console that I activate
> it works just fine…
>
See above.
> I suspect a problem with environment variable since I added a mirror in
> the preseed file "d-i mirror/http/proxy string http://1.2.3.4:3128". So
> maybe the wget tries to use the proxy? I don't know how to see if it is the
> case. I tried to pass the option --no-proxy but this option is not
> supported by the wget that is embedded into the busybox.
>
The proxy environment will need to be unset for the wget to work.
–no-proxy is definitely supported by the squeeze installer, I use it
myself. You could also call "unset http-proxy" before the wget.
···
On 24 April 2013 08:46, Guillaume Thouvenin wrote:
>
>
>> Hello,
>>
>> I'm having the same problem. I think that there is an error in the
>> command because the wget command download the finish file at *
>> /target/tmp/finish.sh* and after, this is /tmp/finish.sh that is used
>> instead of /target/tmp/finish.sh
>>
>
> This is correct - the command is run in the /target chroot, so the path is
> actually /tmp/finish.sh
>
Oh I understand the in-target now… Thanks.
> The proxy environment will need to be unset for the wget to work.
> --no-proxy is definitely supported by the squeeze installer, I use it
> myself. You could also call "unset http-proxy" before the wget.
>
I will try with unset http-proxy then. I restore the finish script with
the right path but I still have the problem: Execution of the preseed
command "wget --no-proxy http://…" failed with exit code 1. And if I
look the log on console I can see:
So it works for me but I need to add http_proxy= before wget command. I
don't know why but –no-proxy is not working.
Otherwise I have still an error but now it is "error 8". I think that it
is because the host "seems to be adrift". So it works
···
On Wednesday, April 24, 2013 12:33:39 PM UTC+2, Guillaume Thouvenin wrote:
>
>
> I will try with unset http-proxy then. I restore the *finish* script with
> the right path but I still have the problem: Execution of the preseed
> command "wget --no-proxy http://......" failed with exit code 1. And if I
> look the log on console I can see:
>
> log-output: wget: unrecognized option '--no-proxy'
> log-output: BusyBox v1.18.5 (Ubuntu 1:1.8.18.5-1ubuntu4)
> log-output: multi-call binary
>
The --proxy does not seem to work for me, but "-Y off" does the trick
···
On Wednesday, April 24, 2013 7:49:30 AM UTC-4, Guillaume Thouvenin wrote:
>
>
> On Wednesday, April 24, 2013 12:33:39 PM UTC+2, Guillaume Thouvenin wrote:
>>
>>
>> I will try with unset http-proxy then. I restore the *finish* script
>> with the right path but I still have the problem: Execution of the preseed
>> command "wget --no-proxy http://......" failed with exit code 1. And if I
>> look the log on console I can see:
>>
>> log-output: wget: unrecognized option '--no-proxy'
>> log-output: BusyBox v1.18.5 (Ubuntu 1:1.8.18.5-1ubuntu4)
>> log-output: multi-call binary
>>
>
> So it works for me but I need to add *http_proxy=* before wget command. I
> don't know why but *--no-proxy* is not working.
> Otherwise I have still an error but now it is "error 8". I think that it
> is because the host "seems to be adrift". So it works :)
>
I has been workin' with foreman and preseed ubuntu 10.04 provision, stuff,
and i faced the same issue related here, googlin' more that usual i found
this<https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/833994>post , explaining why … and overall… why do not try modify foreman
config to use plain http
···
El miércoles, 8 de mayo de 2013 14:28:08 UTC-4, Guy Matz escribió:
>
> I think the installer runs under busybox (
> http://www.busybox.net/downloads/BusyBox.html) and uses busybox's wget,
> which has slightly different command-line options:
>
> wget [-c|--continue] [-s|--spider] [-q|--quiet] [-O|--output-document file][--header
> 'header: value'] [-Y|--proxy on/off] [-P DIR][-U|--user-agent agent] url
>
> The --proxy does not seem to work for me, but "-Y off" does the trick
>
> On Wednesday, April 24, 2013 7:49:30 AM UTC-4, Guillaume Thouvenin wrote:
>>
>>
>> On Wednesday, April 24, 2013 12:33:39 PM UTC+2, Guillaume Thouvenin wrote:
>>>
>>>
>>> I will try with unset http-proxy then. I restore the *finish* script
>>> with the right path but I still have the problem: Execution of the preseed
>>> command "wget --no-proxy http://......" failed with exit code 1. And if I
>>> look the log on console I can see:
>>>
>>> log-output: wget: unrecognized option '--no-proxy'
>>> log-output: BusyBox v1.18.5 (Ubuntu 1:1.8.18.5-1ubuntu4)
>>> log-output: multi-call binary
>>>
>>
>> So it works for me but I need to add *http_proxy=* before wget command.
>> I don't know why but *--no-proxy* is not working.
>> Otherwise I have still an error but now it is "error 8". I think that it
>> is because the host "seems to be adrift". So it works :)
>>
>
