Skip to content

New ObsPy logging configurations appear to break fdsn_fetcher.py logging, leading to the download subcommand failing

Created by: gferragu

Describe the bug Changes in a recent release to ObsPy's logging break our current logging approach in fdsn_fetcher.py.

As is, fdsn_fetchery.py attempts to grab a handler object from the FDSN mass downloader logger, replacing it with our own root handler.

After the ObsPy release, this handler object is empty, leading to an IndexError that is not caught, causing the download to fail.

Their logging changes in the release move logger setup into the MassDownloader class object and as such ObsPy's own logging handler for MassDownloader is only added when the object is initialized.

Possible fixes

  1. Just handle the exception and move on without logging. This is obviously a poor fix
  2. Do not try to replace an existing ObsPy handler here, instead just add ours. It's not clear to me how this would be impacted later on when an additional handler is added during the initialization of the MassDownloader object

So far I have tried option (2) and this allows the download subcommand to run without error, however, when stations and data are found, no data is actually downloaded followed by HTTP Status code: 204 being printed out.