The rationale for excess replication by default was that there were so many individual task failures in the early days of BOINC due to an extensive list of problems (both client and server), as well as the small host population back then, it was felt that having backup wingmen right from the start (rather than waiting for one to get shot down first) helped expedite troubleshooting and debugging efforts.
Alinator, would you agree the rationale for IR=5 MQ=3 was valid back then (4 years ago) but it was invalidated more than 2 years ago when the relevant client and server problems were fixed? Would you say LHC@home simply hasn't kept up with the changes and improvements to BOINC?
But, have you tried accessing their site lately? Here, every time I try to connect, I get a "connection error" message. And, it's been like that for the past several months. It shouldn't be due to anything on my end, since everything else I access works just fine.
Seriously, the site is fine, both the website and with BOINC Manager.
Can you reach them on your BOINC Manager and get a "No Work" message from them, or is neither working?
No, even with BOINC, I get connection errors.
Not that I'm worried about missing any work. Mainly, I'm just curious about the project's status.
Looks like a DNS problem. Try "traceroute 138.37.50.115" and post the output.
No, that's not it either. I tried traceroute without any option switches, and then with the "-U" option. Either way, I get nothing but strings of asterisks.
Well the LHC site is up and running whithout any problems.
Tha fact that you only get asterisks means that the problem is somewhere on your side. If the problem was with the LHC server, you should at least get responses from the hubs on the way to it.
So try "netstat -r" to see if there is a route on your system for 138.37.50.115 (or a part of it) which causes it to look in the wrong place.
Well the LHC site is up and running whithout any problems.
Tha fact that you only get asterisks means that the problem is somewhere on your side. If the problem was with the LHC server, you should at least get responses from the hubs on the way to it.
So try "netstat -r" to see if there is a route on your system for 138.37.50.115 (or a part of it) which causes it to look in the wrong place.
Perhaps your firewall somehow blocked outgoing packages to this IP/domain
No, because I've made no changes to the firewall. Also, I've tried it from other machines that don't have a firewall installed, only to get the same results.
The only thing I can figure, is that my ISP is blocking the address for some strange reason. I guess I'll have to call them and see what's up.
Quote:
PS.
lhcathome.cern.ch is an alias,
the actual server is running on: hepboinc.ph.qmul.ac.uk
Yeah, I saw that when I did a Sam Spade search. Either way, though, I still can't get to it, even though Sam Spade was able to gather the DNS data.
have you tryd a nslookup? just throwing out idea's here. heres my results for both an nslookup and a tracert
C:\>nslookup lhcathome.cern.ch
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
Tracing route to hepboinc.ph.qmul.ac.uk [138.37.50.115]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 23 ms 21 ms 34 ms 10.20.109.1
3 22 ms 35 ms 21 ms 12-215-8-129.client.mchsi.com [12.215.8.129]
4 31 ms 28 ms 35 ms 12.88.33.61
5 30 ms 28 ms 28 ms cr2.attga.ip.att.net [12.122.140.66]
6 29 ms 27 ms 29 ms ggr4.attga.ip.att.net [12.122.140.89]
7 28 ms 28 ms 28 ms 192.205.34.234
8 45 ms 49 ms 45 ms ash-bb1-link.telia.net [80.91.248.138]
9 121 ms 121 ms 123 ms ldn-bb1-link.telia.net [213.248.65.97]
10 120 ms 123 ms 125 ms ldn-b4-link.telia.net [80.91.250.233]
11 121 ms 122 ms 120 ms jnt-ic-122984-ldn-b4.c.telia.net [213.248.96.38]
12 130 ms 143 ms 121 ms so-6-0-0.lond-sbr1.ja.net [146.97.33.153]
13 140 ms 121 ms 123 ms LMN-LMN1.site.ja.net [146.97.42.62]
14 124 ms 120 ms 121 ms city-wmin.lmn.net.uk [194.83.102.38]
15 121 ms 121 ms 126 ms dewberry-ebr3.core-net.qmul.ac.uk [138.37.3.204]
16 126 ms 115 ms 105 ms hepboinc.ph.qmul.ac.uk [138.37.50.115]
Trace complete.
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
have you tryd a nslookup? just throwing out idea's here. heres my results for both an nslookup and a tracert
Well, this is getting even more interesting.
The first time that I did "traceroute", it was on a Linux machine. That's when I got nothing but asterisks for output. This time, I did it on a Windows machine, and got the following:
Anyway, I did a trace from a Finnish server, and it completed just fine. I then immediately did a trace from my own machine, and got the same results that I posted above. So, yeah, for some reason the LHC@home folk are blocking me out.
Oh well, I guess there's not much that I can do about it.
RE: The rationale for
)
Alinator, would you agree the rationale for IR=5 MQ=3 was valid back then (4 years ago) but it was invalidated more than 2 years ago when the relevant client and server problems were fixed? Would you say LHC@home simply hasn't kept up with the changes and improvements to BOINC?
BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux
RE: RE: RE: RE: But,
)
No, that's not it either. I tried traceroute without any option switches, and then with the "-U" option. Either way, I get nothing but strings of asterisks.
Well the LHC site is up and
)
Well the LHC site is up and running whithout any problems.
Tha fact that you only get asterisks means that the problem is somewhere on your side. If the problem was with the LHC server, you should at least get responses from the hubs on the way to it.
So try "netstat -r" to see if there is a route on your system for 138.37.50.115 (or a part of it) which causes it to look in the wrong place.
RE: Well the LHC site is up
)
Nope, nothing there.
So, the mystery continues.
Perhaps your firewall somehow
)
Perhaps your firewall somehow blocked outgoing packages to this IP/domain
PS.
lhcathome.cern.ch is an alias,
the actual server is running on: hepboinc.ph.qmul.ac.uk
RE: RE: Perhaps your
)
Yeah, I saw that when I did a Sam Spade search. Either way, though, I still can't get to it, even though Sam Spade was able to gather the DNS data.
have you tryd a nslookup?
)
have you tryd a nslookup? just throwing out idea's here. heres my results for both an nslookup and a tracert
Non-authoritative answer:
Name: hepboinc.ph.qmul.ac.uk
Address: 138.37.50.115
Aliases: lhcathome.cern.ch
C:\>tracert lhcathome.cern.ch
Tracing route to hepboinc.ph.qmul.ac.uk [138.37.50.115]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 23 ms 21 ms 34 ms 10.20.109.1
3 22 ms 35 ms 21 ms 12-215-8-129.client.mchsi.com [12.215.8.129]
4 31 ms 28 ms 35 ms 12.88.33.61
5 30 ms 28 ms 28 ms cr2.attga.ip.att.net [12.122.140.66]
6 29 ms 27 ms 29 ms ggr4.attga.ip.att.net [12.122.140.89]
7 28 ms 28 ms 28 ms 192.205.34.234
8 45 ms 49 ms 45 ms ash-bb1-link.telia.net [80.91.248.138]
9 121 ms 121 ms 123 ms ldn-bb1-link.telia.net [213.248.65.97]
10 120 ms 123 ms 125 ms ldn-b4-link.telia.net [80.91.250.233]
11 121 ms 122 ms 120 ms jnt-ic-122984-ldn-b4.c.telia.net [213.248.96.38]
12 130 ms 143 ms 121 ms so-6-0-0.lond-sbr1.ja.net [146.97.33.153]
13 140 ms 121 ms 123 ms LMN-LMN1.site.ja.net [146.97.42.62]
14 124 ms 120 ms 121 ms city-wmin.lmn.net.uk [194.83.102.38]
15 121 ms 121 ms 126 ms dewberry-ebr3.core-net.qmul.ac.uk [138.37.3.204]
16 126 ms 115 ms 105 ms hepboinc.ph.qmul.ac.uk [138.37.50.115]
Trace complete.
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
You can try tracert from
)
You can try tracert from different places (tracert.com), or use the tracert tools (tracert.org) for more 'info'.
RE: have you tryd a
)
Well, this is getting even more interesting.
The first time that I did "traceroute", it was on a Linux machine. That's when I got nothing but asterisks for output. This time, I did it on a Windows machine, and got the following:
C:\> nslookup lhcathome.cern.ch
Server: ubuntu3.xyzwidgets.com
Address: 192.168.0.6
Non-authoritative answer:
Name: hepboinc.ph.qmul.ac.uk
Address: 138.37.50.115
Aliases: lhcathome.cern.ch
C:\Documents and Settings\HP_Administrator>tracert lhcathome.cern.ch
Tracing route to hepboinc.ph.qmul.ac.uk [138.37.50.115]
over a maximum of 30 hops:
1
So, it seems that my access requests are getting blocked in London, for some strange reason.
It makes me wonder why they're blocking me.
RE: You can try tracert
)
Very cool. I never know about these.
Anyway, I did a trace from a Finnish server, and it completed just fine. I then immediately did a trace from my own machine, and got the same results that I posted above. So, yeah, for some reason the LHC@home folk are blocking me out.
Oh well, I guess there's not much that I can do about it.