Opened 11 years ago
Closed 10 years ago
#410 closed enhancement (invalid)
rasserver silently shuts down when a port is already in use
Reported by: | Dimitar Misev | Owned by: | uadhikari |
---|---|---|---|
Priority: | minor | Milestone: | 9.0.x |
Component: | rasserver | Version: | 8.4 |
Keywords: | Cc: | ||
Complexity: | Medium |
Description
It should report a meaningful message, took me a few days to realize that rasserver was shutting down because another server was already running on that port.
Change History (5)
comment:1 by , 11 years ago
Priority: | major → minor |
---|
comment:2 by , 11 years ago
Milestone: | 8.5 → Future |
---|
comment:3 by , 10 years ago
Milestone: | Future → 9.0.x |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:4 by , 10 years ago
The output message: "Bind: Address already in use" is printed in the log file nohup.out already with the existing implementation. To see that, one may execute start_rasdaman.sh twice.
comment:5 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
To test bind port 7002 (or whichever other one is used by rasservers in rasmgr.conf) by some other process, and then try to
start_rasdaman.sh