Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home for cloudfoundry.org
« Groups Home
"cannot access agent" error while deploying micro-bosh
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  10 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
animesh nandanwar  
View profile  
 More options Sep 5 2012, 7:11 pm
From: animesh nandanwar <animeshnandan...@gmail.com>
Date: Wed, 5 Sep 2012 16:11:51 -0700 (PDT)
Local: Wed, Sep 5 2012 7:11 pm
Subject: "cannot access agent" error while deploying micro-bosh

Hi All,
While deploying a micro bosh instance, I  get a "cannot access agent"
error. I did netstat on the microbosh instance, it shows that connection
gets established on port 25889 and then eventually gets closed.

below are the logs
root@inception-vm:/var/vcap/deployments# bosh micro deployment
microbosh-openstack
WARNING! Your target has been changed to `http://microbosh-openstack:25555'!
Deployment set to '/var/vcap/deployments/microbosh-openstack/micro_bosh.yml'
root@inception-vm:/var/vcap/deployments# bosh micro deploy
/var/vcap/stemcells/micro-bosh-stemcell-openstack-0.6.4.tgz
Deploying new micro BOSH instance `microbosh-openstack/micro_bosh.yml' to
`http://microbosh-openstack:25555' (type 'yes' to continue): yes

Verifying stemcell...
File exists and readable                                     OK
Using cached manifest...
Stemcell properties                                          OK

Stemcell info
-------------
Name:    micro-bosh-stemcell
Version: 0.6.4

Deploy Micro BOSH
  unpacking stemcell (00:00:05)
  uploading stemcell (00:02:04)
  creating VM from 2944aac0-077f-4b92-833d-dff5232e5ff7 (00:01:00)
Waiting for the agent        |ooooo              | 3/11 00:19:14  ETA:
--:--:--*BOSH CLI Error: cannot access agent (Connection refused -
connect(2) (http://10.0.0.3:6868))*
*Error information saved in /root/.bosh_error*
*
*
*On Bosh VM:*
vcap@bm-6add4350-4fc5-4fe6-a538-6ed0c0b93b5d:~$ netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 vm-1e12c276-8828-:45101 169.254.169.254:www    
TIME_WAIT
tcp        0      0 vm-1e12c276-8828-:45102 169.254.169.254:www    
TIME_WAIT
tcp        0      0 vm-1e12c276-8828-4b:ssh inception-vm.nova:48635
ESTABLISHED
tcp        0      0 vm-1e12c276-8828-:45103 169.254.169.254:www    
TIME_WAIT
tcp        0      0 vm-1e12c276-8828-4b:ssh inception-vm.nova:35952
ESTABLISHED
tcp        0      0 vm-1e12c276-8828-:45107 169.254.169.254:www    
ESTABLISHED
tcp        0      0 vm-1e12c276-8828-:45106 169.254.169.254:www    
ESTABLISHED
tcp        0      0 vm-1e12c276-8828-:45105 169.254.169.254:www    
ESTABLISHED
*tcp6       0      0 localhost:55047         localhost:25889        
ESTABLISHED*
*tcp6       0      0 localhost:25889         localhost:55047        
ESTABLISHED*

*vcap@bm-6add4350-4fc5-4fe6-a538-6ed0c0b93b5d:~$ netstat*
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 vm-1e12c276-8828-4b:ssh inception-vm.nova:48635
ESTABLISHED
tcp        0      0 vm-1e12c276-8828-4b:ssh inception-vm.nova:35952
ESTABLISHED
tcp        0      0 vm-1e12c276-8828-:45107 169.254.169.254:www    
ESTABLISHED
tcp        0      0 vm-1e12c276-8828-:45106 169.254.169.254:www    
ESTABLISHED
tcp        0      0 vm-1e12c276-8828-:45105 169.254.169.254:www    
ESTABLISHED
*tcp6       1      0 localhost:55047         localhost:25889        
CLOSE_WAIT*
*tcp6       0      0 localhost:25889         localhost:55047        
FIN_WAIT2*

Thanks,
Animesh


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Martin Englund  
View profile  
 More options Sep 5 2012, 7:15 pm
From: Martin Englund <mengl...@vmware.com>
Date: Wed, 5 Sep 2012 20:15:55 -0300
Local: Wed, Sep 5 2012 7:15 pm
Subject: Re: [bosh-users] "cannot access agent" error while deploying micro-bosh
Animesh,

how is the security group you are using configured? You need the
following ports open from your where you run "bosh micro deploy":
- 22
- 6868 (agent http interface)
- 25555 (bosh director)

cheers,
/Martin

On Wed, Sep 5, 2012 at 8:11 PM, animesh nandanwar

--
cheers,
/Martin
--
Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
animesh nandanwar  
View profile  
 More options Sep 6 2012, 11:56 am
From: animesh nandanwar <animeshnandan...@gmail.com>
Date: Thu, 6 Sep 2012 08:56:26 -0700
Local: Thurs, Sep 6 2012 11:56 am
Subject: Re: [bosh-users] "cannot access agent" error while deploying micro-bosh

Hi Martin,
The required ports are opened on inception vm as well as on BOSH vm.

Thanks,
Animesh


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
animesh nandanwar  
View profile  
 More options Sep 6 2012, 3:08 pm
From: animesh nandanwar <animeshnandan...@gmail.com>
Date: Thu, 6 Sep 2012 12:08:47 -0700
Local: Thurs, Sep 6 2012 3:08 pm
Subject: Re: [bosh-users] "cannot access agent" error while deploying micro-bosh

I did netstat on both inception VM and micro bosh vm. It shows that tcp
connection first gets established on port 25889 and then it is closed down.
It has no entry for port 6868.

*on Inception VM:*
root@inception-vm:/var/vcap/deployments/microbosh-openstack# netstat
tcp        0      0 localhost:33497         localhost:25889
ESTABLISHED
tcp        0      0 localhost:25889         localhost:33497
ESTABLISHED

*on microbosh vm:*
vcap@bm-cafb0248-5c08-4da6-9aca-bd95b6068b86:~$ netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        1      0 localhost:54149         localhost:25889
CLOSE_WAIT
tcp        0      0 localhost:25889         localhost:54149
FIN_WAIT2

Thanks,
Animesh

On Thu, Sep 6, 2012 at 8:56 AM, animesh nandanwar <


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
nasara...@gmail.com  
View profile  
 More options Sep 17 2012, 4:55 am
From: nasara...@gmail.com
Date: Mon, 17 Sep 2012 01:55:34 -0700 (PDT)
Local: Mon, Sep 17 2012 4:55 am
Subject: Re: [bosh-users] "cannot access agent" error while deploying micro-bosh

Hi Animesh,

    Is this issue solved for you.  If so please share the solution.  I am
getting the same error when trying to deploy following the instructions in
the deploying to aws using cloud foundry bosh blog post.
(http://blog.cloudfoundry.org/2012/09/06/deploying-to-aws-using-cloud-...).
 The console information is as follows

anbarasan@ubuntu:~/deployments$ bosh micro deploy ami-64d59436


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
animesh nandanwar  
View profile  
 More options Sep 17 2012, 11:30 am
From: animesh nandanwar <animeshnandan...@gmail.com>
Date: Mon, 17 Sep 2012 08:30:03 -0700
Local: Mon, Sep 17 2012 11:30 am
Subject: Re: [bosh-users] "cannot access agent" error while deploying micro-bosh

No, Issue still persists.
One more observation is this issue is seen with folsom release and not with
Essex.

Thanks,
Animesh


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Ferran Rodenas  
View profile  
 More options Sep 17 2012, 1:38 pm
From: Ferran Rodenas <frode...@gmail.com>
Date: Mon, 17 Sep 2012 19:38:42 +0200
Local: Mon, Sep 17 2012 1:38 pm
Subject: Re: [bosh-users] "cannot access agent" error while deploying micro-bosh

Can you please paste your .bosh_error file?

- Ferdy

2012/9/17 animesh nandanwar <animeshnandan...@gmail.com>


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Martin Englund  
View profile  
 More options Sep 17 2012, 3:29 pm
From: Martin Englund <mengl...@vmware.com>
Date: Mon, 17 Sep 2012 12:29:06 -0700
Local: Mon, Sep 17 2012 3:29 pm
Subject: Re: [bosh-users] "cannot access agent" error while deploying micro-bosh
Can you ssh onto the VM and check the agent log for error messages:
/var/vcap/bosh/log/current

Cheers,
/Martin

On Mon, Sep 17, 2012 at 8:30 AM, animesh nandanwar

--
cheers,
/Martin
--
Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
animesh nandanwar  
View profile  
 More options Sep 17 2012, 4:21 pm
From: animesh nandanwar <animeshnandan...@gmail.com>
Date: Mon, 17 Sep 2012 13:21:41 -0700
Local: Mon, Sep 17 2012 4:21 pm
Subject: Re: [bosh-users] "cannot access agent" error while deploying micro-bosh

Hi Ferdy,
I am currently on Essex so can not provide you logs. Will update you today
EOD about required information.
May be  nasara...@gmail.com  can update, if he has system in failed state.

Thanks,
Animesh

On Mon, Sep 17, 2012 at 12:29 PM, Martin Englund <mengl...@vmware.com>wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Anbarasan Gangadaran  
View profile  
 More options Sep 18 2012, 1:46 am
From: Anbarasan Gangadaran <nasara...@gmail.com>
Date: Tue, 18 Sep 2012 11:16:14 +0530
Local: Tues, Sep 18 2012 1:46 am
Subject: Re: [bosh-users] "cannot access agent" error while deploying micro-bosh

Hi Ferdy,

    find attached the .bosh_error file.

Thanks,
Anbarasan

On Tue, Sep 18, 2012 at 1:51 AM, animesh nandanwar <

  .bosh_error
2K Download

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »