This may be a problem with Tomcat 4.0.3 - we had a room full of people all
install successfully last week on Tomcat 4.0.6, and one person had the
"can't resolve..." problem. And restarting Tomcat fixed it. Could you try
upgrading Tomcat to 4.0.6? Tomcat seems to have more variety between
releases than we can track. (4.0.6 is our recommended release right now.)
We've never had to change TOMCAT4_SECURITY.
Interesting question about where logging happens. We'll be adding a section
to the documentation on where log messages get written. There's a bunch of
them, but here are the two most useful:
/dspace/log/dspace.log - where most usage and errors get logged -
[tomcat]/logs/catalina.out - where most Tomcat errors get logged
Then there's the Apache log, the handle-plugin log, the handle-server log,
the PostgreSQL log, an https log, etc. These rarely have much useful
information in them compared to dspace.log and catalina.out
From: Havard Bell [mailto:HBell@...]
Sent: Friday, February 07, 2003 2:46 AM
Subject: [Dspace-tech] RE: Absolute url (
http://www.dspace.org/dspace-tag s.tl d ) cannot be resolved
> Have you folks managed to resolve this issue? Restarting Tomcat
> is always a good place to start.
I had the exact same problem as described, also running on a Debian 3.0
system. To "resolve" it, I had to turn of tomcat security, by editing the
file /etc/default/tomcat4, and setting TOMCAT4_SECURITY="no".
Obviously this is not ideal for a production system, and I have no idea of
the consequences this may have either. Any comments on this is most welcome.
The next problem I ran into was that I cannot create a community. I get a
friendly error message from DSpace itself, but cannot find the root of the
problem. DSpace says the error is logged, but where would this be?
Anyways, I just got this working, so I will look through some more
documentation on this. The answers I seek may be there.
o Havard Bell, PhD
o Interlect Co., Ltd.