Does anyone know why I get this error message?


2006-09-09 15:37:40 [rosetta@home] Requesting 8640 seconds of new work
2006-09-09 15:37:50 [rosetta@home] Scheduler request failed: Unrecognized HTTP Content-Encoding

TIA,

/mike

---

Are you using any proxy or firewall, SkyDSL or something like that?

If the proxy/firewall is optional, try a direct connect and see if that works better.

Are you using any proxy or firewall, SkyDSL or something like that?

If the proxy/firewall is optional, try a direct connect and see if that works better.

I think that must be the issue. I just upgraded to Boinc 5.4.11. I just read there that it has proxy issues sometimes and users should wait for the fix in
the works.

Thanks for the reply, ananas.

/mike

---

After doing more experimenting, I think the problem lies with freeproxy trying to proxy one port via modem, while I have my switch all linked thru a
router to my satellite modem at the same time. I'm not sure what exactly is
mis-configured, but if I shutdown the freeproxy program that has one incoming
nic to use on one box, while the other nic is to the local lan that shares the
router to sat modem, all seems ok for now.

Obviously there is a lot I'm missing here.... (!!)

Thanks to all who replied with suggestions, including Jord who got me researching deeper to try to experiment which led to this last discovery.

/mike

Does anyone know why I get this error message?


2006-09-09 15:37:40 [rosetta@home] Requesting 8640 seconds of new work
2006-09-09 15:37:50 [rosetta@home] Scheduler request failed: Unrecognized HTTP Content-Encoding

TIA,

/mike

---

---

I don't know if you experimented with the 5.5.x and 5.6.x released of BOINC, at some point in the 5.5.x they think they fixed the proxy problems (it usually only proxies that require authentication). You could try them out
5.6.x can be seen as Release Candidates (in a windows world), since 5.4.x are the real developmental releases. Well that's what the version numbers should mean ;-).

If you really want to figure it out you can switch on various debugging messages, though inless you can actually understand them you'd need to post them on the BOINC forum.

BOINC downloads (inc development) http://boinc.berkeley.edu/download_all.php?min_version=5.0&dev=1
Debugging options http://boinc.berkeley.edu/client_msgs.php

---

Team mauisun.org

Thanks for those suggestions, FluffyChicken. For whatever reason I switched all my boxes back to rosetta yesterday and they all have been running fine and transferring work and results as needed. I changed all my boxes to DHCP addressing from static IP's but I really can't believe this has anything to do with anything. I think my boxes were grabbing work before I made those changes anyhow. I still think it's the satellite delay. I'll try what you suggest next time the work flow stops.
Thanks and have a great weekend!

/mike

I don't know if you experimented with the 5.5.x and 5.6.x released of BOINC, at some point in the 5.5.x they think they fixed the proxy problems (it usually only proxies that require authentication). You could try them out
5.6.x can be seen as Release Candidates (in a windows world), since 5.4.x are the real developmental releases. Well that's what the version numbers should mean ;-).

If you really want to figure it out you can switch on various debugging messages, though inless you can actually understand them you'd need to post them on the BOINC forum.

BOINC downloads (inc development) http://boinc.berkeley.edu/download_all.php?min_version=5.0&dev=1
Debugging options http://boinc.berkeley.edu/client_msgs.php

---

Maybe this will help other people on satellite ISP, it seems to be working for me so far but as someone suggested to me a while back ( forgot who ) I extended my work unit load to ~ 8 hrs. per unit and set my connection settings
to only connect once or twice a day. This *so far* seems to be working great.
I still get periods where I can't connect, but with the longer, 8hr. per unit
work load my machines can run non-stop and not run out of work (so far).

Thanks to everyone who gave me suggestions and mega-thanks to the person that suggested this approach quite awhile ago that took me some time to try....
8^).

/mike

Thanks for those suggestions, FluffyChicken. For whatever reason I switched all my boxes back to rosetta yesterday and they all have been running fine and transferring work and results as needed. I changed all my boxes to DHCP addressing from static IP's but I really can't believe this has anything to do with anything. I think my boxes were grabbing work before I made those changes anyhow. I still think it's the satellite delay. I'll try what you suggest next time the work flow stops.
Thanks and have a great weekend!

/mike

I don't know if you experimented with the 5.5.x and 5.6.x released of BOINC, at some point in the 5.5.x they think they fixed the proxy problems (it usually only proxies that require authentication). You could try them out
5.6.x can be seen as Release Candidates (in a windows world), since 5.4.x are the real developmental releases. Well that's what the version numbers should mean ;-).

If you really want to figure it out you can switch on various debugging messages, though inless you can actually understand them you'd need to post them on the BOINC forum.

BOINC downloads (inc development) http://boinc.berkeley.edu/download_all.php?min_version=5.0&dev=1
Debugging options http://boinc.berkeley.edu/client_msgs.php

---