Researcher One

I have 43 days to go ’til exam day. I’m nervious as hell and have thought about pushing back the testing date more times than once in the past week. Also questioning my life choices in more than one way. I need more sleep. I had my 2 cups of coffee and maybe that’s what has my mind bouncing around from task to task instead of remaining focused at the moment.

Over memorial day weekend, I got some solid study time in on Saturday. A little bit of study time on Sunday and a little less on Monday. On Monday, I ran into an issue while starting up the msfdb database on my VM. I usually don’t spin up the database when using msf at this point. However, in reviewing some course materials I thought I’d give it a shot. I suspect it to be platform related. Here’s the error:

└─$ sudo msfdb init      
[sudo] password for parallels: 
[+] Starting database
WARNING:  database "postgres" has a collation version mismatch
DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.41.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
[+] Creating database user 'msf'
WARNING:  database "postgres" has a collation version mismatch
DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.41.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
WARNING:  database "postgres" has a collation version mismatch
DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.41.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
[+] Creating databases 'msf'
WARNING:  database "postgres" has a collation version mismatch
DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.41.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
WARNING:  database "postgres" has a collation version mismatch
DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.41.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
[+] Creating databases 'msf_test'
WARNING:  database "postgres" has a collation version mismatch
DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.41.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
[+] Creating configuration file '/usr/share/metasploit-framework/config/database.yml'
[+] Creating initial database schema
double free or corruption (out)
/usr/bin/msfdb: line 67: 310824 Aborted                 bundle exec rake db:migrate > /dev/null

I tried the usualy apt-get update and then tried a reinstall of metasploit-framework. That didn’t work. After attempting to start it up post update and reinstall I got the following:

/usr/lib/ruby/3.3.0/bundler/definition.rb:599:in `materialize': Could not find bcrypt-3.1.20, bootsnap-1.18.6, json-2.12.0, msgpack-1.6.1, network_interface-0.0.4, nokogiri-1.14.5, pcaprub-0.13.3, pg-1.5.9, redcarpet-3.6.1, puma-6.6.0, thin-1.8.2, bson-5.0.2, ed25519-1.4.0, bcrypt_pbkdf-1.1.1, ffi-1.16.3, sqlite3-1.4.4, eventmachine-1.2.7, bigdecimal-3.1.9, fiddle-1.1.8, racc-1.8.1, nio4r-2.7.4, http_parser.rb-0.8.0, strptime-0.2.5, date-3.4.1, websocket-driver-0.7.7, io-console-0.8.0 in locally installed gems 

Added these to a file to try and install/update these ruby gems only to result in Bundler complaining about something else. Brought back nightmares from the early days of Ruby on Rails. This instance is a little bit older, so when I got home, I tried it on a newer instance only to result in a different bundler error. I’ll spin up a new instance on a PC later today or tomorrow and see how it goes.