Port already in use .when starting a secondary boker
- Thread starter chakkucit
- Start date
RealHeavyDude
Well-Known Member
Each login broker must have its own port number. If you specified the same port number for both login brokers then you must change it for one. Otherwise you have a conflict in that another service is running on one of the ports and therefore the login broker can't start listening on that port. If that's the case you need to find out what the other service is, stop it and run it on a different port.
On rare occasions the broker process or parts of it are in limbo - hanging about blocking the port. If that's the case you must kill the process.
Heavy Regards, RealHeavyDude.
On rare occasions the broker process or parts of it are in limbo - hanging about blocking the port. If that's the case you must kill the process.
Heavy Regards, RealHeavyDude.
RealHeavyDude
Well-Known Member
Reserving a port in /etc/services does not have any meaning apart from being able to define an alias for the port number and declare that this port is intended for usage as you describe. But that does not prevent any other service to occupy this port and therefore conflicting with your declaration in /etc/services.
To find out which process is occupying a port reserved for a database broker in order to kill it depends on which operating system you are running. As you are talking /etc/services it is either some Linux or *nix. AFAIK you can use netstat for that - but as I have never used it myself I can't tell you the exact syntx, googling on it should give you what you need.
But: Killing the process which occupies the port is one thing. The other thing is to prevent this from happening in the future. If it is some other service that occupies the port you either need to fix that service or you need to change the port for the login broker.
Heavy Regards, RealHeavyDude.
To find out which process is occupying a port reserved for a database broker in order to kill it depends on which operating system you are running. As you are talking /etc/services it is either some Linux or *nix. AFAIK you can use netstat for that - but as I have never used it myself I can't tell you the exact syntx, googling on it should give you what you need.
But: Killing the process which occupies the port is one thing. The other thing is to prevent this from happening in the future. If it is some other service that occupies the port you either need to fix that service or you need to change the port for the login broker.
Heavy Regards, RealHeavyDude.