Strange error on first vagrant up [Mac OS 10.8/10.9]

[ryanpcmcquen]

I have received the same error on 2 separate machines (Macbook Pro @ 10.8 /iMac @ 10.9):

~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:107:in `digest': can't convert nil into String (TypeError)
  from ~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:107:in `hexdigest'
  from ~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:107:in `signature'
  from ~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:70:in `block in getHostEntries'
  from ~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:69:in `each'
  from ~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:69:in `getHostEntries'
  from ~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:33:in `block in addHostEntries'
  from ~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:32:in `each'
  from ~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:32:in `addHostEntries'
  from ~/.vagrant.d/gems/gems/vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/Action/UpdateHosts.rb:18:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:57:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:57:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:57:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builder.rb:116:in `call'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/machine.rb:147:in `action'
  from /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'

This is my Vagrantfile:
https://raw.github.com/milojennings/zippy/0.1/Vagrantfile

Everything works perfectly on the second vagrant up.

[mvance]

I tried using vagrant-hostsupdater for the first time today, while trying out kalastack. I ran into the same error mentioned above the first time I ran vagrant up. I had to vagrant destroy and rerun vagrant up to get the hosts file entries added correctly.

In searching out a fix, I also found someone else mentioning the same error with the varying-vagrant-vagrants.

It seems the issue may be specific to the very first time you use vagrant-hostsupdater.

[longwave]

I also saw this error the first time I ran vagrant up on Linux after installing the hostsupdater plugin, but it also worked perfectly the second time round.

[blongden]

Same for me - arrived at this issue when searching for the error message above.

[ryanpcmcquen]

Still no ideas for a fix? Is this plugin still being maintained?

[wheelsandcogs]

Same problem here - seems to happen the first time you vagrant up a nonexistent box, works fine for existing boxes.

[mikesimons]

As @wheelsandcogs has observed, this does seem to be reproducible by creating a vagrantfile that has the box_url as some locally downloaded box and the box name to be something different each run.

Interestingly it seems fixed in Vagrant 1.5.0 so this might be an issue in Vagrant itself (which is something I've suspected).

[opepin]

got the same issue on 1.4.3 - vagrant-hostsupdater (0.0.11) on Mac

[es] Checking for host entries
[es] Forcing shutdown of VM...
[es] Destroying VM and associated drives...
[es] Running cleanup tasks for 'chef_solo' provisioner...
vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:107:in `digest': no implicit conversion of nil into String (TypeError)
    from vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:107:in `hexdigest'
    from vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:107:in `signature'
    from vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:70:in `block in getHostEntries'
    from vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:69:in `each'
    from vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:69:in `getHostEntries'
    from vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:33:in `block in addHostEntries'
    from vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:32:in `each'
    from vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/HostsUpdater.rb:32:in `addHostEntries'
    from vagrant-hostsupdater-0.0.11/lib/vagrant-hostsupdater/Action/UpdateHosts.rb:18:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in `call'

Works the second time (and asked for the sudo password to edit the /etc/hosts file)

[aistis-]

@opepin vagrant halt && vagrant up solved the error for me.

[cgsmith]

I am not seeing this issue occurring. Is there a simpler Vagrantfile to use to replicate? Does it only happen on new boxes?

[ryanpcmcquen]

@cgsmith you can try this one: https://gist.github.com/ryanpcmcquen/e2f1e9424671c2bbd251

I haven't tried any of these projects in over a year, so the issue may have been fixed by something else at this point.

[ryanpcmcquen]

And yes it only happens on new boxes, as @wheelsandcogs said.

[dtbaker]

Ditto getting the same error here. Fresh install, just install vagrant 1.7.4 from https://www.vagrantup.com/downloads.html and ran vagrant plugin install vagrant-hostsupdater then vagrant plugin install vagrant-triggers then vagrant up and received:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Removing hosts
==> default: No machine id, nothing removed from /etc/hosts
==> default: Checking for host entries
/home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/HostsUpdater.rb:110:in `digest': no implicit conversion of nil into String (TypeError)
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/HostsUpdater.rb:110:in `hexdigest'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/HostsUpdater.rb:110:in `signature'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/HostsUpdater.rb:73:in `block in getHostEntries'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/HostsUpdater.rb:72:in `each'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/HostsUpdater.rb:72:in `getHostEntries'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/HostsUpdater.rb:36:in `block in addHostEntries'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/HostsUpdater.rb:35:in `each'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/HostsUpdater.rb:35:in `addHostEntries'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/Action/UpdateHosts.rb:17:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-hostsupdater-1.0.0/lib/vagrant-hostsupdater/Action/RemoveHosts.rb:23:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-triggers-0.5.2/lib/vagrant-triggers/action/trigger.rb:17:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-triggers-0.5.2/lib/vagrant-triggers/action/trigger.rb:17:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
    from /home/dtbaker/.vagrant.d/gems/gems/vagrant-triggers-0.5.2/lib/vagrant-triggers/action/trigger.rb:17:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

[cgsmith]

I'll try and find what is going on - I am seeing the issue as well.