Homestead: php7.2-fpm Error after laravel/homestead box update

[bbsnly]

Versions

• Vagrant: 2.0.0
• Provider: VirtualBox 5.1.30
• Homestead: 6.4.0

Host operating system

MacOS

Homestead.yaml

---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: ~/Code
      to: /home/vagrant/Code
      type: "nfs"

sites:
    - map: demo.dev
      to: /home/vagrant/Code/demo

databases:
    - demo

Error

When running vagrant up|reload --provision it fails to restart Nginx: php7.2-fpm.service not found.
Somehow the php7.2-fpm is not installed, inside the /etc/php/7.2/ there is just the mods-available folder

[sumityadav]

As per the release notes we need to upgrade the box to version 4.0.0 but when I run vagrant box update it doesn't update.

$ vagrant box update
==> homestead-7: Checking for updates to 'laravel/homestead'
    homestead-7: Latest installed version: 3.0.0
    homestead-7: Version constraints: 3.0.0
    homestead-7: Provider: virtualbox
==> homestead-7: Box 'laravel/homestead' (v3.0.0) is running the latest version.

[svpernova09]

@bbsnly You must vagrant destroy && vagrant up everytime you download a base box update.

@sumityadav I have no idea, it's definitely released: https://app.vagrantup.com/laravel/boxes/homestead/versions/4.0.0 I've upgraded all of my machines without issue.

[roberto-aguilar]

@sumityadav and @bbsnly probably that is because you haven't pulled the latest changes from the Homestead repository. In the v6.4.0 tag, this file updated the vagrant box required version from >=3.0.0 to >=4.0.0.

[sumityadav]

@DojoGeekRA the issue was, I had specified the version as 3.0.0 in my Homestead.yml file. Changing it to 4.0.0 worked.

[garbinmarcelo]

I'm having the same error when: vagrant --provision

Return:

==> homestead-7: Failed to restart php7.2-fpm.service: Unit php7.2-fpm.service not found.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

[svpernova09]

@marcelogarbin your code repo is newer than you box version. make sure you run vagrant box update && vagrant destroy && vagrant up

[garbinmarcelo]

@svpernova09 I was afraid of losing something after running the "vagrant destroy", I had already updated everything.. That was what was missing, so worked the "provision". I'm just going to have to recreate all the tables again.

Is there any way I can't lose data from tables using "destroy" or not?

Thank's my friend

[svpernova09]

@marcelogarbin you should never have anything IN the VM you can't reinsert easily™.

That being said. You should be able to run dbexport from inside Homestead and you should see the database exports appear in the folder you're running vagrant from. Double check these exports before you destroy.

Whenever you update the base box you must destroy & up to get the new base box image in your virtual machine