Apache requires restart after rebooting the VM

[MatthewHager]

valk3[master] $ drush vup
Update the Valkyrie code in this project (at '.valkyrie/valkyrie') with the latest from /Users/matthew/.drush/valkyrie? (y/n): y
Valkyrie code updated.                                                                                                                                                                           [ok]
valk3[master*] $ vagrant reload
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> 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 => 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: ubuntu
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
vagrant-dns: trying to stop process with pid 1273...
vagrant-dns: process with pid 1273 successfully stopped.
==> default: Restarted DNS Service
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
Password:
==> default: Mounting NFS shared folders...
==> default: Mounting shared folders...
    default: /vagrant => /Users/matthew/Development/valk3
    default: /tmp/vagrant-puppet/modules-667fa919e8829f39f79c58a620b3c3b5 => /Users/matthew/Development/valk3/.valkyrie/valkyrie/vagrant/puppet/modules
    default: /tmp/vagrant-puppet/manifests-f7ceef9fa5d40cc35a133ee8757acb27 => /Users/matthew/Development/valk3/.valkyrie/valkyrie/vagrant/puppet/manifests
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: to force provisioning. Provisioners marked to run always will still run.
==> default: Running triggers after reload...
Starting DNS resolver...
ERROR: there is already one or more instance(s) of the program running
valk3[master*] $ drush sa
camcms-com
none
test
test-com
valkyrie
vm_valkyrie
valk3[master*] $ drush @camcms-com uli
http://camcms-com.val/user/reset/1/1422065370/1G1jrTMRowT09WAyovtIjlxnE1S7sF_ZvbwGmMyG7DA/login
valk3[master*] $ ping valkyrie.val
PING valkyrie.val (10.42.0.10): 56 data bytes
64 bytes from 10.42.0.10: icmp_seq=0 ttl=64 time=0.337 ms
^C
--- valkyrie.val ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.337/0.337/0.337/0.000 ms
valk3[master*] $ vagrant ssh
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-44-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

  System information as of Sat Jan 24 02:09:30 UTC 2015

  System load:  0.18              Processes:           102
  Usage of /:   8.1% of 39.34GB   Users logged in:     0
  Memory usage: 11%               IP address for eth0: 10.0.2.15
  Swap usage:   0%                IP address for eth1: 10.42.0.10

  Graph this data and manage this system at:
    https://landscape.canonical.com/

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

Last login: Fri Jan 23 04:13:33 2015 from 10.0.2.2
ubuntu@valkyrie:~$ sudo service apache2
Usage: apache2 {start|stop|graceful-stop|restart|reload|force-reload|start-htcacheclean|stop-htcacheclean}
ubuntu@valkyrie:~$ sudo service apache2 sttaus
Usage: apache2 {start|stop|graceful-stop|restart|reload|force-reload|start-htcacheclean|stop-htcacheclean}
ubuntu@valkyrie:~$ sudo service apache2 status
 * apache2 is not running
ubuntu@valkyrie:~$

[MatthewHager]

sudo service apache2 start fixes the issue and I'm good until the next restart.

[MatthewHager]

This is still happening quite a bit.

[ergonlogic]

Why are you reloading after a 'vup'? In case there were changes to the shared dirs in the Vagrantfile? Try 'reload --provision' instead. I think we should consider running that as part of 'vup', actually.

[MatthewHager]

This last time I just restarted my computer and then ran vagrant up to start my vm

[ergonlogic]

yeah, we could add a puppet service for Apache, rather than just relying on Ubuntu.

I still think a 'vagrant reload --provision' is a reasonable default operation at the end of 'vup'. Thoughts?

[ergonlogic]

I believe this was an issue with Puppet, and has been resolved with the move to Ansible. Feel free to open a new issue if you see this on 0.4.x and up.