I found the error, I didn't have a a xmlui-context path in
../tomcat/conf/server.xml, after I put in:
<!-- DEFINE A CONTEXT PATH FOR DSpace XMLUI User Interface -->
<Context path="/xmlui"
docBase="/usr/local/dspace/webapps/xmlui" debug="99"
reloadable="true" cachingAllowed="false"
allowLinking="true"/>
It worked. I hadn't thought to check this file as xmlui had worked in
1.7.x (and now I wonder how it could have worked there).
Anyway, thanks for the help. :-)
Regards
Kai Bjørnenak
On 10/09/2012 12:47 PM, helix84 wrote:
> On Tue, Oct 9, 2012 at 12:30 PM, Kai Bjørnenak <[email protected]> wrote:
>> Ok, tried running chown on the dspace-folder, still same error-messages.
> OK, I said it was a far cry :)
>
> I think the problem is that for some reason DSpace is not able to load
> all configuration. How did you migrate your configuration when
> upgrading from 1.7 to 1.8. Did you copy your 1.7 configuration over
> the default 1.8 configuration? There have been many changes, so you
> should instead take the default 1.8 installation and only change the
> things you want to change in there. To find out what you actually
> changed, you can take the default 1.7 configuration directory and do:
> diff -ur /default/dspace1.7/config/ /your/dspace17/config/ | view -
>
> Look at the diff and make your changes in the default 1.8 config
> directory, then use that and restart Tomcat.
>
> Regards,
> ~~helix84
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
