Varying-Vagrant-Vagrants / VVV

An open source Vagrant configuration for developing with WordPress
https://varyingvagrantvagrants.org
MIT License
4.54k stars 848 forks source link

Bug: VVV_LOG unbound variable #2613

Closed tomjn closed 2 years ago

tomjn commented 2 years ago

Are you using the latest stable or develop branch version of VVV?

Yes (develop)

Is it a new VVV or an existing VVV that used to work?

Existing, worked but now broken

Whats the problem?

    default: /srv/provision/provision-helpers.sh: line 255: VVV_LOG: unbound variable

How do we reproduce it?

I ran: vagrant reload

VVV Status screen

~/dev/vvv ᚴ:develop 
❯ vagrant reload
__ __ __ __
\ V\ V\ V / v3.10.0 Ruby:2.7.4, Path:"/Users/tarendai/dev/vvv"
 \_/\_/\_/  git::develop(a5db7c2)

Platform: darwin19 shell:/bin/bash vagrant-goodhosts vagrant-vbguest shared_db_folder_disabled
Vagrant: v2.2.19, virtualbox: v6.1.24

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

==> default: Running action triggers before reload ...
==> default: Running trigger: VVV Pre-Reload...
    default: Running: inline script
    default:  * Performing Database Backups
    default: /srv/provision/provision-helpers.sh: line 255: VVV_LOG: unbound variable
    default:    .  ★         ☁           ★          .
    default: Z        ☽    ★         .        ☁
    default:  Z ▄▀▀▀▄▄▄▄▄▄▄▀▀▀▄   ★            __★__ __ __
    default: ☁ z█▒▒░░░░░░░░░▒▒█    Sleep tight \ V\ V\ V /
    default:  ★  █░░▁░░░░░▁░░█  ★               \_/\_/\_/
    default:    . █░░░▀█▀░░░█ .          ★
    default:  ★   ▀▄░░░░░░░▄▀  ★     .
    default: 
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 vvv.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 one.wordpress.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 one.wordpress.test.192.168.50.4.xip.io
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 two.wordpress.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 multisite.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 tomjn.test
==> default: [vagrant-goodhosts] - found entry for: 192.168.56.4 multisite-subdir.test
==> default: [vagrant-goodhosts] Checking for host entries
==> default: Attempting graceful shutdown of VM...
==> 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 (guest) => 2222 (host) (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: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default: 
    default: Guest Additions Version: 5.2.8_KernelUbuntu r120774
    default: VirtualBox Version: 6.1
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /srv/www => /Users/tarendai/dev/vvv/www
    default: /srv/config => /Users/tarendai/dev/vvv/config
    default: /var/log/php => /Users/tarendai/dev/vvv/log/php
    default: /srv/database => /Users/tarendai/dev/vvv/database/sql
    default: /var/log/nginx => /Users/tarendai/dev/vvv/log/nginx
    default: /srv/provision => /Users/tarendai/dev/vvv/provision
    default: /srv/certificates => /Users/tarendai/dev/vvv/certificates
    default: /var/log/memcached => /Users/tarendai/dev/vvv/log/memcached
    default: /var/log/provisioners => /Users/tarendai/dev/vvv/log/provisioners
==> default: Detected mount owner ID within mount options. (uid: 0 guestpath: /var/log/memcached)
==> default: Detected mount group ID within mount options. (gid: 0 guestpath: /var/log/memcached)
==> default: Detected mount owner ID within mount options. (uid: 0 guestpath: /var/log/nginx)
==> default: Detected mount group ID within mount options. (gid: 0 guestpath: /var/log/nginx)
==> default: Detected mount owner ID within mount options. (uid: 0 guestpath: /var/log/php)
==> default: Detected mount group ID within mount options. (gid: 0 guestpath: /var/log/php)
==> default: Detected mount owner ID within mount options. (uid: 0 guestpath: /var/log/provisioners)
==> default: Detected mount group ID within mount options. (gid: 0 guestpath: /var/log/provisioners)
==> default: Detected mount owner ID within mount options. (uid: 1000 guestpath: /srv/www)
==> default: Detected mount group ID within mount options. (gid: 33 guestpath: /srv/www)
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.
==> default: Running action triggers after reload ...
==> default: Running trigger: VVV Post-Reload...
    default: Running: inline script
    default:  * Restarting Nginx
    default:  * Restarting MariaDB
    default:  * Syncing clocks
    default: 13 Jun 16:27:42 ntpdate[3529]: step time server 185.125.190.56 offset 2.319678 sec
    default:  * clocks synced
    default: ──────────────────────────────────────────────────────────────────────
    default:  ! WARNING
    default:  ! 
    default:  ! Problems occurred in the last provision, VVV may
    default:  ! not work as expected. Check the logs, and don't be 
    default:  ! afraid to ask for help on slack/github
    default: ──────────────────────────────────────────────────────────────────────
~/dev/vvv ᚴ:develop 
❯

Which Operating System are you using?

Apple MacOS (Intel)

Which provider are you using?

VirtualBox