Virtuoso was terminated by the out-of-memory killer. Most of my Virtuoso
nodes had thread cleanup and resource cleanup set to 1, but not the one that
failed. So, this was a case of me not changing ThreadCleanupInterval and
ResourceCleanupInterval when I installed this node. I don’t trust my install
script enough, and most people use puppet/chef or other tools.
From: Hugh Williams [mailto:hwilli...@openlinksw.com]
Sent: Wednesday, March 30, 2016 4:53 PM
To: Davis, Daniel (NIH/NLM) [C] <daniel.da...@nih.gov>
Cc: virtuoso-users <virtuoso-users@lists.sourceforge.net>
Subject: Re: [Virtuoso-users] Temporary DB size and server restart
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]
<daniel.da...@nih.gov<mailto:daniel.da...@nih.gov>> 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
<virtuoso-users@lists.sourceforge.net<mailto:virtuoso-users@lists.sourceforge.net>>
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&iu=/4140_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net<mailto:Virtuoso-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
------------------------------------------------------------------------------
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&iu=/4140
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
