Summary: | Virtuoso fails to start if there exists a transaction log from an earlier version | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | Will Stephenson <wstephenson> |
Component: | storage | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kde, me, trueg |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Will Stephenson
2011-11-18 18:59:21 UTC
Indeed the server will not start if there is a log from another version. So in order to get this situation you need to kill KILL virtuoso, then update it, and then try to start Nepomuk again. I already talked to OpenLink about some option to throw away old logs if not compatible but they did not like the idea. Thus, we need to create our own solution. I am not entirely sure yet how to do that though. I'm marking this bug as FIXED. It is almost 2 years old and hopefully future versions of virtuoso have fixed this issue. Please feel free to reopen if you encounter this again. This does not appear to be fixed in virtuoso. Sequence of events today: - upgrade some stuff including virtuoso - reboot (probably uncleanly) - use Nepomuk - can't connect to server. - nepomukstorage says "Failed to start Virtuoso" - delete the soprano-virtuoso.trx file - everything works! Marking as FIXED. It's fixed in soprano master and 2.9 branch. I'll release 2.9.5 so that everyone else can update. |