Sponsored by: █ Sparkhost - Hosting Without Compromises! █ Hybrid Performance Web Hosting █ Spark Host Stream Hosting █ Hybrid IRC & IRCd Server Shell Accounts
Metasploit Framework Not Installing
#1
Posted 01 January 2011 - 01:55 PM
I am trying to install Metasploit Framework 3.5.1 and it's stopping halfway through with this error:
There has been an error.
Error running su postgres -c '"/opt/framework-3.5.1/postgresql/bin/psql" -c "ALTER USER postgres PASSWORD '\''f2040535'\''" ' : psql.bin: could not connect to server: Connection refused
Is the server running on host "localhost" and accepting
TCP/IP connections on port 7175?
The application will exit now.
I have installed postgresql and all the ruby dependencies and all but it still says this error. I accidentally installed metasploit express before I realized it wasn't free before I tried installing the framework and I didn't install any of the dependencies and it installed fine. So I'm not sure how to progress.
Anyone know?
#2
Posted 01 January 2011 - 05:30 PM
http://www.metasploi.../Postgres_setup
#3
Posted 02 January 2011 - 04:48 PM
This simply asks if you have installed pssql before starting metasploit installation.
http://www.metasploi.../Postgres_setup
I appreciate the response, however, I've already done all that specifically from that site two or three times now to make sure it's all there. I'm still getting this error. Any other reason this error would pop up? I should also mention I'm on Fedora 13.
EDIT
OK so I'm running through the steps on that site again and I get this error:
[root@Fxxx]]# su postgres
[postgres@xxx]$ createuser msf_user -P
could not change directory to "/home/me"
Enter password for new role:
Enter it again:
Shall the new role be a superuser? (y/n) n
Shall the new role be allowed to create databases? (y/n) n
Shall the new role be allowed to create more new roles? (y/n) n
createuser: could not connect to database postgres: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
I'm gonna start running through some fedora tutorials on setting it up and I'll come back and edit this as necessary but as of right now I'm not sure what's going wrong.
#4
Posted 02 January 2011 - 11:01 PM
netstat -an | grep 7175
will tell you if have postgres listening on the port.
#5
Posted 03 January 2011 - 10:55 AM
netstat -an | grep 7175
will tell you if have postgres listening on the port.
[root@xxx /]# netstat -an | grep 7175
[root@xxx /]#
Nothing happens. I assume that means it isn't listening but I edited my postgresql.conf file already and it still isn't listening?
# - Connection Settings -
listen_addresses = '*' # what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost', '*' = all
# (change requires restart)
port = 7175 # (change requires restart)
max_connections = 100 # (change requires restart)
#6
Posted 03 January 2011 - 10:58 AM
#7
Posted 03 January 2011 - 11:12 AM
on unix systems instead of netstat I always use lsof, it's just faster.
lsof is used to list open files, but since everything on linux is a file..
so instead of netstat -an | grep 7175 I would do lsof -i :7175 > works faster and types faster
PS: you sure you configured the port right? 7175 is not the default port postgres listens to.. look up the default port and check your error messages!!
Read the rules before you post
#8
Posted 03 January 2011 - 11:31 AM
precisely, you don't have postgres running.
[root@xxx]# service postgresql status
postmaster (pid 4689) is running...
[root@xxx]# netstat -an | grep 7175
[root@xxx]#
I made an edit earlier that I had edited my .conf file to listen on 7175 instead of the default 5432 and that port is opened on my router so I don't understand why its still not working.
#9
Posted 03 January 2011 - 01:02 PM
you sure
Cause this can only mean one thing:
Postgres is not running on 7175..[root@xxx]# netstat -an | grep 7175
[root@xxx]#
Also I do not see why you feel the need to open that port on your router..
Read the rules before you post
#10
Posted 04 January 2011 - 11:47 AM
hence my reaction:
you sure
Cause this can only mean one thing:Postgres is not running on 7175..[root@xxx]# netstat -an | grep 7175
[root@xxx]#
Also I do not see why you feel the need to open that port on your router..
I opened the port just in case it was necessary. Apparently it's not.
So there are two .conf files, postgresql.conf and pg_hba.conf. I edited the postgresql.conf file to run on port 7175 as seen a couple posts up. In order to make this bastard run on port 7175 do I have to edit pg_hba.conf too? And if not, then what's wrong with my edit of postgresql.conf?
netstat -an | grep 5432
This shows that it's still listening on 5432 despite the fact I edited and uncommented the port setting in the postgresql to be 7175. Is there somewhere else I need to edit?
#11
Posted 04 January 2011 - 11:24 PM
Make sure you are using the right package and update it if you got it from the svn.
#12
Posted 06 January 2011 - 05:33 PM
I checked the metasploit wiki nowhere does it mention that you need port 7175 for postgres.
Make sure you are using the right package and update it if you got it from the svn.
I just deleted and uninstalled everything and reinstalled fresh and updated. I am still getting this message. I'm getting really frustrated because it seems hardly anyone else even gets this error message. My only plan of attack at this point is to get postgresql to run on port 7175. I have edited the postgresql.conf file to run on port 7175 and it won't listen to me and continues on it's merry (filtered) way on 5432. The fact that the wiki doesn't even mention changing the from the default port is pissing me off because if that's not the problem I'm having when I try installing then what else can I even do to fix this?? I've spent many many hours researching this problem and I've got NOWHERE (filtered)!
#13
Posted 07 January 2011 - 11:51 AM
Don't.. It's not supposed to run at that portMy only plan of attack at this point is to get postgresql to run on port 7175
Examine the first error you got:
[root@Fxxx]]# su postgres
[postgres@xxx]$ createuser msf_user -P
could not change directory to "/home/me"
Enter password for new role:
Enter it again:
Shall the new role be a superuser? (y/n) n
Shall the new role be allowed to create databases? (y/n) n
Shall the new role be allowed to create more new roles? (y/n) n
createuser: could not connect to database postgres: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
These have nothing to do with the port at all. Postgres is supposed to run at 5432. What went wrong is creating the user..
Read the rules before you post
#14
Posted 10 January 2011 - 05:51 PM
#15
Posted 10 January 2011 - 06:16 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users












