I have also been having problems for the last day & a half. My one and only completed ABP WU successfully achieved a partial upload, but has been unable to upload the final result file.
-----------------
5/4/2010 7:44:56 AM Resuming network activity
5/4/2010 7:44:56 AM Einstein@Home Started upload of p2030_53771_57665_0061_G59.53-00.37.S_3.dm_492_1_2
5/4/2010 7:45:42 AM Project communication failed: attempting access to reference site
5/4/2010 7:45:42 AM Einstein@Home Temporarily failed upload of p2030_53771_57665_0061_G59.53-00.37.S_3.dm_492_1_2: HTTP error
5/4/2010 7:45:42 AM Einstein@Home Backing off 3 hr 33 min 19 sec on upload of p2030_53771_57665_0061_G59.53-00.37.S_3.dm_492_1_2
5/4/2010 7:45:43 AM Internet access OK - project servers may be temporarily down.
5/4/2010 7:45:55 AM Suspending network activity - user request
-------------
I have experienced rare upload problems with Einstein@Home, but not for many months.
The only (apparently) unusual response is the initial "back-off" of two to three hours. It seems to me that after an initial failed upload a "back-off" of a few minutes would be followed by ever longer "back-off" times. This WU is immediately jumping to a multiple hour back-off time. ie "Backing off 3 hr 33 min 19 sec." on the initial upload attempt of the day!
Could these internet problems have to do with the rollout of DNSSEC? ISPs updating in anticipation of this new thing? I know my ISP has had its fair share of DNS trouble the past few days.
Could these internet problems have to do with the rollout of DNSSEC? ISPs updating in anticipation of this new thing? I know my ISP has had its fair share of DNS trouble the past few days.
as for my problems i have no idea, the 0 byte is showing up on both of my hosts, the only comonality is comodo but ive verified e@h is an exception on both systems. so im at a loss :|
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
Yes, but it depends on one's local arrangements for DNS resolution. There is a DNS server hierarchy, so an unserviceable request gets bumped up to a higher level - and the ( successful or not ) answer comes back down - translating a domain name to an IP address. If a lower level DNS server is not set up for this new validation system, and having referred the matter upwards can't then understand the reply returned ( or punts it out as abnormal because it's not the traditional UDP packet < 512 bytes ) then you can't resolve.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Yes, but it depends on one's local arrangements for DNS resolution. There is a DNS server hierarchy, so an unserviceable request gets bumped up to a higher level - and the ( successful or not ) answer comes back down - translating a domain name to an IP address. If a lower level DNS server is not set up for this new validation system, and having referred the matter upwards can't then understand the reply returned ( or punts it out as abnormal because it's not the traditional UDP packet < 512 bytes ) then you can't resolve.
Cheers, Mike.
ah, i stand corrected. and since my router cant handle < 512 UDP i may then have a problem :|
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
You could try OpenDNS to avoid whatever your ISP has setup for DNS resolution.
Ah. I previously mentioned that one of my five hosts, while experiencing a significant failure rate, nevertheless is doing so much better at this than the others that it has not been building up a queue of retrying transfers.
I previously mentioned that was my sole host on BOINC 5.10.45 (others on 5.10.20), a possibly spurious correlation. I now realize that was the only host I had previously set to use Google's Public DNS.
Even if it helps an individual machine, this is no Panacea--my "good" host was suffering an appreciable failure rate all along, and at this typing actually has three uploads on retry with retry counts of 9 or 10, but this is far better than the others.
As to the alternative--my ISP is Comcast, and my location Albuqerque NM. I think my actual Comcast DNS service comes from Colorado, perhaps.
RE: ]But perhaps the trick
)
Nope. ABP work is only served from this server.
BM
BM
I have also been having
)
I have also been having problems for the last day & a half. My one and only completed ABP WU successfully achieved a partial upload, but has been unable to upload the final result file.
-----------------
5/4/2010 7:44:56 AM Resuming network activity
5/4/2010 7:44:56 AM Einstein@Home Started upload of p2030_53771_57665_0061_G59.53-00.37.S_3.dm_492_1_2
5/4/2010 7:45:42 AM Project communication failed: attempting access to reference site
5/4/2010 7:45:42 AM Einstein@Home Temporarily failed upload of p2030_53771_57665_0061_G59.53-00.37.S_3.dm_492_1_2: HTTP error
5/4/2010 7:45:42 AM Einstein@Home Backing off 3 hr 33 min 19 sec on upload of p2030_53771_57665_0061_G59.53-00.37.S_3.dm_492_1_2
5/4/2010 7:45:43 AM Internet access OK - project servers may be temporarily down.
5/4/2010 7:45:55 AM Suspending network activity - user request
-------------
I have experienced rare upload problems with Einstein@Home, but not for many months.
The only (apparently) unusual response is the initial "back-off" of two to three hours. It seems to me that after an initial failed upload a "back-off" of a few minutes would be followed by ever longer "back-off" times. This WU is immediately jumping to a multiple hour back-off time. ie "Backing off 3 hr 33 min 19 sec." on the initial upload attempt of the day!
Could these internet problems
)
Could these internet problems have to do with the rollout of DNSSEC? ISPs updating in anticipation of this new thing? I know my ISP has had its fair share of DNS trouble the past few days.
RE: Could these internet
)
my understanding is the initial rollout of dnssec applys to the root zone only and the internet wont break. No, DNSSEC Upgrades Won't Break The Internet Next Week
as for my problems i have no idea, the 0 byte is showing up on both of my hosts, the only comonality is comodo but ive verified e@h is an exception on both systems. so im at a loss :|
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
RE: my understanding is the
)
Yes, but it depends on one's local arrangements for DNS resolution. There is a DNS server hierarchy, so an unserviceable request gets bumped up to a higher level - and the ( successful or not ) answer comes back down - translating a domain name to an IP address. If a lower level DNS server is not set up for this new validation system, and having referred the matter upwards can't then understand the reply returned ( or punts it out as abnormal because it's not the traditional UDP packet < 512 bytes ) then you can't resolve.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Seems to me that the problems
)
Seems to me that the problems are project specific (ie Einstein) -- and also affect downloads.
I recall that this project has had similar problems in the past -- as have other projects with I/O problems (SETI for example).
Perhaps it could be because
)
Perhaps it could be because you are the first project in the BOINC Pentathlon? You do know your project was chosen as the first leg?
There are now 31 teams pounding away at your servers.....
BOINC Pentathlon einstein standings
RE: RE: my understanding
)
ah, i stand corrected. and since my router cant handle < 512 UDP i may then have a problem :|
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
You could try OpenDNS to
)
You could try OpenDNS to avoid whatever your ISP has setup for DNS resolution.
RE: You could try OpenDNS
)
Ah. I previously mentioned that one of my five hosts, while experiencing a significant failure rate, nevertheless is doing so much better at this than the others that it has not been building up a queue of retrying transfers.
I previously mentioned that was my sole host on BOINC 5.10.45 (others on 5.10.20), a possibly spurious correlation. I now realize that was the only host I had previously set to use Google's Public DNS.
Even if it helps an individual machine, this is no Panacea--my "good" host was suffering an appreciable failure rate all along, and at this typing actually has three uploads on retry with retry counts of 9 or 10, but this is far better than the others.
As to the alternative--my ISP is Comcast, and my location Albuqerque NM. I think my actual Comcast DNS service comes from Colorado, perhaps.