Set-up monitoring for all our pre-dogfood servers for all the checks we have, but especially last successful re-index. If last successful re-index is more than x (ex.:3) days old, an email alert should be sent out.
Here is a real-world example of why having checks on all pre-dogfood servers would have made everything smoother. An unidentified commit in trunk is causing indexing to crash:
If we had been warned by a pre-dogfood sever, we could have found the commit and fixed the problem a few days after it appearing.
Note that this type of crash can also happen with some data not yet supported by the indexer, and thus, it can happen at any time, not just on code changes. And with a broken index, a Tiki site can be in big trouble because it doesn't just skip over the problem, it just dies. We are fortunate to have tons of data on all the pre-dogfood servers.
Because of issue 4609, we are stuck with respect to testing Unified Search with MySQL in trunk. Once this is solved, maybe something else will be discovered, so we to know ASAP so it's stable enough for Tiki12. This is crucial as per Search Dilemma
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
The URL for the show2.tiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|