The computer at my workplace (ID=5019353 ) is doing E@H work and is connected via proxy to the internet. The problem is: Each time a GW LineVeto task is finished the following upload of the result file fails. Logfile "stdoutdae.txt":Temporarily failed upload of h1_0442.30_S6GC1__1941_S6BucketA_3_0: HTTP error
as an example. Results of all other kinds of E@H tasks are uploaded without any complains. At first sight I couldn't believe the proxy being the part that is preventing BOINC from uploading the results. I first reset E@H, then detached from and reattached to E@H, but the problem continued.
To be certain I don't have a problem with the proxy, I took the computer home and connected it directly to my DSL router at home. As soon as it was connected and I pressed the "Try again" button all the suspended uploads were being performed successfully. It was amazing.
Now I am pretty much confused. Does a proxy distingish between "pleasant" and "unpleasant" files? Those unpleasant files of GW tasks are refused, all others are welcome? ;-) The concluding question now is: By what measures can our network administrator try to get GW LineVeto output files through the proxy?
As an interim solution I switched off "Gravitational Wave S6 LineVeto search" in the venue of my computer 5019353. But the server seems to ignore it. Computer 5019353 is still receiving new GW LinVeto tasks. I would be really glad if that switch worked, since my other computer at home could do the GW job as well and the problem would be solved the easy way.
Gruß von Heinrich
Copyright © 2024 Einstein@Home. All rights reserved.
BOINC doesn't upload GW output files via proxy
)
GW result files are uploaded to einstein.phys.uwm.edu. BRP and FGRP results get uploaded to einstein-dl.aei.uni-hannover.de. I think the problem is the upload URL, not the content of the files (which is actually quite similar).
Disabling the GW apps is broken in the scheduler code currently used on Einstein@Home, it has been for years without being noticed. Sorry.
BM
BM
Thank you, Bernd, for your
)
Thank you, Bernd, for your having taken a look at this problem.
As I know nearly nothing about how a proxy is working, I cannot understand how the URL that BOINC uses when it sends a result to its appropriate server _does_ work without a proxy and if a proxy is in between the same URL _does not_ work. Does a proxy make some kind of URL transformation that potentially can go wrong?
I wouldn't care so much about the problem mentioned above, if BOINC didn't react on failed uploads in an unfavourable manner: Once an upload had failed, all future uploads get stuck. As a consequence I have to load up manually all BRP and FGRP results that are kept from being sent by the congestion that a single not sent GW result provokes. This means a nearly daily maintenance which I can hardly guarantee.
Gruß von Heinrich