Rajeev J Sebastian wrote:
> Hi,
> 
> I am experiencing random hangs of the server when using the SPARQL
> endpoint. Looking in the error log also echoed on console, there is no
> information whatsoever. doing a "kill <pid>" shows "Server received
> signal 2" or some such. However, the server doesnt exit.
> 
> I have to issue a SIGTERM for it to actually exit. restarting the
> server of course replays the transaction logs, and the data seems
> fine. This happens every once in a while, and I have to restart
> several times. However, after 3-4 restarts, suddenly everything
> becomes fine and it works until the next time this happens a few days
> later.
> 
> So, a couple of questions:
> 1) has anyone seen this before ?
> 2) if so, any reason why it occurs and any fixes/workarounds ?
> 3) any way to increase the verbosity of the error log and atleast show
> what its doing at a particular time ?
> 

I can make a couple of suggestions about #3.

a) Enable lots of debug tracing (will require PLDebug=1 in the ini-file):

http://docs.openlinksw.com/virtuoso/fn_trace_on.html

b) As & when it appears hung, try accessing the isql port:

isql> status();

c) see if you can tie it down to particular SPARQL queries somehow?

HTH,

~Tim
-- 
Tim Haynes
Product Development Consultant
OpenLink Software
<http://www.openlinksw.com/>

Reply via email to