incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Spicar (JIRA)" <>
Subject [jira] [Commented] (CLEREZZA-706) Clerezza site deployment not working
Date Tue, 19 Jun 2012 12:05:47 GMT


Daniel Spicar commented on CLEREZZA-706:

Currently I have a different proble,. I am using latest clerezza build from svn trunk and
tdb launcher.

I am following the instructions in readme.txt except I do not execute but instead
try to manually get the

When I request the at http://localhost:8080/admin/offline/download?baseUri=http://localhost:8080/&targetUri=
via web browser or curl i don't get a response in a meaningful time (longest run I let it
run for almost 40 min).

Looking at wireshark log I see that the process seems to do many other HTTP requests and gets
many 500 error "no suitable renderer found".
> Clerezza site deployment not working
> ------------------------------------
>                 Key: CLEREZZA-706
>                 URL:
>             Project: Clerezza
>          Issue Type: Bug
>            Reporter: Daniel Spicar
>            Assignee: Daniel Spicar
>         Attachments: zz-706-wireshark.pcap
> There are some issues in
> - The script tries to connect to via SSH but does not specify the SSH
user. Probabaly the system user name is used but that may be wrong.
> - The script tries to deploy the site to  '/www/' but the
correct location is '/www/'
> Issues probably related to offline site generator:
> - The site<id>.zip contains the old version of the page as *.html file (e.g. index.html)
and the new version of the page as *.xhtml file (e.g. index.xhtml). By default the apache
webserver configuration will use the index.html file and thus ignore changes. (not sure if
this happens under all circumstances but it happened when I tried to update the website)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message