-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
two blocks persistently failed to migrate to phys03 #115
Comments
I looked in logs myself and found this for the second migration ID in above sample: 4889788
|
culprit seems to be this Message:unable to find parent lfn /store/mc/Run3Winter24Reco/JPsiToMuMu_PT-0to100_pythia8-gun/AODSIM/KeepSi_133X_mcRun3_2024_realistic_v8-v2/2540000/deab1d58-e1f5-4498-8642-da601a52cb51.root |
that makes little sense since that file exists in DBS with valid status or in short belforte@lxplus826/~> dasgoclient --query 'file file=/store/mc/Run3Winter24Reco/JPsiToMuMu_PT-0to100_pythia8-gun/AODSIM/KeepSi_133X_mcRun3_2024_realistic_v8-v2/2540000/deab1d58-e1f5-4498-8642-da601a52cb51.root | grep file.is_file_valid'
1
belforte@lxplus826/~> something wrong in DBS code ? full error message seems to complain about SQL but it is possibly a consequence of the file not found [2024-11-27 13:23:15.509599491 +0000 UTC m=+1377063.689315803] migrate.go:1116: insert bulkblocks for mid 4889788 error DBSError Code:101 Description:DBS DB error Function:dbs.bulkblocks.InsertBulkBlocksConcurrently Message:unable to find parent lfn /store/mc/Run3Winter24Reco/JPsiToMuMu_PT-0to100_pythia8-gun/AODSIM/KeepSi_133X_mcRun3_2024_realistic_v8-v2/2540000/deab1d58-e1f5-4498-8642-da601a52cb51.root Error: nested DBSError Code:103 Description:DBS DB query error, e.g. mailformed SQL statement Function:dbs.GetID Message: Error: sql: no rows in result set that line is in |
hi @belforte looking into it |
hi @todor-ivanov |
hi @belforte I was not able to spot anything more than what you were already reporting. The parent lfn is indeed in DBS. As a last resort, I restarted the service few minutes ago, as you suggested. Please let me know if the error persists. I am also watching the logs on the |
thanks Todor, I will let you know how it goes in next iteration |
still failing. I will force Publisher to ignore the corresponding requests |
Hi @belforte how many were those? |
two tasks. retrying sine beginning of November. Publication in DBS is the default for CRAB, in this case chances are that the user does not even care. Yet it is the first time that we have a "permanently failed" migration in all of DBS history. Until now those could always be recovered. |
blocks
when trying to migrate in CRAB Publisher the migration request always fails with
(status=9)
In such cases the Publisher deletes the migration and submits a new one, which solves rare issues related to e.g. servers restarts while migrations were going on).
But for those thow blocks any new request keeps failing. Since more than ten days.
Can you look in logs from your side ?
Latest example:
The text was updated successfully, but these errors were encountered: