Difference between revisions of "Installation/Compilation problems"

From MidasWiki
Jump to navigation Jump to search
(Created page with "=== How to recover from a corrupted ODB === - Stop your front-ends, mlogger, mhttpd, etc. - Remove the shared memory associated to ODB buffer. Find the shared memory segment ...")
 
Line 1: Line 1:
 
=== How to recover from a corrupted ODB ===
 
=== How to recover from a corrupted ODB ===
  
- Stop your front-ends, mlogger, mhttpd, etc.
+
# Stop your front-ends, mlogger, mhttpd, etc.
- Remove the shared memory associated to ODB buffer. Find the shared memory segment by doing  
+
# Remove the shared memory associated to ODB buffer. Find the shared memory segment by doing  
 
  ls -l /dev/shm
 
  ls -l /dev/shm
 
then remove the segment that will be something like /dev/shm/*_test_ODB_SHM
 
then remove the segment that will be something like /dev/shm/*_test_ODB_SHM
 
+
# Move the old ODB
- Move the old ODB
 
 
  cd online
 
  cd online
 
  mv .ODB.SHM .ODB.SHM.BAD
 
  mv .ODB.SHM .ODB.SHM.BAD
- Restart ODB with larger size
+
# Restart ODB with larger size
 
  odbedit -s 10000000
 
  odbedit -s 10000000
- Reload the last saved ODB dump you have. These dumps are typically called something like 'online/history/*.xml'.
+
# Reload the last saved ODB dump you have. These dumps are typically called something like 'online/history/*.xml'.
 
So from odbedit you do something like
 
So from odbedit you do something like
 
  odbedit> load history/run00071.xml
 
  odbedit> load history/run00071.xml
- OK, now your ODB should be fixed.
+
# OK, now your ODB should be fixed.

Revision as of 10:41, 26 July 2013

How to recover from a corrupted ODB

  1. Stop your front-ends, mlogger, mhttpd, etc.
  2. Remove the shared memory associated to ODB buffer. Find the shared memory segment by doing
ls -l /dev/shm

then remove the segment that will be something like /dev/shm/*_test_ODB_SHM

  1. Move the old ODB
cd online
mv .ODB.SHM .ODB.SHM.BAD
  1. Restart ODB with larger size
odbedit -s 10000000
  1. Reload the last saved ODB dump you have. These dumps are typically called something like 'online/history/*.xml'.

So from odbedit you do something like

odbedit> load history/run00071.xml
  1. OK, now your ODB should be fixed.