TECHZEN Zenoss User Community ARCHIVE  

unable to remove old app and host

Subject: unable to remove old app and host
Author: [Not Specified]
Posted: 2015-05-05 01:18

Hi Zenoss guys, Basically, I built a control center with zenoss 5 running in my test env, after completed the test, I export it to an ovf then deployed to production env.

So the most obvious thing was to change the ip address, I keep the hostname the same, just update the DNS records. I have read some threads in this forum about changing the master host address, which is OK, basically, add a new localhost and deploy the zenoss app. however, the problems came when I tried to remove the stale host object and application object. See error below.

Error message: Removing service failed Internal Server Error: service 8nykl3iannd2nbjvigr5dloa9 has 1 running instances

Error message link: http://i1068.photobucket.com/albums/u443/hhe2015/zenoss/zenoss5-error_zp...

[root@zenossmaster volumes]# serviced service status 8nykl3iannd2nbjvigr5dloa9

NAME ID STATUS UPTIME HOST IN_SYNC DOCKER_ID

Zenoss.core 83ervr0s6o33c3e1eoje0lriu Stopping 168h36m33.474796132s zenossmaster Y 57b295aca34a

localhost 1lxltea549jphkvre9p7uusd4

localhost eqxfj3k9355ze2jy9da01qwaa

zencommand 8nykl3iannd2nbjvigr5dloa9 Stopping 168h36m43.997563208s zenossmaster Y 780f7525868d

According to Andrew, before removing the host, we have to remove the app first, but the old app doesn't like to be removed for some reason. Struggling on this for a few hours, including trying to nail it by command line. still no luck. Hope someone can help.



Subject: You need to stop service,
Author: Jan Garaj
Posted: 2015-05-05 12:40

You need to stop service, stopping state != stopped.
1.) Try to stop serviced and then start serviced again.
If it doesn't help, then:
2.) Try to stop serviced and docker and then start docker and serviced.

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



Subject: Try to start and then stop
Author: Jan Garaj
Posted: 2015-05-05 19:52

Try to start and then stop/remove service from cmd line.
Use journalctl for log, for example: journalctl -u serviced -f -l -n 1000
If it doesn't help, then probably reinstall.

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



Subject: still no luck, so frustrated.
Author: [Not Specified]
Posted: 2015-05-06 01:00

still no luck, so frustrated.



< Previous
check_http ssl error
  Next
URL device search not working properly
>