WebDAV problem and some questions

30 views
Skip to first unread message

Rafael Morales

unread,
Oct 11, 2009, 2:43:56 PM10/11/09
to Conzilla
Hello,

I have installed Collaborilla on our colab.udgvirtual.udg.mx server
and set the collaborilla.properties file as follows:

# Port to listen on
server.listenport=8182

# Login data for the LDAP connections
ldap.hostname=localhost
ldap.serverdn=dc\=colab,dc\=udgvirtual,dc\=udg,dc\=mx
ldap.logindn=cn\=admin,dc\=colab,dc\=udgvirtual,dc\=udg,dc\=mx
ldap.password=conzilla-collab

I have also enabled the WebDAV and Digest Authentication functionality
on our Apache2 server, defining one user for publishing our context
maps.

Then I ran Conzilla and tried to publish a context map, using the URL

dav://user:pass...@colab.udgvirtual.udg.mx/webdav/

but then I got the error messages

Uploading container urn:path:/mx/udg/udgvirtual/colab/users/rmorales/
Prueba/information.rdf to
dav://user:pass...@colab.udgvirtual.udg.mx/webdav/urn_path_/mx/udg/udgvirtual/colab/users/rmorales/Prueba/information.rdf
ERROR: org.apache.commons.httpclient.ProtocolException: Unbuffered
entity enclosing request can not be repeated.

Publishing cancelled. Please check for errors above.

I have checked the directory on our server and found the directory
chain has been created, but the file is missing. I did some search on
the Web and it seems my use of Digest instead of Basic authentication
can be the issue. People recommend to active preemptive
authentication, so I went to Conzilla code, got lost and so decided to
sent you this message, wondering whether you have seen this error
message before and asking for your help.

Regards,
Rafael


Hannes Ebner

unread,
Oct 12, 2009, 11:26:52 AM10/12/09
to Conzilla
Hi Rafel,

On Oct 11, 8:43 pm, Rafael Morales <r.moralesgam...@gmail.com> wrote:
> I have checked the directory on our server and found the directory
> chain has been created, but the file is missing. I did some search on
> the Web and it seems my use of Digest instead of Basic authentication
> can be the issue.

you are quite right, the Collaborilla server (and also Conzilla) only
support HTTP Basic at the moment.

Best regards,
Hannes

Rafael Morales

unread,
Oct 12, 2009, 10:07:58 PM10/12/09
to Conzilla
Dear Hannes,
hae
Thank you very much for your response. I have switched to Basic
Authentication and things have started to move forward, but stopped
again before 100% publishing progress. Now Conzilla reaches 50% and
stops, displaying the following messages:

Uploading container urn:path:/mx/udg/udgvirtual/colab/users/rmorales/
Prueba/information.rdf to
dav://user:pass...@colab.udgvirtual.udg.mx/webdav/urn_path_/mx/udg/udgvirtual/colab/users/rmorales/Prueba/information.rdf
Uploading container urn:path:/mx/udg/udgvirtual/colab/users/rmorales/
Prueba/presentation.rdf to
dav://user:pass...@colab.udgvirtual.udg.mx/webdav/urn_path_/mx/udg/udgvirtual/colab/users/rmorales/Prueba/presentation.rdf
Announced containers at Sindice.com
Using Collaborilla Service at http://colab.udgvirtual.udg.mx:8182
ERROR: null

Publishing cancelled. Please check for errors above.

On Collaborilla side I got the following messages:

INFO: 2009-10-12 20:16:41 148.202.240.32 -
- 8182 GET /element uri=urn%3Apath%3A%2Fmx%2Fudg
%2Fudgvirtual%2Fcolab%2Fusers%2Frmorales%2FPrueba
%2Finformation.rdf 406 0 - 1
http://colab.udgvirtual.udg.mx:8182 Collaborilla Client 1.1 -
Oct 12, 2009 8:16:41 PM com.noelios.restlet.http.HttpServerConverter
commit
WARNING: A response with an unavailable entity was returned. Ignoring
the entity
Oct 12, 2009 8:16:52 PM com.noelios.restlet.LogFilter afterHandle
INFO: 2009-10-12 20:16:52 148.202.240.32 -
- 8182 GET /element uri=http%3A%2F
%2Fcolab.udgvirtual.udg.mx%2Fusers%2Frmorales%2Flayout%2Fcontextmap
%23-22816a3a1243bf7f15c 406 0 - 1
http://colab.udgvirtual.udg.mx:8182 Collaborilla Client 1.1 -
Oct 12, 2009 8:16:52 PM com.noelios.restlet.http.HttpServerConverter
commit
WARNING: A response with an unavailable entity was returned. Ignoring
the entity
Oct 12, 2009 8:16:53 PM com.noelios.restlet.LogFilter afterHandle
INFO: 2009-10-12 20:16:53 148.202.240.32 -
- 8182 PUT /element uri=http%3A%2F
%2Fcolab.udgvirtual.udg.mx%2Fusers%2Frmorales%2Flayout%2Fcontextmap
%23-22816a3a1243bf7f15c 405 369 - 1
http://colab.udgvirtual.udg.mx:8182 Collaborilla Client 1.1 -
Oct 12, 2009 8:16:53 PM com.noelios.restlet.LogFilter afterHandle
INFO: 2009-10-12 20:16:53 148.202.240.32 -
- 8182 GET /element uri=http%3A%2F
%2Fcolab.udgvirtual.udg.mx%2Fusers%2Frmorales%2Flayout%2Fcontextmap
%23-22816a3a1243bf7f15c 406 0 - 1
http://colab.udgvirtual.udg.mx:8182 Collaborilla Client 1.1 -
Oct 12, 2009 8:16:53 PM com.noelios.restlet.http.HttpServerConverter
commit
WARNING: A response with an unavailable entity was returned. Ignoring
the entity

