[Mesa-users] ./build_and_test FAILED for eos

RICHARD H D TOWNSEND townsend at astro.wisc.edu
Fri Feb 23 12:43:28 EST 2018


Hi Marcel --

On a final note -- you can keep using the custom SDK I built for you, but you can also switch back to the "official" SDK if you require.

cheers,

Rich

> On Feb 23, 2018, at 7:08 AM, Marcel Agüeros <marcel at astro.columbia.edu> wrote:
> 
> 
> 	that worked! Thanks so much for all your help with this.
> 	Take care,
> 	Marcel.
> 
> On Fri, 23 Feb 2018, Rob Farmer wrote:
> 
>> Thanks, can you try setting:
>> export MESA_TEMP_CACHES_DISABLE=1
>> in your terminal then trying the build again
>> It looks like you system is having issues with memory limits, setting this option will stop us trying to run the mv command to move the eos cache
>> around and hopefully will get you around this issue.
>> Rob
>> On 23 February 2018 at 14:25, Marcel Agüeros <marcel at astro.columbia.edu> wrote:
>> 
>>                    total        used        free      shared  buff/cache   available
>>      Mem:          3.7G        2.5G        223M        248M        1.0G     724M
>>      Swap:         487M        484M        3.4M
>>              Take care,
>>              Marcel.
>> 
>>      On Fri, 23 Feb 2018, Rob Farmer wrote:
>> 
>>      > and also do you have /swap setup? You can send the output of:
>>      >
>>      > free -h
>>      >
>>      > to get both the swap and memory info
>>      >
>>      > Thanks
>>      > Rob
>>      >
>>      > On 23 February 2018 at 14:14, Rob Farmer <r.j.farmer at uva.nl> wrote:
>>      >       > System call failed: Cannot allocate memory
>>      >
>>      >       Interesting your system is running out of memory, how much RAM does your machine have?
>>      >
>>      > Rob
>>      >
>>      > On 23 February 2018 at 14:06, Marcel Agüeros <marcel at astro.columbia.edu> wrote:
>>      >
>>      >               Thanks, Rich. I've attached the file from running
>>      >       ./tester. It doesn't include the following, which appeared
>>      >       in my terminal:
>>      >       ERROR STOP 1
>>      >
>>      >       Error termination. Backtrace:
>>      >       #0  0x55ac22 in __utils_lib_MOD_mesa_error
>>      >               at ../public/utils_lib.f:1008
>>      >       #1  0x55b8ce in __utils_lib_MOD_mv
>>      >               at ../public/utils_lib.f:855
>>      >       #2  0x46a4c2 in __eosdt_load_tables_MOD_load1_eosdt_table
>>      >               at ../private/eosdt_load_tables.f90:416
>>      >       #3  0x46a687 in read_one
>>      >               at ../private/eosdt_load_tables.f90:174
>>      >       #4  0x46a7cd in do_read
>>      >               at ../private/eosdt_load_tables.f90:156
>>      >       #5  0x46a7cd in __eosdt_load_tables_MOD_load_single_eosdt_table_by_id
>>      >               at ../private/eosdt_load_tables.f90:149
>>      >       #6  0x42cd1f in __eosdt_eval_MOD_get_eosdt_xtable_results
>>      >               at ../private/eosdt_eval.f90:1494
>>      >       #7  0x42d630 in __eosdt_eval_MOD_get_opal_scvh_for_x
>>      >               at ../private/eosdt_eval.f90:1318
>>      >       #8  0x42e6a3 in do_interp2
>>      >               at ../private/eosdt_eval.f90:1153
>>      >       #9  0x42e6a3 in __eosdt_eval_MOD_get_opal_scvh_results
>>      >               at ../private/eosdt_eval.f90:1118
>>      >       #10  0x430469 in __eosdt_eval_MOD_get_opal_scvh_helm_pc_eosdt_results
>>      >               at ../private/eosdt_eval.f90:765
>>      >       #11  0x43180e in __eosdt_eval_MOD_get1_eosdt_results
>>      >               at ../private/eosdt_eval.f90:396
>>      >       #12  0x432460 in __eosdt_eval_MOD_get_eosdt_results
>>      >               at ../private/eosdt_eval.f90:176
>>      >       #13  0x41ff60 in __eos_lib_MOD_eosdt_get
>>      >               at ../public/eos_lib.f90:511
>>      >       #14  0x40b9c3 in __test_eos_support_MOD_do_one_trho
>>      >               at ../src/test_eos_support.f:2183
>>      >       #15  0x40c567 in doit
>>      >               at ../src/test_eos_support.f:1598
>>      >       #16  0x41092e in __test_eos_support_MOD_do_one
>>      >               at ../src/test_eos_support.f:1556
>>      >       #17  0x4036f6 in test_eos
>>      >               at ../src/test_eos.f:36
>>      >       #18  0x4036f6 in main
>>      >               at ../src/test_eos.f:2
>>      >
>>      >               Take care,
>>      >               Marcel.
>>      >
>>      >
>>      >       On Thu, 22 Feb 2018, RICHARD H D TOWNSEND wrote:
>>      >
>>      >       > Hi Marcel --
>>      >       >
>>      >       > I've built a special version of the MESA SDK, which prints out more information on what's going wrong when the crash occurs.
>>      >       Please download the SDK from here:
>>      >       >
>>      >       > http://www.astro.wisc.edu/~townsend/resource/download/mesasdk/mesasdk-x86_64-linux-20180222.tar.gz
>>      >       >
>>      >       > ...and install it as usual. Then, repeat the steps that Rob Farmer details below.
>>      >       > cheers,
>>      >       >
>>      >       > Rich
>>      >       >
>>      >       >> On Feb 22, 2018, at 9:52 AM, Marcel Agüeros <marcel at astro.columbia.edu> wrote:
>>      >       >>
>>      >       >>
>>      >       >>      Hi Rob--
>>      >       >>      it did fail, and after I ran ./tester I got the
>>      >       >> attached run.log file.
>>      >       >>      Take care,
>>      >       >>      Marcel.
>>      >       >>
>>      >       >> On Thu, 22 Feb 2018, Rob Farmer wrote:
>>      >       >>
>>      >       >>> Hi Marcel,
>>      >       >>> Can you put this file inside $MESA_DIR/utils/public and then do:
>>      >       >>> cd $MESA_DIR
>>      >       >>> ./clean
>>      >       >>> ./install
>>      >       >>> if/when mesa fails do:
>>      >       >>> cd $MESA_DIR/eos/test
>>      >       >>> rm $MESA_DIR/data/eos*/cache/*
>>      >       >>> ./mk
>>      >       >>> ./tester | tee run.log
>>      >       >>> Thanks
>>      >       >>> Rob
>>      >       >>> On 22 February 2018 at 13:21, Marcel Agüeros <marcel at astro.columbia.edu>
>>      >       >>> wrote:
>>      >       >>>
>>      >       >>>              Hi Aaron--
>>      >       >>>              sorry, it was late last night and I wasn't paying
>>      >       >>>      attention to the terminals--
>>      >       >>>
>>      >       >>>      gfortran -v returns
>>      >       >>>      Using built-in specs.
>>      >       >>>      COLLECT_GCC=/home/marcel/Desktop/mesasdk/bin/gfortran.exec
>>      >       >>> COLLECT_LTO_WRAPPER=/home/marcel/Desktop/mesasdk/bin/../libexec/gcc/x86_64-
>>      >       >>>      pc-linux-gnu/7.2.0/lto-wrapper
>>      >       >>>      Target: x86_64-pc-linux-gnu
>>      >       >>>      Configured with: /root/mesasdk-src/gcc/configure CC=gcc
>>      >       >>>      --build=x86_64-pc-linux-gnu --prefix=/root/mesasdk
>>      >       >>>      --with-gmp=/root/mesasdk --with-mpfr=/root/mesasdk
>>      >       >>>      --with-mpc=/root/mesasdk --enable-languages=c,c++,fortran
>>      >       >>>      --disable-multilib --disable-nls --disable-libsanitizer
>>      >       >>>      --enable-clocale=generic
>>      >       >>>      Thread model: posix
>>      >       >>>      gcc version 7.2.0 (GCC)
>>      >       >>>
>>      >       >>>      which gfortran
>>      >       >>>      /home/marcel/Desktop/mesasdk/bin/gfortran
>>      >       >>>
>>      >       >>>              Take care,
>>      >       >>>              Marcel.
>>      >       >>>
>>      >       >>>      On Wed, 21 Feb 2018, Aaron Dotter wrote:
>>      >       >>>
>>      >       >>>     > Hi Marcel,
>>      >       >>>     >             what version of the mesasdk are you using?
>>      >       >>>     >
>>      >       >>>     >       mesasdk-x86_64-linux-20180127.tar.gz
>>      >       >>>     >
>>      >       >>>     >
>>      >       >>>     >       gcc version 5.4.0 20160609 (Ubuntu
>>      >       >>>      5.4.0-6ubuntu1~16.04.9)
>>      >       >>>     >
>>      >       >>>     >
>>      >       >>>     > Somehow or other you're getting the system-installed
>>      >       >>>      gfortran.  You can compare the dates (SDK: 20180127 vs.
>>      >       >>>      20160609) in the lines above.
>>      >       >>>     >
>>      >       >>>     > You should be able to confirm this by typting 'which
>>      >       >>>      gfortran'.  Just out of curiosity, are you using more than one
>>      >       >>>      terminal window?  And have
>>      >       >>>     > they all been sourced properly?
>>      >       >>>     >
>>      >       >>>     >
>>      >       >>>     > Aaron
>>      >       >>>     >
>>      >       >>> ------------------------------------------------------------------
>>      >       >>> Marcel Agüeros
>>      >       >>> Associate Professor, Department of Astronomy
>>      >       >>> Columbia University
>>      >       >>> Mail Code 5246
>>      >       >>> 550 W120 Street
>>      >       >>> NY, NY 10027
>>      >       >>> 1 212 854 6814
>>      >       >>> ------------------------------------------------------------------
>>      >       >>> _______________________________________________
>>      >       >>> mesa-users at lists.mesastar.org
>>      >       >>> https://lists.mesastar.org/mailman/listinfo/mesa-users
>>      > >> <run.log>_______________________________________________
>>      > >> mesa-users at lists.mesastar.org
>>      > >> https://lists.mesastar.org/mailman/listinfo/mesa-users
>>      >
>>      >
>>      >
>>      >
>>      >
>>         Take care,
>>         Marcel.
>> ------------------------------------------------------------------
>> Marcel Agüeros
>> Associate Professor, Department of Astronomy
>> Columbia University
>> Mail Code 5246
>> 550 W120 Street
>> NY, NY 10027
>> 1 212 854 6814
>> ------------------------------------------------------------------
> _______________________________________________
> mesa-users at lists.mesastar.org
> https://lists.mesastar.org/mailman/listinfo/mesa-users
> 



More information about the Mesa-users mailing list