Bugzilla – Bug 12042
Need UI to change server port 9000, in case of conflict
Last modified: 2009-09-08 09:32:22 UTC
Currently there is code in place in our installer that detects conflicts with port 9000 and tries to correct it. But it only tries X times then stops. If Support encounters a user who cannot get the server running, having an option to alter the port manually would be ideal. Perhaps an option on the Diagnostics page?
> Currently there is code in place in our installer that detects conflicts > with port 9000 and tries to correct it. Please not that in 7.3.3+ there's code in SC to fix this issue. Have you ever had reports of this failing (except for ESET users)?
Well the vast majority of our users are using 7.3.2 or older. So my answer won't really address 7.3.3+. But... We get this issue about 1-2 per month and it tends to be very difficult. This would take out the guesswork.
> We get this issue about 1-2 per month and it tends to be very > difficult. This would take out the guesswork. As mentioned elsewhere this is imho obsolete. BTW: What's considered difficult with this issue? Is it the changing of the port (now done automatically) or the analysis (should be logged as the last entry in server.log)?
Michael-- fair enough. Let's close this bug and I'll reopen if we encounter a need to have this feature again. However before I close it, can you add a comment listing any previous bugs that dealt with the port conflict code? I just want to connect the dots. Lastly, per your email, this is how SC works currently: SC detects port conflicts automatically and will use alternative ports (9000-9010, 9100, 8000, 10000) if needed. If none of these fourteen ports does work, then there's very likely a different issue than a port conflict (like eg. ESET AV).
James provided this list of relevant bugs... Legacy bugs: * bug 120 * bug 146 * bug 417 * bug 528 * bug 602 * bug 2703 * bug 4254 SC 7.0+ bugs: * bug 8257 * bug 8586 * bug 9389 * bug 9454 * bug 10913