I have run into a few issues after an upgrade of my 1.8.0-beta dev Xibo environment today. It was a non-docker environment, running with the DB external in AWS RDS. So I downloaded the xibo-docker folder for 1.8.0 and added the shared folder and subfolders manually. Then I copied the contents of my library folder to the new location and didn’t get any errors along the way. I took a data export using MySQL Admin from the current DB, but before I did that, I created a cms user account and set a complex password. I then changed that dump to import.sql and dropped it in the backup directory. I put the MySQL password in the config file and saved it. I stopped and removed apache2 and then ran the docker upgrade. It all seemed to work without issues, but once I logged into the upgraded server I started seeing issues.
First I am not able to see any media, yet I can see the media when I connect to the DB inside the docker container. I also cannot see any layouts, but if I select a display, I am able to see the layouts when I go to set the default layout for that display. When I go to the schedule section, there is no calendar showing. Again, I can see schedules in the DB, but not even a calendar to show them on in the portal. A few other things weren’t saved. For example, the CMS secret key field was blank.
I have a backup of the server that I can roll back to, but I would love to see if you had any thoughts.
The user you’re logging in as definitely has permission to see these things inside the CMS? Can you try with the xibo_admin user. It will be the same password as before your import.
I’m wondering if the export file you created has a CREATE DATABASE line in it?
If it does, we might get the symptoms you have.
Can you check the top of your import.sql(.done) file and see?
It should be something like this:
-- MySQL dump 10.13 Distrib 5.5.54, for debian-linux-gnu (x86_64)
--
-- Host: mysql Database: cms
-- ------------------------------------------------------
-- Server version 5.6.35
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table `auditlog`
--
DROP TABLE IF EXISTS `auditlog`;
ie specifically, there should be no CREATE DATABASE line between the top of the file and the first DROP TABLE IF EXISTS line.
If there is, you need to comment out that CREATE DATABASE line, then do the following:
docker-compose down
Delete the shared/db directory
Put the modified version of import.sql in the correct location, renamed to import.sql if not so already docker-compose up -d
I did, however, I just tried to view it in Chrome Incognito mode, and I can see the calendar now. Seems cashing may be a factor here. Let me look a bit more.
I can confirm that I can now see the Media and Layouts as well. I have to change the view count from 10 to 25 to force it to display, and then it takes quite a while to show them, due to the number of assets I have. Current count is 7882 layouts and 8027 media assets. I think everything is good now, just slow due to the size.
