From: Daniel S. <dan...@ao...> - 2012-10-11 22:02:03
|
Hi Florent, thanks for your hint! I totally forgot to mention that eXist is running behind an nginx service – D'oh! Actually, disabling the proxy makes the installation script finish. For the configuration of the proxy I followed the instructions in [1], changing the proxy_pass parameter to proxy_pass http://localhost:8080; as I'm using the wrapper-script in $EXIST_HOME/tools/wrapper/exist.sh and jetty is configured to listen to port 8080 (in /tools/jetty/jetty.xml). - So maybe I'm missing something in the proxy configuration? (headers.txt just shows a 404 error by nginx, tools/wrapper/logs/exist.log doesn't notice the request at all.) To be honest I wasn't aware that the package installer is accessing the downloaded xar-file via rest. So for curiosity I tried to disable rest-browsing in $EXIST_HOME/webapp/WEB-INF/web.xml - which led to the same "package not found" error. – So, just to get it straight: It's not possible to use the packaging mechanism on a production system with rest-browsing disabled, right? Sorry for all the (probably trivial) questions and thanks again for your help! Daniel [1] http://exist-db.org/exist/production_web_proxying.xml#d11894e324 headers.txt HTTP/1.1 404 Not Found Server: nginx/1.2.0 Date: Thu, 11 Oct 2012 13:18:44 GMT Content-Type: text/html Content-Length: 168 Connection: keep-alive Am 11.10.12 13:52, schrieb Florent Georges: > Can you try the following command on > the same machine? > > curl -D headers.txt -o content.txt \ > http://localhost:80/exist/rest/db/system/repo/demo-0.1.xar > It will create two files with the result of the HTTP request > (namely headers.txt and content.txt) That might give more > information on the real cause. If you could also try to see if > there is anything appearing on the eXist logs when you run this > command... |