Solr service fails to start in Vagrant during second boot

[hackdna]

• Specific code commit: 61af81d
• Version of the web browser and OS: N/A
• Environment where the error occurred: Vagrant

Steps to reproduce

1. Set up a new instance from scratch (https://github.com/refinery-platform/refinery-platform#configure-and-load-virtual-machine)
2. vagrant halt
3. vagrant up

Observed behavior

Vagrant log:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/xenial64' version '20190514.0.1' 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 (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: Machine booted and ready!
[default] GuestAdditions 5.2.28 running --- OK.
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /Users/isytchev/code/refinery-platform
    default: /vagrant/transfer => /Users/isytchev/Downloads
    default: /tmp/vagrant-puppet/manifests-5fec6b2a028448772d49fb34206edacc => /Users/isytchev/code/refinery-platform/deployment/puppet/manifests
==> 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 provisioner: shell...
    default: Running: inline script
    default: Job for solr.service failed because the control process exited with error code. See "systemctl status solr.service" and "journalctl -xe" for details.
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.

vagrant@refinery:~$ systemctl status solr.service
● solr.service - LSB: Controls Apache Solr as a Service
   Loaded: loaded (/etc/init.d/solr; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-06-19 10:28:42 EDT; 18min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3144 ExecStart=/etc/init.d/solr start (code=exited, status=1/FAILURE)

System log (journal -xe):

Jun 19 10:32:38 refinery puppet-agent[1898]: Could not request certificate: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)

vagrant@refinery:~$ sudo journalctl -u solr.service
-- Logs begin at Wed 2019-06-19 10:28:32 EDT, end at Wed 2019-06-19 10:51:10 EDT. --
Jun 19 10:28:35 refinery systemd[1]: Starting LSB: Controls Apache Solr as a Service...
Jun 19 10:28:35 refinery su[1404]: Successful su for vagrant by root
Jun 19 10:28:35 refinery su[1404]: + ??? root:vagrant
Jun 19 10:28:35 refinery su[1404]: pam_unix(su:session): session opened for user vagrant by (uid=0)
Jun 19 10:28:35 refinery solr[1395]: Solr home directory /vagrant/refinery/solr not found!
Jun 19 10:28:35 refinery systemd[1]: solr.service: Control process exited, code=exited status=1
Jun 19 10:28:35 refinery systemd[1]: Failed to start LSB: Controls Apache Solr as a Service.
Jun 19 10:28:35 refinery systemd[1]: solr.service: Unit entered failed state.
Jun 19 10:28:35 refinery systemd[1]: solr.service: Failed with result 'exit-code'.
Jun 19 10:28:42 refinery systemd[1]: Stopped LSB: Controls Apache Solr as a Service.
Jun 19 10:28:42 refinery systemd[1]: Starting LSB: Controls Apache Solr as a Service...
Jun 19 10:28:42 refinery su[3147]: Successful su for vagrant by root
Jun 19 10:28:42 refinery su[3147]: + ??? root:vagrant
Jun 19 10:28:42 refinery su[3147]: pam_unix(su:session): session opened for user vagrant by (uid=0)
Jun 19 10:28:42 refinery solr[3144]: Port 8983 is already being used by another process (pid: 3144)
Jun 19 10:28:42 refinery solr[3144]: Please choose a different port using the -p option.
Jun 19 10:28:42 refinery systemd[1]: solr.service: Control process exited, code=exited status=1
Jun 19 10:28:42 refinery systemd[1]: Failed to start LSB: Controls Apache Solr as a Service.
Jun 19 10:28:42 refinery systemd[1]: solr.service: Unit entered failed state.
Jun 19 10:28:42 refinery systemd[1]: solr.service: Failed with result 'exit-code'.

Expected behavior

Solr service is started with no errors

[hackdna]

Not reproducible in 37a9314