|
|
| Subject: | upgrading from 5.0.0 to 5.0.3 failing ! |
| Author: | [Not Specified] |
| Posted: | 2015-08-12 16:18 |
Hello,
I am having an issue while upgrading from 5.0.0 to 5.0.3.
I currently have two v5.0.0 Zenoss.core instances deployed in one master server; One instance never actually was started ever since I deployed from 1st time, whereas the other has been started and collecting perf data for about 2 months now.
While following the Zenos_core_upgrade_guide / section "upgrade from to 1.0.3 / 5.0.3" all instruction goes succesfully for the unused instance whereas for the other it it throws the following error:
[root@srv~]# serviced script run /root/5.0.x/upgrade-core.txt --service 1c2holhuohf7el2g91jyq0pj4
Logging to logfile: /var/log/serviced/script-2015-08-12-204139-root.log
Script started, file is /var/log/serviced/script-2015-08-12-204139-root.log
I0812 20:41:39.945890 04294 runner.go:160] executing step 0: DESCRIPTION Zenoss Core 5.0.3 upgrade
I0812 20:41:39.945990 04294 runner.go:160] executing step 1: VERSION core-5.0.3
I0812 20:41:39.946004 04294 runner.go:160] executing step 2: REQUIRE_SVC
I0812 20:41:39.946017 04294 eval.go:329] checking service requirement
I0812 20:41:39.946030 04294 eval.go:333] verifying service 1c2holhuohf7el2g91jyq0pj4
I0812 20:41:39.946564 04294 eval.go:339] found 1c2holhuohf7el2g91jyq0pj4 tenant id for service 1c2holhuohf7el2g91jyq0pj4
I0812 20:41:39.946588 04294 runner.go:160] executing step 3: SNAPSHOT
I0812 20:41:39.946601 04294 eval.go:22] performing snapshot
E0812 20:42:12.669905 04294 runner.go:162] error executing step 3: SNAPSHOT: signal: killed
I0812 20:42:12.669962 04294 runner.go:152] Executing exit functions
signal: killed
Script done, file is /var/log/serviced/script-2015-08-12-204139-root.log
Apparently it is failing at the phase where is creating a security SNAPSHOT.
I have plenty of disk space for covering snapshot related jobs.
Can you guys suggest a check point I might be missing here
Thanks,
--
Daniel b.
| Subject: | paste the output of 'mount' |
| Author: | Andrew Kirch |
| Posted: | 2015-08-24 14:26 |
paste the output of 'mount'
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: | is selinux enabled? |
| Author: | Andrew Kirch |
| Posted: | 2015-08-26 15:28 |
is selinux enabled
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: | disable it entirely and try |
| Author: | Andrew Kirch |
| Posted: | 2015-08-27 11:54 |
disable it entirely and try again.
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: | SElinux disabled |
| Author: | [Not Specified] |
| Posted: | 2015-09-02 14:01 |
[root@srv~]# sestatus
SELinux status: disabled
[root@srv~]# cat /var/log/serviced/script-2015-09-02-185419-root.log
Script started on Wed 02 Sep 2015 06:54:19 PM UTC
I0902 18:54:20.475476 10203 runner.go:160] executing step 0: DESCRIPTION Zenoss Core 5.0.3 upgrade
I0902 18:54:20.475613 10203 runner.go:160] executing step 1: VERSION core-5.0.3
I0902 18:54:20.475631 10203 runner.go:160] executing step 2: REQUIRE_SVC
I0902 18:54:20.475646 10203 eval.go:329] checking service requirement
I0902 18:54:20.475662 10203 eval.go:333] verifying service 1c2holhuohf7el2g91jyq0pj4
I0902 18:54:20.476053 10203 eval.go:339] found 1c2holhuohf7el2g91jyq0pj4 tenant id for service 1c2holhuohf7el2g91jyq0pj4
I0902 18:54:20.476100 10203 runner.go:160] executing step 3: SNAPSHOT
I0902 18:54:20.476111 10203 eval.go:22] performing snapshot
E0902 18:54:52.618296 10203 runner.go:162] error executing step 3: SNAPSHOT: signal: killed
I0902 18:54:52.618348 10203 runner.go:152] Executing exit functions
signal: killed
Script done on Wed 02 Sep 2015 06:54:52 PM UTC
Any more ideas.
could you point a document to backup all collected data both performance and events, and then restore it into a freshly installed zenoss
| Subject: | Make sure that you set |
| Author: | [Not Specified] |
| Posted: | 2015-09-11 14:40 |
Make sure that you set SERVICED_FS_TYPE=btrfs in /etc/default/serviced. When using the default (rsync-based snapshots), they can be too slow and eventually time out.
| Subject: | thank you Ian, nice catch !. |
| Author: | [Not Specified] |
| Posted: | 2015-09-15 15:19 |
yes ! yes ! yes ! yes !
thank you Ian, nice catch !.
root cause: it was timing out while using rsync based snapshots in prepration for upgrading.
This time it went through the different stages of the upgrade:
[...]
I0915 20:03:14.713245 03742 runner.go:160] executing step 0: DESCRIPTION Zenoss Core 5.0.3 upgrade
I0915 20:03:14.713394 03742 runner.go:160] executing step 1: VERSION core-5.0.3
I0915 20:03:14.713416 03742 runner.go:160] executing step 2: REQUIRE_SVC
I0915 20:03:14.713436 03742 eval.go:329] checking service requirement
I0915 20:03:14.713453 03742 eval.go:333] verifying service 1c2holhuohf7el2g91jyq0pj4
I0915 20:03:14.713921 03742 eval.go:339] found 1c2holhuohf7el2g91jyq0pj4 tenant id for service 1c2holhuohf7el2g91jyq0pj4
I0915 20:03:14.713976 03742 runner.go:160] executing step 3: SNAPSHOT
I0915 20:03:14.713995 03742 eval.go:22] performing snapshot
I0915 20:03:16.755621 03742 eval.go:41] snapshot id: 1c2holhuohf7el2g91jyq0pj4_20150915-200316
I0915 20:03:16.755675 03742 runner.go:160] executing step 4: SVC_USE zenoss/core_5.0:5.0.3
I0915 20:03:16.755696 03742 eval.go:59] preparing to use image: zenoss/core_5.0:5.0.3
I0915 20:03:16.755726 03742 service_client.go:31] Pulling zenoss/core_5.0:5.0.3, tagging to latest, and pushing to registry localhost:5000 - this may take a while
I0915 20:03:21.919250 03742 eval.go:68] Successfully tagged new image localhost:5000/1c2holhuohf7el2g91jyq0pj4/core_5.0:latest
I0915 20:03:21.919287 03742 runner.go:160] executing step 5: SVC_START Zenoss.core/mariadb
I0915 20:03:23.010236 03742 eval.go:159] starting service Zenoss.core/mariadb 6hypsdw7d411i82owmtnddidg
I0915 20:03:23.102715 03742 runner.go:160] executing step 6: SVC_START Zenoss.core/RabbitMQ
I0915 20:03:24.253449 03742 eval.go:159] starting service Zenoss.core/RabbitMQ bnte30bx6tacponw6iwxxp15s
I0915 20:03:24.324914 03742 runner.go:160] executing step 7: SVC_START Zenoss.core/zeneventserver
I0915 20:03:25.432590 03742 eval.go:159] starting service Zenoss.core/zeneventserver 3ldnyyl8lxes53zi1qvqj6jt5
I0915 20:03:25.684709 03742 runner.go:160] executing step 8: SVC_START Zenoss.core/redis
I0915 20:03:26.735271 03742 eval.go:159] starting service Zenoss.core/redis 8vth3g485a3g8wd8v9opqzrmw
I0915 20:03:26.838587 03742 runner.go:160] executing step 9: SVC_WAIT Zenoss.core/mariadb Zenoss.core/RabbitMQ Zenoss.core/zeneventserver Zenoss.core/redis started 600
I0915 20:03:30.939215 03742 eval.go:123] waiting 600 for services Zenoss.core/mariadb, Zenoss.core/RabbitMQ, Zenoss.core/zeneventserver, Zenoss.core/redis to be started
I0915 20:03:36.561025 03742 runner.go:160] executing step 10: SVC_RUN Zenoss.core/Zope upgrade
I0915 20:03:37.590078 03742 eval.go:259] running: serviced service run 4lquddapn7y3fo8vxhd566tyw upgrade
I0915 20:03:38.582421 04150 server.go:341] Connected to the control center at port 10.71.16.166:4979
I0915 20:03:38.817736 04150 server.go:435] Acquiring image from the dfs...
I0915 20:03:38.819481 04150 server.go:437] Acquired! Starting shell
[...]
| < |
Previous Can't Ping or SNMP to ESXi |
Next Threshold for vSphere Interface Speeds |
> |