Difference: JobExitCodes (1 vs. 89)

Revision 892019-07-26 - JeanrochVlimant

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

IMPORTANT:

Any change which are done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py
Line: 157 to 157
 
    • 71301 - The job was killed by the WMAgent because the site it was running at was set to Aborted (WMAgent)
    • 71302 - The job was killed by the WMAgent because the site it was running at was set to Draining (WMAgent)
    • 71303 - The job was killed by the WMAgent because the site it was running at was set to Down (WMAgent)
Changed:
<
<
    • 71304 - The job was killed by the WMAgent for using too much wallclock time (WMAgent)
>
>
    • 71304 - The job was killed by the WMAgent for using too much wallclock time (WMAgent) Job status was Running.
    • 71305 - The job was killed by the WMAgent for using too much wallclock time (WMAgent) Job status was Pending.
    • 71306 - The job was killed by the WMAgent for using too much wallclock time (WMAgent) Job status was Error.
    • 71307 - The job was killed by the WMAgent for using too much wallclock time (WMAgent) Job status was Unkown.
 
    • 70318 - Failure in DQM upload.
    • 70452 - No run/lumi information in file (WMAgent)

Revision 882018-06-13 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

IMPORTANT:

Any change which are done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py
Line: 24 to 24
  ALERT! indicates site error
Changed:
<
<
  • Error exit code of the cmsRun application itself - range 0-10000 (Exit codes in 1-512 are standard ones in Unix and indicate a CMSSW abort that the cmsRun did not catch as exception)
    • -1 - Error return without specification
    • 1 - Hangup (POSIX)
    • 2 - Interrupt (ANSI)
    • 4 - Illegal instruction (ANSI)
    • 5 - Trace trap (POSIX)
    • 6 - Abort (ANSI) or IOT trap (4.2BSD)
    • 7 - BUS error (4.2BSD)
    • 8 - Floating point exception (ANSI)
    • 9 - killed, unblockable (POSIX) kill -9
    • 11 - segmentation violation (ANSI) (most likely user application crashed)
    • 15 - Termination (ANSI)
    • 24 - Soft CPU limit exceeded (4.2 BSD)
    • 25 - File size limit exceeded (4.2 BSD)
    • 30 - Power failure restart (System V.)
    • 50 - Required application version not found at the site.
    • 64 - I/O error: cannot open data file (SEAL)
    • 65 - End of job from user application (CMSSW)
    • 66 - Application exception
    • 73 - Failed writing to read-only file system
    • 81 - Job did not find functioning CMSSW on worker node.
    • 84 - Some required file not found; check logs for name of missing file.
    • 85 - Job failed to open local and fallback files.
    • 90 - Application exception
    • 92 - Job failed to open local and fallback files.
    • 126 - Permission problem or command is not an executable
    • 127 - Command not found
    • 129 - Hangup (POSIX)
    • 132 - Illegal instruction (ANSI)
    • 133 - Trace trap (POSIX)
    • 134 - Abort (ANSI) or IOT trap (4.2 BSD) (most likely user application crashed)
    • 135 - Bus error (4.2 BSD)
    • 137 - SIGKILL; likely an unrelated batch system kill.
    • 139 - Segmentation violation (ANSI)
    • 143 - Termination (ANSI)(or incorporate in the msg text)
    • 147 - Error during attempted file stageout.
    • 151 - Error during attempted file stageout.
    • 152 - CPU limit exceeded (4.2 BSD)
    • 153 - File size limit exceeded (4.2 BSD)
    • 155 - Profiling alarm clock (4.2 BSD)
    • 195 - Job did not produce a FJR; will retry.
    • 243 - Timeout during attempted file stageout.
>
>
  • Error exit code of the cmsRun application itself - range 0-10000
  • Exit codes in 1-255 are standard ones in Unix and indicate a CMSSW abort that the cmsRun did not catch as exception
 
  • cmsRun (CMSSW) exit codes. range 7000-9000 * *These codes may depend on specific CMSSW version, the list is maintained in here and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
    • // The first three are specific categories of CMS Exceptions.
Line: 105 to 68
 
    • 8030 - Exceeded maximum allowed VSize (ExceededResourceVSize).
    • 8031 - Exceeded maximum allowed RSS (ExceededResourceRSS).
    • 8032 - Exceeded maximum allowed time (ExceededResourceTime).
Changed:
<
<
    • ALERT! 8033 - Could now write output file (FileWriteError) (usually local disk problem)
>
>
    • ALERT! 8033 - Could not write output file (FileWriteError) (usually local disk problem)
 
    • 9000 - cmsRun caught (SIGINT and SIGUSR2) signal.
  • ALERT! Failures related to the environment setup - range 10000-19999
    • 10001 - Connectivity problems

Revision 872018-06-11 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

IMPORTANT:

Any change which are done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py
Line: 102 to 102
 
    • 8026 - NotFound (something other than a product or dictionary not found)
    • 8027 - FormatIncompatibility
    • ALERT! 8028 - FileOpenError with fallback
Changed:
<
<
>
>
    • 8030 - Exceeded maximum allowed VSize (ExceededResourceVSize).
    • 8031 - Exceeded maximum allowed RSS (ExceededResourceRSS).
    • 8032 - Exceeded maximum allowed time (ExceededResourceTime).
    • ALERT! 8033 - Could now write output file (FileWriteError) (usually local disk problem)
 
    • 9000 - cmsRun caught (SIGINT and SIGUSR2) signal.
  • ALERT! Failures related to the environment setup - range 10000-19999
    • 10001 - Connectivity problems

Revision 862017-09-21 - RokasMaciulaitis

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

IMPORTANT:

Any change which are done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py
Line: 107 to 107
 
    • 8032 - Exceeded maximum allowed time (ExceededResourceTime).
    • 9000 - cmsRun caught (SIGINT and SIGUSR2) signal.
  • ALERT! Failures related to the environment setup - range 10000-19999
Changed:
<
<
    • ALERT! 10031 - Directory VO_CMS_SW_DIR not found
>
>
    • 10001 - Connectivity problems
    • 10002 - CPU load is too high
    • 10003 - CMS software initialisation script cmsset_default.sh failed
    • 10004 - CMS_PATH not defined
    • 10005 - CMS_PATH directory does not exist
    • 10006 - scramv1 command not found
    • 10007 - Some CMSSW files are corrupted/non readable
    • 10008 - Scratch dir was not found
    • 10009 - Less than 5 GB/core of free space in scratch dir
    • 10010 - Could not find X509 certificate directory
    • 10011 - Could not find X509 proxy certificate
    • 10012 - Unable to locate the glidein configuration file
    • 10013 - No sitename detected! Invalid SITECONF file
    • 10014 - No PhEDEx node name found for local or fallback stageout
    • 10015 - No LOCAL_STAGEOUT section in site-local-config.xml
    • 10016 - No frontier-connect section in site-local-config.xml
    • 10017 - No callib-data section in site-local-config.xml
    • 10018 - site-local-config.xml was not found
    • 10019 - TrivialFileCatalog string missing
    • 10020 - event_data section is missing
    • 10021 - no proxy string in site-local-config.xml
    • 10022 - Squid test was failed
    • 10023 - Clock skew is bigger than 60 sec
    • 10031 - Directory VO_CMS_SW_DIR not found
 
    • ALERT! 10032 - Failed to source CMS Environment setup script such as cmssset_default.sh, grid system or site equivalent script
    • ALERT! 10034 - Required application version is not found at the site (see HERE.)
    • ALERT! 10040 - failed to generate cmsRun cfg file at runtime
    • ALERT! 10042 - Unable to stage-in wrapper tarball.
    • ALERT! 10043 - Unable to bootstrap WMCore libraries (most likely site python is broken).
Added:
>
>
    • ALERT! 10050 - WARNING test_squid.py: One of the load balance Squid proxies
    • ALERT! 10051 - WARNING less than 20 GB of free space per core in scratch dir
    • ALERT! 10052 - WARNING less than 10MB free in /tmp
    • ALERT! 10053 - WARNING CPU load of last minutes + pilot cores is higher than number of physical CPUs
    • ALERT! 10054 - WARNING proxy shorther than 6 hours
 
  • Executable file related failures - range 50000-59999
    • 50110 - Executable file is not found

Revision 852017-03-21 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

IMPORTANT:

Any change which are done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py
Line: 136 to 136
 
    • 60312 - Failed to get file TURL via lcg-lr command
    • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
    • 60316 - Failed to create a directory on the SE
Added:
>
>
    • 60317 - Forced timeout for stuck stage out
 
    • 60318 - Internal error in Crab cmscp.py stageout script
    • 60319 - Failure to do AlcaHarvest stageout (WMAgent)
    • 60320 - Failure to communicate with ASO server
    • ALERT! 60321 - Site related issue: no space, SE down, refused connection.
    • 60322 - User is not authorized to write to destination site.
    • 60323 - User quota exceeded.
Changed:
<
<
    • 60324 - Asynchonous stageout transfer request timed out
    • 60325 - Other stageout exception.
>
>
    • 60324 - Other stageout exception.
 
    • 60401 - Failure to assemble LFN in direct-to-merge by size (WMAgent)
    • 60402 - Failure to assemble LFN in direct-to-merge by event (WMAgent)
    • 60403 - Timeout during attempted file transfer - status unknown (WMAgent)

Revision 842017-03-21 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

IMPORTANT:

Any change which are done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py
Line: 137 to 137
 
    • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
    • 60316 - Failed to create a directory on the SE
    • 60318 - Internal error in Crab cmscp.py stageout script
Changed:
<
<
    • 60319 - Failure to do asynchronous stageout
>
>
 
    • 60320 - Failure to communicate with ASO server
    • ALERT! 60321 - Site related issue: no space, SE down, refused connection.
    • 60322 - User is not authorized to write to destination site.
    • 60323 - User quota exceeded.
Changed:
<
<
    • 60324 - Other stageout exception.
>
>
    • 60324 - Asynchonous stageout transfer request timed out
    • 60325 - Other stageout exception.
 
    • 60401 - Failure to assemble LFN in direct-to-merge by size (WMAgent)
    • 60402 - Failure to assemble LFN in direct-to-merge by event (WMAgent)
    • 60403 - Timeout during attempted file transfer - status unknown (WMAgent)

Revision 832016-03-14 - MarcoMascheroni

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

IMPORTANT:

Any change which are done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py
Line: 169 to 169
 
  • Failures related only for CRAB3- range 80000-89999
    • 80000 - Internal error in CRAB job wrapper
Added:
>
>
    • 80001 - No exit code set by job wrapper.
 
    • 80453 - Unable to determine pset hash from output file (CRAB3).

  • Other problems which does not fit to any range before.- range 90000-99999

Revision 822015-12-07 - JustasBalcas

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

IMPORTANT:

Changed:
<
<
Any change which is done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py
>
>
Any change which are done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py
 
  • Range(1 - 512)
    • standard ones in Unix and indicate a CMSSW abort that the cmsRun did not catch as exception
Line: 28 to 28
 
    • -1 - Error return without specification
    • 1 - Hangup (POSIX)
    • 2 - Interrupt (ANSI)
Deleted:
<
<
    • 3 - unknown
 
    • 4 - Illegal instruction (ANSI)
    • 5 - Trace trap (POSIX)
    • 6 - Abort (ANSI) or IOT trap (4.2BSD)
    • 7 - BUS error (4.2BSD)
    • 8 - Floating point exception (ANSI)
    • 9 - killed, unblockable (POSIX) kill -9
Deleted:
<
<
    • 10 - User defined
 
    • 11 - segmentation violation (ANSI) (most likely user application crashed)
Deleted:
<
<
    • 12 - User defined
 
    • 15 - Termination (ANSI)
    • 24 - Soft CPU limit exceeded (4.2 BSD)
    • 25 - File size limit exceeded (4.2 BSD)
Deleted:
<
<
    • 29 - nondefined
 
    • 30 - Power failure restart (System V.)
Changed:
<
<
    • 33 - nondefined
>
>
    • 50 - Required application version not found at the site.
 
    • 64 - I/O error: cannot open data file (SEAL)
    • 65 - End of job from user application (CMSSW)
    • 66 - Application exception
Deleted:
<
<
    • 67 - unknown
    • 68 - unknown
 
    • 73 - Failed writing to read-only file system
Added:
>
>
    • 81 - Job did not find functioning CMSSW on worker node.
 
    • 84 - Some required file not found; check logs for name of missing file.
