I have resolved the configuration - and have logged an issue for the GUI behaviour when config failed. I had failed to save an update to the MARMOTTA_HOME variable - dumb error - but it would have been nice to get a meaningful report or log result.
This still leaves the major issue - what caused the configuration to be lost? I checked and on ubuntu the default /tmp/marmotta configuration location is not a tempfs (though it may not be a safe place as in some setups it may be!). Rob On Mon, 6 Jun 2016 at 23:21 Rob Atkinson <[email protected]> wrote: > I previously successfully set up Marmotta on a remote server, under > tomcat7 using postgres. > > I went back to it today and it seems to have overwritten its config file - > maybe due to system reboot? > > I changed the location and set MARMOTTA-HOME and it is now reading the > properties file - reverted to h2 initially but when I get the admin > interface runnning again I'll test a postgres connection.. > > but when I access marmotta via any GUI it throws an error to the log > 09:08:53.239 ERROR - templating did not work: WELD-000049: Unable to > invoke public void > org.apache.marmotta.platform.core.services.templating.TemplatingServiceImpl.initDataModel() > on > org.apache.marmotta.platform.core.services.templating.TemplatingServiceImpl@62515e6f > > and displays a page with no CSS (and effectively non-functional) > > Am thinking it may be necessary to wipe the db? Looking at the code wasnt > easy to see what cofigurations may affect this. > > So - three questions: > 1) what causes a configuration to be lost (and has it lost the data?) > 2) does anything need to be done if you move MARMOTTA HOME > 3) why is templating failing and how can it be fixed? > > Rob > >
