nooblag / cdn-upcheck Goto Github PK

Currently noting:

• Sometimes HTTP code in MP4 file check can be empty if there's a remote timeout, i.e.
  [WARN] (empty here) Problem checking MP4 file: Cloudflare connection timeout. https://server/path.file.mp4

• MP4 check is able to send a 404 email subject, but the message is not for a 404 error, e.g.
  https://server/path/file.mp4 could not be accessed, 522 error: Cloudflare connection timeout.

Currently if remote end is timing out, the process trundles along, with each identifier returning invalid metadata.

What to do if building check list time exceeds the refresh time as we get an endless loop there--next cron that runs starts building a new check list (since it's after the refresh time) and those metadata scrapes also timeout; etc, etc.

In second-pass checkstream, we have stray curl output (probably on item that has no CDN ID:

 5:44:08  33 of 48  cdnXXXXXX	[ OK ]  200  Identifier01    
curl: (7) couldn't connect to host
 5:46:19  34 of 48           	[ OK ]  302  Identifier02

Currently, in the checkstream, if an identifier returns 404, its metadata is not refreshed and should be.

Rather than running curl twice, capture $exitcode on first check.

Also improve handling of 000 error in MP4 checks.