[cf-lattice] Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Ramesh Sambandan
I just tried lattice following instructions in
     https://github.com/cloudfoundry-incubator/lattice/tree/v0.4.0
When I do the ./ltc target 192.168.11.11.xip.io I get i/o timeout.
Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

I am using virtualbox in Yosimitte

I tried older versions(up to v0.2.3) and nightly release with the same results.

I did try to flush the DNS cache as in https://support.apple.com/en-us/HT202516

Can somebody help,

thanks
-Ramesh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Marco Nicosia
Hi Ramesh,

Just a guess, are you perhaps having a problem doing DNS resolution with .xip.io? What happens if you run:

If that looks right, what happens when you run:


--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.


On Thu, Sep 10, 2015 at 1:08 PM, Ramesh Sambandan <[hidden email]> wrote:
I just tried lattice following instructions in
     https://github.com/cloudfoundry-incubator/lattice/tree/v0.4.0
When I do the ./ltc target 192.168.11.11.xip.io I get i/o timeout.
Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

I am using virtualbox in Yosimitte

I tried older versions(up to v0.2.3) and nightly release with the same results.

I did try to flush the DNS cache as in https://support.apple.com/en-us/HT202516

Can somebody help,

thanks
-Ramesh

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Ramesh Sambandan
It does not appear to be DNS resolution problem. Following are results of my dig and telnet (port 80)

guests-MacBook-Pro:bin rsamban$ dig receptor.192.168.11.11.xip.io

; <<>> DiG 9.8.3-P1 <<>> receptor.192.168.11.11.xip.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38123
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;receptor.192.168.11.11.xip.io. IN A

;; ANSWER SECTION:
receptor.192.168.11.11.xip.io. 300 IN A 192.168.11.11

;; Query time: 61 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Sep 10 14:59:00 2015
;; MSG SIZE  rcvd: 63

guests-MacBook-Pro:bin rsamban$ telnet receptor.192.168.11.11.xip.io 80
Trying 192.168.11.11...
Connected to receptor.192.168.11.11.xip.io.
Escape character is '^]'.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Re: Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Daniel Watrous
It's not a resolution issue, but it keeps coming up. Here's the last thread on this issue:

Daniel

On Thu, Sep 10, 2015 at 4:01 PM, Ramesh Sambandan <[hidden email]> wrote:
It does not appear to be DNS resolution problem. Following are results of my dig and telnet (port 80)

guests-MacBook-Pro:bin rsamban$ dig receptor.192.168.11.11.xip.io

; <<>> DiG 9.8.3-P1 <<>> receptor.192.168.11.11.xip.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38123
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;receptor.192.168.11.11.xip.io. IN      A

;; ANSWER SECTION:
receptor.192.168.11.11.xip.io. 300 IN   A       192.168.11.11

;; Query time: 61 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Sep 10 14:59:00 2015
;; MSG SIZE  rcvd: 63

guests-MacBook-Pro:bin rsamban$ telnet receptor.192.168.11.11.xip.io 80
Trying 192.168.11.11...
Connected to receptor.192.168.11.11.xip.io.
Escape character is '^]'.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Re: Re: Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Ramesh Sambandan
How do I use precise image. I tried replacing trusty with precise in the Vagrantfile
config.vm.box = "lattice/ubuntu-trusty-64"

but it does not work.

guests-MacBook-Pro:vagrant rsamban$ vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'lattice/ubuntu-precise-64' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: 0.4.0
The box 'lattice/ubuntu-precise-64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/lattice/ubuntu-precise-64"]
Error: The requested URL returned error: 404 Not Found

Please advise.

thanks
-Ramesh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Re: Re: Re: Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Daniel Watrous

On Thu, Sep 10, 2015 at 4:30 PM, Ramesh Sambandan <[hidden email]> wrote:
How do I use precise image. I tried replacing trusty with precise in the Vagrantfile
config.vm.box = "lattice/ubuntu-trusty-64"

but it does not work.

guests-MacBook-Pro:vagrant rsamban$ vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'lattice/ubuntu-precise-64' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: 0.4.0
The box 'lattice/ubuntu-precise-64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/lattice/ubuntu-precise-64"]
Error: The requested URL returned error: 404 Not Found

Please advise.

thanks
-Ramesh

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Re: Re: Re: Re: Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Ramesh Sambandan
Thanks for quick response Daniel, I tried, but still does not work. The vm is up, but it appears there is an error during startup. I made following changes to Vagrantfile

  #config.vm.box = "lattice/ubuntu-trusty-64"
  config.vm.box = "ubuntu/precise64"
  #config.vm.box_version = '0.4.0'

****Error from vagrant up --provider=virtualbox
==> default: /tmp/install-from-tar: line 9: /etc/init.d/lighttpd: No such file or directory
******

