Hi all,
in the light of recent events (forum posts and other requests) related to
BerkeleyDB problems, died assp and SEGV signals,
I have made some additions to the GUI description of 'DBdriver'. These
description changes will be available in the next version.
How ever - I think, it is important to show them here as a preview.
Anyone of you, who uses BerkeleyDB in assp, should read the following.
'DBdriver','database driver name'
.....
..... nothing changed here
.....
If you specify BerkeleyDB here, the values for myhost, mydb, myuser and
mypassword will be ignored.
All possible BerkeleyDB option must be defined here - the option for
'-Filename' is already set by ASSP!
Options could be defined for example:
BerkeleyDB,-Pagesize=>number,-Env=>[-Cachesize=>number,-Mode=>mode,...,...],...,...
If '-Env=>[-Cachesize=>number]' (number in bytes) is specified, this cache
size will be used at minimum
for every single list. Setting the cache size is not recommended (as long
as do not you really know what you do),
because ASSP does automatically calculate the right cache for every list
at startup. You may setup configuration
values for any BerkeleyDB, creating a file DB_CONFIG (case sensitive)
(
http://www.oracle.com/technology/documentation/berkeley-db/db/ref/env/db_config.html
)
in the corresponding directory ./tmpDB/[list]. Please use the BerkeleyDB
documentation, if you don't know the
syntax of this file. Any value defined in that file will overwrite the
corresponding internal ASSP configuration
for this DB.
As with each other database engine, you should know how to handle
BerkeleyDB large shared BDB-environments
(CDB - DB_INIT_CDB and DB_INIT_MPOOL), how to repair database files and
all the other important stuff.
ASSP has several buildin mechanism to detect and repair corrupt BerkeleyDB
files, but they may not work in every case!
If you have specified BerkeleyDB here and your system shows unexpected
SEGV or ASSP died unexpected,
think about the BDB settings. If you can't fix such an issue, it may be an
good idea to switch over to MySQL or
another database engine.
KEEP IN MIND:
BerkeleyDB files are shared opened and accessed by all threads using
BDB-CDB.
The last terminated thread closes the BDB-files (shutdown the BDB-engine)
for the systems file system.
It is important, that (especially) linux and unix system shutdown scripts
are waiting until ALL assp/perl
processes are ended (this may take up to one minute - see
MaxFinConWaitTime )!
Otherwise, the kernel will kill the assp/perl process at shutdown and the
BerkeleyDB DB-files and environment-files
WILL BE DESTROYED and cause to 100% unexpected behavior or crashes at the
next start or run!
The same applies to Windows systems, if assp is not running as system
service - the windows
system-service-manager will wait until the process is finished.
Thomas
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
