1. Azimuth Backup
  2. Azimuth Backup Project
  3. azimuth-inventory
  4. Issues
Issue #15 closed

U.S. Forest Service Climate Change Atlas Web site

Jan Galkowski
created an issue

http://www.fs.fed.us/nrs/atlas/

Replicate

#!shell

http://www.fs.fed.us/nrs/atlas/

at

#!shell

/media/jan-one/fs.fed.us.nrs.atlas

using

#!shell

wget --wait=5 -nv -4 --output-file=fs-fed-nrs-atlas-us-errors.log -t 40 -nc -r --no-check-certificate -p http://www.fs.fed.us/nrs/atlas/

Comments (13)

  1. Jan Galkowski reporter

    The same problem that afflicts Issue #13 "NOAA ESRL CT2015 Carbon Tracker Web site" is seen here ... Embedded slashes. Again, the approach that will be taken is to peruse the transfer log after initial completion of transfer to /media/jan-one/, rename the offending files, and just transfer those.

  2. Jan Galkowski reporter

    Also, there appear to be certain files missing. For instance,

    #!shell
    
    http://www.fs.fed.us/foresthealth/fhm/em/mtgs/wg/reporting_plan.pdf:
    2016-12-20 09:35:05 ERROR 404: Not Found.
    http://www.fs.fed.us/foresthealth/fhm/em/annc/strategic_plan03.pdf:
    2016-12-20 09:35:10 ERROR 404: Not Found.
    http://www.fs.fed.us/foresthealth/fhm/em/fhh/fhh_format/fhh_format.pdf:
    2016-12-20 09:35:15 ERROR 404: Not Found.
    http://www.fs.fed.us/foresthealth/fhm/em/pubs/ufhm/ufhm_09_02.pdf:
    2016-12-20 09:35:20 ERROR 404: Not Found.
    http://www.fs.fed.us/na/durham/foresthealth/text/stressor_report/stressor_report.shtml:
    2016-12-20 09:35:25 ERROR 404: Not Found.
    

    I am compiling the reports Scott recommended at https://bitbucket.org/azimuth-backup/azimuth-inventory/wiki/Generating%20SHA-256%20hashes.md

    And, by the way, some of these files are in fact inaccessible, per below, for

    #!shell
    
    http://www.fs.fed.us/foresthealth/fhm/em/mtgs/wg/reporting_plan.pdf
    

    fs_atlas_missing_2016-12-22_185349.jpg

  3. Jan Galkowski reporter

    This dataset has been uploaded, and, apart from some changes needed in certain filenames, due to embedded urlencodes, specifically %2F, being mapped to their respective characters, the SHA256 sums check out. Below is a difference report, showing the files which are on the archive but not in my original because these were uploaded with name changes one at a time.

    #!shell
    
    
    [ 1 ] C:\builds\ClarXiv\fs-fed-us-nrs-atlas-web-on-archive-sorted.sha256-sha-only.txt 12/23/2016, 2:18:07 PM
    [ 2 ] C:\builds\ClarXiv\fs-fed-nrs-atlas-web-sorted.sha256_sha-only.txt 12/23/2016, 2:18:27 PM
    ------------------------------------------------------------------------------------------------------------------------
    =======
    39058   <!  c6c7530e9adaf02a51ad2c6033781eec232d3feecbff764dc79cacf1fe45957f¬
    =======
    =======
    44137   <!  e15293bef31a1189b18c8a1a1d1950beda865c129b37569d7fca0bee35c97ee1¬
    =======
    =======
    44581   <!  e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855¬
    44582   <!  e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855¬
    44583   <!  e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855¬
    =======
    ------------------------------------------------------------------------------------------------------------------------
    
    Report type: Just Differences
    
    Summary for 1 <--> 2:
    3 Block(s) diff   5 : 0 Line(s) diff
    
    ------------------------------------------------------------------------------------------------------------------------
    

    The filename changes involved replacing the %2F with a hyphen.

  4. Log in to comment