Understanding EasyBuild logs

EasyBuild thoroughly keeps track of the executed build and install procedures. This page details some of the specifics, to help you making sense of them.

Basic information

During an invocation of the eb command, a temporary log file is provided. This log can be consulted in case any problems occur during the process. Right before completing successfully, EasyBuild will clean up this temporary log file.

A separate log file is created for each build and install procedure that is performed. After each successful installation, this application log file is copied to the install directory for future reference.

By default, the application log file is copied to a subdirectory of the installation prefix named easybuild, and has a filename like easybuild-HPL-2.0-20141103.104412.log for example, which corresponds to the filename template easybuild-%(name)s-%(version)s-%(date)s.%(time)s.log. This aspect can be tweaked via the --logfile-format configuration option.


$ eb HPL-2.0-goolf-1.4.10.eb
== temporary log file in case of crash /tmp/easybuild-rHHgBu/easybuild-XD0Ae_.log
== building and installing HPL/2.0-goolf-1.4.10...
== COMPLETED: Installation ended successfully
== Results of the build can be found in the log file /home/example/.local/easybuild/software/HPL/2.0-goolf-1.4.10/easybuild/easybuild-HPL-2.0-20141103.104412.log
== Build succeeded for 1 out of 1
== temporary log file /tmp/easybuild-rHHgBu/easybuild-XD0Ae_.log has been removed.
== temporary directory /tmp/easybuild-rHHgBu has been removed.


Enabling debug mode using the --debug or -d command line option ensures that all details of the executed build and installation procedure are included in the log file, but will also result is significantly bigger and more verbose logs.


Always include a reference to a log file (even if partial) when reporting a potential bug in EasyBuild. A particularly useful way of doing so is by creating a Gist (https://gist.github.com/), and sharing the corresponding URL. This is much better than sending a lengthy log file via email, since it can be easily shared across different communication channels (mailing list, IRC, IM, etc.).