Hi Hugh,
Unfortunately I am not able to provide test case for that condition. One
thing I did notice about this error is that until we insert triples
without plain literal object values there is no error. After a triple
with object value as plain literal without type reference the error
occurs and then it keeps occurring for every type of triples.
Tried to do "Crash Recovery When The Normal Crash Recovery Fails” as you
indicated, but it seems that something has gone very wrong in the
database as the first point "Do a crash dump of the schema tables (using
the '+crash-dump +mode oa +dumpkeys schema' virtuoso command line
options).":
virtuoso-t -c /etc/virtuoso-opensource-7/virtuoso.ini -f
+crash-dump +mode oa +dumpkeys schema
ended with the following error log:
12:48:26 virtuoso-t() [0x8d365a]
12:48:26 virtuoso-t() [0x8d36b8]
12:48:26 virtuoso-t() [0x486c1f]
12:48:26 virtuoso-t() [0x487f4e]
12:48:26 virtuoso-t() [0x48a15d]
12:48:26 virtuoso-t() [0x47d615]
12:48:26 virtuoso-t() [0x47dad5]
12:48:26 virtuoso-t() [0x47de81]
12:48:26 virtuoso-t() [0x5d59e1]
12:48:26 virtuoso-t() [0x4101e3]
12:48:26 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
[0x7faaea098ec5]
12:48:26 virtuoso-t() [0x4103c4]
12:48:26 GPF: extent.c:952 no dp even though brand new ext
Segmentation fault (core dumped)
The backtrace of core dump is the following:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00000000008d371e in ?? ()
(gdb) bt
#0 0x00000000008d371e in ?? ()
#1 0x0000000000486c1f in ?? ()
#2 0x0000000000487f4e in ?? ()
#3 0x000000000048a15d in ?? ()
#4 0x000000000047d615 in ?? ()
#5 0x000000000047dad5 in ?? ()
#6 0x000000000047de81 in ?? ()
#7 0x00000000005d59e1 in ?? ()
#8 0x00000000004101e3 in ?? ()
#9 0x00007faaea098ec5 in __libc_start_main (main=0x40fcd0, argc=9,
argv=0x7fff1a927108, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fff1a9270f8) at
libc-start.c:287
#10 0x00000000004103c4 in ?? ()
Can you recommend any other means to recover our database or should we
do a quad dump according to
http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtRDFDumpNQuad
and upload data to a new clean and fresh database?
Best wishes,
Piret
On 08.01.16 14:51, Hugh Williams wrote:
> Hi Piret,
>
> Have you attempted a "Crash Recovery When The Normal Crash Recovery Fails”
> which rebuild schema and system keys etc as detailed in section 6.1.5.4.3. of
> the docs at:
>
> http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#backup
>
> Also, do you have "Log Audit Trail" an "On-line Backups" enabled as indicated
> section 6.1.5.1. & 6.1.5.2. of the backup docs above, which is always
> recommend such you can can always recover to the last known good state of the
> database ?
>
> As for the "SQL Error: XXXXX : COL..: Insert stopped because out of seg data
> here or elsewhere host 0 key RDF_QUAD slice” error I have tested the previous
> test case we have for this issue with the last VOS 7.2.2 binary and it does
> still work, so if you are experiencing this error still it may be due to
> another condition, thus are you able to provide a reproducible test case for
> it ?
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc. // http://www.openlinksw.com/
> Weblog -- http://www.openlinksw.com/blogs/
> LinkedIn -- http://www.linkedin.com/company/openlink-software/
> Twitter -- http://twitter.com/OpenLink
> Google+ -- http://plus.google.com/100570109519069333827/
> Facebook -- http://www.facebook.com/OpenLinkSoftware
> Universal Data Access, Integration, and Management Technology Providers
>
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
