I am using following code to waiting client connect.
use exploit/multi/handler
set payload windows/meterpreter/reverse_tcp
set lhost 192.168.56.1
set lport 4444
run -jz
The question is: port listening was stopped after one connection was established. It cause subsequent connection failed. I have to type run -jz manually again and again after connection established.
Is there any way to continue listening to the port with just typing command once?
ps: Manjaro Llinux with Metasploit5-dev
Found the solution: execute "set ExitOnSession false" before "run -jz". that's what I need.
Related
I am trying to run an application on port 8080 but I received a message that says "Web server failed to start. Port 8080 was already in use." I tried to access localhost:8080 on my browser and it says "unable to connect". I searched on how to handle this problem and it was to kill whatever activity is going on in port 8080. It didn't work. I tried the command netstat -a -n -o | find "8080" and netstat -ano | findstr :, but it didn't produce any results. I even tried to run as administrator but it still wouldn't show any results. According to the solutions that I found, I expect to find something along the lines of TCP and LISTENING. I accessed localhost:8080 a couple of days back and it was fine. Can anyone tell me what went wrong?
picture attached
The only recent changes I made was to enable VMX on my laptop a few days ago. Other than that, I did not change nor configure any settings whatsoever.
Simply running "netstat -ab" will display all ports taken. Try to run it and see which process is using port 8080. It always lists all ports taken.
Description:
The Tomcat connector configured to listen on port 9009 failed to start. The port may already be in use or the connector may be misconfigured.
Action:
Verify the connector's configuration, identify and stop any process that's listening on port 9009, or configure this application to listen on another port.
I get an error of this kind, but I have not changed the port, what should I do in this case?
I can throw application.properties
First, if you would like to check application running on that port please either do netstat command or resmon.exe and if application is user then exit it.
Or start appliation with new port number
I've had no luck in starting the postgres server. I can add new databases, tables, etc to the postgres from the terminal, but can't add things to the tables through a webpage. The webpage is running on a localhost for now.
The postgres data folder was originally created in a root user, but I moved it to my own user account and it solved many problems, but I'm back at the same old error I keep getting after entering postgres -D data (data being the data cluster folder)
EDT LOG: could not bind IPv4 socket: Address already in use
2015-06-18 11:11:35 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2015-06-18 11:11:35 EDT LOG: could not bind IPv6 socket: Address already in use
2015-06-18 11:11:35 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2015-06-18 11:11:35 EDT WARNING: could not create listen socket for "*"
2015-06-18 11:11:35 EDT FATAL: could not create any TCP/IP sockets
I tried two different commands to start the server.
pg_ctl -D data -l logfile start
which gave me this, but it's not correct
server starting
and
pg_ctl -D /Library/PostgreSQL/9.4/data -l log file start
which gave me this
LOG: skipping missing configuration file "/Library/PostgreSQL/9.4/data/postgresql.auto.conf"
pg_ctl: another server might be running; trying to start server anyway
server starting
The postgresql.auto.conf file is most definitely there with correct name and everything. If I try to stop the supposedly started server it results in this with the first one from the first command I tried and the second stop with the second command.
Is server running?
and
LOG: skipping missing configuration file "/Library/PostgreSQL/9.4/data/postgresql.auto.conf"
pg_ctl: could not send stop signal (PID: 83): Operation not permitted
Something seems to already use port 5432.
Try to find out, which program (maybe another instance of postgres) is blocking that port and decide whether to stop that other process, or not.
As an alternative reconfigure postgres to use other ports.
Maybe you can find out, what is blocking that port by typing this into the console:
lsof -n -i4TCP:5432 | grep LISTEN
Its clear that there is another instance of postgres running. You have to stop that one before starting yours manually as this will go in conflict with the port numbers.
sudo launchctl stop com.edb.launchd.postgresql-9.4
The try and launch with your command.
When I run the command to start SUMO,it prints Listening on port 9999 and starts directly to print also :
Handling connection from 127.0.0.1 on port 63825
Got Traci message of length 1347375952
Got Traci command of length 31
Got Traci command 0x2f
Aborting on error:Expected CMD-FILE_SEND(0x75),but got 0x2f
Closing connection from 127.0.0.1 on port 63825
Connection from 127.0.0.1 on port 63826
Handling connection from 127.0.0.1 on port 63826
Got........
And so one
Instead of waiting for the simulation to start.
And it continues to print the same error message even if I start the simulation or I close the simulation.
So the same error message continues to be printed on the command terminal until I close it.
What is wrong? And someone knows how can I fix this problem?
Your system seems to run another program that tries to connect to TCP port 9999. Independent of whether you are running this program knowingly or if it is malware, either shutting down the conflicting program or changing the sumo-launchd.py port number will help. See the sumo-launchd.py documentation for how to change its port number.
i am facing the issue in webshpere ..the server is not staringReading configuration for server: server1
ADMU3028I: Conflict detected on port 8896. Likely causes: a) An instance of
the server server1 is already running b) some other process is
using port 8896
ADMU3027E: An instance of the server may already be running: server1
ADMU0111E: Program exiting with error:
com.ibm.websphere.management.exception.AdminException: ADMU3027E: An
instance of the server may already be running: server1
The error seems quite explicit: another program is using port 8896.
To verify this you can use these commands:
(Linux) sudo netstat -lptu|grep 8896
(Windows) netstat -a -b (or other tools)
You can decide to stop the process that create the conflict or change the ports used by WAS:
Updating ports in existing profile
This can be caused when the services don't shut down correctly and the java.exe processes hold a lock on the applications port. (8896).
To resolve this problem you can use one of the following options.
1) Open your taskmanager and end task the java.exe process for your JVM that is holding a lock on the servers port then restart the JVM from the WebSphere console
2) You can restart the physical server so the java.exe process shuts down and releases the port. Once the server starts back up you can start JVM and bring the application up.