LaTeXRuntimeException: LaTeX compilation of /opt/indico/tmp/indico-texgen-5XEFFs/report.tpl.tex failed

Administrators
1

Indico 2.0

We are getting error:

Comment
-------
error.

Traceback
---------
Traceback (most recent call last):
File "/opt/indico/.venv/lib/python2.7/site-packages/flask/app.py", line 1612, in full_dispatch_request
rv = self.dispatch_request()
File "/opt/indico/.venv/lib/python2.7/site-packages/flask/app.py", line 1598, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "/opt/indico/.venv/lib/python2.7/site-packages/indico/web/flask/util.py", line 114, in wrapper
return obj().process()
File "/opt/indico/.venv/lib/python2.7/site-packages/indico/web/rh.py", line 270, in process
res = self._do_process()
File "/opt/indico/.venv/lib/python2.7/site-packages/indico/modules/events/controllers/base.py", line 63, in _do_process
return RHEventBase._do_process(self)
File "/opt/indico/.venv/lib/python2.7/site-packages/indico/web/rh.py", line 249, in _do_process
return self._process()
File "/opt/indico/.venv/lib/python2.7/site-packages/indico/modules/events/abstracts/controllers/common.py", line 81, in _process
return send_file('abstracts.pdf', pdf.generate(), 'application/pdf')
File "/opt/indico/.venv/lib/python2.7/site-packages/indico/legacy/pdfinterface/base.py", line 683, in generate
pdffile = latex.run(self._tpl_filename, **self._args)
File "/opt/indico/.venv/lib/python2.7/site-packages/indico/legacy/pdfinterface/base.py", line 749, in run
raise LaTeXRuntimeException(source_filename, log_filename)
LaTeXRuntimeException: LaTeX compilation of /opt/indico/tmp/indico-texgen-5XEFFs/report.tpl.tex failed

(Remainder of error cut because not allowed to post > 2 links.)

-rw-r-----  1 indico apache      0 Jun 19 11:05 output.log
-rw-r-----  1 indico apache 119871 Jun 19 11:05 report.tpl.tex

If I xelatex report.tpl.tex:

! Illegal unit of measure (pt inserted).
<to be read again> 
                   }
l.4194 [2]
           Weingartner et al. Phys. Rev. ST Accel. Beams 15, 111302 (2012)\\
! Illegal unit of measure (pt inserted).
<to be read again> 
                   }
l.4195 [3]
           Barber et al. Phys. Rev. Lett. 119, 104801 (2017)\\
? 
! Illegal unit of measure (pt inserted).
<to be read again> 
                   }
l.4196 [4]
           Barber et al. Plasma Phys. Controlled Fusion 60, 054415 (2018)
? 
[27] [28] (./report.tpl.aux) )
Output written on report.tpl.pdf (29 pages).
Transcript written on report.tpl.log.

Is this a problem with xelatex ??

Any assistance or pointers greatly appreciated.

2

Could you attach the .tex file here?

3

I don’t see a way to attach a file. Should I paste inline?

4

It is 4487 lines, 119k

5

Best to upload it somewhere else and just post the link.

Anyway, if this is the PDF for the selected abstracts, try to narrow it down to find out which abstract is causing it (select half the abstracts, see if it fails again, and so on). Then posting the content of the abstract causing the problem should be enough (wrap it in triple backticks here so it keeps its original formatting)

6

Thank you TM for your reply

https://nucleus.txcorp.com/~hammond/report.tpl.tex

Here are the lines where it is complaining:

[1] Steinke et al. Nature 530, 190 (2016)\\
[2] Weingartner et al. Phys. Rev. ST Accel. Beams 15, 111302 (2012)\\
[3] Barber et al. Phys. Rev. Lett. 119, 104801 (2017)\\
[4] Barber et al. Plasma Phys. Controlled Fusion 60, 054415 (2018)
    }
    \vspace{1.5em}
\end{addmargin}

After CR through the errors, it does create a .pdf file. I can see the
abstract where the error was created (Abstract ID : 146)

The .pdf file is:

[1] Steinke et al. Nature 530, 190 (2016)
Weingartner et al. Phys. Rev. ST Accel. Beams 15, 111302 (2012)
Barber et al. Phys. Rev. Lett. 119, 104801 (2017)
Barber et al. Plasma Phys. Controlled Fusion 60, 054415 (2018)
7

Thanks for your help.

elatex is complaining about the text input from one of the submitted abstracts when creating a .pdf file.

So one needs to determine which abstract is causing the problem, and modify
the source.

8

What is the exact version you are using? https://github.com/indico/indico/commit/0839c48ee13f935433bf79de7d07c41c837c9dc7 that made it into 2.0.1 seems like a candidate for fixing this.

9

Thanks bpedersen2.

On the Administration page it says:

A new Indico version (2.1.2) is available! Your current version is 2.0.

But 2.0.1 does look like it fixed it.

10

You should upgrade to 2.1.2 :slight_smile: It’s quite stable and has lots of new features (and some more bugfixes)!