Problem connecting to project server to report.


log in

Advanced search

Questions and Answers : Unix/Linux : Problem connecting to project server to report.

Author Message
technot
Send message
Joined: 16 Jul 09
Posts: 1
Credit: 1,804
RAC: 0
Norway
Message 919487 - Posted: 19 Jul 2009, 20:48:51 UTC

Hello. I seem to have problems reporting finished work.

I've set some debug flags in the cc_config.xml, and renamed stdoutdae.txt to stdoutdae.old. when i fired up boinc again it dont seem to make a new stdoutdae.txt..

however, i'll post my ping and traceroute results, and also the error message from my stdoutdae.old :>


-- ping --
PING setiathome.SSL.berkeley.edu (128.32.18.150) 56(84) bytes of data.
64 bytes from thinman.ssl.berkeley.edu (128.32.18.150): icmp_seq=1 ttl=49 time=193 ms
64 bytes from thinman.ssl.berkeley.edu (128.32.18.150): icmp_seq=2 ttl=49 time=192 ms
64 bytes from thinman.ssl.berkeley.edu (128.32.18.150): icmp_seq=3 ttl=49 time=192 ms
64 bytes from thinman.ssl.berkeley.edu (128.32.18.150): icmp_seq=4 ttl=49 time=193 ms

-----


-- traceroute --
traceroute to setiathome.berkeley.edu (128.32.18.150), 30 hops max, 60 byte packets
1 1.84-234-185.customer.lyse.net (84.234.185.1) 15.648 ms 15.888 ms 16.233 ms
2 13.84-234-190.customer.lyse.net (84.234.190.13) 16.493 ms 16.741 ms 16.994 ms
3 249.84-234-190.customer.lyse.net (84.234.190.249) 17.246 ms 17.500 ms 17.753 ms
4 138.213-167-114.customer.lyse.net (213.167.114.138) 18.320 ms 18.574 ms *
5 oso-b2-link.telia.net (213.248.99.45) 20.521 ms 20.776 ms 21.375 ms
6 s-bb1-link.telia.net (80.91.251.69) 30.701 ms 23.169 ms 17.408 ms
7 s-b1-link.telia.net (80.91.249.71) 17.076 ms 19.871 ms 20.270 ms
8 level3-ic-130907-s-b1.c.telia.net (213.248.77.198) 22.677 ms 22.937 ms 23.194 ms
9 ae-5-5.ebr1.Dusseldorf1.Level3.net (4.69.140.198) 47.086 ms 48.715 ms 49.007 ms
10 ae-2-2.ebr2.Frankfurt1.Level3.net (4.69.132.138) 51.354 ms 51.611 ms 51.937 ms
11 ae-43-43.ebr2.Washington1.Level3.net (4.69.137.58) 133.131 ms 121.480 ms ae-44-44.ebr2.Washington1.Level3.net (4.69.137.62) 121.649 ms
12 ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 130.161 ms 127.955 ms 127.811 ms
13 ae-84-84.ebr4.Washington1.Level3.net (4.69.134.185) 122.278 ms ae-94-94.ebr4.Washington1.Level3.net (4.69.134.189) 135.746 ms ae-74-74.ebr4.Washington1.Level3.net (4.69.134.181) 153.388 ms
14 ae-3-3.ebr1.NewYork1.Level3.net (4.69.132.94) 122.578 ms 122.520 ms 124.479 ms
15 ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70) 134.782 ms ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 127.907 ms ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70) 152.392 ms
16 ae-84-84.ebr4.NewYork1.Level3.net (4.69.134.121) 133.033 ms ae-94-94.ebr4.NewYork1.Level3.net (4.69.134.125) 130.784 ms ae-84-84.ebr4.NewYork1.Level3.net (4.69.134.121) 127.895 ms
17 ae-2.ebr4.SanJose1.Level3.net (4.69.135.185) 198.591 ms 215.413 ms 215.439 ms
18 ae-74-74.csw2.SanJose1.Level3.net (4.69.134.246) 192.384 ms ae-94-94.csw4.SanJose1.Level3.net (4.69.134.254) 190.329 ms ae-74-74.csw2.SanJose1.Level3.net (4.69.134.246) 190.075 ms
19 ae-92-92.ebr2.SanJose1.Level3.net (4.69.134.221) 208.291 ms ae-72-72.ebr2.SanJose1.Level3.net (4.69.134.213) 191.977 ms ae-92-92.ebr2.SanJose1.Level3.net (4.69.134.221) 202.687 ms
20 ae-5-5.car1.Oakland1.Level3.net (4.69.134.37) 192.177 ms 191.162 ms 192.690 ms
21 CORP-FOR-ED.car1.Oakland1.Level3.net (4.71.164.66) 218.356 ms 217.625 ms 217.989 ms
22 inet-ucb--oak-isp.cenic.net (137.164.24.142) 208.665 ms 191.945 ms 192.742 ms
23 g4-1.inr-202-reccev.Berkeley.EDU (128.32.0.50) 192.473 ms 192.018 ms 193.122 ms
24 g6-2.inr-230-spr.Berkeley.EDU (128.32.255.114) 220.262 ms 192.905 ms 193.507 ms
25 * * *

----

-- stdoutae --

19-Jul-2009 22:34:16 [SETI@home] Temporarily failed upload of ap_29au08ac_B4_P1_00147_20090718_30715.wu_0_0: HTTP error
19-Jul-2009 22:34:16 [SETI@home] Backing off 2 min 22 sec on upload of ap_29au08ac_B4_P1_00147_20090718_30715.wu_0_0
19-Jul-2009 22:34:17 [---] Internet access OK - project servers may be temporarily down.
19-Jul-2009 22:36:40 [SETI@home] Started upload of ap_29au08ac_B4_P1_00147_20090718_30715.wu_0_0
19-Jul-2009 22:36:41 [---] Project communication failed: attempting access to reference site
19-Jul-2009 22:36:41 [SETI@home] Temporarily failed upload of ap_29au08ac_B4_P1_00147_20090718_30715.wu_0_0: HTTP error
19-Jul-2009 22:36:41 [SETI@home] Backing off 2 min 16 sec on upload of ap_29au08ac_B4_P1_00147_20090718_30715.wu_0_0
19-Jul-2009 22:36:42 [---] Internet access OK - project servers may be temporarily down.



----


All help is appriciated.

- technot

Profile Gundolf Jahn
Send message
Joined: 19 Sep 00
Posts: 3184
Credit: 356,746
RAC: 15
Germany
Message 919490 - Posted: 19 Jul 2009, 21:01:14 UTC - in response to Message 919487.

The Server status page reads:

upload server bruno Disabled

Gruß,
Gundolf
____________
Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Questions and Answers : Unix/Linux : Problem connecting to project server to report.

Copyright © 2014 University of California