Changed:
<
<
    • 88 - unknown
>
>
    • 85 - Job failed to open local and fallback files.
 
    • 90 - Application exception
Changed:
<
<
    • 100 - nondefined
    • 126 - unknown
    • 127 - Error while loading shared library
>
>
    • 92 - Job failed to open local and fallback files.
    • 126 - Permission problem or command is not an executable
    • 127 - Command not found
 
    • 129 - Hangup (POSIX)
    • 132 - Illegal instruction (ANSI)
    • 133 - Trace trap (POSIX)
    • 134 - Abort (ANSI) or IOT trap (4.2 BSD) (most likely user application crashed)
    • 135 - Bus error (4.2 BSD)
Changed:
<
<
    • 136 - unknown
    • 137 - killed, unblockable (POSIX) kill -9
    • 138 - User defined
>
>
    • 137 - SIGKILL; likely an unrelated batch system kill.
 
    • 139 - Segmentation violation (ANSI)
Deleted:
<
<
    • 140 - User defined
 
    • 143 - Termination (ANSI)(or incorporate in the msg text)
Added:
>
>
    • 147 - Error during attempted file stageout.
    • 151 - Error during attempted file stageout.
 
    • 152 - CPU limit exceeded (4.2 BSD)
    • 153 - File size limit exceeded (4.2 BSD)
    • 155 - Profiling alarm clock (4.2 BSD)
Changed:
<
<
    • 251 - nondefined
    • 255 - nondefined
    • 256 - Application exception
    • 512 - nondefined
    • 2304 - nondefined
    • 0001 - Plug-in or message service initialization Exception
>
>
    • 195 - Job did not produce a FJR; will retry.
    • 243 - Timeout during attempted file stageout.
 
Changed:
<
<
  • cmsRun (CMSSW) exit codes. These codes may depend on specific CMSSW version, the list is maintained in here and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
>
>
  • cmsRun (CMSSW) exit codes. range 7000-9000 * *These codes may depend on specific CMSSW version, the list is maintained in here and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
 
    • // The first three are specific categories of CMS Exceptions.
    • 7000 - Exception from command line processing
    • 7001 - Configuration File Not Found
Line: 112 to 102
 
    • 8026 - NotFound (something other than a product or dictionary not found)
    • 8027 - FormatIncompatibility
    • ALERT! 8028 - FileOpenError with fallback
Added:
>
>
 
  • ALERT! Failures related to the environment setup - range 10000-19999
Deleted:
<
<
    • ALERT! 10001 - LD_LIBRARY_PATH is not defined
    • ALERT! 10002 - Failed to setup LCG_LD_LIBRAR_PATH
    • ALERT! 10016 - OSG $WORKING_DIR could not be created
    • ALERT! 10017 - OSG $WORKING_DIR could not be deleted
    • ALERT! 10018 - OSG $WORKING_DIR could not be deleted
    • ALERT! 10020 - Shell script cmsset_default.sh to setup cms environment is not found
    • ALERT! 10021 - Failed to scram application project using the afs release area
    • ALERT! 10022 - Failed to scram application project using CMS sw disribution on the LCG2
    • ALERT! 10030 - middleware not identified
 
    • ALERT! 10031 - Directory VO_CMS_SW_DIR not found
    • ALERT! 10032 - Failed to source CMS Environment setup script such as cmssset_default.sh, grid system or site equivalent script
Deleted:
<
<
    • ALERT! 10033 - Platform is incompatible with the scram version
 
    • ALERT! 10034 - Required application version is not found at the site (see HERE.)
Deleted:
<
<
    • ALERT! 10035 - Scram Project Command Failed
    • ALERT! 10036 - Scram Runtime Command Failed
    • ALERT! 10037 - Failed to find cms_site_config file in software area
    • ALERT! 10038 - Failed to find cms_site_catalogue.sh file in software area
    • ALERT! 10039 - cms_site_catalogue.sh failed to provide the catalogue
 
    • ALERT! 10040 - failed to generate cmsRun cfg file at runtime
Deleted:
<
<
    • ALERT! 10041 - fail to find valid client for output stage out
 
    • ALERT! 10042 - Unable to stage-in wrapper tarball.
    • ALERT! 10043 - Unable to bootstrap WMCore libraries (most likely site python is broken).

  • Executable file related failures - range 50000-59999
    • 50110 - Executable file is not found
    • 50111 - Executable file has no exe permissions
Deleted:
<
<
    • 50112 - User executable shell file is not found
 
    • 50113 - Executable did not get enough arguments
Deleted:
<
<
    • 50114 - OSG $WORKING_DIR could not be deleted
 
    • 50115 - cmsRun did not produce a valid job report at runtime (often means cmsRun segfaulted)
    • 50116 - Could not determine exit code of cmsRun executable at runtime
Deleted:
<
<
    • 50117 - Could not update exit code in job report (a variation of 50115)
 
    • 50513 - Failure to run SCRAM setup scripts
    • 50660 - Application terminated by wrapper because using too much RAM (RSS)
    • 50661 - Application terminated by wrapper because using too much Virtual Memory (VSIZE)
Line: 153 to 128
 
    • 50664 - Application terminated by wrapper because using too much Wall Clock time
    • 50665 - Application terminated by wrapper because it stay idle too long
    • 50669 - Application terminated by wrapper for not defined reason
Deleted:
<
<
    • 50700 - Job Wrapper did not produce any usable output file
    • 50800 - Application segfaulted (likely user code problem)
    • 50998 - Problem calculating file details (i.e. size, checksum etc)
    • 50999 - OSG $WORKING_DIR could not be deleted
 
  • Staging-OUT related troubles- range 60000-69999
Deleted:
<
<
    • 60300 - Either OutputSE or OutputSE_DIR not defined
    • 60301 - Neither zip nor tar exists
 
    • 60302 - Output file(s) not found (see HERE.)
Deleted:
<
<
    • 60303 - File already exists on the SE
    • 60304 - Failed to create the summary file (production)
    • 60305 - Failed to create a zipped archive (production)
    • 60306 - Failed to copy and register output file
 
    • 60307 - Failed to copy an output file to the SE (sometimes caused by timeout issue). Or by the issues mentioned HERE.
Deleted:
<
<
    • 60308 - An output file was saved to fall back local SE after failing to copy to remote SE
    • 60309 - Failed to create an output directory in the catalogue
    • 60310 - Failed to register an output file in the catalogue
 
    • ALERT! 60311 - Local Stage Out Failure using site specific plugin
    • 60312 - Failed to get file TURL via lcg-lr command
Deleted:
<
<
    • 60313 - Failed to delete the output from the previous run via lcg-del command
    • 60314 - Failed to invoke ProdAgent StageOut Script
 
    • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
    • 60316 - Failed to create a directory on the SE
Deleted:
<
<
    • 60317 - Forced timeout for stuck stage out (see HERE.)
 
    • 60318 - Internal error in Crab cmscp.py stageout script
    • 60319 - Failure to do asynchronous stageout
    • 60320 - Failure to communicate with ASO server
Added:
>
>
    • ALERT! 60321 - Site related issue: no space, SE down, refused connection.
    • 60322 - User is not authorized to write to destination site.
    • 60323 - User quota exceeded.
    • 60324 - Other stageout exception.
 
    • 60401 - Failure to assemble LFN in direct-to-merge by size (WMAgent)
    • 60402 - Failure to assemble LFN in direct-to-merge by event (WMAgent)
    • 60403 - Timeout during attempted file transfer - status unknown (WMAgent)
    • 60404 - Timeout during staging of log archives - status unknown (WMAgent)
    • 60405 - General failure to stage out log archives (WMAgent)
Deleted:
<
<
    • 60406 - Failure in staging in log files during log collection (WMAgent)
 
    • 60407 - Timeout in staging in log files during log collection (WMAgent)
    • 60408 - Failure to stage out of log files during log collection (WMAgent)
    • 60409 - Timeout in stage out of log files during log collection (WMAgent)
Changed:
<
<
    • 60410 - Failure in deleting log files in log collection (WMAgent)
    • 60411 - Timeout in deleting log files in log collection (WMAgent)
>
>
    • 60450 - No output files present in the report
 
    • 60451 - Output file lacked adler32 checksum (WMAgent)
Deleted:
<
<
    • 60452 - No run/lumi information in file (WMAgent)
    • 60453 - Unable to determine pset hash from output file (CRAB3)
    • 60999 - SG $WORKING_DIR could not be deleted
    • 61101 - No sites are available to submit the job because the location of its input(s) do not pass the site whitelist/blacklist restrictions (WMAgent)
    • 61102 - The job can only run at a site that is currently in Aborted state (WMAgent)
    • 61103 - The JobSubmitter component could not load the job pickle (WMAgent)
    • 61104 - The job can run only at a site that is currently in Draining state (WMAgent)
    • 61300 - The job was killed by the WMAgent, reason is unknown (WMAgent)
    • 61301 - The job was killed by the WMAgent because the site it was running at was set to Aborted (WMAgent)
    • 61302 - The job was killed by the WMAgent because the site it was running at was set to Draining (WMAgent)
    • 61303 - The job was killed by the WMAgent because the site it was running at was set to Down (WMAgent)
    • 61304 - The job was killed by the WMAgent for using too much wallclock time (WMAgent)

  • Problems saving output via output sandbox- range 70000-70009
    • 70000 - Output_sandbox too big for WMS: output can not be retrieved
    • 70500 - Warning: problem with ModifyJobReport (see HERE.)
 
Changed:
<
<
  • Other problems
>
>
  • Failures related only for WMAgent.- range 70000-79999
    • 71101 - No sites are available to submit the job because the location of its input(s) do not pass the site whitelist/blacklist restrictions (WMAgent) Twas 61101
    • 71102 - The job can only run at a site that is currently in Aborted state (WMAgent)
    • 71103 - The JobSubmitter component could not load the job pickle (WMAgent)
    • 71104 - The job can run only at a site that is currently in Draining state (WMAgent)
    • 71300 - The job was killed by the WMAgent, reason is unknown (WMAgent)
    • 71301 - The job was killed by the WMAgent because the site it was running at was set to Aborted (WMAgent)
    • 71302 - The job was killed by the WMAgent because the site it was running at was set to Draining (WMAgent)
    • 71303 - The job was killed by the WMAgent because the site it was running at was set to Down (WMAgent)
    • 71304 - The job was killed by the WMAgent for using too much wallclock time (WMAgent)
    • 70318 - Failure in DQM upload.
    • 70452 - No run/lumi information in file (WMAgent)

  • Failures related only for CRAB3- range 80000-89999
 
    • 80000 - Internal error in CRAB job wrapper
Added:
>
>
    • 80453 - Unable to determine pset hash from output file (CRAB3).

  • Other problems which does not fit to any range before.- range 90000-99999
 
    • 90000 - Error in CRAB3 post-processing step (currently includes basically errors in stage out and file metadata upload).
    • 99109 - Uncaught exception in WMAgent step executor
\ No newline at end of file

Revision 812015-12-07 - JustasBalcas

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"
Added:
>
>

IMPORTANT:

Any change which is done here also must be done in: https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMExceptions.py

  • Range(1 - 512)
    • standard ones in Unix and indicate a CMSSW abort that the cmsRun did not catch as exception
  • Range(7000 - 9000)
  • Range(10000 - 19999)
    • Failures related to the environment setup
  • Range(50000 - 59999)
    • Failures related executable file
  • Range(60000 - 69999)
    • Failures related staging-OUT
  • Range(70000 - 79999)
    • Failures related only for WMAgent. (which does not fit into ranges before)
  • Range(80000 - 89999)
    • Failures related only for CRAB3. (which does not fit into ranges before)
  • Range(90000 - 99999)
    • Other problems which does not fit to any range before.
 

Error codes currently sent from CMS jobs to the dashboard

ALERT! indicates site error

Revision 802015-08-21 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 16 to 16
 
    • 8 - Floating point exception (ANSI)
    • 9 - killed, unblockable (POSIX) kill -9
    • 10 - User defined
Changed:
<
<
    • 11 - segmentation violation (ANSI)
>
>
    • 11 - segmentation violation (ANSI) (most likely user application crashed)
 
    • 12 - User defined
    • 15 - Termination (ANSI)
    • 24 - Soft CPU limit exceeded (4.2 BSD)
