Project

General

Profile

Bug #13819

prodcosmics_corsika_sbnd.fcl Error

Added by Kelwin Matias over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Simulation
Start date:
09/08/2016
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Duration:

Description

Corsika crashes after running the command lar -c prodcosmics_corsika_sbnd.fcl

My work area is: /sbnd/app/users/kmatias/SBND_Data

Error log:

-bash-4.1$ lar -c prodcosmics_corsika_sbnd.fcl
fNcryostat: 1
fPlanePerAPA: 3
fNTPC0: 2
fWiresPerPlane0[0][0] 1982
fWiresPerPlane0[0][1] 1982
fWiresPerPlane0[0][2] 1666
fWiresPerPlane0[1][0] 1982
fWiresPerPlane0[1][1] 1982
fWiresPerPlane0[1][2] 1666
Failed to acquire credentials.
GSS Major Status: General failure

GSS Minor Status Error Chain:
globus_gsi_gssapi: Error with GSI credential
globus_gsi_gssapi: Error with gss credential handle
globus_credential: Valid credentials could not be found in any of the possible locations specified by the credential search order.
Valid credentials could not be found in any of the possible locations specified by the credential search order.
Attempt 1
globus_credential: Error reading host credential
globus_sysconfig: Could not find a valid certificate file: The host cert could not be found in:
1) env. var. X509_USER_CERT
2) /etc/grid-security/hostcert.pem
3) $GLOBUS_LOCATION/etc/hostcert.pem
4) $HOME/.globus/hostcert.pem

The host key could not be found in:
1) env. var. X509_USER_KEY
2) /etc/grid-security/hostkey.pem
3) $GLOBUS_LOCATION/etc/hostkey.pem
4) $HOME/.globus/hostkey.pem

Attempt 2
globus_credential: Error reading proxy credential
globus_sysconfig: Could not find a valid proxy certificate file location
globus_sysconfig: Error with key filename
globus_sysconfig: File does not exist: /tmp/x509up_u50929 is not a valid file
Attempt 3
globus_credential: Error reading user credential
globus_sysconfig: Error with certificate filename: The user cert could not be found in:
1) env. var. X509_USER_CERT
2) $HOME/.globus/usercert.pem
3) $HOME/.globus/usercred.p12

Failed to acquire credentials.
GSS Major Status: General failure

GSS Minor Status Error Chain:
globus_gsi_gssapi: Error with GSI credential
globus_gsi_gssapi: Error with gss credential handle
globus_credential: Valid credentials could not be found in any of the possible locations specified by the credential search order.
Valid credentials could not be found in any of the possible locations specified by the credential search order.
Attempt 1
globus_credential: Error reading host credential
globus_sysconfig: Could not find a valid certificate file: The host cert could not be found in:
1) env. var. X509_USER_CERT
2) /etc/grid-security/hostcert.pem
3) $GLOBUS_LOCATION/etc/hostcert.pem
4) $HOME/.globus/hostcert.pem

The host key could not be found in:
1) env. var. X509_USER_KEY
2) /etc/grid-security/hostkey.pem
3) $GLOBUS_LOCATION/etc/hostkey.pem
4) $HOME/.globus/hostkey.pem

Attempt 2
globus_credential: Error reading proxy credential
globus_sysconfig: Could not find a valid proxy certificate file location
globus_sysconfig: Error with key filename
globus_sysconfig: File does not exist: /tmp/x509up_u50929 is not a valid file
Attempt 3
globus_credential: Error reading user credential
globus_sysconfig: Error with certificate filename: The user cert could not be found in:
1) env. var. X509_USER_CERT
2) $HOME/.globus/usercert.pem
3) $HOME/.globus/usercred.p12

%MSG-s ArtException: CORSIKAGen:generator@Construction 08-Sep-2016 20:30:50 CDT ModuleConstruction
cet::exception caught in art
---- CORSIKAGen BEGIN
No files returned for path:pattern: /pnfs/larsoft/persistent/physics/cosmics/Fermilab/CORSIKA/standard:p_showers_*.db
---- CORSIKAGen END
%MSG
Art has completed and will exit with status 65.

History

#1 Updated by Gianluca Petrillo about 3 years ago

  • Category set to Simulation
  • Status changed from New to Feedback
  • Occurs In v05_12_01 added

I can't reproduce the problem.
It might be related to missing credentials (see Get a certificate proxy).
If the problem persists, please attach to this bug report the messages.log file produced by the job.

#2 Updated by Gianluca Petrillo about 3 years ago

  • Status changed from Feedback to Closed

Closing for lack of feedback.
If the problem persists, just reopen this ticket or open a new one.



Also available in: Atom PDF