Page MenuHomeSoftware Heritage

Investigate spurious deposit logs
Closed, MigratedEdits Locked


Within the deposit logs, we can see lots of prometheus metrics query noise [1]:

Dec 11 09:59:06 deposit python3[3678588]: 2020-12-11 09:59:06 [3678588] Invalid HTTP_HOST header: ''. You may need to add '' to ALLOWED_HOSTS.
Dec 11 09:59:06 deposit python3[3678588]: 2020-12-11 09:59:06 [3678588] django.request:WARNING Bad Request: /metrics/prometheus
Dec 11 09:59:06 deposit python3[3678588]: 2020-12-11 09:59:06 [3678588] gunicorn.access:INFO - - [11/Dec/2020:09:59:06 +0000] "GET /metrics/prometheus HTTP/1.1" 400 26 "-" "Prometheus/2.7.1+ds"

After investigation, this is due to the fallback mechanism of vhosts in
varnish. As no query matches the vhost selection, neither webapp nor deposit
matches (due to the extra :443), those queries end up being forwarded to the
default vhost, the deposit. Most probably determined by lexicographic order on
the file name.

Note that it currently works in production because the webapp there is not
named webapp (after "deposit" in lexicographic order) but archive (so
before the deposit).

A fix is currently being cooked so that the match work properly and the
requests are forwarded to the proper server.

Event Timeline

ardumont triaged this task as Normal priority.Dec 11 2020, 11:17 AM
ardumont created this task.

You could just add a 00-default vhost that shows a generic error message. (that's not even a hack to rely on alphabetical order for vhost configs)

I agree for the default site but we have several legit requests from the monitoring not correctly routed so the configuration needs to be adapted.

Deployed (rp0.staging,, moma).

And now spurious logs are gone for the deposit.

ardumont removed ardumont as the assignee of this task.