Provision failure.

[jason-horvath]

Hello, Perhaps you may have an idea of what is happening here. I was able to manually get things running which I will mention at the the end.

zepgram: [Progress: 1314 / 1314]
    zepgram: [SUCCESS]: Magento installation complete.
    zepgram: [SUCCESS]: Magento Admin URI: /admin
    zepgram: Nothing to import.
    zepgram: <warning>Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/</warning>
    zepgram: ./composer.json has been updated
    zepgram: Loading composer repositories with package information
    zepgram: <warning>Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/</warning>
    zepgram: Updating dependencies (including require-dev)
    zepgram: Package operations: 20 installs, 0 updates, 0 removals
    zepgram:   - Installing magento/module-catalog-sample-data (100.4.0): 
    zepgram: Downloading
    zepgram:  (100%)
    zepgram: Installing "magento/composer-root-update-plugin: 1.1.2" for the Web Setup Wizard
    zepgram: Loading composer repositories with package information
    zepgram: <warning>Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/</warning>
    zepgram: Updating dependencies
    zepgram: /tmp/vagrant-shell: line 82:  6387 Killed                  sudo -u vagrant php -d memory_limit=-1 "$PROJECT_PATH"/bin/magento sampledata:deploy
    zepgram: Cache types config flushed successfully
    zepgram: Cache cleared successfully
    zepgram: File system cleanup:
    zepgram: /home/vagrant/magento/generated/code/Composer
    zepgram: /home/vagrant/magento/generated/code/Dotdigitalgroup
    zepgram: /home/vagrant/magento/generated/code/Magento
    zepgram: /home/vagrant/magento/generated/code/PayPal
    zepgram: /home/vagrant/magento/generated/code/Psr
    zepgram: /home/vagrant/magento/generated/code/Symfony
    zepgram: /home/vagrant/magento/generated/code/Yotpo
    zepgram: The directory '/home/vagrant/magento/generated/metadata/' doesn't exist - skipping cleanup
    zepgram: /home/vagrant/magento/pub/static/deployed_version.txt
    zepgram: Updating modules:
    zepgram: Could not validate a connection to Elasticsearch. No alive nodes found in your cluster
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.

Also missing:

Jun 23 19:52:47 zepgram systemd[1]: Starting A high performance web server and a reverse proxy server...
Jun 23 19:52:48 zepgram nginx[7090]: nginx: [emerg] open() "/home/vagrant/extra/magento.nginx.conf" failed (2: No such file or directory) in /etc/ngi
Jun 23 19:52:48 zepgram nginx[7090]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jun 23 19:52:48 zepgram systemd[1]: nginx.service: Control process exited, code=exited status=1
Jun 23 19:52:48 zepgram systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Jun 23 19:52:48 zepgram systemd[1]: nginx.service: Unit entered failed state.
Jun 23 19:52:48 zepgram systemd[1]: nginx.service: Failed with result 'exit-code'.

Now, for how I was able to get it running post failure.

1.) I immediately ssh'd into the box, running bin/magento setup:upgrade 2.) then created a `/home/vagrant/extra/magento.nginx.conf with a sample config with this content: https://raw.githubusercontent.com/magento/magento2/2.4-develop/nginx.conf.sample

Any ideas why it fails at that point mentioned above? Thanks in advance for your help.

[zepgram]

Hello @KainGNX, well it failed on sample data installation due to lake of memory:

This error should not happen in first place, right after the post-installation could not be executed, so installation was not fully completed, and you finalize it by yourself.

I hope it happens randomly.

[jason-horvath]

Thanks for the quick response, that makes sense. Unfortunately for me, it was happening consistently, so I went in to manually get it going.

Also, I wanted to add. I am using a Late 2016 MacBook Pro with a 2.7 GHz Quad-Core Intel Core i7 and 16GB of memory with over 300GB of free space, so that should be good. I could try upping the memory allocation from the default 4096 in the config.

[jason-horvath]

Just reran this in another directory with the config changed to 8192 RAM, and the install completed, thanks again!