Skip to content

General Issues

Jump to bottom
Jeffrey Martin edited this page Apr 1, 2019 · 7 revisions

Common issues:

  • No memory: The VM itself requires minimum of 2 GB. When the system fails to allot 2GB of RAM, the VM hangs - most commonly while waiting for SSH. (View comment by moj0x0 on issue #20)
  • Waiting for SSH takes a long time: It is found to occur on different operating systems. Possible solution is to manually login via rdp and start ssh-agent.exe at the location C:\Program Files\OpenSSH\bin\. (So many issues. Look at longest issue thread #20)
  • Rubygems SSL error: If you are using a laptop with intercepting proxy (usually company provided laptop), there will be Rubygems SSL error during installation. The gems will not be installed which doesn’t break the build at the initial stage, but does break during the final stages of the build. (Issue #12 and #66)
  • C:\Vagrant... not present: Guest Additions should be installed, so that Vagrant folder on the host system could be shared with the VM. (Issue #75)
  • Non-Latin characters: Vagrant doesn’t work properly when you run it on a machine which contains non-Latin characters. There are different stages where vagrant build fails on a system with non-Latin characters in absolute file paths.
  • Fail to install Chocolatey: Known bug with VirtualBox 5.1.16 which fails to install chocolatey. Upgrade to 5.1.18 (Issue #97)
  • Error during installation of tomcat: Known bug with chocolatey which produces verbose XML output. The error does not affect the installation of tomcat. (Issue #74)

Mac OS X

  • Force shutdown of VM: There is a known bug with Vagrant 1.8.5 which results in force shutdown of VM. Please use 1.9.1 (Refer comment by jbarnett-r7 on issue #4)
  • Failure to start glassfish service on VMware Fusion 10: There is a known issue in VMware Fusion 10 that results in failure to provision glassfish resulting in abort of VM creation. Current workaround is to build using VMware Fusion 9.x

Windows 10

  • Files not found error: If you have turned on your AV, some files like jenkins.exe and meterpreter.php are flagged as Trojan and are deleted/quarantined. Please turn off your AV / whitelist this folder, failing to do so would interrupt the build process. (Refer comment by atarii on issue #51 and by vkrzv on issue #59)
  • Ruby bug: Absolute path for vagrant home directory should not contain any spaces. If you have a space in your system username, please change your vagrant home directory by altering the VAGRANT_HOME environment variable. (Refer comment by Sliim on issue #83)

Linux

  • On Linux systems (particularly Arch Linux), the Vagrant which comes with the OS does not contain support for winrm. Possible solution: remove and install from its official website or install plugins vagrant plugin install winrm winrm-fs (Arch Linux users, refer comment on issue #75)
  • In Kali Linux and other Linux distros, VirtualBox installed via apt-get install virtualbox is known to create issues during the build process, instead download and execute the VirtualBox-5.1.xx-xxxxxx-Linux_amd64.run file from the website (Refer comments by pat-riot and maximilli4n on issue #45)
  • In Cent OS and Fedora, there is a preinstalled package named packer which may collide with the packer executable required for setting up Metasploitable 3. Please follow the installation steps provided in this comment. (Refer #128)

Current supported versions:

Software Version
Packer 1.3.4
Vagrant 1.9.1
VirtualBox 5.2.8 (5.1.14 is awesome as it had least issues)
Clone this wiki locally