[Mesa-users] Failure to write kap_data for one user on a system

[Rob Farmer]

Hi,
Note this shouldn't be affecting the run itself, you'll just end up with
some files left over in the .mesa_temp_cache folder in your work folder
(which can be safely deleted when the run finishes)

These errors are usually related to the type of file system you are running
on:

Does the user have write permissions for the folder
$MESA_DIR/data/kap_data/cache/?
Are you on a network file system?
Is $MESA_DIR on the same file system as the work folder you are using?

Rob

On Fri, 15 Oct 2021 at 18:35, Francis Timmes via Mesa-users <
mesa-users at lists.mesastar.org> wrote:

> hi ben,
>
> a few perhaps silly questions:
> 1) does the machine have enough disk space and/or memory?
> 2) are multiple users trying to write to the same cache directory at the
> same time?
>
> this thread reported a similar issue when writing eos data
>
> https://lists.mesastar.org/pipermail/mesa-users/2018-February/008753.html
>
> and its solution / debug steps might be useful.
>
> fxt
>
>
>
>
>
> > On Oct 15, 2021, at 5:18 AM, Ben Pepper via Mesa-users <
> mesa-users at lists.mesastar.org> wrote:
> >
> > Dear Mesa users,
> >
> > Our group has a shared computer that has MESA version-r15140 installed.
> For some reason, one user within our group cannot write some opacity data
> from the default cache, particularly when the star begins to burn helium
> (regardless of how degenerate the core is) and when it enters the final
> cooling track. I have not experienced this problem and others have told me
> that they haven't either. An example of the given error is below:
> >
> > write /home/MESA/15140/mesa/data/kap_data/cache/gs98_co_z0.02_x0.0.bin
> >  mv failed for './.mesa_temp_cache/kap_cache/gs98_co_z0.02_x0.0.bin'
> > '/home/MESA/15140/mesa/data/kap_data/cache/gs98_co_z0.02_x0.0.bin'
> skippin
> >
> > So far I have tried to create a local cache in the working directory,
> compute exact sequences that I know to work and even create a new user for
> the student. None of these solutions have worked. Does anyone else have an
> idea of how I can fix this particular problem?
> >
> > Kind regards,
> >
> > Ben Pepper
> > _______________________________________________
> > 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/20211018/4059b485/attachment.htm>