Hi all,
I am using a particular server for a large number of constant and concurrent
SPARUL INSERT's and it seems that it has broken itself somehow because the
conductor doesn't show anymore. The SPARQL interface and INSERTS and
CONSTRUCT's are still actually working but it is still worrying that the
conductor could be broken so easily.
As I was told to do in a past thread related to concurrency failures I added
"define sql:log-enable 2 " to the front of all of my SPARUL queries to work
around the issue with multiple concurrent SPARUL INSERT queries breaking the
internal Virtuoso locking (or deadlock prevention) model, but it is possible
that it has now broken the conductor.
The message I am seeing whenever I try to access the /conductor page is:
"Error 42000
SR471: log_enable () called twice to disable the already disabled log output
There are no errors at all in the log since the last reboot so the log file
won't be any help, and I am not sure I can replicate the issue after I reboot
the server. The really puzzling thing about this error is that from a naive
point of view it doesn't look fatal but it has fatal consequences! What could
go wrong with someone trying to confirm that the log is disabled by calling the
function again? Does the function have un-log-related sideeffects?
The server version according to the logs is:
"17:14:18 OpenLink Virtuoso Universal Server
17:14:18 Version 05.11.3039-pthreads for Linux as of Jul 9 2009"
Cheers,
Peter
__________________________________________________________________________________
Find local businesses and services in your area with Yahoo!7 Local.
Get started: http://local.yahoo.com.au
