Hi Hugh, On 29-03-16 01:00, Hugh Williams wrote: > Hi Roland, > > Is the log snippet below from the initial crash or the subsequent failed > attempt to restart or is the same error occurring in both cases ? The log is from the subsequent failed attempt to restart the server. > Is a core file being created (assuming "ulimit -c unlimited” set) such that a > gdb back trace can be obtained ? No, that is not set ... no core file created > > Can you provide a copy of the virtuoso.log file ? I'll send you a link by mail. > > Do you have online backups and audit log trails in place from which the > database can be recovered to a known good state, as indicated in section > "6.1.5.1. Log Audit Trail" of the documentation link ? No, Audit log trail is set to 0 in virtuoso.ini so I suppose we have no audit log trail...
Looks not so good from as I look at my answers above..... :( Thanks, Roland > > Certainly upgrading to to the latest VOS 7.2.2 release is advised but it will > not necessarily resolve the problem thus come form of recovery will still be > required ... > > 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 > > > >> On 28 Mar 2016, at 20:20, Roland Cornelissen <metamatter...@gmail.com> wrote: >> >> Hi, >> >> Our VOS instance crashed with a segmentation fault and cann't be started >> again. Below the logmesaage when it is restarted and crashes. >> Before we start the recovery procedure as is described in [1], paragraph >> '6.1.5.4.3. Crash Recovery When The Normal Crash Recovery Fails' >> is there any other trick in the book to try? >> The VOS version is Version 07.20.3212-pthreads for Linux as of Mar 19 2015 >> >> It is probably a good idea to first upgrade to the latest development >> version.... Could that help anything in recovering from this situation, >> before we start the recovery procedure? >> >> Thanks, >> Roland >> >> [1] http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#backup >> >> >> >> log: >> >> 18:47:30 Compiler unit is timed at 0.001480 msec >> 18:48:25 Free blob page refd start = 1325 L=1325 >> 18:48:25 Free blob page refd start = 1325 L=1326 >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x924968] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x9249d6] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x86f88f] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x4fdae7] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t(dc_itc_delete+0xd9) >> [0x670d49] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t(itc_vec_row_check+0x30b) >> [0x67c04b] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x54c387] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x54d109] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x67e28f] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x612590] >> 18:48:25 >> /opt/virtuoso/ose/7.2.0/bin/virtuoso-t(table_source_input_unique+0xa7) >> [0x61b107] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x612f05] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x6133ce] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x647e91] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x612f05] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t(insert_node_run+0x354) >> [0x614164] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t(insert_node_input+0x9e) >> [0x61457e] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x5e94f1] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x5e95f7] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x5e6830] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x613012] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x5e4d46] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x5e5895] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x5e7c3c] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x612eee] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x618d81] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x6197d6] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x8a9389] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x8a944c] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x61c3f0] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x624847] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x4590a0] >> 18:48:25 /lib64/libc.so.6(__libc_start_main+0xfd) [0x360b41ed5d] >> 18:48:25 /opt/virtuoso/ose/7.2.0/bin/virtuoso-t() [0x453cb9] >> 18:48:25 GPF: blob.c:1320 Scheduling bad bl for delete at commit/rollback >> GPF: blob.c:1320 Scheduling bad bl for delete at commit/rollback >> start.sh: line 13: 22663 Segmentation fault (core dumped) >> /opt/virtuoso/ose/7.2.0/bin/virtuoso-t -f -c "$iniFile" >> >> >> ------------------------------------------------------------------------------ >> Transform Data into Opportunity. >> Accelerate data analysis in your applications with >> Intel Data Analytics Acceleration Library. >> Click to learn more. >> http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 >> _______________________________________________ >> Virtuoso-users mailing list >> Virtuoso-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/virtuoso-users ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 _______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
