Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  11 Apr 2013, Thorsten Lux, Forum, Persistent ipcrm error 
    Reply  11 Apr 2013, Konstantin Olchanski, Forum, Persistent ipcrm error 
    Reply  11 Apr 2013, Stefan Ritt, Forum, Persistent ipcrm error 
       Reply  12 Apr 2013, Thorsten Lux, Forum, Persistent ipcrm error 
          Reply  12 Apr 2013, Stefan Ritt, Forum, Persistent ipcrm error 
             Reply  12 Apr 2013, Thorsten Lux, Forum, Persistent ipcrm error 
    Reply  12 Apr 2013, Thorsten Lux, Forum, Persistent ipcrm error 
       Reply  12 Apr 2013, Stefan Ritt, Forum, Persistent ipcrm error 
Message ID: 879     Entry time: 12 Apr 2013     In reply to: 873     Reply to this: 880
Author: Thorsten Lux 
Topic: Forum 
Subject: Persistent ipcrm error 
Hi,

it seems that I solved the problem in a quite brutal way.
I opened the database with odbedit and saved first the whole database as a ASCII
file and then I did the same for each section separately. Then I closed odbedit.
Afterwards I deleted all .*.SHM files including .ODB.SHM and rebooted the system.
After the restart I opened odbedit and started mhttpd. With this blank system
the problem had disappeared. Afterwards I loaded section by section from the
previous created ASCII files. After each section I tested if I can start and
stop runs and it worked without problems. At the end I also loaded the ASCII
file which contained the whole database. In this case I got the following error
message:
[odb.c:6038:db_paste,ERROR] found string exceeding MAX_STRING_LENGTH

However, after a reboot everything worked fine. I can start and stop runs, with
and without frontend, without any error message. Only the mlogger resisted to
work again. 

But also this problem we solved. It seems it was related to a missing library
path. It is strange since while in the mhttpd web page the command does not work
and is not giving any error message, copying the same command to a terminal and
to start it manually does the job. We solved it by putting the start of mlogger
in a simple shell script and to execute it then from the mhttpd web page.
Probably not an elegant solution but it does the job.

Well, with this I can enjoy my weekend to start over with data taking next week!

Thanks a lot!

Thorsten
ELOG V3.1.4-2e1708b5