[TYPO3-dev] Fail-safe mechanism for database connectivity problem

John Angel johnange at gmail.com
Fri Oct 6 08:50:23 CEST 2006


Ref: http://bugs.typo3.org/view.php?id=4332

The general idea is to prevent displaying error message "Database Error; The
current username, password or host was not accepted when the connection to
the database was attempted to be established" instead of real page.

I you stop mysql server, Typo3 will usually display it right away.

Resolution (beside expensive redundant database usage such as Oracle):

1/ All pages should be exported to static HTML pages on regular basis
(incrementally & automatically)

2/ If Typo3 detects database connectivity problem - it should display
static HTML pages previously exported in step 1.

The same idea can be used to run website powered by Typo3 faster.

Step (1) can be run in background after some page is being created/updated.
If [FE][pageCacheToExternalFiles] set to TRUE, the majority of things are
done, but not the complete (1).

As Michael Stucki noted, parts like the search engine which are purely
dynamic can never be cached and would never work without a database access,
but this part of site can be down. The goal is that majority of site is 
always up.

Please advise.


More information about the TYPO3-dev mailing list