bento/centos-6.7 won't vagrant up after halt or reload

[danemacmillan]

Since moving to the bento/centos-6.7 box, I'm unable to vagrant halt then vagrant up, or do a vagrant reload. The build performs well, and everything installs as expected. The issue comes when I want to suspend or shut down the box for a while and then try to resume it. The box is just completely unable to resume. The following message is output:

The configured shell (config.ssh.shell) is invalid and unable
to properly execute commands. The most common cause for this is
using a shell that is unavailable on the system. Please verify
you're using the full path to the shell and that the shell is
executable by the SSH user.

Would you have any idea why this is happening?

The repository for provisioning the box is located at https://github.com/danemacmillan/vagrantshell, should the VagrantFile indicate anything. I've tried playing with the config.ssh.shell option, but have had no success.

Here is the full output that shows the steps taken:

1403|danemacmillan@dane ~/vagrantshell (master) $ vagrant halt
==> develop: Attempting graceful shutdown of VM...
==> develop: Clearing any previously set forwarded ports...
1420|danemacmillan@dane ~/vagrantshell (master) $ vagrant up
Bringing machine 'develop' up with 'virtualbox' provider...
==> develop: Checking if box 'bento/centos-6.7' is up to date...
==> develop: Preparing network interfaces based on configuration...
    develop: Adapter 0: shared
    develop: Adapter 1: hostonly
==> develop: Clearing any previously set network interfaces...
==> develop: Forwarding ports...
    develop: 2368 => 2368
    develop: 6081 => 6081
    develop: 6379 => 6379
    develop: 27017 => 27017
==> develop: Running 'pre-boot' VM customizations...
==> develop: Booting VM...
==> develop: Waiting for machine to boot. This may take a few minutes...
    develop: SSH address: 10.211.55.4:22
    develop: SSH username: vagrant
    develop: SSH auth method: private key
    develop: Warning: Connection timeout. Retrying...
    develop: Warning: Host appears down. Retrying...
    develop: Warning: Connection refused. Retrying...
The configured shell (config.ssh.shell) is invalid and unable
to properly execute commands. The most common cause for this is
using a shell that is unavailable on the system. Please verify
you're using the full path to the shell and that the shell is
executable by the SSH user.
1421|danemacmillan@dane ~/vagrantshell (master) $ vagrant up
Bringing machine 'develop' up with 'virtualbox' provider...
==> develop: Checking if box 'bento/centos-6.7' is up to date...
==> develop: VirtualBox is already running.

==> develop: Machine 'develop' has a post `vagrant up` message. This is a message
==> develop: from the creator of the Vagrantfile, and not from Vagrant itself:
==> develop:
==> develop: Having issues? Check the 'vagrantshell' documentation: https://github.com/danemacmillan/vagrantshell.
1426|danemacmillan@dane ~/vagrantshell (master) $ vagrant ssh
Last login: Sat Oct  3 17:54:28 2015 from 10.211.55.2
Connection to 10.211.55.4 closed.
1426|danemacmillan@dane ~/vagrantshell (master) $ vagrant status
Current machine states:

develop                   suspended (virtualbox)

The VM is suspended. To resume this VM you can run `vagrant resume`
or `vagrant up` to restart it again, so that vagrant would be able
to control the VM again.
1427|danemacmillan@dane ~/vagrantshell (master) $ vagrant resume
==> develop: Forwarding ports...
    develop: 2368 => 2368
    develop: 6081 => 6081
    develop: 6379 => 6379
    develop: 27017 => 27017
==> develop: Resuming suspended VM...
==> develop: Waiting for machine to boot. This may take a few minutes...
    develop: SSH address: 10.211.55.4:22
    develop: SSH username: vagrant
    develop: SSH auth method: private key
The configured shell (config.ssh.shell) is invalid and unable
to properly execute commands. The most common cause for this is
using a shell that is unavailable on the system. Please verify
you're using the full path to the shell and that the shell is
executable by the SSH user.
1429|danemacmillan@dane ~/vagrantshell (master) $ vagrant resume
==> develop: Fixed port collision for 2368 => 2368. Now on port 2200.
==> develop: Fixed port collision for 6081 => 6081. Now on port 2201.
==> develop: Fixed port collision for 6379 => 6379. Now on port 2202.
==> develop: Fixed port collision for 27017 => 27017. Now on port 2203.
==> develop: Forwarding ports...
    develop: 2368 => 2200
    develop: 6081 => 2201
    develop: 6379 => 2202
    develop: 27017 => 2203
==> develop: Waiting for machine to boot. This may take a few minutes...
    develop: SSH address: 10.211.55.4:22
    develop: SSH username: vagrant
    develop: SSH auth method: private key
The configured shell (config.ssh.shell) is invalid and unable
to properly execute commands. The most common cause for this is
using a shell that is unavailable on the system. Please verify
you're using the full path to the shell and that the shell is
executable by the SSH user.

[danemacmillan]

I ended up testing a couple other boxes and they all had the same issue after reload. The issue came down to including a custom security/limits.conf file. Removing it fixed the issue.

[ptumuluri8]

@danemacmillan did you find any solution to the problem.
I had same issue I am running my vagrant on windows machine