RPi Distcc - failed to distribute running locally - [SOLVED]

njcwotx · Guru Joined: 25 Feb 2005 Posts: 587 Location: Texas

I am posting this because I was regularly getting "failed to distribute running locally" in my distcc pump mode when compiling on my Raspberry Pi. It would compile remotely, but preprocessing always ran locally.

The other day I was running a reallly long compile and was looking into this again and I found a solution in the depths of some forum linked to some other forum, linked again to some other post. I have been unable to re-find this, but I was able to figure out what I did. I decided to post this here for others in case they run into this issue, or if I need to do this again someday.

Problem. Distcc is setup properly, but you still see "failed to get includes from include server, failed to distrbute running locally" in emerge and in ("DISTCC_DIR=/var/tmp/portage/.distcc/" distccmon-text 1) distccmon shows preproccessing always running locally.

Solution. On the distcc compling host, the one referenced inside the '/etc/distcc/hosts' file, there is a file in python under the following path:

/usr/lib/python2.7/site-packages/include_server/basics.py

Inside this file there is a value for USER_TIME_QUOTA and its set to 3.8 seconds. I increased this value to 10.8 seconds (it was arbitrary but works, you can experiment with other values). This made my failed to distrbutes disappear.

Also as an added bonus, I had an issue in the hosts file unrelated to this, but make sure the hosts line syntax is correct in /etc/distcc/hosts. "w.x.y.z/#,lzo,cpp" is how I have it. I left a comma at end and it also failed to pump.

happy compiling!

Another note: when I wrote this I was setting this up again, I still got the failed to distribute error, I increased the USER_TIME_QUOTA to 20.8 second and it started to work properly, so I guess there is some experimenting with the number of seconds.

Another note 2: Started to get a message actually saying I ran past the 3.8 secs of USER_TIME_QUOTA on the pi again. I changed basic.py on the pi as well and the error cleared and started preprossesing remote again.
_________________
Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.

xaviermiller · Posted: Tue May 14, 2013 7:47 pm Post subject:

Good to know!

But isn't there a better place to configure that?
_________________
Kind regards,
Xavier Miller

njcwotx · Guru Joined: 25 Feb 2005 Posts: 587 Location: Texas

xaviermiller · Posted: Tue May 14, 2013 8:08 pm Post subject:

Me neither. I watch this topic

_________________
Kind regards,
Xavier Miller

xaviermiller · Posted: Sat May 18, 2013 10:39 am Post subject:

Hmm, this file comes from distcc, so we can define a patch to apply to distcc, or use an environment variable.

I tried in make.conf, and it seems working.
_________________
Kind regards,
Xavier Miller

njcwotx · Guru Joined: 25 Feb 2005 Posts: 587 Location: Texas

good to know.
_________________
Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.

nagmat84 · Apprentice Joined: 27 Mar 2007 Posts: 205

I found this rather old topic because I have the same problem. My machine is so slow that the include-server runs out of time before finishing its job. Is there already a better solution to configure the timeout than manually modifying the Python source code?

krinn · Watchman Joined: 02 May 2003 Posts: 7470

You must have a really slow host, or misconfiguration in distcc.
Make sure that the pump server appears after localhost in distcc hosts file
Pump use lzo compression, if really the localhost cannot get enough time to compress and upload the files, you should find a different solution to your problem (binary host)
Or you could still edit the python file as i don't know another way myself.

nagmat84 · Apprentice Joined: 27 Mar 2007 Posts: 205

krinn · Watchman Joined: 02 May 2003 Posts: 7470

sorry, s/after/before... :/
you got it right of course.