Loading...
 

After an install with upgrade, tiki-admin displays the error "invalid database" ad-vitam

Status
Open
Subject
After an install with upgrade, tiki-admin displays the error "invalid database" ad-vitam
Version
8.x
Category
  • Error
  • Usability
  • Regression
  • Consistency
Feature
Database MySQL (MyISAM)
Installer (profiles, upgrades and server-related issues)
Submitted by
Bernard TREMBLAY
Lastmod by
Bernard TREMBLAY
Rating
(0)
Description

(Not yet checked for trunk)

After running installer with upgrade we get the message "Invalid database run installer..."

Running installer don't changes anything to database, but the message is still displayed.
It is a consistency "deadlock by soft".

The lonely thing generated by installer is a reset which needs to reset manually the admin account and clear all caches and cookies (see #4066 admin login problem).

!!!Going on 12/06/2011

I need to check the soft.

The message is sent by "installer" $installer instance of class installer in installib
It checks before the validation of patches on db using $installer->recordPatch($patch) for each one.
recordPatch function in installer records the patch into tiki_schema as done with his full date.

The concerned (got by a var_dump) patch is "20110904_shoutbox_def_tweetid_tiki"
is not into the tiki_schema table.
So the test functions, but the tiki-install failed to make this patch on another version OK, as it is defined.

__When it runs now (installer at 8.1 level) it don't tries to make the upgrade. This is the deadlock.
What is done if an old patch is not there !!!

More there is no report at all.__



Solution

? I began to look at, but I don't know this part of the soft.

!!!Going on 12/06/2011

In my opinion, there is no solution with a good reliability while :

  • we will not have soft part able to make a comparison of db schema included into the tiki.sql releases, and with get and check the actual schema and report with the actual tiki.sql schema
  • When the actual schema at the end of installer is not OK :

run a comparison to find which version is really installed

  • Generate a report which can be read by a link into the warning message.
  • Further tiki_schema could have two new columns the version which is the first, the latest version of validity. So when old patches are into the list the could be run automatically if they are valid.


When last functions is unable to treat all patches, the database needs to be treated by somebody who knows exactly what he is doing, the upgrade can be complex.

The whole problem is that it is impossible to be sure that an old patch as been well done without the treatment that I describe here. This process give the necessary security and reliability.
It needs work but it is not terrible.
The particular case treatment :
In my case it have been simple. The level of tiki_shoutbox was 4.1 but as empty I have replaced it with the last version. The installer in 8.1 could not run 20110904_shoutbox_def_tweetid_tiki2010 because 2010_better_column_fix_tiki.php had not run for unknown reason in his time (the other update of the same patch had been done normally before... nothing to explain).
We cannot, we must'nt risk bugs for this problem

To do ?

Workaround


!!!Going on 12/06/2011
Know everything above.

  • Add var dump into the function to dump the id of the patch var_dump($this->patches) in requiresUpdate() function of installib . This will display the patch(es) not done.
  • You will find the sql instruction with the name into the dir

installer/schema

  • Directly make the upgrade with phphmyadmin (if mysql) manually
  • Add the record to tiki_schema
Importance
9 high
Priority
45
Demonstrate Bug (Tiki 19+)
Please demonstrate your bug on show2.tiki.org
 About show2.tiki.org

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.

Version: Create show2.tiki.org instance
Demonstrate Bug (older Tiki versions)
Please demonstrate your bug on show.tikiwiki.org
 About show.tikiwiki.org

To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.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 show.tikiwiki.org.

Version: Create show.tikiwiki.org instance
Ticket ID
4072
Created
Saturday 03 December, 2011 19:11:27 GMT-0000
by Bernard TREMBLAY
LastModif
Wednesday 07 December, 2011 02:21:32 GMT-0000

Attachments

 filenamecreatedhitscommentversionfiletype 
8.1-Invalid-db-after-installer-01.jpg 03 Dec 11 19:13 GMT-000064The invalid db message8.1
8.1-Invalid-db-after-installer-02.jpg 07 Dec 11 02:27 GMT-000069The trac - var_dump8.1-rt


Keywords

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.

Accessibility (WAI & 508)
Accounting
Administration
Ajax
Articles & Submissions
Backlinks
Banner
Batch
BigBlueButton audio/video/chat/screensharing
Blog
Bookmark
Browser Compatibility
Calendar
Category
Chat
Comment
Communication Center
Consistency
Contacts Address book
Contact us
Content template
Contribution
Cookie
Copyright
Credits
Custom Home (and Group Home Page)
Database MySQL - MyISAM
Database MySQL - InnoDB
Date and Time
Debugger Console
Diagram
Directory (of hyperlinks)
Documentation link from Tiki to doc.tiki.org (Help System)
Docs
DogFood
Draw -superseded by Diagram
Dynamic Content
Preferences
Dynamic Variable
External Authentication
FAQ
Featured links
Feeds (RSS)
File Gallery
Forum
Friendship Network (Community)
Gantt
Group
Groupmail
Help
History
Hotword
HTML Page
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Import-Export
Install
Integrator
Interoperability
Inter-User Messages
InterTiki
jQuery
Kaltura video management
Kanban
Karma
Live Support
Logs (system & action)
Lost edit protection
Mail-in
Map
Menu
Meta Tag
Missing features
Visual Mapping
Mobile
Mods
Modules
MultiTiki
MyTiki
Newsletter
Notepad
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Organic Groups (Self-managed Teams)
Packages
Payment
PDF
Performance Speed / Load / Compression / Cache
Permission
Poll
Profiles
Quiz
Rating
Realname
Report
Revision Approval
Scheduler
Score
Search engine optimization (SEO)
Search
Security
Semantic links
Share
Shopping Cart
Shoutbox
Site Identity
Slideshow
Smarty Template
Social Networking
Spam protection (Anti-bot CATPCHA)
Spellcheck
Spreadsheet
Staging and Approval
Stats
Survey
Syntax Highlighter (Codemirror)
Tablesorter
Tags
Task
Tell a Friend
Terms and Conditions
Theme
TikiTests
Federated Timesheets
Token Access
Toolbar (Quicktags)
Tours
Trackers
TRIM
User Administration
User Files
User Menu
Watch
Webmail and Groupmail
WebServices
Wiki History, page rename, etc
Wiki plugins extends basic syntax
Wiki syntax text area, parser, etc
Wiki structure (book and table of content)
Workspace and perspectives
WYSIWTSN
WYSIWYCA
WYSIWYG
XMLRPC
XMPP




Useful Tools