search

mozilla / tls-observatory

An observatory for TLS configurations, X509 certificates, and more.
Mozilla Public License 2.0
535 stars 88 forks source link

Scan error on column index 9, name "scan_error" #382

Open drwetter opened 5 years ago

drwetter commented 5 years ago

Hello,

I tried e.g. to run curl 'https://tls-observatory.services.mozilla.com/api/v1/results?id=12302333' which made problems:

Failed to retrieve scan id 12302333 from database: sql: Scan error on column index 9, name "scan_error": unsupported Scan, storing driver.Value type <nil> into type *string
sql: Scan error on column index 9, name "scan_error": unsupported Scan, storing driver.Value type <nil> into type *string

(I was using a similar call to retrieve cipher usage statistics.)

Cheers, Dirk

jvehent commented 5 years ago

hmmm that's a very old scan. not sure what is happening there. All scans until https://tls-observatory.services.mozilla.com/api/v1/results?id=26449359 show that error, and https://tls-observatory.services.mozilla.com/api/v1/results?id=26449360, the next one in line, is fine.

@autrilla do you have any way to check which release was running on 2018-03-02 ?

autrilla commented 5 years ago

@jvehent based on the Jenkins job history, I see the following deploys around that date:

1.2.36 was deployed on 2018-02-27 1.2.37 was deployed on 2018-03-02 at 1:17:58 PM UTC 1.2.38 was deployed on 2018-03-02 at 6:45:54 PM UTC 1.2.39 was deployed on 2018-03-03 at 2:51:34 PM UTC 1.2.40 was deployed on 2018-03-08

So depending on when it happened, I'd guess either 1.2.36, 1.2.37, or 1.2.38.

autrilla commented 5 years ago

Based on the timestamp on https://tls-observatory.services.mozilla.com/api/v1/results?id=26449360, I've narrowed it down to 1.2.37 being the buggy version. The timestamp coincides perfectly with the deployment of version 1.2.38.