Error: Directory not empty @ dir_s_rmdir on puppet module install

[Eugen Stranz]

Hello there,

I'm using the latest files of the master branch => https://github.com/joomlatools/joomlatools-vagrant

I'm following the steps under "Hacking on the box" to set it up.

Unfortunately I'm running into an error while executing puppet module install. I googled my ass of but without success....

I'm getting the same errors when I use the v1.5.1 release.

I can't get the joomla box running again. I'm a big fan of the box and have used it in the past.

I'm literally ready to pay one of u guys to help me fix that during a screen share session so I can "box restore" again ;-)

VirtualBox 6.0

Vagrant 2.2.5

MacOS Mojave 10.14.6

[Steven Rombauts]

Hi Eugen,

Sorry to hear you're not getting the box to work again. Could you copy the selected text and post it here? I can't read your screenshot properly, it's a little bit too small.

Cheers,

Steven

[Eugen Stranz]

default: Successfully installed librarian-puppet-2.2.3

    default: 15 gems installed

    default: Error executing puppet module install. Check that this command succeeds:

    default: puppet module install --version 4.25.1 --target-dir /vagrant/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/4.25.1 --module_repository https://forgeapi.puppetlabs.com --modulepath /vagrant/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/4.25.1 --module_working_dir /vagrant/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/4.25.1 --ignore-dependencies puppetlabs-stdlib

    default: Error:

    default: Error: Directory not empty @ dir_s_rmdir - /vagrant/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/4.25.1/cache/puppetlabs-stdlib20190916-21452-1glt4a5

    default: Error: Try 'puppet help module install' for usage

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.

[Eugen Stranz]

And this:

default: Successfully installed librarianp-0.6.4

    default: Successfully installed librarian-puppet-2.2.3

    default: 15 gems installed

    default: /vagrant/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppetlabs-stdlib/4.25.1/stdlib does not exist, something went wrong. Try removing it manually

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

Am Montag, 16. September 2019 18:51:35 UTC+8 schrieb Steven Rombauts:

[Steven Rombauts]

Hi Eugen,

Unfortunately I don't have a straightforward answer to this one either. Is it possible that file permissions were changed because of previous attempts? Did you try anything using "sudo" at some point?

I would try to:

- Destroy to broken box: vagrant destroy

- Make sure to remove the Puppet Librarian directories on your host: <path to the Joomlatools Vagrant repository>/puppet/.tmp and <repository>/puppet/.librarian 

- Try again with vagrant up

Alternatively, the error could suggest the mounted directory is not writable from inside the box. Worst-case, this could mean that your disk is full? Maybe the NFS mount did not succeed correctly, in which case I would try to log in to the box (after a failed configuration attempt) with vagrant ssh and try to write and delete something in the /vagrant/puppet directory to see what happens. 

Cheers,

Steven