You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
Errors can be introduced onto a Parrot disk (in my case after a failed parrot provision when trying to add a large database):
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
echo; printf $SSH_AUTH_SOCK
An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.
If the problem persists, please report a bug to the net-ssh project.
timeout during server version negotiating
This can be resolved as follows:
download an Ubuntu disk image (e.g. ubuntu-14.04.4-server-amd64.iso)
add the disk image as a CD drive on the parrot virtual machine
boot from the CD drive (press F12 on startup)
select Rescue option and (eventually) getting to a terminal prompt
unmount /dev/sda1 (if it is mounted) - umount /dev/sda1
repair errors - fsck.ext4 /dev/sda1
on host machine: parrot restart
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Errors can be introduced onto a Parrot disk (in my case after a failed
parrot provision
when trying to add a large database):This can be resolved as follows:
umount /dev/sda1
fsck.ext4 /dev/sda1
parrot restart
The text was updated successfully, but these errors were encountered: