Cannot Launch Msfconsole: Could not find rake-10.3.2
Hi,
So after an update I can no longer launch metasploit(msfconsole). I did try some different repositories, so it is possible that I could have broken something, but I am back to using normal repositories now, and everything else seems to work fine so far.
When I try to run "msfconsole" I get the following error:
Code:
/usr/local/rvm/gems/ruby-2.1.5@global/gems/bundler-1.7.6/lib/bundler/spec_set.rb:92:in `block in materialize': Could not find rake-10.3.2 in any of the sources (Bundler::GemNotFound)
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/bundler-1.7.6/lib/bundler/spec_set.rb:85:in `map!'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/bundler-1.7.6/lib/bundler/spec_set.rb:85:in `materialize'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/bundler-1.7.6/lib/bundler/definition.rb:132:in `specs'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/bundler-1.7.6/lib/bundler/definition.rb:177:in `specs_for'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/bundler-1.7.6/lib/bundler/definition.rb:166:in `requested_specs'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/bundler-1.7.6/lib/bundler/environment.rb:18:in `requested_specs'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/bundler-1.7.6/lib/bundler/runtime.rb:13:in `setup'
from /usr/local/rvm/gems/ruby-2.1.5@global/gems/bundler-1.7.6/lib/bundler.rb:121:in `setup'
from /usr/share/metasploit-framework/config/boot.rb:33:in `<top (required)>'
from /usr/local/rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/local/rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /opt/metasploit/apps/pro/msf3/msfconsole:45:in `<main>'
I am using Kali 64bit, everything is updated. The gemfile really should be installed.
Gem list:
Code:
*** LOCAL GEMS ***
bigdecimal (1.2.5, 1.2.4)
bundler (1.7.6)
bundler-unload (1.0.2)
executable-hooks (1.3.2)
gem-wrappers (1.2.7)
io-console (0.4.2)
json (1.8.1)
minitest (5.4.3, 4.7.5)
power_assert (0.2.1)
psych (2.0.6, 2.0.5)
rake (10.1.0)
rdoc (4.1.2, 4.1.0)
rubygems-bundler (1.4.4)
rvm (1.11.3.9)
test-unit (3.0.7, 2.1.5.0)
I have tried doing apt-get "autoremove && apt-get autoclean".
Postgresql is running fine.
The Metasploit Service will not launch.
Systemctl status metasploit.service:
Code:
● metasploit.service - LSB: Metasploit RPC and web daemons
Loaded: loaded (/etc/init.d/metasploit)
Active: failed (Result: exit-code) since Fri 2014-11-21 14:52:35 EST; 8s ago
Process: 3439 ExecStart=/etc/init.d/metasploit start (code=exited, status=127)
Nov 21 14:52:35 unknown metasploit[3439]: /etc/init.d/metasploit: invalid arguments
Nov 21 14:52:35 unknown metasploit[3439]: Starting Metasploit rpc server: prosvc/opt/metasploit/apps/pro/engine/scripts/ctl.sh: 17: /opt/metasploit/apps/pro/engine/scripts/ctl.sh: ruby: not found
Nov 21 14:52:35 unknown systemd[1]: metasploit.service: control process exited, code=exited status=127
Nov 21 14:52:35 unknown systemd[1]: Failed to start LSB: Metasploit RPC and web daemons.
Nov 21 14:52:35 unknown systemd[1]: Unit metasploit.service entered failed state.
I did a journalctl -xn, and it seems like metasploit cannot find ruby somehow?
Code:
- Logs --
Nov host metasploit[3439]: /etc/init.d/metasploit: invalid arguments
Nov host metasploit[3439]: Starting Metasploit rpc server: prosvc/opt/metasploit/apps/pro/engine/scripts/ctl.sh: 17: /opt/metasploit/apps/pro/engine/scripts/ctl.sh: ruby: not found
Nov host systemd[1]: metasploit.service: control process exited, code=exited status=127
Nov host systemd[1]: Failed to start LSB: Metasploit RPC and web daemons.
-- Subject: Unit metasploit.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit metasploit.service has failed.
--
-- The result is failed.
Nov unknown systemd[1]: Unit metasploit.service entered failed state.
I am close to just reinstalling, but it would be rather painful with how much customization I have into everything, and I'd rather not do a full backup/restore if it can be avoided.
Thanks!
