Topic Thread

Expand all | Collapse all

Tip: eHealth debugging can crash eHealth

  • 1.  Tip: eHealth debugging can crash eHealth

    Posted 08-27-2015 09:38 AM

    I just ran into this, just to make you aware:

     

    I crashed my ehealth by enabling debugging for the nhiCfgServer process in startup.cfg

      program nhiCfgServer {

         restart     all     # Requires complete server restart

         wait        2

         arguments "-Dall -Dt"

      }

     

    and letting it run overnight. This produced a 2GB log file

    While this is no problem for the OS, it seems to be a file size limit for the CfgServer, which crashes the process!

     

    The effect is that CfgServer crashes at every startup, and because eHealth depends on it, it does no longer start

     

    Symptoms are:

    - debug logfile size of exactly 2^31 -1 bytes

    - sudden restarts in system.log with no error

    - no new entries in this file when ehealth tries to start

     

    Remedy:

    - rename the log file

    and/or

    - stop debugging

     

    Not sure if the same applies to debugging of other processes



  • 2.  Re: Tip: eHealth debugging can crash eHealth

    Posted 08-27-2015 10:11 AM

    Hi Jan,

    thanks for posting - can you confirm the versions of eHealth and the OS please.

    Can you also raise an issue with support and we will see if we can replicate this to establish if there is a solution.

     

    thx

    Pete



  • 3.  Re: Tip: eHealth debugging can crash eHealth

    Posted 08-27-2015 10:17 AM

    Hi Pete

     

    ehealth 6.3.2.08 on Linux

    There is an open ticket (00187134) owned by Alain P. who is in contact with SE

     

    Cheers Jan



  • 4.  Re: Tip: eHealth debugging can crash eHealth

    Posted 08-27-2015 11:25 AM

    It usually stops writing information to the log file. I never had it crash. I can confirm however the limit on the advanced logging size. There's not logrotation mechanism in place. There is a separate thread on this, you can create a log rotation mechanism that will move the log file whenever reaches size close to max. I had once created one, but I'm having hard times find it. I will share it when I find it. It's not very complex, thow. Some scripting over monitoring the size of the file and disabling/enabling advanced logging.