Bridges include or-address [::]:$port in their server descriptor
Since yesterday 16:05 UTC, metrics-db is complaining about or-address lines in bridge server descriptors that it cannot parse and sanitize. Here are two server descriptors it doesn't like with [scrubbed] parts put in by me:
router Unnamed [scrubbed] 9001 0 0
or-address [::]:9001
platform Tor 0.2.3.12-alpha (git-5c7b9174848cc05b) on Linux i686
opt protocols Link 1 2 Circuit 1
published 2012-02-15 21:08:13
...router Unnamed [scrubbed] 443 0 0
or-address [::]:9090
platform Tor 0.2.3.12-alpha (git-5c7b9174848cc05b) on Linux x86_64
opt protocols Link 1 2 Circuit 1
published 2012-02-16 03:37:30
...The [::] address part probably comes from some misconfiguration on the bridge. But the bridge shouldn't include this address in its server descriptor.
I'm cc'ing murble who is running these bridges. (Maybe don't fix the configuration yet, so that we can figure out how to fix Tor.)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information