Line: 39 to 39
 
    • 129 - Hangup (POSIX)
    • 132 - Illegal instruction (ANSI)
    • 133 - Trace trap (POSIX)
Changed:
<
<
    • 134 - Abort (ANSI) or IOT trap (4.2 BSD)
>
>
    • 134 - Abort (ANSI) or IOT trap (4.2 BSD) (most likely user application crashed)
 
    • 135 - Bus error (4.2 BSD)
    • 136 - unknown
    • 137 - killed, unblockable (POSIX) kill -9

Revision 792015-08-13 - JadirSilva

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 131 to 131
 
    • 50662 - Application terminated by wrapper because using too much disk
    • 50663 - Application terminated by wrapper because using too much CPU time
    • 50664 - Application terminated by wrapper because using too much Wall Clock time
Added:
>
>
    • 50665 - Application terminated by wrapper because it stay idle too long
 
    • 50669 - Application terminated by wrapper for not defined reason
    • 50700 - Job Wrapper did not produce any usable output file
    • 50800 - Application segfaulted (likely user code problem)

Revision 782015-06-15 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 46 to 46
 
    • 138 - User defined
    • 139 - Segmentation violation (ANSI)
    • 140 - User defined
Changed:
<
<
    • 143 - Termination (ANSI)
>
>
    • 143 - Termination (ANSI)(or incorporate in the msg text)
 
    • 152 - CPU limit exceeded (4.2 BSD)
    • 153 - File size limit exceeded (4.2 BSD)
    • 155 - Profiling alarm clock (4.2 BSD)
Line: 57 to 57
 
    • 2304 - nondefined
    • 0001 - Plug-in or message service initialization Exception
Changed:
<
<
  • cmsRun (CMSSW) exit codes. These codes may depend on specific CMSSW version, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
>
>
  • cmsRun (CMSSW) exit codes. These codes may depend on specific CMSSW version, the list is maintained in here and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
 
    • // The first three are specific categories of CMS Exceptions.
    • 7000 - Exception from command line processing
    • 7001 - Configuration File Not Found

Revision 772015-05-11 - AndresTanasijczuk

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 190 to 190
 
  • Other problems
    • 80000 - Internal error in CRAB job wrapper
Added:
>
>
    • 90000 - Error in CRAB3 post-processing step (currently includes basically errors in stage out and file metadata upload).
 
    • 99109 - Uncaught exception in WMAgent step executor
\ No newline at end of file

Revision 762015-01-28 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 149 to 149
 
    • 60308 - An output file was saved to fall back local SE after failing to copy to remote SE
    • 60309 - Failed to create an output directory in the catalogue
    • 60310 - Failed to register an output file in the catalogue
Changed:
<
<
>
>
    • ALERT! 60311 - Local Stage Out Failure using site specific plugin
 
    • 60312 - Failed to get file TURL via lcg-lr command
    • 60313 - Failed to delete the output from the previous run via lcg-del command
    • 60314 - Failed to invoke ProdAgent StageOut Script

Revision 752014-12-08 - SeangchanRyu

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 182 to 182
 
    • 61301 - The job was killed by the WMAgent because the site it was running at was set to Aborted (WMAgent)
    • 61302 - The job was killed by the WMAgent because the site it was running at was set to Draining (WMAgent)
    • 61303 - The job was killed by the WMAgent because the site it was running at was set to Down (WMAgent)
Added:
>
>
    • 61304 - The job was killed by the WMAgent for using too much wallclock time (WMAgent)
 
  • Problems saving output via output sandbox- range 70000-70009
    • 70000 - Output_sandbox too big for WMS: output can not be retrieved

Revision 742014-10-30 - IanTomalin

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 82 to 82
 
    • 8017 - ScheduleExecutionFailure
    • 8018 - EventProcessorFailure
    • 8019 - FileInPathError
Changed:
<
<
    • ALERT! 8020 - FileOpenError (Likely a site error)
>
>
    • ALERT! 8020 - FileOpenError (Likely a site error) (see HERE.)
 
Line: 105 to 105
 
    • ALERT! 10031 - Directory VO_CMS_SW_DIR not found
    • ALERT! 10032 - Failed to source CMS Environment setup script such as cmssset_default.sh, grid system or site equivalent script
    • ALERT! 10033 - Platform is incompatible with the scram version
Changed:
<
<
    • ALERT! 10034 - Required application version is not found at the site
>
>
    • ALERT! 10034 - Required application version is not found at the site (see HERE.)
 
    • ALERT! 10035 - Scram Project Command Failed
    • ALERT! 10036 - Scram Runtime Command Failed
    • ALERT! 10037 - Failed to find cms_site_config file in software area
Line: 140 to 140
 
  • Staging-OUT related troubles- range 60000-69999
    • 60300 - Either OutputSE or OutputSE_DIR not defined
    • 60301 - Neither zip nor tar exists
Changed:
<
<
    • 60302 - Output file(s) not found
>
>
    • 60302 - Output file(s) not found (see HERE.)
 
    • 60303 - File already exists on the SE
    • 60304 - Failed to create the summary file (production)
    • 60305 - Failed to create a zipped archive (production)
    • 60306 - Failed to copy and register output file
Changed:
<
<
    • 60307 - Failed to copy an output file to the SE (sometimes caused by timeout issue).
>
>
    • 60307 - Failed to copy an output file to the SE (sometimes caused by timeout issue). Or by the issues mentioned HERE.
 
    • 60308 - An output file was saved to fall back local SE after failing to copy to remote SE
    • 60309 - Failed to create an output directory in the catalogue
    • 60310 - Failed to register an output file in the catalogue
Line: 155 to 155
 
    • 60314 - Failed to invoke ProdAgent StageOut Script
    • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
    • 60316 - Failed to create a directory on the SE
Changed:
<
<
    • 60317 - Forced timeout for stuck stage out
>
>
    • 60317 - Forced timeout for stuck stage out (see HERE.)
 
    • 60318 - Internal error in Crab cmscp.py stageout script
    • 60319 - Failure to do asynchronous stageout
    • 60320 - Failure to communicate with ASO server
Line: 185 to 185
 
  • Problems saving output via output sandbox- range 70000-70009
    • 70000 - Output_sandbox too big for WMS: output can not be retrieved
Changed:
<
<
    • 70500 - Warning: problem with ModifyJobReport
>
>
    • 70500 - Warning: problem with ModifyJobReport (see HERE.)
 
  • Other problems
    • 80000 - Internal error in CRAB job wrapper

Revision 732014-10-23 - AndresTanasijczuk

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 158 to 158
 
    • 60317 - Forced timeout for stuck stage out
    • 60318 - Internal error in Crab cmscp.py stageout script
    • 60319 - Failure to do asynchronous stageout
Added:
>
>
    • 60320 - Failure to communicate with ASO server
 
    • 60401 - Failure to assemble LFN in direct-to-merge by size (WMAgent)
    • 60402 - Failure to assemble LFN in direct-to-merge by event (WMAgent)
    • 60403 - Timeout during attempted file transfer - status unknown (WMAgent)

Revision 722014-09-01 - AndresTanasijczuk

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 187 to 187
 
    • 70500 - Warning: problem with ModifyJobReport

  • Other problems
Added:
>
>
    • 80000 - Internal error in CRAB job wrapper
 
    • 99109 - Uncaught exception in WMAgent step executor

Revision 712014-05-20 - BrianBockelman

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 171 to 171
 
    • 60411 - Timeout in deleting log files in log collection (WMAgent)
    • 60451 - Output file lacked adler32 checksum (WMAgent)
    • 60452 - No run/lumi information in file (WMAgent)
Added:
>
>
    • 60453 - Unable to determine pset hash from output file (CRAB3)
 
    • 60999 - SG $WORKING_DIR could not be deleted
    • 61101 - No sites are available to submit the job because the location of its input(s) do not pass the site whitelist/blacklist restrictions (WMAgent)
    • 61102 - The job can only run at a site that is currently in Aborted state (WMAgent)

Revision 702014-05-05 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 187 to 187
 
  • Other problems
    • 99109 - Uncaught exception in WMAgent step executor
Deleted:
<
<
META PREFERENCE name="ALLOWTOPICVIEW" title="ALLOWTOPICVIEW" type="Set" value="cms-web-access,cms-computing-web-access,cms-cern-it-web-access"

Revision 692014-04-30 - JamesLetts

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 138 to 138
 
    • 50999 - OSG $WORKING_DIR could not be deleted

  • Staging-OUT related troubles- range 60000-69999
Changed:
<
<
>
>
    • 60300 - Either OutputSE or OutputSE_DIR not defined
 
    • 60301 - Neither zip nor tar exists
    • 60302 - Output file(s) not found
    • 60303 - File already exists on the SE
Line: 152 to 152
 
    • ALERT! 60311 - Stage Out Failure in ProdAgent job
    • 60312 - Failed to get file TURL via lcg-lr command
    • 60313 - Failed to delete the output from the previous run via lcg-del command
Changed:
<
<
>
>
    • 60314 - Failed to invoke ProdAgent StageOut Script
    • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
 
    • 60316 - Failed to create a directory on the SE
    • 60317 - Forced timeout for stuck stage out
    • 60318 - Internal error in Crab cmscp.py stageout script
Line: 174 to 174
 
    • 60999 - SG $WORKING_DIR could not be deleted
    • 61101 - No sites are available to submit the job because the location of its input(s) do not pass the site whitelist/blacklist restrictions (WMAgent)
    • 61102 - The job can only run at a site that is currently in Aborted state (WMAgent)
Changed:
<
<
    • 61103 - The JobSubmitter component could not load the job pickle (WMAgent)
>
>
    • 61103 - The JobSubmitter component could not load the job pickle (WMAgent)
 
    • 61104 - The job can run only at a site that is currently in Draining state (WMAgent)
    • 61300 - The job was killed by the WMAgent, reason is unknown (WMAgent)
    • 61301 - The job was killed by the WMAgent because the site it was running at was set to Aborted (WMAgent)
Line: 183 to 183
 
  • Problems saving output via output sandbox- range 70000-70009
    • 70000 - Output_sandbox too big for WMS: output can not be retrieved
Changed:
<
<
>
>
    • 70500 - Warning: problem with ModifyJobReport
 
  • Other problems
    • 99109 - Uncaught exception in WMAgent step executor

Revision 682014-04-28 - JamesLetts

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 62 to 62
 
    • 7000 - Exception from command line processing
    • 7001 - Configuration File Not Found
    • 7002 - Configuration File Read Error
Changed:
<
<
    • 8001 = Other CMS Exception
    • 8002 = std::exception (other than bad_alloc)
    • 8003 = Unknown Exception
    • 8004 = std::bad_alloc (memory exhaustion)
    • 8005 = Bad Exception Type (e.g throwing a string)
>
>
    • 8001 - Other CMS Exception
    • 8002 - std::exception (other than bad_alloc)
    • 8003 - Unknown Exception
    • 8004 - std::bad_alloc (memory exhaustion)
    • 8005 - Bad Exception Type (e.g throwing a string)
 
    • // The rest are specific categories of CMS Exceptions.
Changed:
<
<
    • 8006 = ProductNotFound
    • 8007 = DictionaryNotFound
    • 8008 = InsertFailure
    • 8009 = Configuration
    • 8010 = LogicError
    • 8011 = UnimplementedFeature
    • 8012 = InvalidReference
    • 8013 = NullPointerError
    • 8014 = NoProductSpecified
    • 8015 = EventTimeout
    • 8016 = EventCorruption
    • 8017 = ScheduleExecutionFailure
    • 8018 = EventProcessorFailure
    • 8019 = FileInPathError
    • ALERT! 8020 = FileOpenError (Likely a site error)
    • ALERT! 8021 = FileReadError (May be a site error)
>
>
    • 8006 - ProductNotFound
    • 8007 - DictionaryNotFound
    • 8008 - InsertFailure
    • 8009 - Configuration
    • 8010 - LogicError
    • 8011 - UnimplementedFeature
    • 8012 - InvalidReference
    • 8013 - NullPointerError
    • 8014 - NoProductSpecified
    • 8015 - EventTimeout
    • 8016 - EventCorruption
    • 8017 - ScheduleExecutionFailure
    • 8018 - EventProcessorFailure
    • 8019 - FileInPathError
    • ALERT! 8020 - FileOpenError (Likely a site error)
    • ALERT! 8021 - FileReadError (May be a site error)
 
