12.x svn LTS recent regression: mysql table for unified index doesn't exist and page edit displays fatal error (even if edition saved properly)
I recently noticed that, in a few tikis that I migrated from a server to a new one. They were working fine for a few days, unified search index being updated on a cron job at night time, page edits fine, etc.
And suddenly, page edits in some tiki sites started to display this fatal error message of missing mysql table for the index (using Mysql Full Text Search engine for the advanced unified search).
I also noticed that the index update failed for one site because some tracker field had a perm name too long for Mysql Full Text Search as unified search engine.
Anyway, I'll dop a note here just in case other people start to experience similar issues, so that we can look for common patterns to track the issue down.
In myc ase, workaround was to manually reindex again the site through console. Then no error was shown in further wiki page edits for the same users, etc.
No idea what happened, but at some point in May or June 2015, this error might have stopped existing. I've reverted the production sites to default value again (index updated automatically upon site changes, and index refreshed only once per day based on cron job) and site doesn't show that error any more.
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|