ERROR: Server has encountered a problem and needs to close. Crash dump with detailed information saved to Data directory: crash_e2c91b1d-5007-47f4-8bef-19ebce0f1933.dmp

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • ERROR: Server has encountered a problem and needs to close. Crash dump with detailed information saved to Data directory: crash_e2c91b1d-5007-47f4-8bef-19ebce0f1933.dmp

    Hi,

    During loading a lot of data to my cube, i got in ETL the error '2013-06-24 05:03:04,395 ERROR : Failed to load Cube MYCUBE: not enough memory,Not enough memory(Palo error code: 1023)'
    • I've shutdown the machine
    • I've inserted extra RAM, and i'm trying the boot the server again.

    Now i'm facing the next error in olap_server.txt:

    2013-06-24 09:28:44 INFO: starting Jedox OLAP 5.0.2 (4218)
    2013-06-24 09:28:44 INFO: using extension 'palo https interface'
    2013-06-24 09:28:44 INFO: using extension 'palo license interface'
    2013-06-24 09:28:44 INFO: registered system database 'System'
    2013-06-24 09:28:44 INFO: registered database 'Demo'
    2013-06-24 09:28:44 INFO: registered database 'Biker'
    2013-06-24 09:28:44 INFO: registered user info database 'Config'
    2013-06-24 09:28:44 INFO: registered user info database 'fgrp1'
    2013-06-24 09:28:44 INFO: registered user info database 'fgrp2'
    2013-06-24 09:28:44 INFO: registered user info database 'rgrp1'
    2013-06-24 09:28:44 INFO: registered user info database 'rgrp2'
    2013-06-24 09:28:44 INFO: registered database 'MYDATABASE'
    2013-06-24 09:28:44 INFO: registered database 'test'
    2013-06-24 09:28:44 INFO: system database not yet loaded, loading now
    2013-06-24 09:28:45 INFO: auto loading database 'Demo'
    2013-06-24 09:28:45 INFO: created CubeDimension
    2013-06-24 09:28:47 INFO: setting client cache type to 0
    2013-06-24 09:28:47 INFO: setting hide elements to 0
    2013-06-24 09:28:47 INFO: auto loading database 'Biker'
    2013-06-24 09:28:47 INFO: created CubeDimension
    2013-06-24 09:28:51 INFO: setting client cache type to 0
    2013-06-24 09:28:51 INFO: setting hide elements to 1
    2013-06-24 09:28:52 INFO: auto loading database 'Config'
    2013-06-24 09:28:52 INFO: created CubeDimension
    2013-06-24 09:28:55 INFO: setting client cache type to 0
    2013-06-24 09:28:55 INFO: setting hide elements to 1
    2013-06-24 09:28:55 INFO: auto loading database 'fgrp1'
    2013-06-24 09:28:55 INFO: created CubeDimension
    2013-06-24 09:28:56 INFO: setting client cache type to 0
    2013-06-24 09:28:56 INFO: setting hide elements to 1
    2013-06-24 09:28:56 INFO: auto loading database 'fgrp2'
    2013-06-24 09:28:56 INFO: created CubeDimension
    2013-06-24 09:28:57 INFO: setting client cache type to 0
    2013-06-24 09:28:57 INFO: setting hide elements to 1
    2013-06-24 09:28:57 INFO: auto loading database 'rgrp1'
    2013-06-24 09:28:57 INFO: created CubeDimension
    2013-06-24 09:28:59 INFO: setting client cache type to 0
    2013-06-24 09:28:59 INFO: setting hide elements to 1
    2013-06-24 09:28:59 INFO: auto loading database 'rgrp2'
    2013-06-24 09:28:59 INFO: created CubeDimension
    2013-06-24 09:29:00 INFO: setting client cache type to 0
    2013-06-24 09:29:00 INFO: setting hide elements to 1
    2013-06-24 09:29:00 INFO: auto loading database 'MYDATABASE'
    2013-06-24 09:29:00 INFO: created CubeDimension
    2013-06-24 09:29:08 INFO: setting client cache type to 0
    2013-06-24 09:29:08 INFO: setting hide elements to 0
    2013-06-24 09:30:29 INFO: unknown cube journal file command: SET_DOUB1372037363.264897
    2013-06-24 09:30:33 INFO: unknown cube journal file command: SET_DOUBLE1372037550.320385
    2013-06-24 09:30:54 INFO: unknown cube journal file command: SE1372038979.424309
    2013-06-24 09:31:17 ERROR: Server has encountered a problem and needs to close. Crash dump with detailed information saved to Data directory: crash_e2c91b1d-5007-47f4-8bef-19ebce0f1933.dmp


    I've been able to re-start from a backup, but how can deal with this in a production enviroment?

    Thanks
    ---
    Testing 5.0.2.8378, in trial mode.
  • I see you are running the system in trial mode. Can you investigate the crash dump file?


    I ran into similar issue when running Palo compiled from source. It seems that there was a problem with JournalFileWriter.h which produced stack overflow resulting in crash dump pretty much every time I started Palo. I have managed to change the code so that it no longer crashes but haven't been able to pinpoint the exact reason for this error though.


    I am wondering if you are having the same issue.