[Mesa-users] Installation r11701 getting stuck on kap data

Thu Jul 4 05:21:11 EDT 2019

Hi Frank, Warrick, and other readers,

As promised the reply from the support team:
"The NFS file system has been updated recently.
There were several mistakes on nfs mounted FS regarding permissions.
This is new one.
Thank you for drawing attention on it!"

So it's an issue unrelated to my set-up and mesa, which closes this thread.

Thanks again for your quick replies,

Jacqueline

On Thu, 4 Jul 2019 at 16:04, Jacqueline Den Hartogh <
j.den.hartogh at keele.ac.uk> wrote:

> Thanks Frank for the suggestion and Warrick for confirming the build
> set-up is looking ok!
>
> I'll get in touch with the support team and let you know if the storage
> space is indeed the issue.
>
> Best,
> Jacqueline
>
> On Thu, 4 Jul 2019 at 15:49, Warrick Ball <W.H.Ball at bham.ac.uk> wrote:
>
>> Hi Jacqueline,
>>
>> Just wanted to add that the non-reproducibility is probably because in
>> trying to decompress `kap_data.tar.xz`, `xz` has created `kap_data.tar`.
>> When the build script runs again, `xz` doesn't want to overwrite the
>> (unsuccessfully) decompressed file.  I expect deleting
>> `$MESA_DIR/kap/kap_data.tar` will allow you to reproduce the first error.
>>
>> FWIW, everything else in your build setup looks correct so I agree with
>> Frank to check things like disk space.  On our University cluster, we
>> only
>> get ~20GB in $HOME, which wouldn't be enough for MESA.
>>
>> Cheers,
>> Warrick
>>
>>
>> ------------
>> Warrick Ball
>> Postdoc, School of Physics and Astronomy
>> University of Birmingham, Edgbaston, Birmingham B15 2TT
>> W.H.Ball at bham.ac.uk
>> +44 (0)121 414 4552
>>
>>
>> On Thu, 4 Jul 2019, mesa-users at lists.mesastar.org wrote:
>>
>> > hi jacqueline,
>> >
>> >
>> >> xz -d kap_data.tar.xz
>> >> xz: kap_data.tar: Cannot set the file group: Invalid argument
>> >
>> > this is the one to resolve.
>> > you're on a cluster and presumably attempting the build on the head
>> node.
>> >
>> > perhaps you are running out disk space on the head node?
>> > a mesa install will consume ~20 gb, with chunk of that in the eos data,
>> > so maybe its not a surprise the fail occurs after the eos portion is
>> built.
>> >
>> > fxt
>> >
>> >
>> >
>> >
>> >
>> >> On Jul 3, 2019, at 8:27 PM, Jacqueline Den Hartogh via Mesa-users <
>> mesa-users at lists.mesastar.org> wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I am trying to install mesa r11701 with mesa sdk, the version of early
>> May this year. The installation stops at the kap-folder. See below for the
>> error, which I cannot reproduce, and the second error that I can reproduce.
>> I have attached the full build log, which includes the environmental
>> variables.
>> >> The machine I am using is a SGI ICE8400EX (the 'debrecen' machine
>> described here:https://wiki.niif.hu/index.php?title=NIIF_HPC_(English)),
>> but it's a little outdated and won't be updated anymore. I hope this isn't
>> the problem.
>> >> I have not been able to find a similar issue on the mesa archive.
>> >>
>> >> Thanks for your help!
>> >>
>> >> Jacqueline
>> >>
>> >>
>> >> After I unzip the mesa folder, clean the folder, and then compile
>> mesa, this message pops up:
>> >> FC ../ceos
>> >>
>> >> mesa/eos has been built, tested, and exported.
>> >>
>> >> ************************************************
>> >>
>> >> /home/mavfoe2/mesa-r11701/kap
>> >> installing mesa kap data.
>> >>
>> >> create kap_data
>> >> xz -d kap_data.tar.xz
>> >> xz: kap_data.tar: Cannot set the file group: Invalid argument
>> >>
>> >>
>> >> I am unable to reproduce this error. When I try to compile mesa a
>> second time (after ./clean), I get this message:
>> >> FC ../ceos
>> >>
>> >> mesa/eos has been built, tested, and exported.
>> >>
>> >> ************************************************
>> >>
>> >> /home/mavfoe2/mesa-r11701/kap
>> >> installing mesa kap data.
>> >>
>> >> create kap_data
>> >> xz -d kap_data.tar.xz
>> >> xz: kap_data.tar: File exists
>> >>
>> >> And this error remains after I clean and compile again.
>> >> I then tried to proceed further by cleaning and compiling the kap
>> folder, and then recompiling the mesa folder (without ./clean):
>> >> DEBRECEN[service0] ~/mesa-r11701 (0)$ cd kap
>> >> DEBRECEN[service0] ~/mesa-r11701/kap (0)$ ./clean
>> >> DEBRECEN[service0] ~/mesa-r11701/kap (0)$ ./mk
>> >> MAKEDEPF90
>> >> COMPILE_CMD ../public/kap_def.f90
>> >> COMPILE_CMD ../private/cubic_interpolator.f90
>> >> COMPILE_CMD ../private/op_def.f90
>> >> COMPILE_LEGACY_NOCHECKS ../private/op_load.f
>> >> COMPILE_LEGACY_NOCHECKS ../private/op_common.f
>> >> COMPILE_LEGACY_NOCHECKS ../private/op_ev.f
>> >> COMPILE_LEGACY_NOCHECKS ../private/op_osc.f
>> >> COMPILE_LEGACY_NOCHECKS ../private/op_radacc.f
>> >> COMPILE_NO_CHECKS ../private/op_eval.f
>> >> COMPILE_CMD ../private/kap_eval_support.f90
>> >> COMPILE_CMD ../private/condint.f90
>> >> COMPILE_CMD ../private/load_co_kap.f90
>> >> COMPILE_CMD ../private/kap_aesopus.f90
>> >> COMPILE_CMD ../private/kapcn.f90
>> >> COMPILE_CMD ../private/load_kap.f90
>> >> COMPILE_CMD ../private/kap_eval_fixed.f90
>> >> COMPILE_CMD ../private/kap_eval_co.f90
>> >> COMPILE_CMD ../private/kap_eval.f90
>> >> COMPILE_CMD ../public/kap_lib.f90
>> >> LIB_TOOL libkap.a
>> >>
>> >> But this gave me the same error again.
>> >>
>> >>
>> >> <build.txt>_______________________________________________
>> >> mesa-users at lists.mesastar.org
>> >> https://lists.mesastar.org/mailman/listinfo/mesa-users
>> >>
>> >
>> > _______________________________________________
>> > mesa-users at lists.mesastar.org
>> > https://lists.mesastar.org/mailman/listinfo/mesa-users
>> >
>> >
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20190704/cfde468e/attachment-0001.html>