2026-10-26 12:58:13,155 : Log file opened 2026-10-26 12:58:13,155 : Starting step 2: Build selection file 2026-10-26 12:58:13,166 : Writing data selection to /tmp/working/1/2025-09-09-mww51-163-km-w-of-port-orford-oregon/ms_selection 2026-10-26 12:58:13,167 : Starting step 3: Fetch timeseries data 2026-10-26 12:58:13,175 : FetchBulkData call: /bin/FetchData -A "Wilber3" -F "notRASPISHAKE" -l "/tmp/working/1/2025-09-09-mww51-163-km-w-of-port-orford-oregon/ms_selection" -O "/tmp/working/1/2025-09-09-mww51-163-km-w-of-port-orford-oregon/2025-09-09-mww51-163-km-w-of-port-orford-oregon.miniseed" -M "/tmp/working/1/2025-09-09-mww51-163-km-w-of-port-orford-oregon/station_metadata" -sd "" 2026-10-26 13:20:30,084 : Return code: 1 2026-10-26 13:20:30,085 : Output: b'Reading data selection from list file \'/tmp/working/1/2025-09-09-mww51-163-km-w-of-port-orford-oregon/ms_selection\'\nReceived 4.4 MB from federator catalog in 14.5 seconds (310.0 KB/s)\nFetching data from IRISDMC (https://www.earthscope.org/data/)\nReceived 5.0 MB of metadata in 12.6 seconds (402.9 KB/s)\nProcessed metadata for 38486 channel epochs in 36.1 seconds\nError fetching time series data: 504 :: Gateway Timeout\n------\n\n\nERROR: The request could not be satisfied\n\n

504 Gateway Timeout ERROR

\n

The request could not be satisfied.

\n
\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
\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
\n
\n
\nGenerated by cloudfront (CloudFront) HTTP3 Server\nRequest ID: D3vBjDObAFrR4NRTFyRE-jHD683X6-BYOYmLOD7xm_d5oMAxK688uA==\n
\n
\n
\n\n------\nRetrying request in 10 seconds (1 of 2 retries)\nError fetching time series data: 504 :: Gateway Timeout\n------\n\n\nERROR: The request could not be satisfied\n\n

504 Gateway Timeout ERROR

\n

The request could not be satisfied.

\n
\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
\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
\n
\n
\nGenerated by cloudfront (CloudFront) HTTP3 Server\nRequest ID: lgbAO8Betmsxz3tPYDPMBImm-EDZT5IijOdD9Vyracup6P0EG855_g==\n
\n
\n
\n\n------\nToo many retries, giving up.\nReceived 294.3 MB of time series data in 923.6 seconds (326.3 KB/s) - written to /tmp/working/1/2025-09-09-mww51-163-km-w-of-port-orford-oregon/2025-09-09-mww51-163-km-w-of-port-orford-oregon.miniseed\nWriting metadata (38486 channel epochs) to file: /tmp/working/1/2025-09-09-mww51-163-km-w-of-port-orford-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 13:20:30\n' 2026-10-26 13:20:30,085 : Partial data downloaded, so processing will continue. 2026-10-26 13:20:30,085 : Starting step 4: Deliver files to pickup area 2026-10-26 13:20:31,617 : No email addresses for status notification 2026-10-26 13:20:31,617 : Closing log file