ClearFoundation Tracker - ClearOS
View Issue Details
0001226ClearOSapp-system-database - System Databasepublic2013-07-15 10:582013-07-15 11:22
user2 
user2 
immediatecrashsometimes
closedfixed 
 
6.4.0 Updates6.4.0 Updates 
0001226: System database may refuse to start in cases where software updates were not applied
If the system-mysql update is installed before the app-system-database-core update, then the my.cnf file will change (*** see note below). That ordering issue can't happen on new installs because of the install wizard, but it certainly could have happened if:

- One of the test repos was used at some point

- Software updates were disabled over a certain time period and the app-system-database-core update (released weeks before the system-mysql update) was never installed

*** this is funky but understandable RPM behavior. If a configuration file has changed, an RPM install will not overwrite the file. However, if a configuration file has not changed, an upgraded configuration file will take its place. I understand the reasoning behind this logic, but it causes surprises and grief when it comes to software maintenance.
No tags attached.
Issue History
2013-07-15 10:58user2New Issue
2013-07-15 11:19user2Assigned To => user2
2013-07-15 11:19user2Statusnew => confirmed
2013-07-15 11:20user2Checkin
2013-07-15 11:20user2Note Added: 0000928
2013-07-15 11:22user2Statusconfirmed => closed
2013-07-15 11:22user2Resolutionopen => fixed
2013-07-15 11:22user2Fixed in Version => 6.4.0 Updates

Notes
(0000928)
user2   
2013-07-15 11:20   
Source Code Changelog
---------------------------------------------------
- Reset ib_logfile due to potential my.cnf change [tracker 0001226]

File Changes
---------------------------------------------------
Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=6218 [^]
U webconfig/apps/system_database/trunk/deploy/info.php
U webconfig/apps/system_database/trunk/deploy/upgrade
U webconfig/apps/system_database/trunk/packaging/app-system-database.spec