Upgrade 1.5.10.2253 to 1.5.10.2482
-
Hello,
I try to upgrade to the last 1.5.10 and I have this :
* Updating Database...........................................Failed! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! The installer was not able to run all the way to the end as !! !! something has caused it to fail. The following few lines are !! !! from the error log file which might help us figure out what's !! !! wrong. Please add this information when reporting an error. !! !! As well you might want to take a look at the full error log !! !! in /root/fogproject-1.5.10.2482/bin/error_logs/fog_error_1.5.10.2482.log !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 17900K .......... .......... .......... .......... .......... 130M 17950K .......... .......... .......... .......... ........ 142M=0,1s 2026-10-09 11:39:11 (128 MB/s) - ‘/home//fogDBbackups/fog_sql_1.5.10.2482_20261009_113907.sql’ enregistré [18430465]Trying with GUI, I have this :
The following errors occurred
Update ID: 284Database Error:
Failed to query: Error: SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for ‘hostSecTime’ Error Message: Error Code: “42000”, Error Message: [“42000”,1067,“Invalid default value for ‘hostSecTime’”], Debug: SQL: [77] ALTER TABLE
hostsMODIFY COLUMNhostLastDeployDATETIME NULL DEFAULT NULL
Params: 0
SQL: ALTER TABLEhostsMODIFY COLUMNhostLastDeployDATETIME NULL DEFAULT NULL
Params: Array
(
)
ErrorInfo: Array
( [0] => 42000 [1] => 1067 [2] => Invalid default value for ‘hostSecTime’
)
Debug: SQL: [77] ALTER TABLEhostsMODIFY COLUMNhostLastDeployDATETIME NULL DEFAULT NULL
Params: 0
Variable contains:Array
( [0] => ALTER TABLEhostsMODIFY COLUMNhostLastDeployDATETIME NULL DEFAULT NULL [1] => UPDATEhostsSEThostLastDeploy= NULL WHEREhostLastDeployIS NOT NULL AND YEAR(hostLastDeploy) = 0 [2] => ALTER TABLEhostsMODIFY COLUMNhostSecTimeTIMESTAMP NULL DEFAULT NULL [3] => UPDATEhostsSEThostSecTime= NULL WHEREhostSecTimeIS NOT NULL AND YEAR(hostSecTime) = 0 [4] => ALTER TABLEimagesMODIFY COLUMNimageLastDeployDATETIME NULL DEFAULT NULL [5] => UPDATEimagesSETimageLastDeploy= NULL WHEREimageLastDeployIS NOT NULL AND YEAR(imageLastDeploy) = 0 [6] => ALTER TABLEimagingLogMODIFY COLUMNilFinishTimeDATETIME NULL DEFAULT NULL [7] => UPDATEimagingLogSETilFinishTime= NULL WHEREilFinishTimeIS NOT NULL AND YEAR(ilFinishTime) = 0 [8] => ALTER TABLEinventoryMODIFY COLUMNiDeleteDateDATETIME NULL DEFAULT NULL [9] => UPDATEinventorySETiDeleteDate= NULL WHEREiDeleteDateIS NOT NULL AND YEAR(iDeleteDate) = 0 [10] => ALTER TABLEmulticastSessionsMODIFY COLUMNmsStartDateTimeDATETIME NULL DEFAULT NULL [11] => UPDATEmulticastSessionsSETmsStartDateTime= NULL WHEREmsStartDateTimeIS NOT NULL AND YEAR(msStartDateTime) = 0 [12] => ALTER TABLEmulticastSessionsMODIFY COLUMNmsCompleteDateTimeDATETIME NULL DEFAULT NULL [13] => UPDATEmulticastSessionsSETmsCompleteDateTime= NULL WHEREmsCompleteDateTimeIS NOT NULL AND YEAR(msCompleteDateTime) = 0 [14] => ALTER TABLEsnapinTasksMODIFY COLUMNstCompleteDateDATETIME NULL DEFAULT NULL [15] => UPDATEsnapinTasksSETstCompleteDate= NULL WHEREstCompleteDateIS NOT NULL AND YEAR(stCompleteDate) = 0 [16] => ALTER TABLEtasksMODIFY COLUMNtaskCheckInDATETIME NULL DEFAULT NULL [17] => UPDATEtasksSETtaskCheckIn= NULL WHEREtaskCheckInIS NOT NULL AND YEAR(taskCheckIn) = 0 [18] => ALTER TABLEtasksMODIFY COLUMNtaskScheduledStartTimeDATETIME NULL DEFAULT NULL [19] => UPDATEtasksSETtaskScheduledStartTime= NULL WHEREtaskScheduledStartTimeIS NOT NULL AND YEAR(taskScheduledStartTime) = 0 [20] => ALTER TABLEuserTrackingMODIFY COLUMNutDateDATE NULL DEFAULT NULL [21] => UPDATEuserTrackingSETutDate= NULL WHEREutDateIS NOT NULL AND YEAR(utDate) = 0
)
Database SQL:ALTER TABLE
hostsMODIFY COLUMNhostLastDeployDATETIME NULL DEFAULT NULL -
@jmeyer This is a bug in schema step 284 on MySQL. Your data did not cause it.
Cause: on MySQL, an ALTER TABLE re-checks the default of every column. Your hosts.hostSecTime still has the old default 0000-00-00 00:00:00. MySQL’s default sql_mode (NO_ZERO_DATE) refuses that default, so the step stops. MariaDB servers do not show the problem.
Fix: https://github.com/FOGProject/fogproject/pull/1838 is merged into dev-branch. While the steps run, the schema updater now relaxes the zero-date check for its own session.
The fix reaches the stable release on October 11. To continue now, install from dev-branch:
cd /root git clone -b dev-branch https://github.com/FOGProject/fogproject.git fogproject-dev cd fogproject-dev/bin ./installfog.sh -yThe failed step changed nothing in your database, so you do not need to restore the backup. The backup the installer made is still at /home/fogDBbackups/fog_sql_1.5.10.2482_20261009_113907.sql.