Actions
Bug #17212
closedOccasional port number conflicts in integration tests
Story points:
-
Release:
Release relationship:
Auto
Description
Example from developer-run-tests-remainder: #2312 /consoleText at 2f8da8b76071a44b0ce28638cf5322b24e15c73d
[z3333] [/usr/lib/postgresql/11/bin/postgres] 2020-12-11 05:59:05.875 UTC [5417] LOG: listening on IPv6 address "::1", port 46561 [z3333] [/usr/lib/postgresql/11/bin/postgres] 2020-12-11 05:59:05.875 UTC [5417] LOG: listening on IPv4 address "127.0.0.1", port 46561 ... [z1111] time="2020-12-11T05:59:31.950763287Z" level=info msg=executing PID=4071 command="[bundle exec passenger start -p 46561 --log-file /dev/stderr --log-level 4 --no-friendly-error-pages --pid-file /tmp/arvados-server-boot-327913257/passenger.services_api.pid]" dir=services/api ... [z1111] [services/api: passenger] 2020/12/11 05:59:32 [emerg] 6131#0: bind() to 0.0.0.0:46561 failed (98: Address already in use) [z1111] [services/api: passenger] nginx: [emerg] bind() to 0.0.0.0:46561 failed (98: Address already in use)
Ideally passenger and postgresql should both be listening on 127.0.0.11 instead of 0.0.0.0.
Updated by Tom Clegg almost 4 years ago
- Target version set to 2021-02-17 sprint
- Assigned To set to Tom Clegg
- Status changed from New to In Progress
17212-fix-port-conflicts @ 64cec283d576c6a5f156cce36dd8622d28f84a9a -- developer-run-tests: #2287
(based on branch from #16306 even though it's not merged yet)
Updated by Tom Clegg over 3 years ago
Rebased
17212-fix-port-conflicts @ e85a787d224545accc7ee1e8cdda0145dd9ac806 -- developer-run-tests: #2303
Updated by Ward Vandewege over 3 years ago
Tom Clegg wrote:
Rebased
17212-fix-port-conflicts @ e85a787d224545accc7ee1e8cdda0145dd9ac806 -- developer-run-tests: #2303
LGTM, thanks!
Updated by Tom Clegg over 3 years ago
- % Done changed from 0 to 100
- Status changed from In Progress to Resolved
Applied in changeset arvados|69260a600b0cf8878292169c8537951e94de9863.
Actions