You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by Rob Atkinson <ro...@metalinkage.com.au> on 2016/06/06 13:21:52 UTC
Marmotta configuration
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
Re: Marmotta configuration
Posted by Rob Atkinson <ro...@metalinkage.com.au>.
1) behaviour is easy to reproduce - just use postgres and invalid login
credentials - then reload the GUI after it reports the failure the first
time.
2) Is there anything in Marmotta that would cause it to overwrite its
configuration? (tempfs was one possibility I explored I was just flagging
might be an issue - but not in this case as I can tell).
On Wed, 8 Jun 2016 at 16:39 Sergio Fernández <wi...@apache.org> wrote:
> On Wed, Jun 8, 2016 at 5:56 AM, Rob Atkinson <ro...@metalinkage.com.au>
> wrote:
>
> > 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.
> >
>
> Did it really failed? Please, report the logs to MARMOTTA-643.
>
> 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!).
> >
>
> Default configuration is at /tmp/marmotta on purpose. Any user who want a
> production system should at least care of such basic configuration details.
>
> Cheers,
>
>
>
>
> > On Mon, 6 Jun 2016 at 23:21 Rob Atkinson <ro...@metalinkage.com.au> 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
> > >
> > >
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>
Re: Marmotta configuration
Posted by Sergio Fernández <wi...@apache.org>.
On Wed, Jun 8, 2016 at 5:56 AM, Rob Atkinson <ro...@metalinkage.com.au> wrote:
> 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.
>
Did it really failed? Please, report the logs to MARMOTTA-643.
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!).
>
Default configuration is at /tmp/marmotta on purpose. Any user who want a
production system should at least care of such basic configuration details.
Cheers,
> On Mon, 6 Jun 2016 at 23:21 Rob Atkinson <ro...@metalinkage.com.au> 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
> >
> >
>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: Marmotta configuration
Posted by Rob Atkinson <ro...@metalinkage.com.au>.
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 <ro...@metalinkage.com.au> 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
>
>