uests-MacBook-Pro:vagrant rsamban$ vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/precise64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/precise64' is up to date...
==> default: Setting the name of the VM: vagrant_default_1441922698790_98236
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> 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 => 2200 (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:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.1.12
    default: VirtualBox Version: 5.0
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /Users/rsamban/cloudFoundry/lattice-bundle-v0.4.0-osx/vagrant
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: mkdir: created directory `/var/lattice'
==> default: mkdir: created directory `/var/lattice/setup'
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: /tmp/install-from-tar: line 9: /etc/init.d/lighttpd: No such file or directory
==> default: Lattice is now installed and running.
==> default: You may target it using: ltc target 192.168.11.11.xip.io
guests-MacBook-Pro:vagrant rsamban$ ../ltc target 192.168.11.11.xip.io
Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Please advise

thanks
-Ramesh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Re: Re: Re: Re: Re: Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Daniel Watrous
Ramesh,

I'm not sure what else to try. In that thread it is explained that the root problem is actually timeout related, but the reason for the delay in some circumstances isn't clear. Everything I know about it is in that thread.

Daniel

On Thu, Sep 10, 2015 at 5:13 PM, Ramesh Sambandan <[hidden email]> wrote:
Thanks for quick response Daniel, I tried, but still does not work. The vm is up, but it appears there is an error during startup. I made following changes to Vagrantfile

  #config.vm.box = "lattice/ubuntu-trusty-64"
  config.vm.box = "ubuntu/precise64"
  #config.vm.box_version = '0.4.0'

****Error from vagrant up --provider=virtualbox
==> default: /tmp/install-from-tar: line 9: /etc/init.d/lighttpd: No such file or directory
******

uests-MacBook-Pro:vagrant rsamban$ vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/precise64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/precise64' is up to date...
==> default: Setting the name of the VM: vagrant_default_1441922698790_98236
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> 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 => 2200 (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:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.1.12
    default: VirtualBox Version: 5.0
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /Users/rsamban/cloudFoundry/lattice-bundle-v0.4.0-osx/vagrant
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: mkdir: created directory `/var/lattice'
==> default: mkdir: created directory `/var/lattice/setup'
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: /tmp/install-from-tar: line 9: /etc/init.d/lighttpd: No such file or directory
==> default: Lattice is now installed and running.
==> default: You may target it using: ltc target 192.168.11.11.xip.io
guests-MacBook-Pro:vagrant rsamban$ ../ltc target 192.168.11.11.xip.io
Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Please advise

thanks
-Ramesh

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Re: Re: Re: Re: Re: Re: Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Sabha Parameswaran
Can you login into vm using ssh or vagrant ssh? 
If unable to login, try to enable the gui option inside the vagrant file and see if it reports any problem. Also, try upgrading to the latest virtualbox and also install latest guest additions/virtual box client tools (seems you are using 4.1.12 while vbox itself is 5.0).

If you can login, then see if the router is up and the routes advertised contains the receptor.


-Sabha

On Thu, Sep 10, 2015 at 3:27 PM, Daniel Watrous <[hidden email]> wrote:
Ramesh,

I'm not sure what else to try. In that thread it is explained that the root problem is actually timeout related, but the reason for the delay in some circumstances isn't clear. Everything I know about it is in that thread.

Daniel

On Thu, Sep 10, 2015 at 5:13 PM, Ramesh Sambandan <[hidden email]> wrote:
Thanks for quick response Daniel, I tried, but still does not work. The vm is up, but it appears there is an error during startup. I made following changes to Vagrantfile

  #config.vm.box = "lattice/ubuntu-trusty-64"
  config.vm.box = "ubuntu/precise64"
  #config.vm.box_version = '0.4.0'

****Error from vagrant up --provider=virtualbox
==> default: /tmp/install-from-tar: line 9: /etc/init.d/lighttpd: No such file or directory
******

uests-MacBook-Pro:vagrant rsamban$ vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/precise64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/precise64' is up to date...
==> default: Setting the name of the VM: vagrant_default_1441922698790_98236
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> 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 => 2200 (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:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.1.12
    default: VirtualBox Version: 5.0
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /Users/rsamban/cloudFoundry/lattice-bundle-v0.4.0-osx/vagrant
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: mkdir: created directory `/var/lattice'
==> default: mkdir: created directory `/var/lattice/setup'
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: /tmp/install-from-tar: line 9: /etc/init.d/lighttpd: No such file or directory
==> default: Lattice is now installed and running.
==> default: You may target it using: ltc target 192.168.11.11.xip.io
guests-MacBook-Pro:vagrant rsamban$ ../ltc target 192.168.11.11.xip.io
Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Please advise

thanks
-Ramesh


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Re: Re: Re: Re: Re: Re: Re: Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Ramesh Sambandan
I can vagrant ssh to the server.
I installed latest vbox  guest additions. Still the same result.

The precise does not have lighttpd and cflinuxfs2
I did the following
1. tar xzf /vagrant/lattice.tgz --strip-components=2 -C /tmp lattice-build/scripts/install-from-tar
2. /tmp/install-from-tar collocated /vagrant/lattice.tgz
        I got an error
            Installing cflinuxfs2 rootfs...
            mv: cannot stat `/var/lattice-image/rootfs/cflinuxfs2': No such file or directory

How do I install cflinuxfs2 in standard ubuntu image. There are some steps missing in the post https://github.com/cloudfoundry-incubator/lattice/issues/128#issuecomment-106187084
with respect to using precise

Please advise.

thanks
-Ramesh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Error verifying target: Get http://receptor.192.168.11.11.xip.io/v1/desired_lrps: dial tcp: i/o timeout

Ramesh Sambandan
Forgot to mention,
I did sudo apt-get install lighttpd
before executing the steps,

I did stop/start the vm several times, no luck so far.

thanks
-Ramesh
Loading...