Changed:
<
<
    • 8022 = FatalRootError
    • 8023 = MismatchedInputFiles
    • 8024 = ProductDoesNotSupportViews
    • 8025 = ProductDoesNotSupportPtr
    • 8026 = NotFound (something other than a product or dictionary not found)
    • 8027 = FormatIncompatibility
    • ALERT! 8028 = FileOpenError with fallback
>
>
    • 8022 - FatalRootError
    • 8023 - MismatchedInputFiles
    • 8024 - ProductDoesNotSupportViews
    • 8025 - ProductDoesNotSupportPtr
    • 8026 - NotFound (something other than a product or dictionary not found)
    • 8027 - FormatIncompatibility
    • ALERT! 8028 - FileOpenError with fallback
 
  • ALERT! Failures related to the environment setup - range 10000-19999
    • ALERT! 10001 - LD_LIBRARY_PATH is not defined
    • ALERT! 10002 - Failed to setup LCG_LD_LIBRAR_PATH

Revision 672014-04-25 - JamesLetts

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 91 to 91
 
    • 8025 = ProductDoesNotSupportPtr
    • 8026 = NotFound (something other than a product or dictionary not found)
    • 8027 = FormatIncompatibility
Changed:
<
<
    • ALERT! 8028 FileOpenError with fallback
>
>
    • ALERT! 8028 = FileOpenError with fallback
 
  • ALERT! Failures related to the environment setup - range 10000-19999
    • ALERT! 10001 - LD_LIBRARY_PATH is not defined
    • ALERT! 10002 - Failed to setup LCG_LD_LIBRAR_PATH

Revision 662014-03-26 - OliverGutsche

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 187 to 187
 
  • Other problems
    • 99109 - Uncaught exception in WMAgent step executor
\ No newline at end of file
Added:
>
>
META PREFERENCE name="ALLOWTOPICVIEW" title="ALLOWTOPICVIEW" type="Set" value="cms-web-access,cms-computing-web-access,cms-cern-it-web-access"

Revision 652014-02-27 - AliMehmetAltundag

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 57 to 57
 
    • 2304 - nondefined
    • 0001 - Plug-in or message service initialization Exception
Changed:
<
<
  • cmsRun (CMSSW) exit codes. These codes may depend on specific CMSSW version, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
>
>
  • cmsRun (CMSSW) exit codes. These codes may depend on specific CMSSW version, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
 
    • // The first three are specific categories of CMS Exceptions.
    • 7000 - Exception from command line processing
    • 7001 - Configuration File Not Found

Revision 642013-12-13 - BrianBockelman

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 114 to 114
 
    • ALERT! 10040 - failed to generate cmsRun cfg file at runtime
    • ALERT! 10041 - fail to find valid client for output stage out
    • ALERT! 10042 - Unable to stage-in wrapper tarball.
Added:
>
>
    • ALERT! 10043 - Unable to bootstrap WMCore libraries (most likely site python is broken).
 
  • Executable file related failures - range 50000-59999
    • 50110 - Executable file is not found

Revision 632013-11-12 - BrianBockelman

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 113 to 113
 
    • ALERT! 10039 - cms_site_catalogue.sh failed to provide the catalogue
    • ALERT! 10040 - failed to generate cmsRun cfg file at runtime
    • ALERT! 10041 - fail to find valid client for output stage out
Added:
>
>
    • ALERT! 10042 - Unable to stage-in wrapper tarball.
 
  • Executable file related failures - range 50000-59999
    • 50110 - Executable file is not found

Revision 622013-11-11 - BrianBockelman

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 155 to 155
 
    • 60316 - Failed to create a directory on the SE
    • 60317 - Forced timeout for stuck stage out
    • 60318 - Internal error in Crab cmscp.py stageout script
Added:
>
>
    • 60319 - Failure to do asynchronous stageout
 
    • 60401 - Failure to assemble LFN in direct-to-merge by size (WMAgent)
    • 60402 - Failure to assemble LFN in direct-to-merge by event (WMAgent)
    • 60403 - Timeout during attempted file transfer - status unknown (WMAgent)

Revision 612013-10-29 - SeangchanRyu

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 167 to 167
 
    • 60410 - Failure in deleting log files in log collection (WMAgent)
    • 60411 - Timeout in deleting log files in log collection (WMAgent)
    • 60451 - Output file lacked adler32 checksum (WMAgent)
Added:
>
>
    • 60452 - No run/lumi information in file (WMAgent)
 
    • 60999 - SG $WORKING_DIR could not be deleted
Added:
>
>
    • 61101 - No sites are available to submit the job because the location of its input(s) do not pass the site whitelist/blacklist restrictions (WMAgent)
    • 61102 - The job can only run at a site that is currently in Aborted state (WMAgent)
    • 61103 - The JobSubmitter component could not load the job pickle (WMAgent)
    • 61104 - The job can run only at a site that is currently in Draining state (WMAgent)
    • 61300 - The job was killed by the WMAgent, reason is unknown (WMAgent)
    • 61301 - The job was killed by the WMAgent because the site it was running at was set to Aborted (WMAgent)
    • 61302 - The job was killed by the WMAgent because the site it was running at was set to Draining (WMAgent)
    • 61303 - The job was killed by the WMAgent because the site it was running at was set to Down (WMAgent)
 
  • Problems saving output via output sandbox- range 70000-70009
    • 70000 - Output_sandbox too big for WMS: output can not be retrieved

Revision 602013-08-06 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 131 to 131
 
    • 50664 - Application terminated by wrapper because using too much Wall Clock time
    • 50669 - Application terminated by wrapper for not defined reason
    • 50700 - Job Wrapper did not produce any usable output file
Added:
>
>
    • 50800 - Application segfaulted (likely user code problem)
 
    • 50998 - Problem calculating file details (i.e. size, checksum etc)
    • 50999 - OSG $WORKING_DIR could not be deleted

Revision 592012-12-05 - SaizSantosLola

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Line: 84 to 84
 
    • 8019 = FileInPathError
    • ALERT! 8020 = FileOpenError (Likely a site error)
    • ALERT! 8021 = FileReadError (May be a site error)
Added:
>
>
 
    • 8022 = FatalRootError
    • 8023 = MismatchedInputFiles
    • 8024 = ProductDoesNotSupportViews

Revision 582012-09-10 - AlisonMcCrea

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

Added:
>
>
 ALERT! indicates site error
Changed:
<
<
  • Error exit code of the cmsRun application itself - range 0-10000 (Exit codes in 1-512 are standard ones in Unix and indicate a CMSSW abort that the cmsRun did not catch as exception)
>
>
  • Error exit code of the cmsRun application itself - range 0-10000 (Exit codes in 1-512 are standard ones in Unix and indicate a CMSSW abort that the cmsRun did not catch as exception)
 
    • -1 - Error return without specification
    • 1 - Hangup (POSIX)
    • 2 - Interrupt (ANSI)
Line: 30 to 30
 
    • 67 - unknown
    • 68 - unknown
    • 73 - Failed writing to read-only file system
Added:
>
>
    • 84 - Some required file not found; check logs for name of missing file.
 
    • 88 - unknown
    • 90 - Application exception
    • 100 - nondefined
Line: 56 to 57
 
    • 2304 - nondefined
    • 0001 - Plug-in or message service initialization Exception

Changed:
<
<
  • cmsRun (CMSSW) exit codes. These codes may depend on specific CMSSW version, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
>
>
  • cmsRun (CMSSW) exit codes. These codes may depend on specific CMSSW version, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
 
    • // The first three are specific categories of CMS Exceptions.
    • 7000 - Exception from command line processing
    • 7001 - Configuration File Not Found

Revision 572012-08-23 - EricVaandering

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

ALERT! indicates site error
Line: 170 to 170
 
  • Problems saving output via output sandbox- range 70000-70009
    • 70000 - Output_sandbox too big for WMS: output can not be retrieved
    • 70500 - Warning: problem with ModifyJobReport
\ No newline at end of file
Added:
>
>
  • Other problems
    • 99109 - Uncaught exception in WMAgent step executor

Revision 562012-05-18 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

ALERT! indicates site error
Line: 129 to 129
 
    • 50663 - Application terminated by wrapper because using too much CPU time
    • 50664 - Application terminated by wrapper because using too much Wall Clock time
    • 50669 - Application terminated by wrapper for not defined reason
Added:
>
>
    • 50700 - Job Wrapper did not produce any usable output file
 
    • 50998 - Problem calculating file details (i.e. size, checksum etc)
    • 50999 - OSG $WORKING_DIR could not be deleted

Revision 552012-05-17 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

ALERT! indicates site error
Line: 121 to 121
 
    • 50114 - OSG $WORKING_DIR could not be deleted
    • 50115 - cmsRun did not produce a valid job report at runtime (often means cmsRun segfaulted)
    • 50116 - Could not determine exit code of cmsRun executable at runtime
Changed:
<
<
    • 50117 - Could not update exit code in job report
      • if you encounter this exit code while using the crab server then you have likely encountered a known crabserver bug.
        <!--* carefully check your crab_fjr file for the job that has this to make sure it isn't completely ok, and used while publishing with crab -publish.
        
      • in crab 273 crap -report does not count jobs with 50117 while crab -publish may publish the job if the fjr is ok. This thus may lead to inconsistencies. -->
>
>
    • 50117 - Could not update exit code in job report (a variation of 50115)
 
    • 50513 - Failure to run SCRAM setup scripts
    • 50660 - Application terminated by wrapper because using too much RAM (RSS)
    • 50661 - Application terminated by wrapper because using too much Virtual Memory (VSIZE)

Revision 542012-04-23 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

ALERT! indicates site error
Line: 131 to 131
 
    • 50662 - Application terminated by wrapper because using too much disk
    • 50663 - Application terminated by wrapper because using too much CPU time
    • 50664 - Application terminated by wrapper because using too much Wall Clock time
Changed:
<
<
    • 50666 - Application terminated by wrapper for not defined reason
>
>
    • 50669 - Application terminated by wrapper for not defined reason
 
    • 50998 - Problem calculating file details (i.e. size, checksum etc)
    • 50999 - OSG $WORKING_DIR could not be deleted

Revision 532012-04-23 - StefanoBelforte

Line: 1 to 1
 
META TOPICPARENT name="Dashboard"

Error codes currently sent from CMS jobs to the dashboard

ALERT! indicates site error
Line: 126 to 126
 
