zalando / zmon

Real-time monitoring of critical metrics & KPIs via elegant dashboards, Grafana3 visualizations & more
https://demo.zmon.io/
Other
359 stars 48 forks source link

Vagrant box error on vagrant provisioning #4

Closed snebel29 closed 8 years ago

snebel29 commented 8 years ago

Hi, Using vagrant 1.7.2 under Ubuntu, trying to start the vagrant box for evaluate zmon I found the following error

/$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/vivid64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/vivid64' is up to date...
==> default: Setting the name of the VM: ZMON-DEMO
==> 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: Forwarding ports...
    default: 8080 => 38080 (adapter 1)
    default: 8084 => 38084 (adapter 1)
    default: 8085 => 38085 (adapter 1)
    default: 8083 => 38083 (adapter 1)
    default: 22 => 2222 (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: 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 its present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

service hostname start

Stdout from the command:

Stderr from the command:

stdin: is not a tty
Failed to start hostname.service: Unit hostname.service is masked.
Jan-M commented 8 years ago

Running Vagrant 1.7.4 i cannot immediately reproduce this.

Can you run: vagrant box update

snebel29 commented 8 years ago

Still the same, let me upgrade to your vagrant version and see, any other idea welcome.. thanks for the quick answer!

/$ vagrant -v
Vagrant 1.7.2
/$ vagrant box update
==> default: Checking for updates to 'ubuntu/vivid64'
    default: Latest installed version: 20151021.0.0
    default: Version constraints: 
    default: Provider: virtualbox
==> default: Box 'ubuntu/vivid64' (v20151021.0.0) is running the latest version.
/$ vagrant destroy
==> default: VM not created. Moving on...
/$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/vivid64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/vivid64' is up to date...
==> default: Setting the name of the VM: ZMON-DEMO
==> 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: Forwarding ports...
    default: 8080 => 38080 (adapter 1)
    default: 8084 => 38084 (adapter 1)
    default: 8085 => 38085 (adapter 1)
    default: 8083 => 38083 (adapter 1)
    default: 22 => 2222 (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: 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 its present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

service hostname start

Stdout from the command:

Stderr from the command:

stdin: is not a tty
Failed to start hostname.service: Unit hostname.service is masked.
Jan-M commented 8 years ago

I know or remember that this was indeed an issue either with the vagrant or the ubuntu version, but newer ubuntu images I believe support this hostname setting.

snebel29 commented 8 years ago

Upgrade to vagrant 1.7.4 helps, I still see the tty error somewhere but provisioning process continues.. I let you know if everything goes fine, may be you should update requirements on README to require vagrant >= 1.7.4 that would help future people :-)

As additional info, for the record I'm running Ubuntu 14.04.3 LTS

Thanks!

Jan-M commented 8 years ago

I am actually running into some Docker issue now, let me know how it works out, I am looking into this on my side.

Jan-M commented 8 years ago

I have now updated the setup.py to reflect the new way how Docker is installed.

Give this a try if earlier version does not work.

snebel29 commented 8 years ago

At first look everything is up and working after login withg admin user, now we'll take a look to the software trying to solve some of our doubts about how it works and its possibilities, thanks for the quick support!

Jan-M commented 8 years ago

Let me know about your doubts and issues ;-)

Jan-M commented 8 years ago

feel free to contact via my personal email, see slides:

https://tech.zalando.com/blog/zmon-zalandos-open-source-monitoring-tool-slides/