Bug: Memcached can't be activated

[emgk]

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?

New fresh install

Whats the problem?

Getting an error on memcached page.

service memcached status outputs:

● memcached.service - memcached daemon
     Loaded: loaded (/lib/systemd/system/memcached.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2022-01-04 05:41:22 UTC; 2min 28s ago
       Docs: man:memcached(1)
   Main PID: 969 (code=exited, status=71)

Jan 04 05:41:22 vvv systemd[1]: memcached.service: Scheduled restart job, restart counter is at 5.
Jan 04 05:41:22 vvv systemd[1]: Stopped memcached daemon.
Jan 04 05:41:22 vvv systemd[1]: memcached.service: Start request repeated too quickly.
Jan 04 05:41:22 vvv systemd[1]: memcached.service: Failed with result 'exit-code'.
Jan 04 05:41:22 vvv systemd[1]: Failed to start memcached daemon.

Its because virtualbox private ip_address was changed to "192.168.56.4" here https://github.com/Varying-Vagrant-Vagrants/VVV/commit/39ee551a9d6a6cb15699ca989cf8d706fbb6f52c but memcache.conf is still using the old IP address https://github.com/Varying-Vagrant-Vagrants/VVV/blob/develop/provision/core/memcached/config/memcached.conf#L38

How do we reproduce it?

• Enable "memcached" extenstion in config.yml
• Re-provision
• Open vvv.test then "phpMemcachedAdmin"

VVV Status screen

\ V\ V\ V / v3.9.0 Path:"/home/gk/Documents/vvv-debug"
 \_/\_/\_/  git::develop(f475296)

Platform: linux-gnu shell:/bin/bash systemd  vagrant-goodhosts CaseSensitiveFS shared_db_folder_disabled
Vagrant: v2.2.9, virtualbox: v6.1.26

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

Current machine states:

default                   running (virtualbox)

The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.

Which Operating System are you using?

Linux

Which provider are you using?

VirtualBox

[tomjn]

@emgk now that the PR is merged does this still happen?

[emgk]

Nope, all good now, thanks @tomjn! :tada:

vagrant@vvv:~$ service memcached status
● memcached.service - memcached daemon
     Loaded: loaded (/lib/systemd/system/memcached.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2022-01-04 16:52:30 UTC; 1min 46s ago
       Docs: man:memcached(1)
   Main PID: 18179 (memcached)
      Tasks: 10 (limit: 2279)
     Memory: 1.7M
     CGroup: /system.slice/memcached.service
             └─18179 /usr/bin/memcached -m 128 -p 11211 -u memcache -l 127.0.0.1,192.168.56.4

Jan 04 16:52:30 vvv systemd[1]: Started memcached daemon.