Re: [Virtuoso-users] Temporary DB size and server restart

[Hugh Williams]

Hi Daniel,

As indicated in the docs at 
http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#ex_threadcleanupinterval
 

 :

TempDBSize
Controls the acceptable size of the temp database file. If on startup it's size 
(in MB) is greater than TempDBSize the file gets deleted and reset. This 
feature can be turned off by setting TempDBSize to 0. Note that the temp db 
file serves as an optimization storage only and doesn't have any client data 
that are not in either the main database files or the corresponding transaction 
log files.
If you Virtuoso database shutdown unexpectedly then the TempDB in use would not 
have been clean up which is what the message is indicated you should the 
consider manually removing as it contains no required data.

Thus you should focus on determining why the Virtuoso server shutdown 
unexpectedly, thus is anything of interest in the log prior to it shutting down 
or in the system log files that might indicate the cause of it shutdown ?

Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc.  //  http://www.openlinksw.com/
Weblog   -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter  -- http://twitter.com/OpenLink
Google+  -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers



> On 30 Mar 2016, at 17:18, Davis, Daniel (NIH/NLM) [C]  
> wrote:
> 
> It looks like this is merely a cache, and it’s OK for it to be bigger.It 
> doesn’t look like it has anything to do with my Virtuoso shutdown issues.
>  
> From: Davis, Daniel (NIH/NLM) [C] 
> Sent: Wednesday, March 30, 2016 12:09 PM
> To: virtuoso-users 
> Subject: Temporary DB size and server restart
>  
> I have a strange failure condition somewhere in my deployment.Virtuoso 
> goes down, and whenever I restart it, I see something like this in the log:
>  
> Unlinked the temp db file /usr/nlm/virtuoso/db/virtuoso-temp.db as its size 
> (8180MB) was greater than TempDBSize INI (10MB)
>  
> Now, that is a big difference.Why would the virtuoso-temp DB size get to 
> be so much bigger than the limit?What removes it?
>  
> Dan Davis, Systems/Applications Architect (Contractor),
> Office of Computer and Communications Systems,
> National Library of Medicine, NIH
>  
> --
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users



smime.p7s
Description: S/MIME cryptographic signature
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

[Virtuoso-users] OAuth request_token endpoint returns OAuth Verification Failed: Bad Signature

[Sunday Ayandokun]

Hello,

I am having issue connecting to the OAuth to get token.

I installed the ods_framework_dav.vad package and generated SPARQL application 
token and secret following the example here 
http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtOAuthSPARQL 



I read this http://docs.openlinksw.com/virtuoso/voauth.html 
 to understand how Oauth 
request should be made to Virtuoso Oauth endpoint.


http://localhost:8890/OAuth/request_token?oauth_version=1.0_nonce=72180780940317254641459358880_timestamp=1459299214_consumer_key=client_key_signature_method=HMAC-SHA1_signature=KmF8ngGHSBQJIDHTDw%2FWP%2Fdqgmc%3D
 


I am using a python library to sign the request.

client_key= token
client_secret = secret

client = oauth1.Client(client_key, client_secret=client_secret)
uri, headers, body = client.sign(request_token_url)

I am getting this response 'OAuth Verification Failed: Bad Signature'


Kindly point me to the best approach.


Kind Regards.
Sunday Ayandokun
University of Tartu
Tel: +37256724770
Skype: sunday.ayandokun

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Re: [Virtuoso-users] Temporary DB size and server restart

[Davis, Daniel (NIH/NLM) [C]]

It looks like this is merely a cache, and it's OK for it to be bigger.It 
doesn't look like it has anything to do with my Virtuoso shutdown issues.

From: Davis, Daniel (NIH/NLM) [C]
Sent: Wednesday, March 30, 2016 12:09 PM
To: virtuoso-users 
Subject: Temporary DB size and server restart

I have a strange failure condition somewhere in my deployment.Virtuoso goes 
down, and whenever I restart it, I see something like this in the log:

Unlinked the temp db file /usr/nlm/virtuoso/db/virtuoso-temp.db as its size 
(8180MB) was greater than TempDBSize INI (10MB)

Now, that is a big difference.Why would the virtuoso-temp DB size get to be 
so much bigger than the limit?What removes it?

Dan Davis, Systems/Applications Architect (Contractor),
Office of Computer and Communications Systems,
National Library of Medicine, NIH

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

[Virtuoso-users] Temporary DB size and server restart

[Davis, Daniel (NIH/NLM) [C]]

I have a strange failure condition somewhere in my deployment.Virtuoso goes 
down, and whenever I restart it, I see something like this in the log:

Unlinked the temp db file /usr/nlm/virtuoso/db/virtuoso-temp.db as its size 
(8180MB) was greater than TempDBSize INI (10MB)

Now, that is a big difference.Why would the virtuoso-temp DB size get to be 
so much bigger than the limit?What removes it?

Dan Davis, Systems/Applications Architect (Contractor),
Office of Computer and Communications Systems,
National Library of Medicine, NIH

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

[Virtuoso-users] Virtuoso tuning parameters for bulk loading

[Francesco Talo']

Hi all,

we are trying to perform on a Virtuoso Instance (version 7.2.2) a bulk 
loading of 100 ttl files using the command rdf_loader_run() with 2 cores 
(I have 7 cores totally on the machine). The size of every file is 
approximately  200 MB.

Our virtual machine where Virtuoso is running has 32 GB of memory totally.

In the virtuoso.ini file we have setup the following parameters

NumberOfBuffers  = 272
MaxDirtyBuffers= 200

following the advice for system with 32 GB.

It happened that after loading roughly 50 files the memory of the 
Virtuoso process (and of the entire machine) was completely exhausted 
causing the the stop of the Virtuoso process due to the complete 
freezing of the machine (all the 32 GB were used).

So we decided to tune the above parameters in order to allow Virtuoso to 
use up to 16 GB and the total loading was successful even if it was slow 
because Virtuoso quickly used all the available memory (16 GB). The only 
difference was that the machine was not struggling (still 16 GB free 
totally) and therefore Virtuoso process was able to work.

My question is how can I prevent Virtuoso to use all its available 
memory? Or how can I tell Virtuoso to perform a better management of the 
memory releasing it when it is not needed anymore? I assume that in the 
batch loading procedure once a file is loaded Virtuoso could remove 
completely from the memory what ever is connected to it immediately. But 
it seems that Virtuoso starts to remove things from the memory only when 
it is running out of it.

Thanks very much,
Francesco



--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140
___
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users