Something similar is happening to me since the graph translation. The thing I barely understand is how virtuoso is crashing so much because DBMS must be rock solid.
On Thu, Jun 20, 2013 at 2:13 PM, Vishesh Handa <[email protected]> wrote: > On Thu, Jun 20, 2013 at 5:41 PM, Lindsay Mathieson > <[email protected]> wrote: > > On Thu, 20 Jun 2013 09:57:41 PM you wrote: > >> On Thu, 20 Jun 2013 04:51:28 PM you wrote: > >> > Please file a bug report, and add the backtrace. > >> > > >> > You can produce the backtrace by running the storage service manually > >> > > >> > $ gdb nepomukstorage > >> > >> Still no stacktrace unfortunately. > >> > >> Program received signal SIGPIPE, Broken pipe. > >> [Switching to Thread 0x7fffea83e700 (LWP 23753)] > >> 0x00007ffff4e6cf17 in send () from /lib/x86_64-linux-gnu/libc.so.6 > > > > The more I test it seems to be a problem with virtuoso-t - it crashes, > storage > > gets a broken pipe signal and doesn't recover. > > > > Which repo does virtuoso-t get build from? kdesupport? > > virtuoso-t is provided by openlink. What version do you have? > > I have Version 6.1.6.3127-pthreads > > > > > -- > > Lindsay > > > > -- > Vishesh Handa > _______________________________________________ > Nepomuk mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/nepomuk > -- Best wishes, Ignacio
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
