|
|
| Subject: | Upgrade from 5.0.3 to 5.0.6 broken |
| Author: | [Not Specified] |
| Posted: | 2015-09-24 18:08 |
So I've just run through the upgrade process from 5.0.3 to 5.0.6 and everything seemed to work fine. Control Center upgraded successfully, the Zenoss application seemed to upgrade successfully and after the upgrade completed, I was able to successfully start the Zenoss core application through control center and log in.
The last step I performed, as per the upgrade guide, was to convert the storage driver for docker from btrfs to xfs. After verifying that /var/lib/docker was on it's own partition, I unmounted /var/lib/docker, updated the file system (mkfs -t xfs -f /dev/sda3), made the required changes to /etc/fstab (comment out existing entry for /var/lib/docker and create new one), changed the docker storage driver in /etc/sysconfig/docker, and restarted docker and serviced.
Now in Control Center, I'm unable to start the Zenoss.core application. All of it's services just remain in the "starting" status indefinitely.
I've tried several restarts of the master host with no luck, starting services individually, double checking config files are correct but no luck so far.
Anyone have any tips or clues to troubleshoot this
| Subject: | as far as i remember, when i |
| Author: | [Not Specified] |
| Posted: | 2015-09-28 14:19 |
as far as i remember, when i did that, the docker partition was empty, and my current install was... no more.
I could restore a backup, i think, something like that i did.
In any case, in my expercience, EVERY upgrade is broken.
Zenpacks you install or upgrade yourself fail to reinstall and are left usually broken.
I ended up doing a clean install in 5.0.1, 5.0.2, 5.0.3 and 5.0.4.
I have not tried upgrading to 5.0.6 yet.
| Subject: | Thanks Rcocchiararo, I kind |
| Author: | [Not Specified] |
| Posted: | 2015-09-28 18:42 |
Thanks Rcocchiararo, I kind of figured as much. To be honest I haven't seen too many good news stories on here about 5.0.x upgrades. Shame because v3.x and v4.x upgrades were never such a drama.
I've tried restoring a backup I took through control centre prior to making the file system change but this is broken too (complains there is insufficient space when there's about 30GB free on the volume) so looks like I'll be turning my old 4.2.3 install back on while I build a fresh v5 instance.... again....
| Subject: | remember that backups need |
| Author: | [Not Specified] |
| Posted: | 2015-09-30 15:53 |
remember that backups need room in the disk/partition where the "backup" folder resides.
The backup is first EXTRACTED there, then restored to the proper place.
Also, when performing a backup, you need room in the volumes disk/partiton (cause it uses that temporarily), and in the backup folder.
| Subject: | First, take a backup of " |
| Author: | [Not Specified] |
| Posted: | 2015-09-30 15:57 |
EDIT: wrong thread
| Subject: | 5.x is awesome. 5.x requires |
| Author: | Andrew Kirch |
| Posted: | 2015-10-01 11:49 |
5.x is awesome. 5.x requires thinking totally differently. There is a learning curve but it's worth it. A lot of what you're seeing is people who put 5.x into prod before climbing that curve, or who are climbing it in a staging or test environment. Don't let it put you off trying it.
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
| < |
Previous INodes and Block Utilization Missing |
Next Core 5 LDAP Connection Issue |
> |