<!--* carefully check your crab_fjr file for the job that has this to make sure it isn't completely ok, and used while publishing with crab -publish. 
      • in crab 273 crap -report does not count jobs with 50117 while crab -publish may publish the job if the fjr is ok. This thus may lead to inconsistencies. -->
  • 50513 - Failure to run SCRAM setup scripts
  • Added:
    >
    >
      • 50660 - Application terminated by wrapper because using too much RAM (RSS)
      • 50661 - Application terminated by wrapper because using too much Virtual Memory (VSIZE)
      • 50662 - Application terminated by wrapper because using too much disk
      • 50663 - Application terminated by wrapper because using too much CPU time
      • 50664 - Application terminated by wrapper because using too much Wall Clock time
      • 50666 - Application terminated by wrapper for not defined reason
     
      • 50998 - Problem calculating file details (i.e. size, checksum etc)
      • 50999 - OSG $WORKING_DIR could not be deleted

    Revision 522012-03-08 - FedericaFanzago

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard

    ALERT! indicates site error
    Line: 123 to 123
     
      • 50116 - Could not determine exit code of cmsRun executable at runtime
      • 50117 - Could not update exit code in job report
        • if you encounter this exit code while using the crab server then you have likely encountered a known crabserver bug.
    Changed:
    <
    <
        • carefully check your crab_fjr file for the job that has this to make sure it isn't completely ok, and used while publishing with crab -publish.
        • in crab 273 crap -report does not count jobs with 50117 while crab -publish may publish the job if the fjr is ok. This thus may lead to inconsistencies.
    >
    >
    <!--* carefully check your crab_fjr file for the job that has this to make sure it isn't completely ok, and used while publishing with crab -publish. 
        • in crab 273 crap -report does not count jobs with 50117 while crab -publish may publish the job if the fjr is ok. This thus may lead to inconsistencies. -->
     
      • 50513 - Failure to run SCRAM setup scripts
      • 50998 - Problem calculating file details (i.e. size, checksum etc)
      • 50999 - OSG $WORKING_DIR could not be deleted

    Revision 512012-02-14 - JuliaAndreeva

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard

    ALERT! indicates site error
    Line: 82 to 82
     
      • 8017 = ScheduleExecutionFailure
      • 8018 = EventProcessorFailure
      • 8019 = FileInPathError
    Changed:
    <
    <
      • 8020 = FileOpenError (Likely a site error)
      • 8021 = FileReadError (May be a site error)
    >
    >
      • ALERT! 8020 = FileOpenError (Likely a site error)
      • ALERT! 8021 = FileReadError (May be a site error)
     
      • 8022 = FatalRootError
      • 8023 = MismatchedInputFiles
      • 8024 = ProductDoesNotSupportViews
      • 8025 = ProductDoesNotSupportPtr
      • 8026 = NotFound (something other than a product or dictionary not found)
      • 8027 = FormatIncompatibility
    Added:
    >
    >
      • ALERT! 8028 FileOpenError with fallback
     
    • ALERT! Failures related to the environment setup - range 10000-19999
      • ALERT! 10001 - LD_LIBRARY_PATH is not defined
      • ALERT! 10002 - Failed to setup LCG_LD_LIBRAR_PATH

    Revision 502011-10-17 - WilliamTanenbaum

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard

    ALERT! indicates site error
    Line: 55 to 55
     
      • 512 - nondefined
      • 2304 - nondefined
      • 0001 - Plug-in or message service initialization Exception
    Deleted:
    <
    <
      • 7000 - Exception from command line processing
      • 7001 - Config File Not Found
      • 7002 - Config File Read Error
     
    • cmsRun (CMSSW) exit codes.
    Changed:
    <
    <
    These codes may depend on specific CMSSW version, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 2_0_x is below
    >
    >
    These codes may depend on specific CMSSW version, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 5_0_X is below
      • // The first three are specific categories of CMS Exceptions.
      • 7000 - Exception from command line processing
      • 7001 - Configuration File Not Found
      • 7002 - Configuration File Read Error
     
      • 8001 = Other CMS Exception
    Changed:
    <
    <
      • 8002 = std::exception
    >
    >
      • 8002 = std::exception (other than bad_alloc)
     
      • 8003 = Unknown Exception
      • 8004 = std::bad_alloc (memory exhaustion)
      • 8005 = Bad Exception Type (e.g throwing a string)
    Line: 89 to 89
     
      • 8024 = ProductDoesNotSupportViews
      • 8025 = ProductDoesNotSupportPtr
      • 8026 = NotFound (something other than a product or dictionary not found)
    Added:
    >
    >
      • 8027 = FormatIncompatibility
     
    • ALERT! Failures related to the environment setup - range 10000-19999
      • ALERT! 10001 - LD_LIBRARY_PATH is not defined
      • ALERT! 10002 - Failed to setup LCG_LD_LIBRAR_PATH

    Revision 492011-09-30 - unknown

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard

    ALERT! indicates site error
    Line: 123 to 123
     
        • if you encounter this exit code while using the crab server then you have likely encountered a known crabserver bug.
        • carefully check your crab_fjr file for the job that has this to make sure it isn't completely ok, and used while publishing with crab -publish.
        • in crab 273 crap -report does not count jobs with 50117 while crab -publish may publish the job if the fjr is ok. This thus may lead to inconsistencies.
    Added:
    >
    >
      • 50513 - Failure to run SCRAM setup scripts
     
      • 50998 - Problem calculating file details (i.e. size, checksum etc)
      • 50999 - OSG $WORKING_DIR could not be deleted

    Revision 482011-08-19 - unknown

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard

    ALERT! indicates site error
    Line: 157 to 157
     
      • 60409 - Timeout in stage out of log files during log collection (WMAgent)
      • 60410 - Failure in deleting log files in log collection (WMAgent)
      • 60411 - Timeout in deleting log files in log collection (WMAgent)
    Added:
    >
    >
      • 60451 - Output file lacked adler32 checksum (WMAgent)
     
      • 60999 - SG $WORKING_DIR could not be deleted

    • Problems saving output via output sandbox- range 70000-70009

    Revision 472011-03-28 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard

    ALERT! indicates site error
    Line: 144 to 144
     
      • 60314 - Failed to invoke ProdAgent StageOut Script
      • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
      • 60316 - Failed to create a directory on the SE
    Changed:
    <
    <
      • 60317 - Forced timeout for stuck stage out.
    >
    >
      • 60317 - Forced timeout for stuck stage out
      • 60318 - Internal error in Crab cmscp.py stageout script
     
      • 60401 - Failure to assemble LFN in direct-to-merge by size (WMAgent)
      • 60402 - Failure to assemble LFN in direct-to-merge by event (WMAgent)
      • 60403 - Timeout during attempted file transfer - status unknown (WMAgent)

    Revision 462011-03-16 - MattiaCinquilli

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard

    ALERT! indicates site error
    Line: 145 to 145
     
      • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
      • 60316 - Failed to create a directory on the SE
      • 60317 - Forced timeout for stuck stage out.
    Changed:
    <
    <
      • The following are for the WMAgent:
      • 60401 - Failure to assemble LFN in direct-to-merge by size
      • 60402 - Failure to assemble LFN in direct-to-merge by event
      • 60403 - Timeout during attempted file transfer - status unknown
      • 60404 - Timeout during staging of log archives - status unknown
      • 60405 - General failure to stage out log archives
      • 60406 - Failure in staging in log files during log collection
      • 60407 - Timeout in staging in log files during log collection
      • 60408 - Failure to stage out of log files during log collection
      • 60409 - Timeout in stage out of log files during log collection
      • 60410 - Failure in deleting log files in log collection
      • 60411 - Timeout in deleting log files in log collection
    >
    >
      • 60401 - Failure to assemble LFN in direct-to-merge by size (WMAgent)
      • 60402 - Failure to assemble LFN in direct-to-merge by event (WMAgent)
      • 60403 - Timeout during attempted file transfer - status unknown (WMAgent)
      • 60404 - Timeout during staging of log archives - status unknown (WMAgent)
      • 60405 - General failure to stage out log archives (WMAgent)
      • 60406 - Failure in staging in log files during log collection (WMAgent)
      • 60407 - Timeout in staging in log files during log collection (WMAgent)
      • 60408 - Failure to stage out of log files during log collection (WMAgent)
      • 60409 - Timeout in stage out of log files during log collection (WMAgent)
      • 60410 - Failure in deleting log files in log collection (WMAgent)
      • 60411 - Timeout in deleting log files in log collection (WMAgent)
     
      • 60999 - SG $WORKING_DIR could not be deleted

    • Problems saving output via output sandbox- range 70000-70009

    Revision 452011-03-16 - unknown

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard

    ALERT! indicates site error
    Line: 145 to 145
     
      • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
      • 60316 - Failed to create a directory on the SE
      • 60317 - Forced timeout for stuck stage out.
    Added:
    >
    >
      • The following are for the WMAgent:
      • 60401 - Failure to assemble LFN in direct-to-merge by size
      • 60402 - Failure to assemble LFN in direct-to-merge by event
      • 60403 - Timeout during attempted file transfer - status unknown
      • 60404 - Timeout during staging of log archives - status unknown
      • 60405 - General failure to stage out log archives
      • 60406 - Failure in staging in log files during log collection
      • 60407 - Timeout in staging in log files during log collection
      • 60408 - Failure to stage out of log files during log collection
      • 60409 - Timeout in stage out of log files during log collection
      • 60410 - Failure in deleting log files in log collection
      • 60411 - Timeout in deleting log files in log collection
     
      • 60999 - SG $WORKING_DIR could not be deleted

    • Problems saving output via output sandbox- range 70000-70009

    Revision 442011-03-16 - MattiaCinquilli

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"
    Changed:
    <
    <

    Error codes currently sent from CMS jobs to the dashboard via CRAB

    >
    >

    Error codes currently sent from CMS jobs to the dashboard

     ALERT! indicates site error

    • Error exit code of the cmsRun application itself - range 0-10000

    Revision 432011-02-18 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via CRAB

    ALERT! indicates site error
    Line: 117 to 117
     
      • 50112 - User executable shell file is not found
      • 50113 - Executable did not get enough arguments
      • 50114 - OSG $WORKING_DIR could not be deleted
    Changed:
    <
    <
      • 50115 - cmsRun did not produce a valid/readable job report at runtime
    >
    >
      • 50115 - cmsRun did not produce a valid job report at runtime (often means cmsRun segfaulted)
     
      • 50116 - Could not determine exit code of cmsRun executable at runtime
      • 50117 - Could not update exit code in job report
        • if you encounter this exit code while using the crab server then you have likely encountered a known crabserver bug.
    Line: 134 to 134
     
      • 60304 - Failed to create the summary file (production)
      • 60305 - Failed to create a zipped archive (production)
      • 60306 - Failed to copy and register output file
    Changed:
    <
    <
      • 60307 - Failed to copy an output file to the SE (sometimes caused by timeout issue).
    >
    >
      • 60307 - Failed to copy an output file to the SE (sometimes caused by timeout issue).
     
      • 60308 - An output file was saved to fall back local SE after failing to copy to remote SE
      • 60309 - Failed to create an output directory in the catalogue
      • 60310 - Failed to register an output file in the catalogue

    Revision 422010-09-23 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"
    Changed:
    <
    <

    Error codes currently sent from CMS jobs to the dashboard via ML

    >
    >

    Error codes currently sent from CMS jobs to the dashboard via CRAB

     ALERT! indicates site error

    • Error exit code of the cmsRun application itself - range 0-10000
    Changed:
    <
    <
    (Exit codes in 1-512 are standard ones in Unix and indicate a CMSSW abort that the cmsRun did not catch as exception)
    >
    >
    (Exit codes in 1-512 are standard ones in Unix and indicate a CMSSW abort that the cmsRun did not catch as exception)
     
      • -1 - Error return without specification
      • 1 - Hangup (POSIX)
      • 2 - Interrupt (ANSI)
    Line: 58 to 58
     
      • 7000 - Exception from command line processing
      • 7001 - Config File Not Found
      • 7002 - Config File Read Error
    Changed:
    <
    <
      • 8000 - SEAL Exception (obsolete)
      • 8001 - CMS Exception
      • 8002 - std Exception
      • 8003 - Unknown Exception
      • 8004 - std::bad_alloc exception (memory exhaustion)
    • new since CMSSW 2_0_10. These codes depend on specific CMSSW, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 2_0_x is below
    >
    >

    • cmsRun (CMSSW) exit codes. These codes may depend on specific CMSSW version, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 2_0_x is below
     
      • 8001 = Other CMS Exception
      • 8002 = std::exception
      • 8003 = Unknown Exception
    Line: 94 to 92
     
    • ALERT! Failures related to the environment setup - range 10000-19999
      • ALERT! 10001 - LD_LIBRARY_PATH is not defined
      • ALERT! 10002 - Failed to setup LCG_LD_LIBRAR_PATH
    Deleted:
    <
    <
      • 10004 - DAR environment setup script is not found obsolete
      • 10005 - DAR environment setup script failed obsolete
     
      • ALERT! 10016 - OSG $WORKING_DIR could not be created
      • ALERT! 10017 - OSG $WORKING_DIR could not be deleted
      • ALERT! 10018 - OSG $WORKING_DIR could not be deleted
    Line: 115 to 111
     
      • ALERT! 10040 - failed to generate cmsRun cfg file at runtime
      • ALERT! 10041 - fail to find valid client for output stage out
    Deleted:
    <
    <
    • Problems related to copying of files different from data files to the worker node - range 20000-29999
      • 20001 - Failed to copy PubDB catalogue to the worker node obsolete
      • 20002 - Failed to copy DAR distribution to the worker node obsolete
      • 20070 - lcg-lr failed obsolete
      • 20071 - lcg-cp failed obsolete

    • ALERT! Input file(s) related failures - range 30000-39999
      • ALERT! 30001 - Fail to read input file(s)
      • 30100 - Staging.sh file is not found (production only) obsolete
      • 31100 - Failed to stage in input file to the local disk (production only) obsolete
      • 30301 - StageInFiles:Neither zip nor tar are found obsolete
      • 30303 - StageInFiles:failed to uncompress the archive obsolete

    • Cobra/POOL related failures- range 40000-49999 OBSOLETE
      • 40101 - FCpublish command failed
      • 40103 - PU catalog not found
      • 40104 - Attachment failed
      • 40105 - FixColl failed
      • 40500 - FCrenamePFN failed"
      • 41030 - Problems renaming pfns of PU META files
      • 41031 - Problems merging the PU Catalog
     
    • Executable file related failures - range 50000-59999
      • 50110 - Executable file is not found
      • 50111 - Executable file has no exe permissions

    Revision 412010-08-25 - StephenJGowdy

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 19 to 19
     
      • 11 - segmentation violation (ANSI)
      • 12 - User defined
      • 15 - Termination (ANSI)
    Added:
    >
    >
      • 24 - Soft CPU limit exceeded (4.2 BSD)
     
      • 25 - File size limit exceeded (4.2 BSD)
      • 29 - nondefined
      • 30 - Power failure restart (System V.)

    Revision 402010-07-18 - FrankWuerthwein

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 145 to 145
     
      • 50115 - cmsRun did not produce a valid/readable job report at runtime
      • 50116 - Could not determine exit code of cmsRun executable at runtime
      • 50117 - Could not update exit code in job report
    Added:
    >
    >
        • if you encounter this exit code while using the crab server then you have likely encountered a known crabserver bug.
        • carefully check your crab_fjr file for the job that has this to make sure it isn't completely ok, and used while publishing with crab -publish.
        • in crab 273 crap -report does not count jobs with 50117 while crab -publish may publish the job if the fjr is ok. This thus may lead to inconsistencies.
     
      • 50998 - Problem calculating file details (i.e. size, checksum etc)
      • 50999 - OSG $WORKING_DIR could not be deleted

    Revision 392010-05-07 - MattiaCinquilli

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 166 to 166
     
      • 60314 - Failed to invoke ProdAgent StageOut Script
      • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
      • 60316 - Failed to create a directory on the SE
    Added:
    >
    >
      • 60317 - Forced timeout for stuck stage out.
     
      • 60999 - SG $WORKING_DIR could not be deleted

    • Problems saving output via output sandbox- range 70000-70009

    Revision 382009-11-24 - IRTomalin

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 156 to 156
     
      • 60304 - Failed to create the summary file (production)
      • 60305 - Failed to create a zipped archive (production)
      • 60306 - Failed to copy and register output file
    Changed:
    <
    <
      • 60307 - Failed to copy an output file to the SE
    >
    >
      • 60307 - Failed to copy an output file to the SE (sometimes caused by timeout issue).
     
      • 60308 - An output file was saved to fall back local SE after failing to copy to remote SE
      • 60309 - Failed to create an output directory in the catalogue
      • 60310 - Failed to register an output file in the catalogue

    Revision 372009-10-28 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 157 to 157
     
      • 60305 - Failed to create a zipped archive (production)
      • 60306 - Failed to copy and register output file
      • 60307 - Failed to copy an output file to the SE
    Added:
    >
    >
      • 60308 - An output file was saved to fall back local SE after failing to copy to remote SE
     
      • 60309 - Failed to create an output directory in the catalogue
      • 60310 - Failed to register an output file in the catalogue
      • ALERT! 60311 - Stage Out Failure in ProdAgent job

    Revision 362009-10-13 - PatrickGartung

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 28 to 28
     
      • 66 - Application exception
      • 67 - unknown
      • 68 - unknown
    Added:
    >
    >
      • 73 - Failed writing to read-only file system
     
      • 88 - unknown
      • 90 - Application exception
      • 100 - nondefined

    Revision 352009-08-04 - StuartWakefield

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 144 to 144
     
      • 50115 - cmsRun did not produce a valid/readable job report at runtime
      • 50116 - Could not determine exit code of cmsRun executable at runtime
      • 50117 - Could not update exit code in job report
    Added:
    >
    >
      • 50998 - Problem calculating file details (i.e. size, checksum etc)
     
      • 50999 - OSG $WORKING_DIR could not be deleted

    • Staging-OUT related troubles- range 60000-69999

    Revision 342009-07-02 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 106 to 106
     
      • ALERT! 10033 - Platform is incompatible with the scram version
      • ALERT! 10034 - Required application version is not found at the site
      • ALERT! 10035 - Scram Project Command Failed
    Changed:
    <
    <
      • ALERT! 10036 - Scram Runtime Command Failed in ProdAgent production job
    >
    >
      • ALERT! 10036 - Scram Runtime Command Failed
     
      • ALERT! 10037 - Failed to find cms_site_config file in software area
      • ALERT! 10038 - Failed to find cms_site_catalogue.sh file in software area
      • ALERT! 10039 - cms_site_catalogue.sh failed to provide the catalogue
      • ALERT! 10040 - failed to generate cmsRun cfg file at runtime
    Changed:
    <
    <
      • 10041 - fail to find valid client for output stage out
    >
    >
      • ALERT! 10041 - fail to find valid client for output stage out
     
    • Problems related to copying of files different from data files to the worker node - range 20000-29999
      • 20001 - Failed to copy PubDB catalogue to the worker node obsolete

    Revision 332009-07-02 - SpigaDaniele

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 105 to 105
     
      • ALERT! 10032 - Failed to source CMS Environment setup script such as cmssset_default.sh, grid system or site equivalent script
      • ALERT! 10033 - Platform is incompatible with the scram version
      • ALERT! 10034 - Required application version is not found at the site
    Changed:
    <
    <
      • ALERT! 10035 - Scram Project Command Failed in ProdAgent production job
    >
    >
      • ALERT! 10035 - Scram Project Command Failed
     
      • ALERT! 10036 - Scram Runtime Command Failed in ProdAgent production job
      • ALERT! 10037 - Failed to find cms_site_config file in software area
      • ALERT! 10038 - Failed to find cms_site_catalogue.sh file in software area

    Revision 322009-04-30 - MarcoCalloni

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 62 to 62
     
      • 8003 - Unknown Exception
      • 8004 - std::bad_alloc exception (memory exhaustion)
    • new since CMSSW 2_0_10. These codes depend on specific CMSSW, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 2_0_x is below
    Changed:
    <
    <
      • Other CMS Exception = 8001,
      • std::exception = 8002,
      • Unknown Exception = 8003,
      • std::bad_alloc = 8004, (memory exhaustion)
      • Bad Exception Type = 8005, (e.g throwing a string)
    >
    >
      • 8001 = Other CMS Exception
      • 8002 = std::exception
      • 8003 = Unknown Exception
      • 8004 = std::bad_alloc (memory exhaustion)
      • 8005 = Bad Exception Type (e.g throwing a string)
     
      • // The rest are specific categories of CMS Exceptions.
    Changed:
    <
    <
      • ProductNotFound = 8006,
      • DictionaryNotFound = 8007,
      • InsertFailure = 8008,
      • Configuration = 8009,
      • LogicError = 8010,
      • UnimplementedFeature = 8011,
      • InvalidReference = 8012,
      • NullPointerError = 8013,
      • NoProductSpecified = 8014,
      • EventTimeout = 8015,
      • EventCorruption = 8016,
      • ScheduleExecutionFailure = 8017,
      • EventProcessorFailure = 8018,
      • FileInPathError = 8019,
      • ALERT! FileOpenError = 8020, (Likely a site error)
      • ALERT! FileReadError = 8021, (May be a site error)
      • FatalRootError = 8022,
      • MismatchedInputFiles = 8023,
      • ProductDoesNotSupportViews = 8024,
      • ProductDoesNotSupportPtr = 8025,
      • NotFound = 8026 (something other than a product or dictionary not found)
    >
    >
      • 8006 = ProductNotFound
      • 8007 = DictionaryNotFound
      • 8008 = InsertFailure
      • 8009 = Configuration
      • 8010 = LogicError
      • 8011 = UnimplementedFeature
      • 8012 = InvalidReference
      • 8013 = NullPointerError
      • 8014 = NoProductSpecified
      • 8015 = EventTimeout
      • 8016 = EventCorruption
      • 8017 = ScheduleExecutionFailure
      • 8018 = EventProcessorFailure
      • 8019 = FileInPathError
      • 8020 = FileOpenError (Likely a site error)
      • 8021 = FileReadError (May be a site error)
      • 8022 = FatalRootError
      • 8023 = MismatchedInputFiles
      • 8024 = ProductDoesNotSupportViews
      • 8025 = ProductDoesNotSupportPtr
      • 8026 = NotFound (something other than a product or dictionary not found)
     
    • ALERT! Failures related to the environment setup - range 10000-19999
      • ALERT! 10001 - LD_LIBRARY_PATH is not defined
      • ALERT! 10002 - Failed to setup LCG_LD_LIBRAR_PATH

    Revision 312009-04-23 - MattiaCinquilli

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 112 to 112
     
      • ALERT! 10038 - Failed to find cms_site_catalogue.sh file in software area
      • ALERT! 10039 - cms_site_catalogue.sh failed to provide the catalogue
      • ALERT! 10040 - failed to generate cmsRun cfg file at runtime
    Changed:
    <
    <
    >
    >
      • 10041 - fail to find valid client for output stage out
     
    • Problems related to copying of files different from data files to the worker node - range 20000-29999
      • 20001 - Failed to copy PubDB catalogue to the worker node obsolete

    Revision 302009-03-19 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 62 to 62
     
      • 8003 - Unknown Exception
      • 8004 - std::bad_alloc exception (memory exhaustion)
    • new since CMSSW 2_0_10. These codes depend on specific CMSSW, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 2_0_x is below
    Changed:
    <
    <
      • ALERT! Other CMS Exception = 8001,
    >
    >
      • Other CMS Exception = 8001,
     
      • std::exception = 8002,
      • Unknown Exception = 8003,
      • std::bad_alloc = 8004, (memory exhaustion)

    Revision 292009-03-19 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 62 to 62
     
      • 8003 - Unknown Exception
      • 8004 - std::bad_alloc exception (memory exhaustion)
    • new since CMSSW 2_0_10. These codes depend on specific CMSSW, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 2_0_x is below
    Changed:
    <
    <
      • Other CMS Exception = 8001,
    >
    >
      • ALERT! Other CMS Exception = 8001,
     
      • std::exception = 8002,
      • Unknown Exception = 8003,
      • std::bad_alloc = 8004, (memory exhaustion)

    Revision 282009-03-09 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error

    • Error exit code of the cmsRun application itself - range 0-10000
    Added:
    >
    >
    (Exit codes in 1-512 are standard ones in Unix and indicate a CMSSW abort that the cmsRun did not catch as exception)
     
      • -1 - Error return without specification
      • 1 - Hangup (POSIX)
      • 2 - Interrupt (ANSI)
    Line: 60 to 61
     
      • 8002 - std Exception
      • 8003 - Unknown Exception
      • 8004 - std::bad_alloc exception (memory exhaustion)
    Changed:
    <
    <
    • new since CMSSW 2_0_10
    >
    >
    • new since CMSSW 2_0_10. These codes depend on specific CMSSW, the list is maintained in CVS and you should look at tags there to find out what is appropriate for a given CMSSW release. The situation as of 2_0_x is below
     
      • Other CMS Exception = 8001,
      • std::exception = 8002,
      • Unknown Exception = 8003,

    Revision 272009-01-29 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 56 to 56
     
      • 7001 - Config File Not Found
      • 7002 - Config File Read Error
      • 8000 - SEAL Exception (obsolete)
    Changed:
    <
    <
      • ALERT! 8001 - CMS Exception
    >
    >
      • 8001 - CMS Exception
     
      • 8002 - std Exception
      • 8003 - Unknown Exception
      • 8004 - std::bad_alloc exception (memory exhaustion)
    Line: 81 to 81
     
      • ScheduleExecutionFailure = 8017,
      • EventProcessorFailure = 8018,
      • FileInPathError = 8019,
    Changed:
    <
    <
      • FileOpenError = 8020, (Likely a site error)
      • FileReadError = 8021, (May be a site error)
    >
    >
      • ALERT! FileOpenError = 8020, (Likely a site error)
      • ALERT! FileReadError = 8021, (May be a site error)
     
      • FatalRootError = 8022,
      • MismatchedInputFiles = 8023,
      • ProductDoesNotSupportViews = 8024,

    Revision 262009-01-18 - SpigaDaniele

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 155 to 155
     
      • 60305 - Failed to create a zipped archive (production)
      • 60306 - Failed to copy and register output file
      • 60307 - Failed to copy an output file to the SE
    Deleted:
    <
    <
      • 60308 - Failed to create a directory on the SE with gsiftp command
     
      • 60309 - Failed to create an output directory in the catalogue
      • 60310 - Failed to register an output file in the catalogue
      • ALERT! 60311 - Stage Out Failure in ProdAgent job
    Line: 163 to 162
     
      • 60313 - Failed to delete the output from the previous run via lcg-del command
      • 60314 - Failed to invoke ProdAgent StageOut Script
      • ALERT! 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
    Added:
    >
    >
      • 60316 - Failed to create a directory on the SE
     
      • 60999 - SG $WORKING_DIR could not be deleted

    • Problems saving output via output sandbox- range 70000-70009

    Revision 252009-01-14 - WilliamTanenbaum

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 67 to 67
     
      • std::bad_alloc = 8004, (memory exhaustion)
      • Bad Exception Type = 8005, (e.g throwing a string)
      • // The rest are specific categories of CMS Exceptions.
    Changed:
    <
    <
    >
    >
      • ProductNotFound = 8006,
      • DictionaryNotFound = 8007,
      • InsertFailure = 8008,
      • Configuration = 8009,
      • LogicError = 8010,
      • UnimplementedFeature = 8011,
      • InvalidReference = 8012,
      • NullPointerError = 8013,
      • NoProductSpecified = 8014,
      • EventTimeout = 8015,
      • EventCorruption = 8016,
      • ScheduleExecutionFailure = 8017,
      • EventProcessorFailure = 8018,
      • FileInPathError = 8019,
      • FileOpenError = 8020, (Likely a site error)
      • FileReadError = 8021, (May be a site error)
      • FatalRootError = 8022,
      • MismatchedInputFiles = 8023,
      • ProductDoesNotSupportViews = 8024,
      • ProductDoesNotSupportPtr = 8025,
      • NotFound = 8026 (something other than a product or dictionary not found)
     
    • ALERT! Failures related to the environment setup - range 10000-19999
      • ALERT! 10001 - LD_LIBRARY_PATH is not defined

    Revision 242009-01-14 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 60 to 60
     
      • 8002 - std Exception
      • 8003 - Unknown Exception
      • 8004 - std::bad_alloc exception (memory exhaustion)
    Changed:
    <
    <
    >
    >
     
    • ALERT! Failures related to the environment setup - range 10000-19999
      • ALERT! 10001 - LD_LIBRARY_PATH is not defined

    Revision 232008-05-06 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    ALERT! indicates site error
    Line: 132 to 132
     
      • 60308 - Failed to create a directory on the SE with gsiftp command
      • 60309 - Failed to create an output directory in the catalogue
      • 60310 - Failed to register an output file in the catalogue
    Changed:
    <
    <
    >
    >
     
      • 60312 - Failed to get file TURL via lcg-lr command
      • 60313 - Failed to delete the output from the previous run via lcg-del command
      • 60314 - Failed to invoke ProdAgent StageOut Script
    Changed:
    <
    <
    >
    >
     
      • 60999 - SG $WORKING_DIR could not be deleted

    • Problems saving output via output sandbox- range 70000-70009

    Revision 222008-04-28 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Added:
    >
    >
    ALERT! indicates site error
     
    • Error exit code of the cmsRun application itself - range 0-10000
      • -1 - Error return without specification
    Line: 55 to 56
     
      • 7001 - Config File Not Found
      • 7002 - Config File Read Error
      • 8000 - SEAL Exception (obsolete)
    Changed:
    <
    <
      • 8001 - CMS Exception
    >
    >
      • ALERT! 8001 - CMS Exception
     
      • 8002 - std Exception
      • 8003 - Unknown Exception
      • 8004 - std::bad_alloc exception (memory exhaustion)

    Changed:
    <
    <
    • Failures related to the environment setup - range 10000-19999
      • 10001 - LD_LIBRARY_PATH is not defined
      • 10002 - Failed to setup LCG_LD_LIBRAR_PATH
      • 10004 - DAR environment setup script is not found
      • 10005 - DAR environment setup script failed
      • 10016 - OSG $WORKING_DIR could not be created
      • 10017 - OSG $WORKING_DIR could not be deleted
      • 10018 - OSG $WORKING_DIR could not be deleted
      • 10020 - Shell script cmsset_default.sh to setup cms environment is not found
      • 10021 - Failed to scram application project using the afs release area
      • 10022 - Failed to scram application project using CMS sw disribution on the LCG2
      • 10030 - middleware not identified
      • 10031 - Directory VO_CMS_SW_DIR not found
      • 10032 - Failed to source CMS Environment setup script such as cmssset_default.sh, grid system or site equivalent script
      • 10033 - Platform is incompatible with the scram version
      • 10034 - Required application version is not found at the site
      • 10035 - Scram Project Command Failed in ProdAgent production job
      • 10036 - Scram Runtime Command Failed in ProdAgent production job
      • 10037 - Failed to find cms_site_config file in software area
      • 10038 - Failed to find cms_site_catalogue.sh file in software area
      • 10039 - cms_site_catalogue.sh failed to provide the catalogue
      • 10040 - failed to generate cmsRun cfg file at runtime
    >
    >
    • ALERT! Failures related to the environment setup - range 10000-19999
      • ALERT! 10001 - LD_LIBRARY_PATH is not defined
      • ALERT! 10002 - Failed to setup LCG_LD_LIBRAR_PATH
      • 10004 - DAR environment setup script is not found obsolete
      • 10005 - DAR environment setup script failed obsolete
      • ALERT! 10016 - OSG $WORKING_DIR could not be created
      • ALERT! 10017 - OSG $WORKING_DIR could not be deleted
      • ALERT! 10018 - OSG $WORKING_DIR could not be deleted
      • ALERT! 10020 - Shell script cmsset_default.sh to setup cms environment is not found
      • ALERT! 10021 - Failed to scram application project using the afs release area
      • ALERT! 10022 - Failed to scram application project using CMS sw disribution on the LCG2
      • ALERT! 10030 - middleware not identified
      • ALERT! 10031 - Directory VO_CMS_SW_DIR not found
      • ALERT! 10032 - Failed to source CMS Environment setup script such as cmssset_default.sh, grid system or site equivalent script
      • ALERT! 10033 - Platform is incompatible with the scram version
      • ALERT! 10034 - Required application version is not found at the site
      • ALERT! 10035 - Scram Project Command Failed in ProdAgent production job
      • ALERT! 10036 - Scram Runtime Command Failed in ProdAgent production job
      • ALERT! 10037 - Failed to find cms_site_config file in software area
      • ALERT! 10038 - Failed to find cms_site_catalogue.sh file in software area
      • ALERT! 10039 - cms_site_catalogue.sh failed to provide the catalogue
      • ALERT! 10040 - failed to generate cmsRun cfg file at runtime
     

    • Problems related to copying of files different from data files to the worker node - range 20000-29999
    Changed:
    <
    <
      • 20001 - Failed to copy PubDB catalogue to the worker node
      • 20002 - Failed to copy DAR distribution to the worker node
      • 20070 - lcg-lr failed
      • 20071 - lcg-cp failed
    >
    >
      • 20001 - Failed to copy PubDB catalogue to the worker node obsolete
      • 20002 - Failed to copy DAR distribution to the worker node obsolete
      • 20070 - lcg-lr failed obsolete
      • 20071 - lcg-cp failed obsolete
     
    Changed:
    <
    <
    • Input file(s) related failures - range 30000-39999
      • 30001 - Fail to read input file(s)
    >
    >
    • ALERT! Input file(s) related failures - range 30000-39999
      • ALERT! 30001 - Fail to read input file(s)
     
      • 30100 - Staging.sh file is not found (production only) obsolete
      • 31100 - Failed to stage in input file to the local disk (production only) obsolete
      • 30301 - StageInFiles:Neither zip nor tar are found obsolete

    Revision 212008-04-18 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 67 to 67
     
      • 10002 - Failed to setup LCG_LD_LIBRAR_PATH
      • 10004 - DAR environment setup script is not found
      • 10005 - DAR environment setup script failed
    Added:
    >
    >
      • 10016 - OSG $WORKING_DIR could not be created
      • 10017 - OSG $WORKING_DIR could not be deleted
      • 10018 - OSG $WORKING_DIR could not be deleted
     
      • 10020 - Shell script cmsset_default.sh to setup cms environment is not found
      • 10021 - Failed to scram application project using the afs release area
      • 10022 - Failed to scram application project using CMS sw disribution on the LCG2
    Changed:
    <
    <
      • 10030 - VO_CMS_SW_DIR is not defined
    >
    >
      • 10030 - middleware not identified
     
      • 10031 - Directory VO_CMS_SW_DIR not found
      • 10032 - Failed to source CMS Environment setup script such as cmssset_default.sh, grid system or site equivalent script
      • 10033 - Platform is incompatible with the scram version
    Line: 109 to 112
     
      • 50110 - Executable file is not found
      • 50111 - Executable file has no exe permissions
      • 50112 - User executable shell file is not found
    Changed:
    <
    <
      • 50113 - Executable shell did not get enough arguments
      • 50114 - Job Terminated Due to exceeding hard timeout
    >
    >
      • 50113 - Executable did not get enough arguments
      • 50114 - OSG $WORKING_DIR could not be deleted
     
      • 50115 - cmsRun did not produce a valid/readable job report at runtime
      • 50116 - Could not determine exit code of cmsRun executable at runtime
      • 50117 - Could not update exit code in job report
    Added:
    >
    >
      • 50999 - OSG $WORKING_DIR could not be deleted
     
    • Staging-OUT related troubles- range 60000-69999
    Line: 132 to 136
     
      • 60313 - Failed to delete the output from the previous run via lcg-del command
      • 60314 - Failed to invoke ProdAgent StageOut Script
      • 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
    Added:
    >
    >
      • 60999 - SG $WORKING_DIR could not be deleted
     
    • Problems saving output via output sandbox- range 70000-70009
      • 70000 - Output_sandbox too big for WMS: output can not be retrieved
    \ No newline at end of file
    Added:
    >
    >

    Revision 202008-01-30 - OlgaKodolova

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    • Error exit code of the cmsRun application itself - range 0-10000
    Changed:
    <
    <
    >
    >
      • -1 - Error return without specification
      • 1 - Hangup (POSIX)
      • 2 - Interrupt (ANSI)
      • 3 - unknown
      • 4 - Illegal instruction (ANSI)
      • 5 - Trace trap (POSIX)
      • 6 - Abort (ANSI) or IOT trap (4.2BSD)
      • 7 - BUS error (4.2BSD)
      • 8 - Floating point exception (ANSI)
      • 9 - killed, unblockable (POSIX) kill -9
      • 10 - User defined
      • 11 - segmentation violation (ANSI)
      • 12 - User defined
      • 15 - Termination (ANSI)
      • 25 - File size limit exceeded (4.2 BSD)
      • 29 - nondefined
      • 30 - Power failure restart (System V.)
      • 33 - nondefined
      • 64 - I/O error: cannot open data file (SEAL)
      • 65 - End of job from user application (CMSSW)
      • 66 - Application exception
      • 67 - unknown
      • 68 - unknown
      • 88 - unknown
      • 90 - Application exception
      • 100 - nondefined
      • 126 - unknown
      • 127 -Error while loading shared library
      • 129 - Hangup (POSIX)
      • 132 - Illegal instruction (ANSI)
      • 133 - Trace trap (POSIX)
      • 134 - Abort (ANSI) or IOT trap (4.2 BSD)
      • 135 - Bus error (4.2 BSD)
      • 136 - unknown
      • 137 - killed, unblockable (POSIX) kill -9
      • 138 - User defined
      • 139 - Segmentation violation (ANSI)
      • 140 - User defined
      • 143 - Termination (ANSI)
      • 152 - CPU limit exceeded (4.2 BSD)
      • 153 - File size limit exceeded (4.2 BSD)
      • 155 - Profiling alarm clock (4.2 BSD)
      • 251 - nondefined
      • 255 - nondefined
      • 256 - Application exception
      • 512 - nondefined
      • 2304 - nondefined
     
      • 0001 - Plug-in or message service initialization Exception
      • 7000 - Exception from command line processing
      • 7001 - Config File Not Found

    Revision 192007-11-13 - StefanoBelforte

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 43 to 43
     
      • 20070 - lcg-lr failed
      • 20071 - lcg-cp failed
    Changed:
    <
    <
    • Staging-IN failures - range 30000-39999
      • 30100 - Staging.sh file is not found (production only)
      • 31100 - Failed to stage in input file to the local disk (production only)
      • 30301 - StageInFiles:Neither zip nor tar are found
      • 30303 - StageInFiles:failed to uncompress the archive
    >
    >
    • Input file(s) related failures - range 30000-39999
      • 30001 - Fail to read input file(s)
      • 30100 - Staging.sh file is not found (production only) obsolete
      • 31100 - Failed to stage in input file to the local disk (production only) obsolete
      • 30301 - StageInFiles:Neither zip nor tar are found obsolete
      • 30303 - StageInFiles:failed to uncompress the archive obsolete
     
    Changed:
    <
    <
    • Cobra/POOL related failures- range 40000-49999
    >
    >
    • Cobra/POOL related failures- range 40000-49999 OBSOLETE
     
      • 40101 - FCpublish command failed
      • 40103 - PU catalog not found
      • 40104 - Attachment failed

    Revision 182007-11-13 - WilliamTanenbaum

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Changed:
    <
    <
    • Error exit code of the application itself - range 0-10000

    Some exit codes from the CMSSW

    >
    >
    • Error exit code of the cmsRun application itself - range 0-10000
     
    Added:
    >
    >
      • 0001 - Plug-in or message service initialization Exception
     
      • 7000 - Exception from command line processing
      • 7001 - Config File Not Found
      • 7002 - Config File Read Error
    Changed:
    <
    <
      • 8000 - SEAL Exception
    >
    >
      • 8000 - SEAL Exception (obsolete)
     
      • 8001 - CMS Exception
    Changed:
    <
    <
    >
    >
      • 8002 - std Exception
     
      • 8003 - Unknown Exception
    Added:
    >
    >
      • 8004 - std::bad_alloc exception (memory exhaustion)
     

    Revision 172007-10-05 - StuartWakefield

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 66 to 66
     
      • 50114 - Job Terminated Due to exceeding hard timeout
      • 50115 - cmsRun did not produce a valid/readable job report at runtime
      • 50116 - Could not determine exit code of cmsRun executable at runtime
    Added:
    >
    >
      • 50117 - Could not update exit code in job report
     
    • Staging-OUT related troubles- range 60000-69999

    Revision 162007-10-03 - MattiaCinquilli

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 84 to 84
     
      • 60313 - Failed to delete the output from the previous run via lcg-del command
      • 60314 - Failed to invoke ProdAgent StageOut Script
      • 60315 - ProdAgent StageOut initialisation error (Due to TFC, SITECONF etc)
    Added:
    >
    >
    • Problems saving output via output sandbox- range 70000-70009
      • 70000 - Output_sandbox too big for WMS: output can not be retrieved
     \ No newline at end of file

    Revision 152007-09-10 - DaveEvans1

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 64 to 64
     
      • 50112 - User executable shell file is not found
      • 50113 - Executable shell did not get enough arguments
      • 50114 - Job Terminated Due to exceeding hard timeout
    Added:
    >
    >
      • 50115 - cmsRun did not produce a valid/readable job report at runtime
      • 50116 - Could not determine exit code of cmsRun executable at runtime
     
    • Staging-OUT related troubles- range 60000-69999

    Revision 142007-06-07 - DaveEvans1

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 63 to 63
     
      • 50111 - Executable file has no exe permissions
      • 50112 - User executable shell file is not found
      • 50113 - Executable shell did not get enough arguments
    Added:
    >
    >
      • 50114 - Job Terminated Due to exceeding hard timeout
     
    • Staging-OUT related troubles- range 60000-69999

    Revision 132007-05-14 - DaveEvans1

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 34 to 34
     
      • 10037 - Failed to find cms_site_config file in software area
      • 10038 - Failed to find cms_site_catalogue.sh file in software area
      • 10039 - cms_site_catalogue.sh failed to provide the catalogue
    Changed:
    <
    <
    >
    >
      • 10040 - failed to generate cmsRun cfg file at runtime
     

    • Problems related to copying of files different from data files to the worker node - range 20000-29999

    Revision 122007-04-30 - DaveEvans1

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 79 to 79
     
      • 60311 - Stage Out Failure in ProdAgent job
      • 60312 - Failed to get file TURL via lcg-lr command
      • 60313 - Failed to delete the output from the previous run via lcg-del command
    \ No newline at end of file
    Added:
    >
    >
     \ No newline at end of file

    Revision 112006-12-07 - JuliaAndreevaSecondary

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    • Error exit code of the application itself - range 0-10000

    Added:
    >
    >
    Some exit codes from the CMSSW

      • 7000 - Exception from command line processing
      • 7001 - Config File Not Found
      • 7002 - Config File Read Error
      • 8000 - SEAL Exception
      • 8001 - CMS Exception
      • 8002 - StdLib Exception
      • 8003 - Unknown Exception

     
    • Failures related to the environment setup - range 10000-19999
      • 10001 - LD_LIBRARY_PATH is not defined
      • 10002 - Failed to setup LCG_LD_LIBRAR_PATH

    Revision 102006-07-04 - JuliaAndreevaSecondary

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 65 to 65
     
      • 60309 - Failed to create an output directory in the catalogue
      • 60310 - Failed to register an output file in the catalogue
      • 60311 - Stage Out Failure in ProdAgent job
    Changed:
    <
    <
    >
    >
      • 60312 - Failed to get file TURL via lcg-lr command
      • 60313 - Failed to delete the output from the previous run via lcg-del command
     \ No newline at end of file

    Revision 92006-06-05 - DaveEvans1

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 64 to 64
     
      • 60308 - Failed to create a directory on the SE with gsiftp command
      • 60309 - Failed to create an output directory in the catalogue
      • 60310 - Failed to register an output file in the catalogue
    Added:
    >
    >

     

    Revision 82006-05-23 - MarcoCorvo

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 19 to 19
     
      • 10034 - Required application version is not found at the site
      • 10035 - Scram Project Command Failed in ProdAgent production job
      • 10036 - Scram Runtime Command Failed in ProdAgent production job
    Changed:
    <
    <
    >
    >
      • 10037 - Failed to find cms_site_config file in software area
      • 10038 - Failed to find cms_site_catalogue.sh file in software area
      • 10039 - cms_site_catalogue.sh failed to provide the catalogue
     

    Revision 72006-04-28 - DaveEvans1

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 14 to 14
     
      • 10022 - Failed to scram application project using CMS sw disribution on the LCG2
      • 10030 - VO_CMS_SW_DIR is not defined
      • 10031 - Directory VO_CMS_SW_DIR not found
    Changed:
    <
    <
      • 10032 - Failed to source cmsset_default.sh script
    >
    >
      • 10032 - Failed to source CMS Environment setup script such as cmssset_default.sh, grid system or site equivalent script
     
      • 10033 - Platform is incompatible with the scram version
      • 10034 - Required application version is not found at the site
    Added:
    >
    >
      • 10035 - Scram Project Command Failed in ProdAgent production job
      • 10036 - Scram Runtime Command Failed in ProdAgent production job
     

    Revision 62006-04-26 - DaveEvans1

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Revision 52006-03-13 - JuliaAndreevaSecondary

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 14 to 14
     
      • 10022 - Failed to scram application project using CMS sw disribution on the LCG2
      • 10030 - VO_CMS_SW_DIR is not defined
      • 10031 - Directory VO_CMS_SW_DIR not found
    Added:
    >
    >
      • 10032 - Failed to source cmsset_default.sh script
      • 10033 - Platform is incompatible with the scram version
      • 10034 - Required application version is not found at the site

     
    • Problems related to copying of files different from data files to the worker node - range 20000-29999
      • 20001 - Failed to copy PubDB catalogue to the worker node
    Line: 40 to 48
     
      • 50110 - Executable file is not found
      • 50111 - Executable file has no exe permissions
      • 50112 - User executable shell file is not found
    Added:
    >
    >
      • 50113 - Executable shell did not get enough arguments
     
    • Staging-OUT related troubles- range 60000-69999
    Line: 52 to 61
     
      • 60307 - Failed to copy an output file to the SE
      • 60308 - Failed to create a directory on the SE with gsiftp command
      • 60309 - Failed to create an output directory in the catalogue
    Added:
    >
    >
      • 60310 - Failed to register an output file in the catalogue
     

    Revision 42006-03-01 - JuliaAndreevaSecondary

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    Line: 39 to 39
     
    • Executable file related failures - range 50000-59999
      • 50110 - Executable file is not found
      • 50111 - Executable file has no exe permissions
    Added:
    >
    >
      • 50112 - User executable shell file is not found
     
    • Staging-OUT related troubles- range 60000-69999

    Revision 32006-01-27 - JuliaAndreevaSecondary

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"
    Deleted:
    <
    <
     

    Error codes currently sent from CMS jobs to the dashboard via ML

    • Error exit code of the application itself - range 0-10000
    Line: 51 to 50
     
      • 60306 - Failed to copy and register output file
      • 60307 - Failed to copy an output file to the SE
      • 60308 - Failed to create a directory on the SE with gsiftp command
    Added:
    >
    >
      • 60309 - Failed to create an output directory in the catalogue
     

    Revision 22006-01-27 - JuliaAndreevaSecondary

    Line: 1 to 1
     
    META TOPICPARENT name="Dashboard"
    Deleted:
    <
    <
     

    Error codes currently sent from CMS jobs to the dashboard via ML

    • Error exit code of the application itself - range 0-10000
    Line: 42 to 41
     
      • 50110 - Executable file is not found
      • 50111 - Executable file has no exe permissions
    Changed:
    <
    <
    • *Staging-OUT related troubles- range 60000-69999
    >
    >
    • Staging-OUT related troubles- range 60000-69999
     
      • 60300 - Either OutputSE or OutputSE_DIR not defined
      • 60301 - Neither zip nor tar exists
      • 60302 - Output file(s) not found

    Revision 12006-01-12 - JuliaAndreevaSecondary

    Line: 1 to 1
    Added:
    >
    >
    META TOPICPARENT name="Dashboard"

    Error codes currently sent from CMS jobs to the dashboard via ML

    • Error exit code of the application itself - range 0-10000

    • Failures related to the environment setup - range 10000-19999
      • 10001 - LD_LIBRARY_PATH is not defined
      • 10002 - Failed to setup LCG_LD_LIBRAR_PATH
      • 10004 - DAR environment setup script is not found
      • 10005 - DAR environment setup script failed
      • 10020 - Shell script cmsset_default.sh to setup cms environment is not found
      • 10021 - Failed to scram application project using the afs release area
      • 10022 - Failed to scram application project using CMS sw disribution on the LCG2
      • 10030 - VO_CMS_SW_DIR is not defined
      • 10031 - Directory VO_CMS_SW_DIR not found

    • Problems related to copying of files different from data files to the worker node - range 20000-29999
      • 20001 - Failed to copy PubDB catalogue to the worker node
      • 20002 - Failed to copy DAR distribution to the worker node
      • 20070 - lcg-lr failed
      • 20071 - lcg-cp failed

    • Staging-IN failures - range 30000-39999
      • 30100 - Staging.sh file is not found (production only)
      • 31100 - Failed to stage in input file to the local disk (production only)
      • 30301 - StageInFiles:Neither zip nor tar are found
      • 30303 - StageInFiles:failed to uncompress the archive

    • Cobra/POOL related failures- range 40000-49999
      • 40101 - FCpublish command failed
      • 40103 - PU catalog not found
      • 40104 - Attachment failed
      • 40105 - FixColl failed
      • 40500 - FCrenamePFN failed"
      • 41030 - Problems renaming pfns of PU META files
      • 41031 - Problems merging the PU Catalog

    • Executable file related failures - range 50000-59999
      • 50110 - Executable file is not found
      • 50111 - Executable file has no exe permissions

    • *Staging-OUT related troubles- range 60000-69999
      • 60300 - Either OutputSE or OutputSE_DIR not defined
      • 60301 - Neither zip nor tar exists
      • 60302 - Output file(s) not found
      • 60303 - File already exists on the SE
      • 60304 - Failed to create the summary file (production)
      • 60305 - Failed to create a zipped archive (production)
      • 60306 - Failed to copy and register output file
      • 60307 - Failed to copy an output file to the SE
      • 60308 - Failed to create a directory on the SE with gsiftp command
     
    This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
    Ideas, requests, problems regarding TWiki? Send feedback