Confirmed users
3,727
edits
TestEngineering/Services/TokenServerAndSyncLoadTesting: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Services/TokenServerAndSyncLoadTesting (view source)
Revision as of 22:56, 19 September 2014
, 19 September 2014→Debugging the Issues
| Line 419: | Line 419: | ||
File \"/data/tokenserver/local/lib/python2.6/site-packages/gunicorn/workers/async.py\"... | File \"/data/tokenserver/local/lib/python2.6/site-packages/gunicorn/workers/async.py\"... | ||
..."Connection pool is full, discarding connection: 127.0.0.1", "... | ..."Connection pool is full, discarding connection: 127.0.0.1", "... | ||
Also, any 499s are probably an artifact of the current (V1) load test. | |||
REF: | REF: | ||
https://bugzilla.mozilla.org/show_bug.cgi?id=1040396 | https://bugzilla.mozilla.org/show_bug.cgi?id=1040396 | ||
| Line 436: | Line 437: | ||
result: 'failure',\n reason: 'algorithms do not match' | result: 'failure',\n reason: 'algorithms do not match' | ||
result: 'failure',\n reason: 'audience mismatch: scheme mismatch' | result: 'failure',\n reason: 'audience mismatch: scheme mismatch' | ||
Also, any 499s in the nginx logs are probably an artifact of the current (V1) load test. | |||
* Acceptable Sync node errors: | * Acceptable Sync node errors: | ||
| Line 448: | Line 450: | ||
Usually, you will not see 304s, 400s, 412s, or 415s for a load test, | Usually, you will not see 304s, 400s, 412s, or 415s for a load test, | ||
although they may show up in the logs after running the remote integration tests. | although they may show up in the logs after running the remote integration tests. | ||
Also, any 499s are probably an artifact of the current (V1) load test. | |||
In /var/log/hekad/sync_1_5.stderr.log | In /var/log/hekad/sync_1_5.stderr.log | ||