You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far I have only been able to reproduce this at Fermilab, not at CERN, but I can quite reliably reproduce it in cvmfs-2.11.0 and 2.11.1 in less than a minute with 5 parallel processes reading from different files in one osgstorage.org repository hosted at Fermilab. /var/log/messages shows junk binary data at the end of the filename in the error message, for example:
Oct 16 16:39:38 dwdosgdev cvmfs2: (uboone.osgstorage.org) failed to fetch /pnfs/fnal.gov/usr/uboone/persistent/stash/uboonebeam/beam_data/bnb_data/00/00/97/19/beamdata_00009719.rootd���#017�#013W#011 (hash: d51f473dec6608c999a8ab9b7352008bbdf9c4bd, error 9 [host returned HTTP error])
Debug logs show that it's not just that error message, that the file name is corrupted in operations before that. This is an excerpt showing the file name transitioning from OK to corrupted:
I can reproduce the problem in the July 12 nightly build but not July 8, so I'm quite confident that the problem was introduced in #3263. CVMFS_STREAMING_CACHE is not set.
The text was updated successfully, but these errors were encountered:
So far I have only been able to reproduce this at Fermilab, not at CERN, but I can quite reliably reproduce it in cvmfs-2.11.0 and 2.11.1 in less than a minute with 5 parallel processes reading from different files in one osgstorage.org repository hosted at Fermilab. /var/log/messages shows junk binary data at the end of the filename in the error message, for example:
Debug logs show that it's not just that error message, that the file name is corrupted in operations before that. This is an excerpt showing the file name transitioning from OK to corrupted:
I can reproduce the problem in the July 12 nightly build but not July 8, so I'm quite confident that the problem was introduced in #3263. CVMFS_STREAMING_CACHE is not set.
The text was updated successfully, but these errors were encountered: