Error al ejecutar Fop para convertir a PDF

136 views
Skip to first unread message

vania mercedes

unread,
Feb 20, 2024, 1:41:52 PMFeb 20
to AtoM Users
Buenas tarde:
Tengo el siguiente error en la clase QubitFindingAidGenerator.class.php, al convertir un archivo xsl a pdf. 

Converting the XSL-FO document to a pdf file has failed

Al ejecutar esta instrucción mediante línea de comando la ejecución es correcta y se genera el PDF,  sin embargo desde la aplicación no es posible obtener el PDF. El detalle de logs y  error es el siguiente:

Generating a public finding aid (directorio)...
Generated EAD file "/tmp/ead_0000000451_directorio.xml"
Rendering XSL template '/var/www/html/atom/lib/task/pdf/ead-pdf-inventory-summary.xsl' to '/tmp/ATMR0kUl6'
Running: java -cp '/var/www/html/atom/vendor/saxon-he-10.6.jar:/var/www/html/atom/vendor/resolver.jar' net.sf.saxon.Transform -s:'/tmp/>
Running: fop -r -q -fo '/tmp/ATMxOoPWd' -pdf '/var/www/html/atom/downloads/directorio.pdf' 2>&1
Converting the XSL-FO document to a pdf file has failed.
Exception: ERROR(FOP): sh: línea 1: fop: orden no encontrada
File: /var/www/html/atom/lib/QubitFindingAidGenerator.class.php
Line: 564
Jobs completed: 1

Gracias por su ayuda para solucionar este problema.
Saludos,

Dan Gillean

unread,
Feb 20, 2024, 3:38:32 PMFeb 20
to ica-ato...@googlegroups.com
Hi there, 

General tips for troubleshooting finding aid generation:

1) If it doesn't work at all, double-check that you have FOP installed::
  • try the command fop -v to see if it returns a version or not
  • It also requires Java to run - see this section of the docs where we install everything required, and run these commands if you cannot find FOP on your server
2) If it works on the command-line, but not via the UI, you might want to double-check your filesystem permissions
  • AtoM expects all files and directories below the root installation directory to be owned by the www-data user
  • If you have followed our recommended installation instructions, you can set this with: sudo chown -R www-data:www-data /usr/share/nginx/atom (described in the documentation here)
  • In your case, it does look like you are maybe using Apache instead of Nginx? So you will need to modify the command's filepath (to at minimum /var/www/html/atom; but I also don't know what else might be different in your installation, so you may need to experiment some)
3) If you see an error that references the Library of Congress (loc) or returns a 403 forbidden error, then you may need to upgrade

As shown in this example screenshot: 


  • In older versions of AtoM, we used to make a call to the copy of the EAD 2002 DTD stored at the library congress when parsing the EAD header
  • We weren't the only ones erroneously doing this, which was inadvertently causing outage issues at the Library of Congress, who hosts the EAD 2002 DTD
  • Consequently, in newer versions of AtoM (2.7.0 and later) we now keep a copy of the DTD stored in AtoM directly, and will reference this
  • You can see the issue tickets #13247 and #13590 for more information if you want
  • Meanwhile, if you are using a version older than 2.7.0 and encountering this issue, upgrade to the latest release
4) If it works for some archival descriptions but not others, then it may be caused by reserved characters in your description
  • Some characters are considered reserved in XML, such as the &, <, and  > symbols
  • If you have used these in your descriptions, they can cause the EAD rendering to fail - and generating the EAD is the first step of finding aid generation
  • This also means if you have added HTML to the AtoM description edit fields to style content (such as bolding or italicizing, etc), this can cause the EAD generation to fail - instead, consider using Markdown to style content in AtoM descriptions
  • Keep reading in the second half  of this section of our Finding aid troubleshooting FAQ for more info


From what you have reported, I would first suggest you try checking and adjusting the filesystem permissions - perhaps AtoM cannot write to the /tmp directory where it is trying to create the finding aid. Let us know how it goes and what you find! 

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory
he / him


--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/3b0386e8-16a3-4081-8135-429792cb791fn%40googlegroups.com.

Ndivhuwo Phaduli

unread,
Feb 21, 2024, 8:31:58 AMFeb 21
to ica-ato...@googlegroups.com
Good day
We are currently running ATOM version 2.5.1 - 123 we want to upgrade to ATOM version Release 2.7.3 What are the implication and processes to follow.
kind regards

Dan Gillean

unread,
Feb 21, 2024, 8:42:19 AMFeb 21
to ica-ato...@googlegroups.com
Hi there, 

There is a newer release available - I would recommend you consider upgrading to release 2.8! See: 
Either way the process is the same. You will essentially: 
  • Install the new version alongside the old one
  • Copy your uploads and downloads directories to the new installation
  • Make a sqldump of the old (2.5.1) database
  • Drop and recreate the new (2.7 or 2.8) database, then load the old sqldump
  • Run the upgrade task
  • Restart some services, reindex, and start using your new site!
All of these steps are described in detail in our upgrading documentation, here: 
Make sure you follow the instructions closely! The most common problems we see from upgrades are: 
  • Users forget to drop and recreate the database BEFORE loading their old sql data, or
  • Users forget to run the upgrade task AFTER loading their old sql data
Let us know how it goes! 

Cheers, 


Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory
he / him


Ndivhuwo Phaduli

unread,
Feb 22, 2024, 4:30:15 AMFeb 22
to ica-ato...@googlegroups.com
Good day
Thank you so much
kind regards

Reply all
Reply to author
Forward
0 new messages