Bug #7324
closed
[Tests] nginx doesn't start when /dev/stderr not accessible
Description
Running the test suite involves starting an nginx proxy to run integration tests for some backend services (in particular arv-git-httpd).
This is started by `python sdk/python/tests/run_test_server.py start_nginx`
The configuration currently uses 'access_log /dev/stderr', presumably because nginx unfortunately does not support configuring access_log to write directly to a file descriptor (as is done with 'error_log stderr') but instead requires a path that can be "open"ed. Unfortunately in some situations nginx does not have permission to open /dev/stderr, and arranging for that to be possible can be difficult (in particular inside of docker containers).
It would be best if the test framework would arrange for nginx's access_log output to be collected another way so that any issues with opening /dev/stderr (or /proc/self/fd/2 for that matter) can be avoided.
Updated by Joshua Randall over 10 years ago
- % Done changed from 0 to 90
- Assigned To set to Joshua Randall
Fixed in https://github.com/curoverse/arvados/pull/28:
```
Fixes 7324 by adding {{ACCESSLOG}} to nginx.conf template and populating it with the path to a fifo created by run_test_server.py in TEST_TMPDIR. Immediately after starting nginx, another process is started to cat the access logs to stderr.
This isn't the most elegant solution, but I'm not sure how else to solve this given the inability to configure nginx to write its access_logs directly to stdout/stderr.
```
Updated by Brett Smith over 10 years ago
- Subject changed from nginx doesn't start when /dev/stderr not accessible to [Tests] nginx doesn't start when /dev/stderr not accessible
- Status changed from New to In Progress
Updated by Brett Smith over 10 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Applied in changeset arvados|commit:3da10f0c0f5a0c0c91d49436a5995c890b03d228.