I've set up SETI@Home/Boinc to use a custom logo in the bottom right. it does OK, loads the logo and everything BUT: boinc keeps giving me the following error now, whether i have the logo active or not (meaning the URL in the prefs or blank):

Can't resolve hostname null (host name not found)
Couldn't start download for null: error -113
Backing off 3 hours, 35 minutes, and 6 seconds on transfer of file user_logo_1089219895

and it will retry after that time, fail, give me the same error, and back off again.

Any idea how to fix this, since getting an (i)nformation warning on Boinc in my systray for this will eventually make me stop paying attention ;) and I'll probably miss more important infos then :P

Thanks.

This is an annoying problem. It will give up eventually if you can stand the message spam for a few weeks. A project reset may fix it, detaching and reattaching also has a chance of fixing it. Neither fix is a given though. The only sure fire way is a clean reinstall.

The client has this file in it's pending transfers list so it is not always affected by project specific actions. As long as you are getting work done I would just let it go, the message spam will get a bit more bearable once the exponetial backoff spreads out some.

John Keck
BOINCing since 2002/12/08

> This is an annoying problem. It will give up eventually if you can stand the
> message spam for a few weeks. A project reset may fix it, detaching and
> reattaching also has a chance of fixing it. Neither fix is a given though. The
> only sure fire way is a clean reinstall.

Detaching and re-attaching didn't fix it, resetting didn't fix it. the uninstall, then total deletion of the install directory after the uninstaller ran, followed by a clean re-install fixed the problem.

> would just let it go, the message spam will get a bit more bearable once the
> exponetial backoff spreads out some.

The exponential back-off seemed to be reset on occasion though, as the time would increase, then be reset to a shorter wait (this machine isn't on 24/7 by the way, perhaps that is why...? Just a guess) anyway, the re-install fixed it; that is the most important thing.