Ubuntu Server 14.04 apt-get update not working!

[julakspro]

Just realized you said server, so I presume you don't have a gui.

Yes

[QIII]

I'm now getting clean results pinging ca.archive.ubuntu.com, the server is showing as keeton.canonical.com

[Bashing-om]

julaksprol Welp;

QIII is hot on this too.
I am presently having my own set of problems . Hard drive being "hot unplugged" and thus my system is crashing. Makes it difficult to respond and keep up !

We know now that you are not talking to the mirror. For some reason .
What are the sources that apt is working with ?

cat /etc/apt/sources.list

Let's get a tale told.

a failure to communicate ??

[QLee]

julakspro; K,

Then let us try and isolate this to your system's update manager .
As a test, what returns:

apt-cache show gedit

checking here that we get a response from your mirror .

now this is a thing

For clarity of anyone reading this thread, this is a minor point and won't interfere with the solution (since it looks a lot like a mirror that was offline for a bit) but I want to mention that, that command will not require a response from the mirror. It is run on the local system information in the APT library of lists that are downloaded when we do an apt or apt-get update.

[julakspro]

julaksprol Welp;

QIII is hot on this too.
I am presently having my own set of problems . Had drive being "hot unplugged" and thus my system is crashing. Makes it adifficult to respond and keep up !

We know now that you are not talking to the mirror. For some reason .
What are the sources that apt is working with ?

cat /etc/apt/sources.list

Let's get a tale told.

a failure to communicate ??

Ok this is what i get when i type in cat /etc/apt/sources.list
sdasda.jpg

[QLee]

This issue may be due to testing or implementation of IPV6 somewhere in the OP's path to the mirror, so even though I can ping the site and QIII can ping it, that might not help the OP.

I found this, julakspro, see if it applies to your situation with the ca archives:
http://askubuntu.com/questions/57456...ive-ubuntu-com

[julakspro]

This issue may be due to testing or implementation of IPV6 somewhere in the OP's path to the mirror, so even though I can ping the site and QIII can ping it, that might not help the OP.

I found this, julakspro, see if it applies to your situation with the ca archives:
http://askubuntu.com/questions/57456...ive-ubuntu-com

Even after changing it:
sd.png

Then when i try to update:
dasdasda.jpg

[QLee]

Sorry that didn't work, it was the link I found that seemed to be most like the problem you told us about.

You were able to ping both by IP Address and Domain Name on IPV4 but somehow when you tried to update, the ca archive gets translated to IPV6 and fails. I know very little about IPV6, but I would have thought the instructions that you followed from that link would have made the system prefer IPV4. My first guess is still that it could be something in the route to the repository that isn't or wasn't IP6 capable.

Is it still not working today? Just to be sure, how long has this been happening and did you make any changes just before it stopped working?

You can try doing the update with an option for apt-get, try

sudo apt-get -o Acquire::ForceIPv4=true update

what results do you get? If I understand it correctly, that command will force apt-get to use IPV4 addressing. Maybe the results can give a clue.

[howefield]

Thread moved to the "Server Platforms" forum.

[julakspro]

Sorry that didn't work, it was the link I found that seemed to be most like the problem you told us about.

You were able to ping both by IP Address and Domain Name on IPV4 but somehow when you tried to update, the ca archive gets translated to IPV6 and fails. I know very little about IPV6, but I would have thought the instructions that you followed from that link would have made the system prefer IPV4. My first guess is still that it could be something in the route to the repository that isn't or wasn't IP6 capable.

Is it still not working today? Just to be sure, how long has this been happening and did you make any changes just before it stopped working?

You can try doing the update with an option for apt-get, try

sudo apt-get -o Acquire::ForceIPv4=true update

what results do you get? If I understand it correctly, that command will force apt-get to use IPV4 addressing. Maybe the results can give a clue.

Its still now working today.
This has been happening for 3 days now. So i installed the ubuntu server 14.04 and tried to update it and this was the first problem. It was never working correctly.

After typing sudo apt-get -o Acquire::ForceIPv4=true update I got:
It just gets stuck on 0% [Connecting to ca.archive.ubuntu.com (91.189.8 .161 [ Connecting to securit.

Not like before now it just gets stuck on this part and doesnt show any errors!