virtuoso-opensource
virtuoso-opensource copied to clipboard
Virtuoso 7.1 crashes on startup
Not knowing any other way to stop Virtuoso than with kill, I killed the Virtuoso process (with no flags), and now it refuses to start up. On start, the server says the following:
09:46:26 { Loading plugin 1: Type `plain', file `wikiv' in `/usr/local/Cellar/virtuoso/7.1.0/lib/virtuoso/hosting'
09:46:26 FAILED plugin 1: Unable to locate file }
09:46:26 { Loading plugin 2: Type `plain', file `mediawiki' in `/usr/local/Cellar/virtuoso/7.1.0/lib/virtuoso/hosting'
09:46:26 FAILED plugin 2: Unable to locate file }
09:46:26 { Loading plugin 3: Type `plain', file `creolewiki' in `/usr/local/Cellar/virtuoso/7.1.0/lib/virtuoso/hosting'
09:46:26 FAILED plugin 3: Unable to locate file }
09:46:26 OpenLink Virtuoso Universal Server
09:46:26 Version 07.10.3207-pthreads for Darwin as of Mar 13 2014
09:46:26 uses parts of OpenSSL, PCRE, Html Tidy
09:46:26 Database version 3126
09:46:26 SQL Optimizer enabled (max 1000 layouts)
09:46:28 Compiler unit is timed at 0.000132 msec
09:46:28 Free blob page refd start = 1308 L=1308
09:46:28 Free blob page refd start = 1308 L=1309
09:46:28 0 virtuoso-t 0x000000010c3fa9e9 print_trace + 54
09:46:28 1 virtuoso-t 0x000000010c3faa62 gpf_notice + 25
09:46:28 2 virtuoso-t 0x000000010bffbf51 blob_schedule_delayed_delete + 59
09:46:28 3 virtuoso-t 0x000000010c09e0a4 itc_delete_blobs + 332
09:46:28 4 virtuoso-t 0x000000010c1cac21 itc_delete_this + 34
09:46:28 5 virtuoso-t 0x000000010c1cb073 delete_node_run + 875
09:46:28 6 virtuoso-t 0x000000010c1cb881 delete_node_input + 114
09:46:28 7 virtuoso-t 0x000000010c1c774c qn_input + 444
09:46:28 8 virtuoso-t 0x000000010c1a243b ins_qnode + 327
09:46:28 9 virtuoso-t 0x000000010c1a3f78 code_vec_run_1 + 1582
09:46:28 10 virtuoso-t 0x000000010c1c773f qn_input + 431
09:46:28 11 virtuoso-t 0x000000010c1cf734 qr_subq_exec + 940
09:46:28 12 virtuoso-t 0x000000010c19eb30 ins_call + 2050
09:46:28 13 virtuoso-t 0x000000010c19f76a ins_call_vec + 145
09:46:28 14 virtuoso-t 0x000000010c1a0ebf code_vec_run_v + 404
09:46:28 15 virtuoso-t 0x000000010c1c7728 qn_input + 408
09:46:28 16 virtuoso-t 0x000000010c1ce7a6 qr_exec + 1852
09:46:28 17 virtuoso-t 0x000000010c1d08ae qr_rec_exec + 470
09:46:28 18 virtuoso-t 0x000000010c351524 xmls_proc + 610
09:46:28 19 virtuoso-t 0x000000010c3c644b bif_xml_load_schema_decl_impl + 1903
09:46:28 20 virtuoso-t 0x000000010c19e184 ins_call_bif + 136
09:46:28 21 virtuoso-t 0x000000010c1a4140 code_vec_run_1 + 2038
09:46:28 22 virtuoso-t 0x000000010c1c773f qn_input + 431
09:46:28 23 virtuoso-t 0x000000010c1ce7a6 qr_exec + 1852
09:46:28 24 virtuoso-t 0x000000010c1d068b qr_quick_exec + 458
09:46:28 25 virtuoso-t 0x000000010c061103 ddl_read_views + 833
09:46:28 26 virtuoso-t 0x000000010c061c69 read_proc_and_trigger_tables + 227
09:46:28 27 virtuoso-t 0x000000010c1d90a1 srv_global_init + 1866
09:46:28 28 virtuoso-t 0x000000010bfda29c main + 401
09:46:28 29 libdyld.dylib 0x00007fff8bd7a5fd start + 1
09:46:28 30 ??? 0x0000000000000002 0x0 + 2
09:46:28 GPF: blob.c:1320 Scheduling bad bl for delete at commit/rollback
GPF: blob.c:1320 Scheduling bad bl for delete at commit/rollback
09:46:28 Server received signal 11. Continuing with the default action for that signal.
To shutdown the Virtuoso server your can always connect with the isql
commandline tool and run:
checkpoint;
shutdown;
to stop the Virtuoso server ...
Due to the error you are getting, I would suggest checking if there is a virtuoso.trx
file of more than 0 bytes in place, and if so, rename it, and restart the server, such that it does not read the trx
file, and see if that enables the server to start?
If not then you may have to perform a crash recovery and restore of the database as detailed in the documentation.
Hi I experienced the same problem, it crashes after a few minutes, and the log shows the following :
19:12:46 Server received signal 11. Continuing with the default action for that signal.
First thing, if you're not certain you're running with the latest 7.2.8 binary, I would strongly advise you plan to apply this update after resolving this crash-near-launch, as the new version brings MANY fixes and enhancements relative to previous 7.x versions.
Next, it's worth discovering and telling us the exact version of Virtuoso you're running, which will be revealed by the first stanza of output from virtuoso-t -?
. There may be specific guidance to provide, depending on this detail.
The advice provided earlier on this issue is a good starting point toward resolving this for you. Please let us know what your experience is, when following that guidance.