[jbosstools-issues] [JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch

Martin Malina (JIRA) issues at jboss.org
Thu Jun 2 05:59:00 EDT 2016


Martin Malina created JBIDE-22501:
-------------------------------------

             Summary: CDK stuck on Starting... after launch
                 Key: JBIDE-22501
                 URL: https://issues.jboss.org/browse/JBIDE-22501
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: cdk
    Affects Versions: 4.4.0.Alpha2
            Reporter: Martin Malina
            Assignee: Rob Stryker


This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this.

This is what I did today (verifying JBDS-3739):
1. Start my Eclipse Neon RC2
2. Updated Eclipse
3. Updated Docker Tools to latest nightly
4. Installed nightly JBoss Tools Abridged
5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before)
6. Start CDK server
Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked.
7. Stop CDK server
8. Start CDK server
This time it's stuck on Starting... even though I can see from the console that the vagrant box started:
{code}
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Guest
    default: additions are required for forwarded ports, shared folders, host only
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default: 
    default: This is not an error message; everything may continue to work properly,
    default: in which case you may ignore this message.
==> default: Configuring and enabling network interfaces...
==> default: Registering box with vagrant-registration...
==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.
{code}

Now it will probably time out and stop the server. And most probably next start will work.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list