TECHZEN Zenoss User Community ARCHIVE  

Error Upgrading 1.06/5.06 to 1.09/5.09

Subject: Error Upgrading 1.06/5.06 to 1.09/5.09
Author: Chris
Posted: 2016-01-20 16:18

Upgrading to 5.0.9 and receive an error when running upgrade core script. Found a similar issue in the forum related to an upgrade to 5.0.3 but that didn't seem to apply to my situation.

# cat /var/log/serviced/script-2016-01-20-160756-root.log
Script started on Wed 20 Jan 2016 04:07:56 PM CST
I0120 16:07:57.431203 26606 runner.go:160] executing step 0: DESCRIPTION Zenoss Core 5.0.9 upgrade
I0120 16:07:57.431280 26606 runner.go:160] executing step 1: VERSION core-5.0.9
I0120 16:07:57.431288 26606 runner.go:160] executing step 2: REQUIRE_SVC
I0120 16:07:57.431294 26606 eval.go:329] checking service requirement
I0120 16:07:57.431308 26606 eval.go:333] verifying service 8hsccwmq70dvqrs7upur9u6eg
I0120 16:07:57.431593 26606 eval.go:339] found 8hsccwmq70dvqrs7upur9u6eg tenant id for service 8hsccwmq70dvqrs7upur9u6eg
I0120 16:07:57.431609 26606 runner.go:160] executing step 3: SNAPSHOT
I0120 16:07:57.431618 26606 eval.go:22] performing snapshot
E0120 16:08:29.198833 26606 runner.go:162] error executing step 3: SNAPSHOT: signal: killed
I0120 16:08:29.198864 26606 runner.go:152] Executing exit functions
signal: killed

Script done on Wed 20 Jan 2016 04:08:29 PM CST

Any ideas/assitance is appreciated. Thank you.



Subject: check disk space, it looks
Author: Andrew Kirch
Posted: 2016-01-29 12:53

check disk space, it looks like it's failing to take a backup prior to upgrade

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



Subject: Thank you for your reply.
Author: Chris
Posted: 2016-01-29 14:39

Thank you for your reply. Disk space looks fine, my install uses hardly any space at all on a large drive.



Subject: In case the information is
Author: Chris
Posted: 2016-02-02 13:01

In case the information is useful
# df -Th
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/rhel_vtx1zenoss-root xfs 240G 21G 220G 9% /
devtmpfs devtmpfs 9.8G 0 9.8G 0% /dev
tmpfs tmpfs 9.8G 0 9.8G 0% /dev/shm
tmpfs tmpfs 9.8G 806M 9.0G 9% /run
tmpfs tmpfs 9.8G 0 9.8G 0% /sys/fs/cgroup
/dev/sdb1 xfs 500G 16G 485G 4% /var/lib/docker
/dev/sdb2 btrfs 1.3T 8.6G 1.3T 1% /opt/serviced/var/volumes
/dev/sda1 xfs 497M 207M 291M 42% /boot
tmpfs tmpfs 2.0G 0 2.0G 0% /run/user/0
tmpfs tmpfs 2.0G 0 2.0G 0% /run/user/1000

# getenforce
Disabled



< Previous
Configuring trap destination to send to Zenoss 5
  Next
Not Able to Model a Device on a Collector via GUI
>