Patrick,
i'm analyzing the problem with Roosevelt ...
Since the first downtime of the publisher machine, the Subscriber instance
is not receiving new triples and in the virtuoso.log it repeats the message:
17:48:50 Connected to replication server 'xx:'.
17:48:50 Requesting sync from '
Patrick,
this is not a stress test anymore. We are already in production mode. :)
It doesn't seem we are running short of memory but i think i can provide you a
sar file if you want. No swapping or so.
Anyway... do you think it is a good idea to reduce some memory parameters?
Cause all we're d
Hi Roosevelt,
we are experiencing downtime at our Virtuoso Database Server. The
message being generated at the log file is listed below:
14:23:49 GPF: bitmap.c:1552 next/prev of non-valid bit pos
This is an assert in the code to prevent the possibility of data
corruption. If you restart
Hi,
we are experiencing downtime at our Virtuoso Database Server. The message being
generated at the log file is listed below:
14:23:49 GPF: bitmap.c:1552 next/prev of non-valid bit pos
Ou virtuoso.ini config file:
; virtuoso.ini params, in general, cannot be changed while db is running
; Da