I would be very grateful if you could provide me with some suggestions
to move forward.

Regards,
Rafael

Hannes Ebner

unread,
Oct 13, 2009, 4:45:14 AM10/13/09
to conz...@googlegroups.com
Hi Rafael,

Rafael Morales wrote:
> Thank you very much for your response. I have switched to Basic
> Authentication and things have started to move forward, but stopped
> again before 100% publishing progress. Now Conzilla reaches 50% and
> stops, displaying the following messages:

the first 50% correspond to the uploaded RDF files (presentation and
information containers), the remaining 50% are about writing information
to the LDAP service.

> WARNING: A response with an unavailable entity was returned. Ignoring
> the entity

I think this warning is the key to your problem, could you check whether
your LDAP service is setup correctly? Are you using OpenLDAP or a
different server?

If the LDAP is up and running you will have to take a closer look on
what is going wrong (by debugging).

Best regards,
Hannes

Rafael Morales

unread,
Oct 14, 2009, 1:41:38 AM10/14/09
to conz...@googlegroups.com
Hello Hannes,

I have checked my OpenLDAP configuration and it was wrong. So I fixed
it and tested it with ldapsearch -x -W -D (I am using the sladp
package for Debian, which it seems to be OpenLDAP) so I know for sure
now that the information stored in collaborilla.properties corresponds
to the slapd configuration.

Now, when installing sldap I was asked whether to install the "old
2.0" access protocol or just install the 3.0 one. As the second one
was the default and Conzilla is not particularly old (I guess) I did
not installled the 2.0 access protocol. Would that be a problem?

A curious thing is that when I use ldapsearch, either with the right
or wrong password, I get log messages in syslog, but when I use
collaborilla nothing appears.

Regards,
Rafael


2009/10/13 Hannes Ebner <heb...@csc.kth.se>:

Hannes Ebner

unread,
Oct 14, 2009, 7:25:14 AM10/14/09
to conz...@googlegroups.com
Hi Rafael,

Rafael Morales wrote:
> Now, when installing sldap I was asked whether to install the "old
> 2.0" access protocol or just install the 3.0 one. As the second one
> was the default and Conzilla is not particularly old (I guess) I did
> not installled the 2.0 access protocol. Would that be a problem?

I think it should work with either version.

> A curious thing is that when I use ldapsearch, either with the right
> or wrong password, I get log messages in syslog, but when I use
> collaborilla nothing appears.

I guess this depends on the configured log level in your slapd.conf. It
could be that ldapsearch produces some own log messages, independently
of slapd. Collaborilla itself does not log anything to syslog, instead
it writes information to the file path which is provided in the LOGFILE
variable in the startup script collaborilla.sh.

Best regards,
Hannes

Rafael Morales

unread,
Oct 14, 2009, 6:39:55 PM10/14/09
to conz...@googlegroups.com
I get the log from ldapsearch interaction with slapd both on
syslog.log and debug.log. This information was not visible before
changes in slapd.conf, so I guess it is information provided by slapd.
Any ideas?

2009/10/14 Hannes Ebner <heb...@csc.kth.se>:

Hannes Ebner

unread,
Oct 15, 2009, 5:55:41 AM10/15/09
to conz...@googlegroups.com
Hi Rafael,

Rafael Morales wrote:
> I get the log from ldapsearch interaction with slapd both on
> syslog.log and debug.log. This information was not visible before
> changes in slapd.conf, so I guess it is information provided by slapd.
> Any ideas?

you can check in the Collaborilla log file whether there are any
attempts to connect to the LDAP service (and if so, whether it succeeds
or fails).

Best regards,
Hannes

Pyradonis Isis

unread,
May 14, 2011, 5:35:34 AM5/14/11
to conz...@googlegroups.com
And then suck my dick
Reply all
Reply to author
Forward
0 new messages