BL4.5.0-32bit - How to get rid of "Timeout was reached" when updating in terminology?

madmax25 · 04-13-2019, 06:44 AM

When I do...

Code:

sudo apt-get update && sudo apt-get dist-upgrade

...I always get that message shown in the topic.

How can I fix this, please?

cordx · 04-13-2019, 09:30 AM

what happens when you run the commands independently? does update finish correctly?

madmax25 · 04-13-2019, 09:41 AM

When run separately, the update command still shows the timeout error, but the process itself does seem to be working fine, and the dist-upgrade command is ok, too.

cordx · 04-13-2019, 09:50 AM

it sounds like the timeout is in regards to a particular repo if the process works and upgrade is also able to finish. i had something similar when i used a ppa in the past that changed and i needed to remove it from my system. can you share your terminal output from update?

madmax25 · 04-13-2019, 10:21 AM

Here it is:

Code:

OK:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Holen:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
OK:3 http://ppa.launchpad.net/clipgrab-team/ppa/ubuntu xenial InRelease
Holen:4 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
OK:5 http://ppa.launchpad.net/dennis-benndorf/ppa/ubuntu xenial InRelease
Ign:6 http://packages.bodhilinux.com/bodhi xenial InRelease
Holen:7 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
OK:8 http://packages.bodhilinux.com/bodhi xenial Release
OK:9 http://ppa.launchpad.net/dominik-stadler/ppa/ubuntu xenial InRelease
Ign:10 http://packages.bodhilinux.com/bodhi xenial Release.gpg
OK:11 http://ppa.launchpad.net/jonathonf/firefox-esr/ubuntu xenial InRelease
OK:12 http://ppa.launchpad.net/me-davidsan...mentine/ubuntu xenial InRelease
OK:13 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu xenial InRelease
OK:14 http://ppa.launchpad.net/ubuntuhandb...videmux/ubuntu xenial InRelease
OK:15 http://ppa.launchpad.net/wseverin/ppa/ubuntu xenial InRelease
Es wurden 325 kB in 7 s geholt (42,1 kB/s).
Fehler: Zeitüberschreitung wurde erreicht
Paketlisten werden gelesen... Fertig

The three lines at the end of the code block are german for...

Code:

Recieved 325 kB in 7 s (42,1 kB/s).
Error: Timeout was reached
Package lists are being read... Done

cordx · 04-13-2019, 04:51 PM

the link below was what i found with a search. there doesn't seem to be a lot in the way of answers, but it's marked as a duplicate so maybe following the link at the top will help? i don't see the connection between the two personally, but hopefully there is something there that will help?

https://askubuntu.com/questions/775224/apt-get-error-timeout-was-reached

since that one didn't look too similar, i kept looking and found this thread her on lq:

https://www.linuxquestions.org/quest...ed-4175641260/

doesn't look like they found a solve though.

madmax25 · 04-13-2019, 05:24 PM

As for the 1st link, i don't have a appstreamcli and I don't know what to to with the code, mentioned there...

Code:

clone(child_stack=null, flags=clone_child_cleartid|clone_child_settid|sigchld, child_tidptr=0x7f1a9e52bed0) = 12189 wait4(12189, error: timeout was reached [{wifexited(s) && wexitstatus(s) == 0}], 0, null) = 12189 --- sigchld {si_signo=sigchld, si_code=cld_exited, si_pid=12189, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---

And regarding the 2nd one, in the end it says, just ignore it.
So, looks like there's no solution for that, doesn't it?

cordx · 04-13-2019, 06:08 PM

agreed as to not having a clue what that code is for or does as well as the fact that i don't see any kind of solution beyond the appstreamcli one.

you could take a look at

Code:

dmesg --level=err

(usually shorter and more immediate concerns) and

Code:

dmesg --level=warn

to see if there is anything that catches your eye related to the update that might give you a better idea of what is not making a connection.

otherwise, like you said, as long as your system finally finishes the update and does upgrade it might not be an issue that has to be "solved".

madmax25 · 04-14-2019, 10:18 AM

In another forum, I got the suggestion to temporarily remove all of my PPA's for testing purposes, but it didn't help.
The timeout error is still present.

the_waiter · 04-14-2019, 10:31 AM

Hello there

I can't reproduce your trouble but I found this solution. Maybe it will help

https://gist.github.com/brutalenemy6...85cdd2bf02b474

madmax25 · 04-14-2019, 11:47 AM

I tried that one already the other day.
Strange, when I tried it the 1st time, aptitude wasn't installed anyway.

But after installing it, nothing changed, i.e. the timeout error is still present.

Is there a way to increase the timeout?

cordx · 04-14-2019, 05:13 PM

Quote:

Originally Posted by madmax25

In another forum, I got the suggestion to temporarily remove all of my PPA's for testing purposes, but it didn't help.
The timeout error is still present.

this thought occurred to me at some point as well. sometimes it is best to run down the option just in case.

the last link i found is to a similar issue in debian from 2013. i didn't share it previously because it doesn't seem probable that yours would be related, but it is an interesting read in how one specific package could cause the issue (if i am reading everything correctly). apparently this was solved for this version of debian by an update to that package.

https://bugs.debian.org/cgi-bin/bugr...cgi?bug=729527

enigma9o7 · 04-15-2019, 01:19 AM

Quote:

Originally Posted by madmax25

In another forum, I got the suggestion to temporarily remove all of my PPA's for testing purposes, but it didn't help.
The timeout error is still present.

That's what I was gunna suggest, but apparently not your issue. I had that message when one of the official palemoon ppa's went down, fortunately there is another (even tho they still list the down one on palemoon website...).. but I think it was clear in the error message I got that it was coming from the stevenpusser ppa or whatever the palemoon one i was using.

I've also got that message a few times randomly for no apparent reason, then just tried again and it worked.

You could try pinging all the sites in your apt sources, see if one really isn't responding... maybe something blocking you... if you're using a vpn try turning it off, or if you have access to one and it's off, try turning it on...

madmax25 · 04-15-2019, 10:20 AM

The ping command didn't help either.

I tried these:

Code:

de.archive.ubuntu.com
security.ubuntu.com
packages.bodhilinux.com

and they are all available.

But as soon as I add

Code:

/ubuntu

to the 1st one and 2nd one or

Code:

/bodhi

to the 3rd one, it says

Code:

unknown host

cordx · 04-15-2019, 03:26 PM

i got the same reaction when adding /ubuntu or /bodhi with ping. well, technically i got "Name or service not known", but i figured it meant about the same.