I feel like I'm hijacking this thread by bringing it back to its original topic, but I recently had a similar experience being unable to go to lhcathome.cern.ch or even ping it.
I have posted the details of my trouble in this post at LHC@home's forum. I have yet to receive a response from either moderators or management. I really want them to acknowledge this problem, but I'm afraid their usual apathy will prevail.
I have no problem in going to their site, but I cannot get any work to do. So I just put it on a NNT condition in order not to have my BOINC client trying continuously to get some work.
Tullio
I have no problem in going to their site, but I cannot get any work to do. So I just put it on a NNT condition in order not to have my BOINC client trying continuously to get some work.
Tullio
The trouble is that unless you watch like a hawk you are just as likely to miss all the work issued. The whole point of exponential back off is to handle this very situation. THough I have found I can't get as much work as I would like regardless. :(
You should allow tasks and just let the system work ... though this is one of the projects that shows the weakness of the "Resource Share" concept because of the lack of reliable work. If you set the share to a value that is truly what you would like, the system still subverts this by limiting the work drawn (on the server side) and the accumulation of debt (on the client side).
Because of the major efforts being made to change the Resource Scheduler several of us suggested changes to make the overall system better (though it would not cure all of the ills of the current Resource Share system) but were rebuffed (sadly).
I feel like I'm hijacking this thread by bringing it back to its original topic, but I recently had a similar experience being unable to go to lhcathome.cern.ch or even ping it.
I have posted the details of my trouble in this post at LHC@home's forum. I have yet to receive a response from either moderators or management. I really want them to acknowledge this problem, but I'm afraid their usual apathy will prevail.
After I saw your post, I tried going to their website again, for the first time in quite a few weeks. I'm still blocked, and can't even see the post that you made about it.
After I saw your post, I tried going to their website again, for the first time in quite a few weeks. I'm still blocked, and can't even see the post that you made about it.
Donald, I ended up discovering that my IP address was somehow being blocked. I couldn't even ping lhcathome.cern.ch (138.37.50.115). The fix was simple; I just reset my Linksys router, forcing it to get a new IP address from AT&T's dynamic IP pool. With a different IP address, everything started working as normal.
I feel like I'm hijacking this thread by bringing it back to its original topic, but I recently had a similar experience being unable to go to lhcathome.cern.ch or even ping it.
I have posted the details of my trouble in this post at LHC@home's forum. I have yet to receive a response from either moderators or management. I really want them to acknowledge this problem, but I'm afraid their usual apathy will prevail.
This post has some new info, about the project rather than the connections.
After I saw your post, I tried going to their website again, for the first time in quite a few weeks. I'm still blocked, and can't even see the post that you made about it.
Donald, I ended up discovering that my IP address was somehow being blocked. I couldn't even ping lhcathome.cern.ch (138.37.50.115). The fix was simple; I just reset my Linksys router, forcing it to get a new IP address from AT&T's dynamic IP pool. With a different IP address, everything started working as normal.
Well, my DSL gateway has been reset numerous times, with numerous new IP addresses. (That happens on a regular basis, without my intervention.) But, still no-go.
On the other hand . . .
My DSL service has been down for the past several days, so I'm now using my dial-up account from another ISP. I can get to LHC with it, but not with my normal ISP's DSL service.
Donald, I would bet that lhcathome.cern.ch was blocking just one IP address in my range, but blocking your entire range. I know you can't see my thread on LHC's forums, but I'm still waiting for a response from them. If a moderator or administrator would acknoledge the problem, I could ask them to fix it.
After I saw your post, I tried going to their website again, for the first time in quite a few weeks. I'm still blocked, and can't even see the post that you made about it.
Donald, I ended up discovering that my IP address was somehow being blocked. I couldn't even ping lhcathome.cern.ch (138.37.50.115). The fix was simple; I just reset my Linksys router, forcing it to get a new IP address from AT&T's dynamic IP pool. With a different IP address, everything started working as normal.
Well, my DSL gateway has been reset numerous times, with numerous new IP addresses. (That happens on a regular basis, without my intervention.) But, still no-go.
On the other hand . . .
My DSL service has been down for the past several days, so I'm now using my dial-up account from another ISP. I can get to LHC with it, but not with my normal ISP's DSL service.
So, the mystery continues.
Mystery solved some time ago. There is an ISP over on the other side of the pond with a misconfiged router. The router will not pass packets with a hop counts over a threshold of about 15. I know this because I first saw it in September. At that time I had access to machines on more the one ISP. I couldn't reach the LHC website via one while I had it up on the other at the same time. Traceroutes from both showed very different routes. Finding the router and who owns it and getting it re-configured will be a PITA.
Mystery solved some time ago. There is an ISP over on the other side of the pond with a misconfiged router. The router will not pass packets with a hop counts over a threshold of about 15. I know this because I first saw it in September. At that time I had access to machines on more the one ISP. I couldn't reach the LHC website via one while I had it up on the other at the same time. Traceroutes from both showed very different routes. Finding the router and who owns it and getting it re-configured will be a PITA.
Gary, that can't be it. First, a simple change of IP address fixed my problem even though I'm still behind the same AT&T router. Second, Alex's traceroute in this LHC@home thread has 21 hops. Third, the building that I had the problem from now successfully connects in 16 hops. Fourth, another building that I never had the problem with is 19 hops away--farther than the one that did have the problem.
I feel like I'm hijacking
)
I feel like I'm hijacking this thread by bringing it back to its original topic, but I recently had a similar experience being unable to go to lhcathome.cern.ch or even ping it.
I have posted the details of my trouble in this post at LHC@home's forum. I have yet to receive a response from either moderators or management. I really want them to acknowledge this problem, but I'm afraid their usual apathy will prevail.
I have no problem in going to
)
I have no problem in going to their site, but I cannot get any work to do. So I just put it on a NNT condition in order not to have my BOINC client trying continuously to get some work.
Tullio
RE: I have no problem in
)
The trouble is that unless you watch like a hawk you are just as likely to miss all the work issued. The whole point of exponential back off is to handle this very situation. THough I have found I can't get as much work as I would like regardless. :(
You should allow tasks and just let the system work ... though this is one of the projects that shows the weakness of the "Resource Share" concept because of the lack of reliable work. If you set the share to a value that is truly what you would like, the system still subverts this by limiting the work drawn (on the server side) and the accumulation of debt (on the client side).
Because of the major efforts being made to change the Resource Scheduler several of us suggested changes to make the overall system better (though it would not cure all of the ills of the current Resource Share system) but were rebuffed (sadly).
RE: I feel like I'm
)
After I saw your post, I tried going to their website again, for the first time in quite a few weeks. I'm still blocked, and can't even see the post that you made about it.
RE: After I saw your post,
)
Donald, I ended up discovering that my IP address was somehow being blocked. I couldn't even ping lhcathome.cern.ch (138.37.50.115). The fix was simple; I just reset my Linksys router, forcing it to get a new IP address from AT&T's dynamic IP pool. With a different IP address, everything started working as normal.
RE: I feel like I'm
)
This post has some new info, about the project rather than the connections.
RE: RE: After I saw your
)
Well, my DSL gateway has been reset numerous times, with numerous new IP addresses. (That happens on a regular basis, without my intervention.) But, still no-go.
On the other hand . . .
My DSL service has been down for the past several days, so I'm now using my dial-up account from another ISP. I can get to LHC with it, but not with my normal ISP's DSL service.
So, the mystery continues.
Donald, I would bet that
)
Donald, I would bet that lhcathome.cern.ch was blocking just one IP address in my range, but blocking your entire range. I know you can't see my thread on LHC's forums, but I'm still waiting for a response from them. If a moderator or administrator would acknoledge the problem, I could ask them to fix it.
RE: RE: RE: After I saw
)
Mystery solved some time ago. There is an ISP over on the other side of the pond with a misconfiged router. The router will not pass packets with a hop counts over a threshold of about 15. I know this because I first saw it in September. At that time I had access to machines on more the one ISP. I couldn't reach the LHC website via one while I had it up on the other at the same time. Traceroutes from both showed very different routes. Finding the router and who owns it and getting it re-configured will be a PITA.
RE: Mystery solved some
)
Gary, that can't be it. First, a simple change of IP address fixed my problem even though I'm still behind the same AT&T router. Second, Alex's traceroute in this LHC@home thread has 21 hops. Third, the building that I had the problem from now successfully connects in 16 hops. Fourth, another building that I never had the problem with is 19 hops away--farther than the one that did have the problem.