> $ grep -l -a -E '^Failed to fetch.+s3' *
> ...
> 2012-03-06-slave-i-63954a07.log
> 2012-04-02-slave-i-7fff1c18.log
<snip>
> 2012-04-04-slave-i-0f32c068.log
> 2012-04-04-slave-i-a5a153c2.log
>
> So yes, we're still having it almost everyday, it's just auto-retrying hides it from our eyes.
I'd really appreciate it if you could put the apt-pipelining change in
place and remove the update loop.
Ie, you can either use a daily ami (or one of those just released today), or
sudo sh -c 'cat > /etc/apt/apt.conf.d/90cloud-init-pipelining' <<EOF
//Written by cloud-init per 'apt_pipelining'
Acquire::http::Pipeline-Depth "0";
EOF
I really, really, value the automated results you're getting, so if you
could turn off the retries and add that, then yell loudly when it fails,
i'd really appreciate it.
If you have disabled pipeline in apt, and are still seeing errors, please
yell loudly.
On Wed, 4 Apr 2012, Paul Sokolovsky wrote:
> $ grep -l -a -E '^Failed to fetch.+s3' * 06-slave- i-63954a07. log 02-slave- i-7fff1c18. log 04-slave- i-0f32c068. log 04-slave- i-a5a153c2. log
> ...
> 2012-03-
> 2012-04-
<snip>
> 2012-04-
> 2012-04-
>
> So yes, we're still having it almost everyday, it's just auto-retrying hides it from our eyes.
I'd really appreciate it if you could put the apt-pipelining change in
place and remove the update loop.
Ie, you can either use a daily ami (or one of those just released today), or apt.conf. d/90cloud- init-pipelining ' <<EOF :http:: Pipeline- Depth "0";
sudo sh -c 'cat > /etc/apt/
//Written by cloud-init per 'apt_pipelining'
Acquire:
EOF
I really, really, value the automated results you're getting, so if you
could turn off the retries and add that, then yell loudly when it fails,
i'd really appreciate it.
If you have disabled pipeline in apt, and are still seeing errors, please
yell loudly.