TURNKEYGNU / LINUX
English

Forum archive

TKLDev builds very slow to build

Support

Any one else getting SLOW build times mostly downloading stuff, headers and certian packages. Like 

 

Get:12 http://http.debian.net jessie InRelease (took 1 min)

mysql-client-5.5

 

Did not used to do this, wonder if these sites are having issues? I updated my system, and tried again. It's stopping at mysql-client-5.5 at 14%

 

 

 

 

Replies (7)

TBH I'm not totally sure

Reply 1
But my guess is that your closest mirror is chocking a bit on that one for some reason... It looks like you are using the default http.debian.net (as is advised) and AFAIK that auto routes you to the closest and fastest mirror to where you are. However perhaps there was something up with the mirror but it hadn't yet discovered that (and adjusted for it...)?

Just guessing really...

LAPP/Postgres Ok, MySQL/LAMP no go

Reply 2

I tried to do a LAMP build and it's stopping at mysql-client-5.5, the MySQL build stops here too.

 

TKLDev uses a proxy right? Could the proxy cache need to be reset or somthing? Going to try with a fresh TKLDev build

 

LAPP/Postgres Ok, MySQL/LAMP no go

Reply 3

I tried to do a LAMP build and it's stopping at mysql-client-5.5, the MySQL build stops here too.

 

TKLDev uses a proxy right? Could the proxy cache need to be reset or somthing? Going to try with a fresh TKLDev build

 

I'd like to

Reply 4
I'd like to but I need to speak with Alon about it. Thanks for the nudge though; I noticed that I hadn't set it to a milestone!

Thanks for the link

Reply 5

Did a quck read on the tracker... I wonder if that's not somthing I was seeing before as well. 

Once I cleared the cache things started working great. In regards to the config change, is that somthinh your looking to include in the TKLDev build?

Thanks Ken

Reply 6
Nice little write up! I haven't ever experienced issues with the Polipo cache; but I have had issues with it's DNS, which in retrospect I should have probably mentioned. TBH I'm not sure why it didn't occur to me... FWIW it's on the tracker here

TKLDev Building / Proxy

Reply 7

So after some digging around in the bowels of the toolkit, I found that TKLDev uses polipo proxy (http://www.pps.univ-paris-diderot.fr/~jch/software/polipo/) to cache apt-get requests to make building quicker and to take the load off of the apt servers (smart move on the core devs parts, I tip my hat to them) 

Polipo uses the user "proxy" and listens on port 8124. Config file is /etc/polipo/config however no useful stuff is there. Polipo has a clear cache command polipo -x but it did not seem to do anything :-(

So I just stopped the service, and removed all the files

service polipo stop
rm -R /var/cache/polipo/*
service polipo start

 

Also for those who want to know how much space is being used by the cache use

du -h /var/cache/polipo