Results 1 to 19 of 19

Thread: trouble with msfconsole after update to kali 3,14

  1. #1
    Join Date
    2013-May
    Posts
    21

    trouble with msfconsole after update to kali 3,14

    Hello all!
    today, after dist upgrading to kali 3.14 i've get error when running msfconsole. can't find any solution with google. any help, please?

    Code:
    /opt/metasploit/apps/pro/ui/vendor/bundle/ruby/2.1.0/gems/packetfu-1.1.8/lib/packetfu.rb:21:in `require': /opt/metasploit/apps/pro/ui/vendor/bundle/ruby/2.1.0/gems/packetfu-1.1.8/lib/packetfu/protos/lldp.rb:19: invalid multibyte escape: /^\x01\x80\xc2\x00\x00[\x0e\x03\x00]/ (SyntaxError)
            from /opt/metasploit/apps/pro/ui/vendor/bundle/ruby/2.1.0/gems/packetfu-1.1.8/lib/packetfu.rb:21:in `block in require_protos'
            from /opt/metasploit/apps/pro/ui/vendor/bundle/ruby/2.1.0/gems/packetfu-1.1.8/lib/packetfu.rb:18:in `each'
            from /opt/metasploit/apps/pro/ui/vendor/bundle/ruby/2.1.0/gems/packetfu-1.1.8/lib/packetfu.rb:18:in `require_protos'
            from /opt/metasploit/apps/pro/ui/vendor/bundle/ruby/2.1.0/gems/packetfu-1.1.8/lib/packetfu.rb:149:in `<top (required)>'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core/db.rb:22:in `require'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core/db.rb:22:in `<top (required)>'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core/db_manager.rb:5:in `require'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core/db_manager.rb:5:in `<top (required)>'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core/framework.rb:69:in `require'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core/framework.rb:69:in `<class:Framework>'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core/framework.rb:13:in `<module:Msf>'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core/framework.rb:5:in `<top (required)>'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core.rb:34:in `require'
            from /opt/metasploit/apps/pro/msf3/lib/msf/core.rb:34:in `<top (required)>'
            from /opt/metasploit/apps/pro/msf3/lib/msf/ui/console/driver.rb:2:in `require'
            from /opt/metasploit/apps/pro/msf3/lib/msf/ui/console/driver.rb:2:in `<top (required)>'
            from /opt/metasploit/apps/pro/msf3/lib/msf/ui/console.rb:11:in `require'
            from /opt/metasploit/apps/pro/msf3/lib/msf/ui/console.rb:11:in `<top (required)>'
            from /opt/metasploit/apps/pro/msf3/lib/msf/ui.rb:11:in `require'
            from /opt/metasploit/apps/pro/msf3/lib/msf/ui.rb:11:in `<top (required)>'
            from /opt/metasploit/apps/pro/msf3/msfconsole:136:in `require'
            from /opt/metasploit/apps/pro/msf3/msfconsole:136:in `<main>'

  2. #2
    Join Date
    2013-Mar
    Location
    Brazil
    Posts
    52
    The METASPLOIT update released yesterday, 13th August, it's not working on Kali when you try to launch the msfconsole.
    The first bug appears on boot.rb file. It reports some error on something named like "GEMFILE".

  3. #3
    Join Date
    2014-Mar
    Posts
    3
    root@Teddy:~# msfconsole
    /usr/share/metasploit-framework/config/boot.rb:4: warning: already initialized constant GEMFILE_EXTENSIONS
    [-] WARNING! The following modules could not be loaded!
    [-] /opt/metasploit/apps/pro/metamodules/firewall_egress/modules/auxiliary/metamodule/firewall_egress.rb: LoadError cannot load such file -- firewall_egress/result_range


    THis is what i'm getting. Very annoying.

  4. #4
    Join Date
    2014-Aug
    Posts
    1
    I have the same issue after update kali yesterday. See screenshot with details.send.jpg

  5. #5
    Join Date
    2013-Feb
    Posts
    13
    Rapid 7 is working on this issue: https://bugs.kali.org/view.php?id=1668

  6. #6
    Join Date
    2014-Jun
    Posts
    3
    Quote Originally Posted by PePeLeGal View Post
    The METASPLOIT update released yesterday, 13th August, it's not working on Kali when you try to launch the msfconsole.
    The first bug appears on boot.rb file. It reports some error on something named like "GEMFILE".
    I have the exact same issue!
    Metasploit boots but it doesn't find any payloads, exploits,...

  7. #7
    Join Date
    2013-May
    Posts
    21
    thnx. i have already figured out it
    i was able to launch msfconsole only under the metasploit dir
    cd /usr/share/metasploit-framework/ && ./msfconsole
    but before it u need manual setup postgress (make user, db and write it in database.yml)

    waiting for fix

  8. #8
    Join Date
    2014-Aug
    Posts
    4
    Quote Originally Posted by 3t3st3r View Post
    thnx. i have already figured out it
    i was able to launch msfconsole only under the metasploit dir
    cd /usr/share/metasploit-framework/ && ./msfconsole
    but before it u need manual setup postgress (make user, db and write it in database.yml)

    waiting for fix
    Its fixed now just update.

  9. #9
    Join Date
    2014-Aug
    Posts
    8
    how exactly? i already tried apt-get update && apt-get upgrade command, but it didn't fix the issue

  10. #10
    Join Date
    2014-Aug
    Posts
    4
    Quote Originally Posted by Martijn1803 View Post
    how exactly? i already tried apt-get update && apt-get upgrade command, but it didn't fix the issue
    apt-get update && apt-get upgrade -y worked for me.

    I assume you are running the latest and great Kali?

  11. #11
    Join Date
    2014-May
    Location
    127.0.1.1
    Posts
    22
    Try

    Code:
     cd /opt/metasploit
    Then type:

    Code:
     msfpro
    the console should load then.

    Or just type:

    Code:
      cd /opt/metasploit && msfpro
    this is a one line input method which does the same as the previous: msfconsole command.
    Last edited by OS-13115; 2014-08-16 at 06:38.

  12. #12
    Join Date
    2014-Aug
    Posts
    8
    i'm running Kali 3.14 i368. unfortunately, your command didn't work either.

    this is the output when i try to execute the msfconsole command (note that both the metasploit service and postgresql service are running just fine)

    Code:
    /usr/share/metasploit-framework/config/boot.rb:4: warning: already initialized constant GEMFILE_EXTENSIONS
    You did not specify how you would like Rails to report deprecation notices for your production environment, please set config.active_support.deprecation to :notify at config/environments/production.rb
    /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/postgresql_adapter.rb:1222:in `initialize': FATAL:  password authentication failed for user "msf3" (PG::ConnectionBad)
    FATAL:  password authentication failed for user "msf3"
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/postgresql_adapter.rb:1222:in `new'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/postgresql_adapter.rb:1222:in `connect'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/postgresql_adapter.rb:324:in `initialize'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/postgresql_adapter.rb:28:in `new'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/postgresql_adapter.rb:28:in `postgresql_connection'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:315:in `new_connection'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:325:in `checkout_new_connection'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:247:in `block (2 levels) in checkout'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:242:in `loop'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:242:in `block in checkout'
    	from /usr/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:239:in `checkout'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:102:in `block in connection'
    	from /usr/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:101:in `connection'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:410:in `retrieve_connection'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_specification.rb:171:in `retrieve_connection'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/connection_adapters/abstract/connection_specification.rb:145:in `connection'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/model_schema.rb:310:in `clear_cache!'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/railtie.rb:103:in `block (2 levels) in <class:Railtie>'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/callbacks.rb:418:in `_run__518135870__prepare__176609281__callbacks'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/callbacks.rb:405:in `__run_callback'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/callbacks.rb:385:in `_run_prepare_callbacks'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/callbacks.rb:81:in `run_callbacks'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.17/lib/action_dispatch/middleware/reloader.rb:74:in `prepare!'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.17/lib/action_dispatch/middleware/reloader.rb:48:in `prepare!'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/application/finisher.rb:47:in `block in <module:Finisher>'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:30:in `instance_exec'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:30:in `run'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:55:in `block in run_initializers'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:54:in `each'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:54:in `run_initializers'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/application.rb:136:in `initialize!'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/railtie/configurable.rb:30:in `method_missing'
    	from /usr/share/metasploit-framework/config/environment.rb:5:in `<top (required)>'
    	from /usr/share/metasploit-framework/lib/fastlib.rb:374:in `require'
    	from /usr/share/metasploit-framework/lib/fastlib.rb:374:in `require'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/polyglot-0.3.3/lib/polyglot.rb:63:in `require'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `block in require'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:236:in `load_dependency'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'
    	from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/application.rb:103:in `require_environment!'
    	from /usr/share/metasploit-framework/lib/metasploit/framework/command/base.rb:68:in `require_environment!'
    	from /usr/share/metasploit-framework/lib/metasploit/framework/command/base.rb:86:in `start'
    	from /opt/metasploit/apps/pro/msf3/msfconsole:26:in `<main>'
    maybe i have to reinstall postgresql and metasploit completely?

  13. #13
    Join Date
    2014-May
    Location
    127.0.1.1
    Posts
    22
    Post the output of:

    Code:
     cd /opt
    and
    Code:
     ls
    please.

    Also, post the output of
    Code:
      cd /opt/metasploit && ls
    Last edited by OS-13115; 2014-08-19 at 17:25.
    "Great understanding comes to those who find questions and question answers."

  14. #14
    Join Date
    2014-Aug
    Posts
    2
    I have exactly the same problem on my VM:

    /usr/share/metasploit-framework/config/boot.rb:4: warning: already initialized constant GEMFILE_EXTENSIONS
    You did not specify how you would like Rails to report deprecation notices for your production environment, please set config.active_support.deprecation to :notify at config/environments/production.rb
    /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/application/configuration.rb:115:in `read': No such file or directory - /opt/metasploit/apps/pro/ui/config/database.yml (Errno::ENOENT)
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/application/configuration.rb:115:in `database_configuration'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/railtie.rb:84:in `block (2 levels) in <class:Railtie>'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/lazy_load_hooks.rb:36:in `instance_eval'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/lazy_load_hooks.rb:26:in `block in on_load'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/lazy_load_hooks.rb:25:in `each'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/lazy_load_hooks.rb:25:in `on_load'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.17/lib/active_record/railtie.rb:80:in `block in <class:Railtie>'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:30:in `instance_exec'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:30:in `run'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:55:in `block in run_initializers'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:54:in `each'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/initializable.rb:54:in `run_initializers'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/application.rb:136:in `initialize!'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/railtie/configurable.rb:30:in `method_missing'
    from /usr/share/metasploit-framework/config/environment.rb:5:in `<top (required)>'
    from /usr/share/metasploit-framework/lib/fastlib.rb:374:in `require'
    from /usr/share/metasploit-framework/lib/fastlib.rb:374:in `require'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/polyglot-0.3.3/lib/polyglot.rb:63:in `require'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `block in require'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:236:in `load_dependency'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'
    from /opt/metasploit/apps/pro/vendor/bundle/ruby/1.9.1/gems/railties-3.2.17/lib/rails/application.rb:103:in `require_environment!'
    from /usr/share/metasploit-framework/lib/metasploit/framework/command/base.rb:68:in `require_environment!'
    from /usr/share/metasploit-framework/lib/metasploit/framework/command/base.rb:86:in `start'
    from /opt/metasploit/apps/pro/msf3/msfconsole:26:in `<main>'

    and the output of the contents of the metasploit directory is as follows:

    app createuser diagnostic_logs.sh msfpro ruby scripts
    apps deleteuser diagnostic_shell resetpw run.sh

    Fortunately I'm not using it at the moment but it's beginning to bug me I can't use the tools.

  15. #15
    Join Date
    2013-Mar
    Location
    Brazil
    Posts
    52
    Today, the problem about GEMFILE was solved.
    However, a new problem has appeared: msfconsole can't connect to the database.
    Last edited by PePeLeGal; 2014-08-22 at 00:33.

  16. #16
    Join Date
    2013-Mar
    Location
    milano
    Posts
    301
    Quote Originally Posted by PePeLeGal View Post
    Today, the problem about GEMFILE was solved.
    However, a new problem has appeared: msfconle can't connect to the database.
    yes confirmed

  17. #17
    Join Date
    2013-Mar
    Location
    milano
    Posts
    301
    hey guys
    I wanted to know if the "database connection" is a "bug-momentary" or now I have to create a "" new-my-db "" ??
    Thanks in advance

    PS:with last Framework Version: 4.10.0-2014082101 the ""problem-remains".. && i 've created a new db in postgres && new connections...now worked-fine...but it is the right way??

  18. #18
    Join Date
    2013-Mar
    Location
    Brazil
    Posts
    52
    Thx for your help zimmaro!

    I think the proper solution must come from metasploit dev team.
    Will see if this week we gonna have this fix.

  19. #19
    Join Date
    2013-Mar
    Location
    Brazil
    Posts
    52
    I agree zimmaro. Framework Version 4.10.0-2014082101 has a bug and is not connecting the database to the console.
    I will wait until the next update.

Similar Threads

  1. Trouble running apt-get update offline
    By yetta in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2017-04-20, 16:51
  2. trouble with apt-get update
    By fulvio97 in forum TroubleShooting Archive
    Replies: 1
    Last Post: 2016-02-29, 12:36
  3. trouble apt-get update
    By ahmedmetwali in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2015-03-07, 08:47
  4. Metasploit & Set update trouble
    By wido046 in forum TroubleShooting Archive
    Replies: 4
    Last Post: 2013-05-03, 14:50

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •