Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  21 Aug 2018, Wes Gohn, Bug Report, mserver problem 
    Reply  28 Aug 2018, Konstantin Olchanski, Bug Report, mserver problem 
Message ID: 1390     Entry time: 28 Aug 2018     In reply to: 1382
Author: Konstantin Olchanski 
Topic: Bug Report 
Subject: mserver problem 
> Hi. We've just updated our midas installation to the newest version, and we now see repeated errors from the 
> mserver in messages. Mostly we see
> 11:17:02.994 2018/08/21 [ODBEdit,TALK] Program mserver restarted
> which happens 2-3 times per minute. 
> We have also been seeing occasional dropped rpc connections to our frontends, which could be related. 
> The version we were running with previously was ~1 year old, and we have just updated to the newest version 
> on bitbucket. 

Hmm... usually mserver will not restart automatically, maybe you have set it to autorestart on ODB (/programs/mserver/auto_restart 
set to "y").

It would be unusual for the main mserver program to crash, to debug it, you will need to run it in a terminal
and see if there is any error messages. Even better to run it in a terminal inside "gdb" and capture the stack trace
when it crashes.

Anyhow, crash of main mserver will not cause "dropped rpc connections" to clients - this would require for their
individual mserver subprocesses to crash. Such crashes would be highly unusual and are harder to debug.

Perhaps for the crashes you see there is some error messages in midas.log?

ELOG V3.1.4-2e1708b5