Firstly, it is additionally necessary to mv goobi-workflow goobi after checking out from Github.
All then goes well until I reach the compilation, which (using -X -e switches) fails producing the output pasted below. Can anyone suggest how to debug this, please?
Thank you.
Stephen
Forking command line: /bin/sh -c cd /tmp/install/goobi/Goobi/module-jar && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -jar /tmp/install/goobi/Goobi/module-jar/target/surefire/surefirebooter524047688732939893.jar /tmp/install/goobi/Goobi/module-jar/target/surefire/surefire4161362115913174063tmp /tmp/install/goobi/Goobi/module-jar/target/surefire/surefire_02787046485377603107tmp Running de.sub.goobi.TestAll 14858 ERROR (Helper.java:274) - Missing value for identifier: 14910 ERROR (Helper.java:274) - testprocess: Can not verify, image path is not set: 14912 ERROR (Helper.java:274) - testprocess: Missing entry: PPN in Monograph must exist only once, but it exists 0 times 14913 ERROR (Helper.java:274) - testprocess: Missing entry: Main title in Monograph must exist only once, but it exists 0 times 17248 ERROR (DocketConverter.java:53) - java.lang.NumberFormatException: For input string: “NAN” 17271 ERROR (DocketConverter.java:56) - de.sub.goobi.helper.exceptions.DAOException: test 18622 ERROR (ProcessConverter.java:52) - java.lang.NumberFormatException: For input string: “NAN”
if your issue is just the compilation of Goobi workflow itself then I would suggest to simply download the compiled release from here:
This release is just two weeks old and ready to be used in production. And in case you would prefer to read more about what is new in this or previous relases then you can find the monthly digests in our documentation platform here:
However we will check our installation guide tomorrow to make sure that your reported issue will not happen in the future anymore. So thanks for describing this issue here.
Thank you very much for your swift and helpful responses, Steffen and Jan.
I copied the latest release to /var/lib/tomcat8/webapps/ as you suggested, and moved to the next step, ‘Deployment of Plugins’. These failed only at the last stage with ‘No such file or directory’ for intrandaStatisticPlugins.
I ignored this and tried to start the Tomcat service, which failed with journalctl -xe revealing the messages copied below.
Perhaps I should abandon this and try Goobi-to-go?
Best wishes,
Stephen
Oct 19 07:19:46 ip-172-31-41-126 sshd[3081]: Invalid user brd from 111.175.186.150 port 22800 Oct 19 07:19:46 ip-172-31-41-126 sshd[3081]: Received disconnect from 111.175.186.150 port 22800:11: Bye Bye [preauth] Oct 19 07:19:46 ip-172-31-41-126 sshd[3081]: Disconnected from invalid user brd 111.175.186.150 port 22800 [preauth] Oct 19 07:20:07 ip-172-31-41-126 systemd[1]: Starting LSB: Start Tomcat… – Subject: Unit tomcat8.service has begun start-up – Defined-By: systemd – – Unit tomcat8.service has begun starting up. Oct 19 07:20:07 ip-172-31-41-126 tomcat8[3085]: * Starting Tomcat servlet engine tomcat8 Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ resumed (module ‘builtin:omfile’) [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [] Oct 19 07:20:07 ip-172-31-41-126 rsyslogd[877]: action ‘action 8’ suspended (module ‘builtin:omfile’), next retry is Mon Oct 19 07:20:37 2020, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.32 Oct 19 07:20:12 ip-172-31-41-126 tomcat8[3085]: …fail! Oct 19 07:20:12 ip-172-31-41-126 systemd[1]: tomcat8.service: Control process exited, code=exited status=1 Oct 19 07:20:12 ip-172-31-41-126 systemd[1]: tomcat8.service: Failed with result ‘exit-code’. Oct 19 07:20:12 ip-172-31-41-126 systemd[1]: Failed to start LSB: Start Tomcat… – Subject: Unit tomcat8.service has failed – Defined-By: systemd – – Unit tomcat8.service has failed.
I’ve kept the failed installation on a dedicated AWS EC2 instance so can go back to it whenever you have a suggestion for me to try out. In the meantime, I’ve got G2g running on another EC2 instance without any difficulties.
We updated the installation guide today. Would you like to give it a try again?
I guess it would be best to start from scratch again. And if you have any question please feel free to ask again here. We are more than happy to make our documentation better understandable.
Thanks again, Steffen. I’ll record my progress here in case it’s helpful for anyone else installing on an Amazon AWS EC2 instance.
After sudo -i, it’s necessary to apt-get update.
BASENAME needs a parameter for every part of the associated domain, for example export BASENAME=dc=GOOBI,dc=EXAMPLE,dc=CO,dc=UK
All proceeds well until restarting the Tomcat service, which fails. Output from “journalctl -xe” copied below: same error as before.
Best wishes,
Stephen
– Unit tomcat8.service has begun starting up. Oct 21 07:19:17 ip-172-31-3-204 tomcat8[14264]: * Starting Tomcat servlet engine tomcat8 Oct 21 07:19:17 ip-172-31-3-204 rsyslogd[13411]: action ‘action 8’ resumed (module ‘builtin:omfile’) [v8.32.0 try http://www.rsyslog.com/e/2359 ] Oct 21 07:19:17 ip-172-31-3-204 rsyslogd[13411]: action ‘action 8’ suspended (module ‘builtin:omfile’), retry 0. There should be messages before this one giving the reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ] [… previous 2 messages repeated several times …] Oct 21 07:19:22 ip-172-31-3-204 tomcat8[14264]: …fail! Oct 21 07:19:22 ip-172-31-3-204 systemd[1]: tomcat8.service: Control process exited, code=exited status=1 Oct 21 07:19:22 ip-172-31-3-204 systemd[1]: tomcat8.service: Failed with result ‘exit-code’. Oct 21 07:19:22 ip-172-31-3-204 systemd[1]: Failed to start LSB: Start Tomcat… – Subject: Unit tomcat8.service has failed
Leaving aside the temporary glitch, I have to congratulate you, Steffen, and your team on the beautifully clear, easy-to-follow instructions.
I’m slightly anxious that my following suggestions might be unnecessary complications, but they would allow straightforward deployment of Goobi on (preconfigured) Amazon AWS EC2+RDS+S3, and presumably in a wide variety of other situations too.
I wonder if you might include the flexibility for configuring an external database server, perhaps by replacing localhost in an initialised session variable? There are a few places in the scripts where mysql commands would require a –host parameter, and at least one instance of localhost that would need a substitution. I guess this would also mean that mariadb-client could be installed rather than mariadb-server.
