Can't get 2.3.0 install to work - SQL Error

Hey folks,

I’ve been on this for some days but I’m stuck now. This is where I am:

# CMS Version: Xibo 2.3.0
# Installation Method: Custom install
# Operating System: Ubuntu 18.04.3
# Issue

Install fails with error “SQLSTATE[HY000]: General error: 1364 Field ‘edit’ doesn’t have a default value”

Background: I’ve had numerous issues installing Xibo. I ran 2.1.0 and 1.8 before that for quite some time. My virtual machine crashed so I decided to redo the install. The pre install check is all checkmarks, I also had rewrite misery but that was solved as well. I now run into this SQL error and I do not know what to do. I’m no SQL expert. The instal_log.txt states this:

[2020-02-21 21:09:19] INSTALL.INFO: Installer Step 1 [] {"uid":"7b34df5","method":"GET","route":"/"}
[2020-02-21 21:12:21] INSTALL.INFO: Installer Step 1 [] {"uid":"655cef8","method":"GET","route":"/"}
[2020-02-21 21:27:55] INSTALL.INFO: Installer Step 1 [] {"uid":"cb307a4","method":"GET","route":"/"}
[2020-02-21 21:32:05] INSTALL.INFO: Installer Step 1 [] {"uid":"a7bb6a9","method":"GET","route":"/"}
[2020-02-21 21:32:40] INSTALL.INFO: Installer Step 1 [] {"uid":"b5564d2","method":"GET","route":"/"}
[2020-02-21 21:33:56] INSTALL.INFO: Installer Step 1 [] {"uid":"0671d8b","method":"GET","route":"/"}
[2020-02-21 21:39:09] INSTALL.INFO: Installer Step 1 [] {"uid":"71754a5","method":"GET","route":"/"}
[2020-02-21 21:39:43] INSTALL.INFO: Installer Step 1 [] {"uid":"dca233a","method":"GET","route":"/"}
[2020-02-21 21:47:15] INSTALL.INFO: Installer Step 1 [] {"uid":"4454927","method":"GET","route":"/"}
[2020-02-21 21:47:17] INSTALL.INFO: Installer Step 1 [] {"uid":"37a65ff","method":"GET","route":"/"}
[2020-02-21 21:48:10] INSTALL.INFO: Installer Step 1 [] {"uid":"83dba29","method":"GET","route":"/"}
[2020-02-21 21:50:12] INSTALL.INFO: Installer Step 1 [] {"uid":"47ff874","method":"GET","route":"/"}
[2020-02-21 21:53:17] INSTALL.INFO: Installer Step 1 [] {"uid":"5fe62db","method":"GET","route":"/"}
[2020-02-21 21:58:53] INSTALL.INFO: Installer Step 1 [] {"uid":"15573f1","method":"GET","route":"/"}
[2020-02-21 21:59:12] INSTALL.INFO: Installer Step 1 [] {"uid":"8b59635","method":"GET","route":"/"}
[2020-02-21 22:07:09] INSTALL.INFO: Installer Step 1 [] {"uid":"6d628e4","method":"GET","route":"/"}
[2020-02-21 22:07:11] INSTALL.INFO: Installer Step 1 [] {"uid":"28d6e88","method":"GET","route":"/"}
[2020-02-21 22:11:16] INSTALL.INFO: Installer Step 1 [] {"uid":"2ec3327","method":"GET","route":"/"}
[2020-02-21 22:13:23] INSTALL.INFO: Installer Step 1 [] {"uid":"6deac03","method":"GET","route":"/"}
[2020-02-21 22:13:40] INSTALL.INFO: Installer Step 1 [] {"uid":"a5f0115","method":"GET","route":"/"}
[2020-02-21 22:13:43] INSTALL.INFO: Installer Step 1 [] {"uid":"c272fb4","method":"GET","route":"/"}
[2020-02-21 22:15:39] INSTALL.INFO: Installer Step 1 [] {"uid":"522ea1f","method":"GET","route":"/"}
[2020-02-21 22:22:30] INSTALL.INFO: Installer Step 1 [] {"uid":"bd2e1bf","method":"GET","route":"/"}
[2020-02-21 22:36:26] INSTALL.INFO: Installer Step 1 [] {"uid":"5066a97","method":"GET","route":"/"}
[2020-02-21 22:38:28] INSTALL.INFO: Installer Step 1 [] {"uid":"3a9b3c4","method":"GET","route":"/"}
[2020-02-21 22:38:29] INSTALL.INFO: Installer Step 1 [] {"uid":"e777509","method":"GET","route":"/"}
[2020-02-21 22:55:16] INSTALL.INFO: Installer Step 1 [] {"uid":"51d6f6b","method":"GET","route":"/"}
[2020-02-21 23:09:26] INSTALL.INFO: Installer Step 1 [] {"uid":"5723872","method":"GET","route":"/"}
[2020-02-21 23:29:34] INSTALL.INFO: Installer Step 1 [] {"uid":"24a6982","method":"GET","route":"/"}
[2020-02-21 23:29:55] INSTALL.INFO: Installer Step 2 [] {"uid":"73d9359","method":"GET","route":"/2"}
[2020-02-21 23:31:12] INSTALL.INFO: Installer Step 3 [] {"uid":"a118f6d","method":"POST","route":"/3"}
[2020-02-21 23:31:12] INSTALL.INFO: Setting unlimited max execution time. [] {"uid":"a118f6d","method":"POST","route":"/3"}

I now get the maintenance display when I open the web console
“The CMS is temporarily off-line as an upgrade is in progress. Please check with your system administrator for updates or refresh your page in a few minutes.”

Does anyone have a clue how to fix this? I’m at a loss here.

Unfortunately we have a small problem with the install on MySQL 5.7 - see here New install xibo : Error SQL during install

Sorry for this - we will be addressing in 2.3.1

Hey Dan,

Thanks for thatI It was sort of driving me mad, so good to know it wasn’t me :slight_smile:

Not to add pressure (totally not, it’s just a home install with 2 displays that publish local news and weather during the morning and evening family rush) but do you guys have a timeline on the release?

Greetz,

Alex

1 Like

Thats a cool use case!!

We dont have a timeline for that yet - we usually collect a few more issues before making a release, unless theres anything major. It will be a few weeks time at a guess.

As you’ve got a custom install you could just patch the file in the meantime?

Hey Dan!

Thanks for the compliment. It took me a while to find you guys but now that I’ve got it, I’m getting quite skilled in publishing local news, weather conditions and traffic to work on a daily basis :slight_smile:

For now I installed 2.2.3 which runs fine. When 2.3.1 is published, I’ll give the upgrade another go.

1 Like

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.