After upgrading to the latest version, the controller fails to start services successfully. Below listed are the running services :
$ grapectl status
[sudo] password for grapevine:
grapevine_capacity_manager RUNNING pid 32743, uptime 1:44:24
grapevine_capacity_manager_lxc_plugin RUNNING pid 32737, uptime 1:44:24
grapevine_cassandra RUNNING pid 32210, uptime 1:44:41
grapevine_client RUNNING pid 32207, uptime 1:44:41
grapevine_coordinator_service RUNNING pid 388, uptime 1:44:21
grapevine_dlx_service RUNNING pid 32212, uptime 1:44:41
grapevine_log_collector RUNNING pid 32222, uptime 1:44:41
grapevine_root RUNNING pid 32211, uptime 1:44:41
grapevine_supervisor_event_listener RUNNING pid 32206, uptime 1:44:41
grapevine_ui RUNNING pid 32208, uptime 1:44:41
reverse-proxy=5.0.0.4270 RUNNING pid 9167, uptime 1:38:00
router=5.0.0.4270 RUNNING pid 9168, uptime 1:38:00
and then did ./bin/reset_grapevine but it stopped at below:
14:09:12,192 | Growing services (this can take several minutes). Please wait...
2017-05-03 14:09:12,312 | Running [12/37]: reverse-proxy postgres cas-service grapevine node-ui rabbitmq grapevine-log-collector election-service router grapevine-coordinator-service rbac-service cassandra
2017-05-03 15:09:13,565 | Config wizard completed with errors
This is usually an indication that the DiskIO is not good enough.Check that you have enough RAM and vcpu.
Can you run the following command on the grapevine console:
dd if=/dev/zero of=/tmp/foo bs=1M count=512 conv=fdatasync
$ dd if=/dev/zero of=/tmp/foo bs=1M count=512 conv=fdatasync
512+0 records in
512+0 records out
536870912 bytes (537 MB) copied, 2.40962 s, 223 MB/s
(grapevine)
Resolved the issue by installing the latest upgrade 1.4.2
Comments
0 comments
Please sign in to leave a comment.