Xibo CMS 1.8.2 - Docker Type (Upgraded from 1.7.x Non-Docker Install)
Hyper-V VM Running Ubuntu 16.04.03 LTS
3GB RAM (Usually at 25-50% usage)
Our Xibo install’s maintenance process seems to be having some trouble. Talking with Peter, we realized the issue as part of debugging the fact that our Xibo web ui would take forever to become available when we rebooted the VM. It seems that when the VM reboots it prompts to run maintenance, at this point mysqld takes up most of the CPU, RAM is fine. It sits like this with mysqld, presumably engaged in the maintenance process. Eating up the CPU for around 12m. Then it starts to taper off and the web ui becomes available and everything seems, on the surface, to be fine.
That said, when we go to the Tasks section of Administration, Daily Maintenance has a gear icon instead of the clock like the rest, Last Run appears to be the time of the reboot, and Next run is a time set after the last run but nonetheless, in the past as of now. If I try to use Run Now, nothing seems to happen or change. The other maintenance processes appear from their entries to be working fine with the exception of Stats Archive which I turned on and which now consistently shows a gear, has no last run, always has a next run of the current time, and doesn’t seem to respond to Run Now.