Closed sermo-de-arboribus closed 3 years ago
Could you please check $EXIST/logs/xmlrpc.log
or $EXIST/logs/exist.log
if there is more info related to the error?
$EXIST/logs/xmlrpc.log
is empty. $EXIST/logs/exist.log
reports exceptions concerning de.betterform.agent.web.resources.ResourceServlet
several times, but does not mention xmlrpc explicitly anywhere.
So maybe this is not an issue with the Ansible role at all, but rather the eXist-5.2.0 package? I've attached a copy of my `exist.lg? here:
Thanks. I don't see anything in your log (ignore the betterform exceptions). Please check whether XMLRPC is enabled in etc/webapp/WEB-INF/web.xml
.
I will try to reproduce the error with 5.2 and Ubutu 20.04.
The web.xml has:
<!--
RpcServlet provides XML-RPC access.
-->
<servlet>
<servlet-name>org.exist.xmlrpc.RpcServlet</servlet-name>
<servlet-class>org.exist.xmlrpc.RpcServlet</servlet-class>
<init-param>
<param-name>enabledForExtensions</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<!--
When no user is specified in an XML-RPC request,
the guest user account will be used.
When useDefaultUser is set to false, the guest user
is prohibited from accessing the XML-RPC API.
-->
<param-name>useDefaultUser</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<!--
The Apache XML-RPC servlet does not set a charset
in the HTTP response, so the default HTTP charset
of ISO-8859-1 is implied.
We override that to make the default UTF-8 here.
You may choose any charset supported by
java.nio.charset.Charset
-->
<param-name>charset</param-name>
<param-value>UTF-8</param-value>
</init-param>
</servlet>
Hmm. Need to reproduce the problem locally.
One last quick suggestion: Try to set Ansible var exist_webxml_from_template: no
, move the previous eXist installation aside, and re-run the Ansible installation.
I can confirm that the execution of the xmlrpc scripts works for me with exist_webxml_from_template: no
!
Great! Thanks for reporting, I just committed a bugfix to disable this by default. We will address this more thoroughly in the upcoming release.
I am aware that the current status of this repo is in beta and that there has been no activity here for a while, so it might be abandoned. Nevertheless I'd like to report a failure of this Ansible role to install a given eXist-db setup, just in case it might be still of interest.
I've been trying to install eXist-db 5.2.0 on an Ubuntu 20.04 server, using the
dev-1.0
branch of this repo. All post-installation tasks that try to send .xql scripts to the running database through thecontrib/execute-xmlrpc.py
orcontrib/upload-xmlrpc.py
are failing with an error like this:Here is my list of ansible variables that I use in my playbook:
The database is up and running. When I am on the server's console I can get default responses for requests like
curl localhost:8080
orcurl 127.0.0.1:8080
. When I try to reach the rpc endpoint manually, I get the same 503 HTTP error as through the ansible task scripts:Is there anything obvious that I could change in my setup to enable the xmlrpc service and let those post-installation scripts succeed?
Context (please always complete the following information):