2026-10-26 17:30:40,780 : Log file opened
2026-10-26 17:30:40,780 : Starting step 2: Build selection file
2026-10-26 17:30:40,813 : Writing data selection to /tmp/working/1/2025-09-26-mww59-239-km-w-of-bandon-oregon/ms_selection
2026-10-26 17:30:40,814 : Starting step 3: Fetch timeseries data
2026-10-26 17:30:40,851 : FetchBulkData call: /bin/FetchData -A "Wilber3" -F "notRASPISHAKE" -l "/tmp/working/1/2025-09-26-mww59-239-km-w-of-bandon-oregon/ms_selection" -O "/tmp/working/1/2025-09-26-mww59-239-km-w-of-bandon-oregon/2025-09-26-mww59-239-km-w-of-bandon-oregon.miniseed" -M "/tmp/working/1/2025-09-26-mww59-239-km-w-of-bandon-oregon/station_metadata" -sd "" 
2026-10-26 17:51:13,625 : Return code: 1
2026-10-26 17:51:13,627 : Output: b'Reading data selection from list file \'/tmp/working/1/2025-09-26-mww59-239-km-w-of-bandon-oregon/ms_selection\'\nReceived 4.4 MB from federator catalog in 14.2 seconds (318.8 KB/s)\nFetching data from IRISDMC (https://www.earthscope.org/data/)\nReceived 5.1 MB of metadata in 12.9 seconds (399.6 KB/s)\nProcessed metadata for 39179 channel epochs in 34.2 seconds\nError fetching time series data: 504 :: Gateway Timeout\n------\n<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">\n<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>504 Gateway Timeout ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size="1px">\nWe can\'t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear="all">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear="all">\n<HR noshade size="1px">\n<PRE>\nGenerated by cloudfront (CloudFront) HTTP3 Server\nRequest ID: CdwJikH6NwEzXb6GBOIgdPBiQm8Y7qE8mhmjRf2WMz_SnXIk_sGADA&#x3D;&#x3D;\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>\n------\nRetrying request in 10 seconds (1 of 2 retries)\nError fetching time series data: 504 :: Gateway Timeout\n------\n<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">\n<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>504 Gateway Timeout ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size="1px">\nWe can\'t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear="all">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear="all">\n<HR noshade size="1px">\n<PRE>\nGenerated by cloudfront (CloudFront) HTTP3 Server\nRequest ID: WW6GN8MJXlCgMvhaJjlwEGRYFkNJYXzifda6JmkkB4jQipEG6KxYMA&#x3D;&#x3D;\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>\n------\nToo many retries, giving up.\nReceived 311.9 MB of time series data in 821.6 seconds (388.7 KB/s) - written to /tmp/working/1/2025-09-26-mww59-239-km-w-of-bandon-oregon/2025-09-26-mww59-239-km-w-of-bandon-oregon.miniseed\nWriting metadata (39179 channel epochs) to file: /tmp/working/1/2025-09-26-mww59-239-km-w-of-bandon-oregon/station_metadata\nFetching data from NCEDC (http://www.ncedc.org)\nError fetching metadata: 500 :: Internal Server Error\n------\nread timeout at /usr/local/share/perl/5.40.1/Net/HTTP/Methods.pm line 274.\n\n------\nReceived 0 Bytes of metadata in 180.6 seconds (0 Bytes/s)\nProcessed metadata for 0 channel epochs in 181.0 seconds\nFetching data from SCEDC (http://scedc.caltech.edu/)\nError fetching metadata: 500 :: Internal Server Error\n------\nread timeout at /usr/local/share/perl/5.40.1/Net/HTTP/Methods.pm line 274.\n\n------\nReceived 0 Bytes of metadata in 180.5 seconds (0 Bytes/s)\nProcessed metadata for 0 channel epochs in 181.0 seconds\nDONE at 2026-10-26 17:51:13\n'
2026-10-26 17:51:13,627 : Partial data downloaded, so processing will continue.
2026-10-26 17:51:13,627 : Starting step 4: Deliver files to pickup area
2026-10-26 17:51:15,267 : No email addresses for status notification
2026-10-26 17:51:15,268 : Closing log file