Hi Hugh, It works again after a server restart so it might be a very intermittent issue, but if you can replicate it with a server that is being fairly regularly given /sparql INSERT queries with the log_enable 2 pragma instruction it would be nice to see if a permanent solution can be found just incase it happens again in future.
Cheers, Peter > >From: Hugh Williams <hwilli...@openlinksw.com> >To: Peter Ansell <p_ans...@yahoo.com> >Cc: Virtuoso Users List <virtuoso-users@lists.sourceforge.net> >Sent: Monday, 10 August, 2009 9:57:52 AM >Subject: Re: [Virtuoso-users] Log enable/disable failure apparently causing >conductor to not display > > >Hi Peter, > > >Has this failure to load the conductor just started occurring as I assume you >have been using this log_enable option for sometime now ? > > >Are you performing these inserts using the Conductor SPARQL UI to perform your >inserts or is a separate program being used for this ? > > >Also, are you saying if the Virtuoso server is restarted the conductor works >but then fails to load after the inserts are started ? > > >Best Regards >Hugh Williams >Professional Services >OpenLink Software >Web: http://www.openlinksw.com >Support: http://support.openlinksw.com >Forums: http://boards.openlinksw.com/support > > > > >On 9 Aug 2009, at 23:35, Peter Ansell wrote: > >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 >> >> >> >> >>------------------------------------------------------------------------------ >>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >>trial. Simplify your report design, integration and deployment - and focus on >>what you do best, core application coding. Discover what's new with >>Crystal Reports now. http://p.sf.net/sfu/bobj-july >>_______________________________________________ >>Virtuoso-users mailing list >>Virtuoso-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/virtuoso-users > ____________________________________________________________________________________ Access Yahoo!7 Mail on your mobile. Anytime. Anywhere. Show me how: http://au.mobile.yahoo.com/mail
