Difference between revisions of "Installation/Compilation problems"

From MidasWiki
Jump to navigation Jump to search
Line 1: Line 1:
 +
== Installation Problems ==
 +
 +
=== SSL certificate errors ===
 +
 +
At some sites you might get a SSL server certificate error during the git clone operation, like
 +
 +
<pre>
 +
error: SSL certificate problem, verify that the CA cert is OK. Details:
 +
</pre>
 +
 +
This indicates that you don't have the proper certificate authority (CA) files installed on your computer. Possible solutions:
 +
 +
* The easiest way out is to tell git to ignore the SSL verification with
 +
 +
<pre>
 +
git config --global http.sslVerify false
 +
</pre>
 +
 +
* Set the environment variable GIT_SSL_NO_VERIFY=true.
 +
* But the best is to just actually install the correct certificate authority files.
 +
 +
 +
== Usage Problems ==
 +
 
=== How to recover from a corrupted ODB ===
 
=== How to recover from a corrupted ODB ===
  
Line 14: Line 38:
 
  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:18, 17 June 2014

Installation Problems

SSL certificate errors

At some sites you might get a SSL server certificate error during the git clone operation, like

error: SSL certificate problem, verify that the CA cert is OK. Details:

This indicates that you don't have the proper certificate authority (CA) files installed on your computer. Possible solutions:

  • The easiest way out is to tell git to ignore the SSL verification with
 git config --global http.sslVerify false
  • Set the environment variable GIT_SSL_NO_VERIFY=true.
  • But the best is to just actually install the correct certificate authority files.


Usage Problems

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.