Cannot start vCO service today, which used to be OK

[Dirty_Hipster]

Hi guys and vCO experts,

I had an issue starting the vCO service. The vCO appliance is on a LinuxSUSE OS.

I did it several times, but still cannot start the service, though the vco server is on and all tabs are green on the vco configuration page. When I clicked the start service link, it will take about 5 minutes and then saying "The server is started" in green letters, but still, the service is stopped. The only changes made recently that I could recall is that, I enabled the "web view development mode" last week and restart the service(it worked), and when I disabled that today and trying to restart again, it stopped and cannot be started again.

Here are the logs from the orchestrator configuration:

2013-06-05 14:44:50.494+0000 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Packages waiting for a deployer ---

org.jboss.deployment.DeploymentInfo@b8e609b5 { url=file:/opt/vmo/app-server/server/vmo/deploy/jboss-base/http-invoker.sar/invoker.war/ }

  deployer: null

  status: Starting

  state: INIT_WAITING_DEPLOYER

  watch: file:/opt/vmo/app-server/server/vmo/deploy/jboss-base/http-invoker.sar/invoker.war/

  altDD: null

  lastDeployed: 1370443489877

  lastModified: 1345562778000

  mbeans:

org.jboss.deployment.DeploymentInfo@a36be76b { url=file:/opt/vmo/app-server/server/vmo/deploy/jboss-deploy-tomcat/jbossweb-tomcat55.sar/ROOT.war/ }

  deployer: null

  status: Starting

  state: INIT_WAITING_DEPLOYER

  watch: file:/opt/vmo/app-server/server/vmo/deploy/jboss-deploy-tomcat/jbossweb-tomcat55.sar/ROOT.war/

  altDD: null

  lastDeployed: 1370443489877

  lastModified: 1345562778000

  mbeans:

org.jboss.deployment.DeploymentInfo@3df89786 { url=file:/opt/vmo/app-server/server/vmo/deploy/jboss-base/jboss-ha-local-jdbc.rar }

  deployer: null

  status: null

  state: INIT_WAITING_DEPLOYER

  watch: file:/opt/vmo/app-server/server/vmo/deploy/jboss-base/jboss-ha-local-jdbc.rar

  altDD: null

  lastDeployed: 1370443490073

  lastModified: 1370443490000

  mbeans:

And the above messages kept repeating...

Thanks so much!

[Burke-]

I posted a reply to your other thread in this same community...

Perhaps you should move that other thread to a vCenter community and we keep this one for the vCO issue... I'll paste my reply here to keep the vCO discussion in one thread:

Yes, it seems you have two separate issues here- 1 with your vCenter (I can't help there) and 1 possibly with vCO... I would focus first on the vCenter issue and get that resolved before spending much time on the vCO issue as vCenter is certainly more critical to get resolved.

As for the vCO side though:

• Make sure the services are stopped
• In vCenter Orchestrator Configuration, go to the Troubleshooting tab of the navigation pane
• Click the link to "Cancel workflow runs" <- if you have any workflows running, caught in loops, etc, they will ALL be stopped the next time vCO successfully starts up
• Click the link to "Clean directories" <- this will cleanup the temporary deployment folders on the vCO server
• Click the link to "Reset current version" <- this will force the re-installation of the plug-ins that are installed and enabled
• Go to the vCenter Server tab of the navigation pane
• Edit and DISABLE your host(s) <- this is just a temporary step for troubleshooting purposes

Ensure your vCO Server has a MINIMUM of 3GB of RAM allocated to it (4GB is recommended). Anything less and you risk adverse effects such as services not starting properly.

Now, attempt to start your vCenter Orchestrator Server service from the "Startup Options" tab of the navigation pane.

[Dirty_Hipster]

let's discuss the vCO issue here please, that post is already long enough,

And I took a snapshot of the vco appliance

I think the RAM should be fine at this time.

I followed all your instructions, though the "clean directories" one did not work, and started the service again, but still couldn't get it started...

[Burke- · Accepted solution]

Yes, the screenshot looks good. It shows used storage same as provisioned - I guess this was thick provisioned, that is fine... Is there free space on the drive? SSH to the VA to confirm.

Aside from maybe running out of space, I'm unsure what is causing this issue - perhaps a corrupt deployment? Your snapshot - was that taken before the issues - if so, you should probably try reverting.

If it were me, I would cut my losses and try deploying another appliance. So far, I have had very good experiences with the vCO Appliance and use it in multiple locations daily for my test/dev work.

[Dirty_Hipster]

The snapshot was taken just now, and I think we have enough storage or space for the vco appliance, please double confirm:

Deploying another vco appliance is the last thing I want to do...

From the vco appliance console, I could start the orchestrator.sh, and run it. But you know, there is no UI but just lines.

Do we have other ways around to check that out?

[Dirty_Hipster]

I start the ./orchestrator.sh file on the vco appliance several times, and for some weird reasons, it came back.

Still haven't figured out how this happened, but it is ok to use now, so I'd like to close this post.

And thanks Burke again.