Closed petrrr closed 6 years ago
I could reproduce it.
It is hopefully fixed with 68b567e8a059321388687062c805bd87656e9aff. It is working for me.
Are there any updates on your side? Did the fix help?
@gempa-jabe: Thanks for your fix and the headup!
We applied the fix some days ago. The problem we observed is gone and so far we have not observed any other similar problems. Here the related log for the same request as reported above.
2018/04/12 17:17:31 [debug/log] request (93.63.207.206): /fdsnws/dataselect/1/query?net=MN&sta=VLC&cha=LHN&start=2008-10-30T23:55:00&end=2008-11-01T00:05:00&nodata=404
2018/04/12 17:17:31 [debug/log] adding stream: MN.VLC..LHN 2008-10-30T23:55:00.0000Z - 2008-11-01T00:05:00.0000Z
2018/04/12 17:17:31 [debug/RecordStream] trying to open stream sdsarchive:///mnt/archive_aufs
2018/04/12 17:17:31 [debug/SDSARCHIVE] SDS request: 2008,10,30,23,55,00 2008,11,01,00,05,00 MN VLC LHN
2018/04/12 17:17:31 [debug/SDSARCHIVE] + /mnt/archive_aufs/2008/MN/VLC/LHN.D/MN.VLC..LHN.D.2008.304 (init:1)
2018/04/12 17:17:31 [debug/SDSARCHIVE] + /mnt/archive_aufs/2008/MN/VLC/LHN.D/MN.VLC..LHN.D.2008.305 (init:0)
2018/04/12 17:17:31 [error/SDSARCHIVE] file read exception: Invalid miniSEED header
2018/04/12 17:17:31 [error/SDSARCHIVE] file read exception: Invalid miniSEED header
2018/04/12 17:17:31 [error/SDSARCHIVE] file read exception: Invalid miniSEED header
2018/04/12 17:17:31 [error/SDSARCHIVE] file read exception: Invalid miniSEED header
2018/04/12 17:17:31 [error/SDSARCHIVE] file read exception: Invalid miniSEED header
2018/04/12 17:17:31 [error/SDSARCHIVE] file read exception: Invalid miniSEED header
2018/04/12 17:17:31 [error/SDSARCHIVE] file read exception: Invalid miniSEED header
2018/04/12 17:17:31 [error/SDSARCHIVE] file read exception: Invalid miniSEED header
2018/04/12 17:17:31 [debug/SDSARCHIVE] + /mnt/archive_aufs/2008/MN/VLC/LHN.D/MN.VLC..LHN.D.2008.306 (not found)
2018/04/12 17:17:31 [debug/log] fdsnws-dataselect: returned 202240 bytes of mseed data
2018/04/12 17:17:31 [info/log] [reactor] 93.63.207.206 - - [12/Apr/2018:17:17:30 +0000] "GET /fdsnws/dataselect/1/query?net=MN&sta=VLC&cha=LHN&start=2008-10-30T23:55:00&end=2008-11-01T00:05:00&nodata=404 HTTP/1.0" 200 202240 "-" "curl/7.58.0"
I think this issue could be closed. Sorry for the delay in reporting back.
Thank you for confirmation. I will close the ticket and include the fixes into a new patch release.
Thanks!
Unfortunately we observe an other case of very similar problems, as already reported in #163 and #167.
Apparently, the SDS request handler ends up in some infinite loop, never returns and therefore the FDSNWS service does stop replying. The problem is again due to a corrupt file, but this case is still no catched.
Here the relevant log:
And the compromised file: