Windows and durable transactions

[ffoulw...@gmail.com]

I am having issues when using durable transactions in Windows 7 while testing our application with Stardog 2.1.2. The easiest way to replicate what I'm seeing is to create a new database with durable transactions, add a bunch of triples and then restart the database:

stardog-admin db create -n testdb -d ..\examples\data\sp2b_10k.n3
stardog data add testdb ..\examples\data\catalog.rdf
stardog-admin server stop
stardog-admin server start

SEVERE: Database testdb will not be available because there was an error initializing the database: There was an error while reading the transaction log, cannot initialize database

No errors seen when using Linux.

Daniel

[Mike Grove]

Is there any additional information in stardog.log?

Is the log file readable by the process running stardog?

Cheers,

Mike 

 

Daniel

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+u...@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en

[ffoulw...@gmail.com]

The error shown on the console about the DB not available isn't even showing up in stardog.log. A db list shows the database but a db status indicates it does not exist.

I'm starting a standalone stardog on the command line, not sure why it wouldn't be able to read any of the files it created previously. My user can see everything fine.

Daniel 

[Mike Grove]

Ok, thanks for reporting, we'll take a look.

Cheers,

Mike

[Mike Grove]

On Tue, Mar 25, 2014 at 12:28 PM, Mike Grove <mi...@clarkparsia.com> wrote:

Ok, thanks for reporting, we'll take a look.

This seems to be an issue with memory-mapped files on windows, we'll include a fix for this in the next release.

Cheers,

Mike