Infralliance Posted January 16, 2016 Report Share Posted January 16, 2016 Oh noes! SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'inv_display_due_date_draft-1' for key 'PRIMARY' on line 124 in /var/www/admin.infralliance.com/lib/model.php Printing Stack Trace: #0 /var/www/admin.infralliance.com/lib/model.php(124): PDOStatement->execute(Array) #1 /var/www/admin.infralliance.com/components/upgrades/tasks/upgrade3_5_0_b1.php(93): Model->query('INSERT INTO `co...', '1') #2 /var/www/admin.infralliance.com/components/upgrades/tasks/upgrade3_5_0_b1.php(52): Upgrade3_5_0B1->addInvoiceDateDueSettings() #3 /var/www/admin.infralliance.com/components/upgrades/upgrades.php(226): Upgrade3_5_0B1->process('addInvoiceDateD...') #4 /var/www/admin.infralliance.com/components/upgrades/upgrades.php(75): Upgrades->processObject(Object(Upgrade3_5_0B1), NULL) #5 /var/www/admin.infralliance.com/app/controllers/admin_upgrade.php(102): Upgrades->start('3.4.3', '3.6.1') #6 /var/www/admin.infralliance.com/lib/dispatcher.php(111): AdminUpgrade->process() #7 /var/www/admin.infralliance.com/index.php(21): Dispatcher::dispatch('/index.php/admi...') #8 {main} Somebody has a clue how I could have that fixed? :\ Although this error is appearing, the version number has changed in the admin portal. How can I be really sure the blesta install is ok and will behave properly? Quote Link to comment Share on other sites More sharing options...
0 Michael Posted January 16, 2016 Report Share Posted January 16, 2016 The version number goes by one of the licensing files. Can you tell us what the DB version is? The database > Settings table > database_version value Quote Link to comment Share on other sites More sharing options...
0 Infralliance Posted January 16, 2016 Author Report Share Posted January 16, 2016 mysql> SHOW VARIABLES LIKE "%version%"; +-------------------------+-------------------------+ | Variable_name | Value | +-------------------------+-------------------------+ | innodb_version | 5.5.46 | | protocol_version | 10 | | slave_type_conversions | | | version | 5.5.46-0ubuntu0.14.04.2 | | version_comment | (Ubuntu) | | version_compile_machine | x86_64 | | version_compile_os | debian-linux-gnu | +-------------------------+-------------------------+ 7 rows in set (0.00 sec) Quote Link to comment Share on other sites More sharing options...
0 Michael Posted January 16, 2016 Report Share Posted January 16, 2016 No database version this is nothing to do with mysql this is the database version for Blesta. Quote Link to comment Share on other sites More sharing options...
0 Tyson Posted January 18, 2016 Report Share Posted January 18, 2016 Did you make any manual changes to the database, or run the upgrade script more than once if it had failed? Several database changes have been made form v3.4.3 and v3.6.1. You'll have to check what partial changes it did make in order to manually adjust the upgrade script to perform the rest. You'll need to see which company settings have been added at the point of the error: SELECT `key`, `value`, `company_id` FROM `company_settings` WHERE `key` LIKE 'inv_display_due%' ; Do you have these three keys set for each company? inv_display_due_date_draft inv_display_due_date_proforma inv_display_due_date_inv What is the structure of the coupons table? DESCRIBE `coupons`; What is the structure of the package options table? DESCRIBE `package_options`; Quote Link to comment Share on other sites More sharing options...
Question
Infralliance
Somebody has a clue how I could have that fixed? :\
Although this error is appearing, the version number has changed in the admin portal. How can I be really sure the blesta install is ok and will behave properly?
Link to comment
Share on other sites
4 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.