Difference between revisions of "Installation/Compilation problems"

From MidasWiki
Jump to navigation Jump to search
Line 14: Line 14:
 
  odbedit> load history/run00071.xml
 
  odbedit> load history/run00071.xml
 
* OK, now your ODB should be fixed.
 
* OK, now your ODB should be fixed.
 +
 +
 +
== Installation Problems ==
 +
 +
=== SSL certificate errors ===

Revision as of 13:14, 17 June 2014

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 by doing
ls -l /dev/shm

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

  • Move the old ODB
cd online
mv .ODB.SHM .ODB.SHM.BAD
  • Restart ODB with larger size
odbedit -s 10000000
  • 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
  • OK, now your ODB should be fixed.


Installation Problems

SSL certificate errors