Unable to run Metasploit Framework on Kali Linux After reinstallation

[titancomputinglegend]

I tried to uninstall and reinstall msfconsole in linux and I got ended up with:

_> Could not find pcaprub-0.13.1, ruby-oci8-2.2.12 in any of the sources

Run bundle install to install missing gems._

I tried to:

_

cd /usr/share/metasploit-framework sudo bundle install

_

But yet still the same issue.

Summary

Relevant information

[gwillcox-r7]

https://stackoverflow.com/questions/11885398/is-there-a-fix-for-the-could-not-find-gem-in-any-of-the-sources-error-that-d

[titancomputinglegend]

https://stackoverflow.com/questions/11885398/is-there-a-fix-for-the-could-not-find-gem-in-any-of-the-sources-error-that-d

Nothing helped me here :-(

[gwillcox-r7]

Are you using Ruby Version manager such as RVM or rbenv?

Also you shouldn't be running sudo bundle install but rather bundle install. If you run bundle with sudo or root permissions there is a good chance you'll end up creating two separate installation states on your system which may cause you to run into issues like this one. I'd recommend trying to run just bundle install and see if that works for you.

If not you may need to uninstall and then reinstall Ruby fresh, and do this installation as a non-root user, which may help clear this issue.

[github-actions[bot]]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

[github-actions[bot]]

Hi again!

It’s been 60 days since anything happened on this issue, so we are going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.