Difference: TroubleshootingMC (1 vs. 9)

Revision 92013-04-12 - DanProtopopescu

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

Troubleshooting MC

Line: 39 to 39
 

Access permissions

Many errors came from read/write access permissions either for the local software area on sites, or for storage paths on various SEs. Using two certificates - one for jobs submission (and writing to the local storage) and the other for output replication to RAL and CERN complicates things somewhat. \ No newline at end of file

Added:
>
>

Utilities

There are many utilities, mostly bash scripts for fixing various problems:

  • recover_zombies.sh - checks ZOMBIE jobs and updates the database if output is on CERN Castor (on svr020)
  • cleanup.sh - deletes old output files from local storage on sites (on svr020)
  • verify-castor.sh - checks if MC outputs are on CERN Castor and updates the DB (ppepc102)
  • castor.sh - produces missing files lists for Janusz's controller

 \ No newline at end of file

Revision 82012-10-09 - DanProtopopescu

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

Troubleshooting MC

Line: 18 to 18
 
Added:
>
>
 

Code compilation

Revision 72012-10-09 - DanProtopopescu

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

Troubleshooting MC

Changed:
<
<
This page lists the most common problems encoutered with the NA62 MC code, along with more or less general solutions.
>
>
This page lists the most common problems encoutered with the NA62 MC code and the whole grid production setup, along with our solutions.
 
Line: 15 to 15
 
Changed:
<
<
>
>
 

Code compilation

Revision 62012-10-08 - DanProtopopescu

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

Troubleshooting MC

Line: 32 to 32
  $(FC) -shared -Wl,-soname,$(CMCLIBNAME) -o $(CMCLIB) $^ This way the .so is linked w/o the full path, which ensures portability of the executable. Same trick in Beam/GNUmakefile, but variable names BEAMLIBNAME and BEAMLIB. \ No newline at end of file
Added:
>
>

Access permissions

Many errors came from read/write access permissions either for the local software area on sites, or for storage paths on various SEs. Using two certificates - one for jobs submission (and writing to the local storage) and the other for output replication to RAL and CERN complicates things somewhat.

Revision 52012-07-09 - DanProtopopescu

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

Troubleshooting MC

Line: 15 to 15
 
Changed:
<
<
>
>
 

Code compilation

Revision 42012-07-02 - DanProtopopescu

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

Troubleshooting MC

Line: 15 to 15
 
Changed:
<
<
>
>
 

Code compilation

Revision 32012-06-21 - DanProtopopescu

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

Troubleshooting MC

Line: 6 to 6
 
Added:
>
>

GGUS tickets

Some of the problems encountered are available as GGUS tickets:

 

Code compilation

Shared object portability issue. In Generator/GNUmakefile, define a new variable CMCLIBNAME, just above the existing CMCLIB definition:

Revision 22012-05-11 - DanProtopopescu

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

Troubleshooting MC

Line: 8 to 8
 

Code compilation

Changed:
<
<
Shared object portability issue. In Generator/GNUmakefile and Beam/GNUmakefile, define a new variable CMCLIBNAME, just above the existing CMCLIB definition:
>
>
Shared object portability issue. In Generator/GNUmakefile, define a new variable CMCLIBNAME, just above the existing CMCLIB definition:
 
CMCLIBNAME := libcmc.so
CMCLIB := $(CMCDIR)/libcmc.so
Line: 20 to 20
 $(CMCLIB): $(OBJF) $(OBJC) $(COMMONOBJ) $(OBJCC) $(FC) -shared -Wl,-soname,$(CMCLIBNAME) -o $(CMCLIB) $^
Changed:
<
<
This way the .so is linked w/o the full path, which ensures portability of the executable.
>
>
This way the .so is linked w/o the full path, which ensures portability of the executable. Same trick in Beam/GNUmakefile, but variable names BEAMLIBNAME and BEAMLIB.
 \ No newline at end of file

Revision 12012-05-08 - DanProtopopescu

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

Troubleshooting MC

This page lists the most common problems encoutered with the NA62 MC code, along with more or less general solutions.

Code compilation

Shared object portability issue. In Generator/GNUmakefile and Beam/GNUmakefile, define a new variable CMCLIBNAME, just above the existing CMCLIB definition:

CMCLIBNAME := libcmc.so
CMCLIB := $(CMCDIR)/libcmc.so
and then the target:
Generator: $(CMCLIB)

$(CMCLIB): $(OBJF) $(OBJC) $(COMMONOBJ) $(OBJCC)
       $(FC) -shared -Wl,-soname,$(CMCLIBNAME) -o $(CMCLIB) $^
This way the .so is linked w/o the full path, which ensures portability of the executable.
 
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