Sage Crash Report

48 views
Skip to first unread message

HANG HUANG

unread,
Apr 13, 2020, 6:52:53 PM4/13/20
to sage-support
I am trying to install Sage version 9.0 on the High performance cluster at my university, which runs Linux (CentOS 7). I am installing to my local "scratch" folder since I do not have administrative permissions. I am trying to install from source code as the installing from pre-built binaries also gives me some other error. I was able to run ./configure without any issues and then when i did make, I received the following log file (attached) and error: 

Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: flint-2.5.2.p5
  log file: /scratch/user/hhuang235/sage-9.0/logs/pkgs/flint-2.5.2.p5.log
  build directory: /scratch/user/hhuang235/sage-9.0/local/var/tmp/sage/build/flint-2.5.2.p5

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

make[1]: *** [all-start] Error 1
make[1]: Leaving directory `/scratch/user/hhuang235/sage-9.0'
make: *** [all] Error 2



Any help would be greatly appreciated! Thank you very much for your time!
flint-2.5.2.p5.log

Justin C. Walker

unread,
Apr 13, 2020, 7:16:52 PM4/13/20
to SAGE Support
Checking the log file for flint that you attached, there is this:

ccache: error: Failed to create temporary file for /home/hhuang235/.ccache/2/9/8e02d78d68b9638edd65c3e5744171-2001.manifest.tmp: Disk quota exceeded

I think that should explain the problem you are having. Is the “scratch folder” on a disk of small size, or does it have a small amount of free space? The source build of Sage does take a lot of space. On my system, Sage 9.0 uses about 7.5 GB (when complete).

HTH

Justin

--
Justin C. Walker
Curmudgeon-at-large
Director
Institute for the Absorption of Federal Funds
----
186,000 Miles per Second
Not just a good idea:
it's the law!
----

HANG HUANG

unread,
Apr 13, 2020, 9:45:42 PM4/13/20
to sage-s...@googlegroups.com
Thanks very much for your reply. In fact, my scratch folder has almost 1T of free space. So I am really confused of why I got that error message.


Best,
Amy


'Justin C. Walker' via sage-support <sage-s...@googlegroups.com> 于2020年4月13日周一 下午6:16写道:
--
You received this message because you are subscribed to the Google Groups "sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/8F194F5B-3706-4290-AB20-9E16425014D4%40mac.com.

Isuru Fernando

unread,
Apr 13, 2020, 9:50:42 PM4/13/20
to sage-s...@googlegroups.com
Looks like you are using ccache, but CCACHE_DIR is not pointing to the scratch folder.
Delete $HOME/.ccache and set CCACHE_DIR env variable to some place like /scratch/user/hhuang235/.ccache

Isuru

HANG HUANG

unread,
Apr 14, 2020, 10:56:43 AM4/14/20
to sage-s...@googlegroups.com
Thank you very much for your suggestion. But now I got another problem about the building the package xz-5.2.2.p0. I attached the log file here. Any help will be greatly appreciated!

Isuru Fernando <isu...@gmail.com> 于2020年4月13日周一 下午8:50写道:
xz-5.2.2.p0.log

Soufiane Lakhlifi

unread,
Apr 23, 2020, 9:22:08 AM4/23/20
to sage-s...@googlegroups.com
Hello,

Here is the report of a crash that happened while trying to lunch sage:

-Operating system: Ubuntu 20.04 beta, upgraded from 19.10.
-Sage (8.9) was build  from the source under Ubuntu 19.10 and by following
 No special flags were used except to change the build directory.
-The crash happened by lunching sage (with no arguments) from the terminal,
 it is worth noting that the crash happened just after I upgraded my Ubuntu from
 19.10 to 20.10.

Best regards,
Soufiane Lakhlifi.
Zone contenant les pièces jointes

Sage_crash_report.txt

Jean-Florent Raymond

unread,
Apr 23, 2020, 9:42:45 AM4/23/20
to sage-s...@googlegroups.com
Hello,

Did you try to rebuild since the upgrade?
If you upgraded a package that sage needs, then sage might complain that
it cannot find the version it was used to.

It seems to be the case with libntl according to the crash report you
attached:
ImportError: libntl.so.35: cannot open shared object file: No such file
or directory

Dima Pasechnik

unread,
Apr 23, 2020, 9:45:59 AM4/23/20
to sage-support
On Thu, Apr 23, 2020 at 9:42 PM Jean-Florent Raymond
<j-floren...@uca.fr> wrote:
>
> Hello,
>
> Did you try to rebuild since the upgrade?
> If you upgraded a package that sage needs, then sage might complain that
> it cannot find the version it was used to.
>
> It seems to be the case with libntl according to the crash report you
> attached:
> ImportError: libntl.so.35: cannot open shared object file: No such file
> or directory

indeed, this is to be expected - an OS update updates libraries your
application is built against, and so
it needs to be re-linked.


>
>
>
> Le 23/04/2020 à 15:10, Soufiane Lakhlifi a écrit :
> > Hello,
> >
> > Here is the report of a crash that happened while trying to lunch sage:
> >
> > -Operating system: Ubuntu 20.04 beta, upgraded from 19.10.
> > -Sage (8.9) was build from the source under Ubuntu 19.10 and by following
> > the instructions in this page
> > http://doc.sagemath.org/html/en/installation/source.html.
> > No special flags were used except to change the build directory.
> > -The crash happened by lunching sage (with no arguments) from the terminal,
> > it is worth noting that the crash happened just after I upgraded my Ubuntu
> > from
> > 19.10 to 20.10.
> >
> > Best regards,
> > Soufiane Lakhlifi.
> > Zone contenant les pièces jointes
> >
>
> --
> You received this message because you are subscribed to the Google Groups "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/31ae06a6-0ace-d577-6d46-ce5e16ca7073%40uca.fr.
Reply all
Reply to author
Forward
0 new messages