lun. 29 août 2011 16:54:58 CEST SETI@home Scheduler request failed: HTTP internal server error
HOME PARTICIPATE ABOUT COMMUNITY ACCOUNT STATISTICS
log in

Advanced search

Questions and Answers : Unix/Linux : lun. 29 août 2011 16:54:58 CEST SETI@home Scheduler request failed: HTTP internal server error

Subscribe Sort
Author Message
pierrotlancien
Send message
Joined: 28 Aug 11
Posts: 3
Credit: 504,957
RAC: 510
France
Message 1146742 - Posted: 29 Aug 2011, 16:19:23 UTC

Hi,

After installing Boinc Manger 6.10.58 on Debian squeeze and creating an account seti@home i can't get any tasks since 24 hours and i get always the message:
Scheduler request failed: HTTP internal server error when contacting scheduler.

Is it necessary to open ports on my router?

Thanks

ID: 1146742 · Report as offensive
 
Volunteer tester
Send message
Joined: 9 Apr 02
Posts: 11987
Credit: 18,260,241
RAC: 57,806
United States
Message 1146751 - Posted: 29 Aug 2011, 16:42:43 UTC - in response to Message 1146742.

BOINC uses common port 80 for all standard downloads, and port 443 for projects that use secure transactions.

If you have a Stateful Packet Inspection firewall, you shouldn't need to open any specific ports to get work. More than likely, you may be having trouble contacting the servers, which has been an ongoing issue for many users for a couple months.

The SETI@Home Project Administrators have been looking into solutions, but a permanent solution has been very slow-coming.

ID: 1146751 · Report as offensive
Profile BilBg
Avatar
Send message
Joined: 27 May 07
Posts: 2023
Credit: 3,056,851
RAC: 6,654
Bulgaria
Message 1146772 - Posted: 29 Aug 2011, 17:42:33 UTC - in response to Message 1146742.
Last modified: 29 Aug 2011, 17:58:55 UTC


Read the first two threads about "HE connection problems" here:
http://setiathome.berkeley.edu/forum_forum.php?id=10

and see if they can help you to understand/overcome the problem.
(I'm not sure if they apply to your problem or you have some local issues)


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

ID: 1146772 · Report as offensive
pierrotlancien
Send message
Joined: 28 Aug 11
Posts: 3
Credit: 504,957
RAC: 510
France
Message 1147136 - Posted: 30 Aug 2011, 8:49:10 UTC - in response to Message 1146772.

Hi,

some indications:

This problem start at the firt time.

My ISP is France Telecom Orange

I'm near Grenoble in France

PING 208.68.240.13 (208.68.240.13) 56(84) bytes of data.
64 bytes from 208.68.240.13: icmp_req=1 ttl=51 time=202 ms
PING 208.68.240.16 (208.68.240.16) 56(84) bytes of data.
64 bytes from 208.68.240.16: icmp_req=1 ttl=51 time=201 ms
PING 208.68.240.18 (208.68.240.18) 56(84) bytes of data.
64 bytes from 208.68.240.18: icmp_req=1 ttl=51 time=193 ms
PING 208.68.240.20 (208.68.240.20) 56(84) bytes of data.
64 bytes from 208.68.240.20: icmp_req=1 ttl=51 time=203 ms

traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 60 byte packets
1 WANADOO-0C7E (192.168.1.1) 1.094 ms 1.912 ms 2.577 ms
2 AGrenoble-753-1-11-1.w90-27.abo.wanadoo.fr (90.27.102.1) 27.723 ms 30.008 ms 30.429 ms
3 10.125.17.10 (10.125.17.10) 32.214 ms 33.256 ms 34.444 ms
4 ge-1-1-0-0.ncgre101.Grenoble.francetelecom.net (193.253.85.125) 35.913 ms 36.867 ms 38.948 ms
5 ae45-0.nilyo101.Lyon.francetelecom.net (193.252.101.26) 42.965 ms 43.417 ms 46.991 ms
6 193.252.161.162 (193.252.161.162) 51.925 ms 34.458 ms 35.715 ms
7 telia-4.GW.opentransit.net (193.251.252.22) 52.431 ms 34.554 ms 34.624 ms
8 prs-bb2-link.telia.net (213.155.133.124) 35.936 ms prs-bb1-link.telia.net (80.91.253.109) 37.231 ms prs-bb1-link.telia.net (80.91.245.30) 38.387 ms
9 ash-bb1-link.telia.net (80.91.251.243) 124.813 ms ash-bb1-link.telia.net (80.91.251.102) 131.321 ms ash-bb1-link.telia.net (80.91.254.214) 122.934 ms
10 sjo-bb1-link.telia.net (213.155.130.213) 204.972 ms sjo-bb1-link.telia.net (213.155.130.211) 208.810 ms sjo-bb1-link.telia.net (213.155.130.213) 191.351 ms
11 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 214.154 ms 214.550 ms 214.949 ms
12 64.71.140.42 (64.71.140.42) 208.149 ms 207.043 ms 207.649 ms
13 208.68.243.254 (208.68.243.254) 195.527 ms 196.576 ms 197.283 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


ID: 1147136 · Report as offensive
Profile Gundolf Jahn
Send message
Joined: 19 Sep 00
Posts: 3078
Credit: 341,914
RAC: 96
Germany
Message 1147139 - Posted: 30 Aug 2011, 9:08:50 UTC - in response to Message 1146742.

Scheduler request failed: HTTP internal server error when contacting scheduler.

An internal server error is usually caused by the server and not by the client (as the message indicates:-), but sometimes a (badly configured) proxy server can be the cause.

Can you ping/tracert the scheduler at SETI@home?

You could also activate some debug output by creating a cc_config.xml file in your BOINC data directory and activating the corresponding logging flags (<http_debug> et al.).

Gruß,
Gundolf

ID: 1147139 · Report as offensive
pierrotlancien
Send message
Joined: 28 Aug 11
Posts: 3
Credit: 504,957
RAC: 510
France
Message 1147448 - Posted: 31 Aug 2011, 11:27:03 UTC - in response to Message 1147139.

Aujourd'hui, tout fonctionne, 8 tâches en cours, sans modification.
Today, all is right, 8 tasks running, without intervention.
Thanks.

ID: 1147448 · Report as offensive

Questions and Answers : Unix/Linux : lun. 29 août 2011 16:54:58 CEST SETI@home Scheduler request failed: HTTP internal server error

HOME PARTICIPATE ABOUT COMMUNITY ACCOUNT STATISTICS
Copyright © 2013 University of California