soeka Posted April 10, 2018 Report Share Posted April 10, 2018 The file exist on the disk, and when new version available, this error always happened when I try to update or check update the application with compare hash option set. I have to force download in order to update. If I remove hash camparison, update or check update work just fine. If this not a bug, can someone help me review my config? (mtk-arm.xml), maybe there is something misconfigured. Thanks. Link to comment Share on other sites More sharing options...
shawn Posted April 11, 2018 Report Share Posted April 11, 2018 Most commonly this problem happens in either of these situations: 1) The destination drive letter has changed (such as a removable device that is no longer the original drive letter). Are you still downloading to the D: drive? That is, does "{path-download}" still reference "D:\Unduhan" and not something different like "J:\Unduhan" or "D:\Unduhan\" (note the trailing slash)? 2) The hash is invalid. This could be from added spaces, tabs, or other invalid characters that are being collected incorrectly. It's also possible that since you're not using capture that this could be the problem. Use this instead: (?<={url:filename}: )([a-z0-9]{64}) Link to comment Share on other sites More sharing options...
Yuri-Tech Posted April 11, 2018 Report Share Posted April 11, 2018 number #2 in shawn's post seems to be the issue. Also check your user agent and spoof refferer to prevent repititive server calls, their firewall might block them.- Sha hashing should not have any issues in comparing with lower case letters so that shouldn't be it. I like these mikrotik equipment:) Link to comment Share on other sites More sharing options...
soeka Posted April 12, 2018 Author Report Share Posted April 12, 2018 Actually, this error always occurs whenever there is a newer version update. Nothing has changed. Download dir, variable regex and other variables and configuration never changed (#1, #2). But still, I always got this error. Update & Check for update log: 12/04/2018 17:58:09: Update started with 1 application(s) 12/04/2018 17:58:11: Mikrotik CHR (img): Replacing {version} in 'https://download2.mikrotik.com/routeros/{version}/chr-{version}.img.zip' with '6.40.7' 12/04/2018 17:58:11: Mikrotik CHR (img): Replacing {url} in '{url}' with 'https://download2.mikrotik.com/routeros/6.40.7/chr-6.40.7.img.zip' 12/04/2018 17:58:11: Mikrotik CHR (img): Using referer: https://mikrotik.com/download 12/04/2018 17:58:12: Mikrotik CHR (img): Server source file: /routeros/6.40.7/chr-6.40.7.img.zip 12/04/2018 17:58:12: Mikrotik CHR (img): Determined target file name: D:\Unduhan\Jaringan\Mikrotik\Bugfix\chr-6.40.7.img.zip 12/04/2018 17:58:12: Mikrotik CHR (img): Checking if update is required... 12/04/2018 17:58:12: Mikrotik CHR (img): Target file missing, comparing to previously downloaded file at D:\Unduhan\Jaringan\Mikrotik\Bugfix\chr-6.39.3.img.zip 12/04/2018 17:58:14: Mikrotik CHR (img): Replacing {version} in 'https://download2.mikrotik.com/routeros/{version}/chr-{version}.img.zip' with '6.40.7' 12/04/2018 17:58:14: Mikrotik CHR (img): Replacing {url} in '(?<=sha256 </b>{url:filename}: )([a-z0-9]{64})' with 'https://download2.mikrotik.com/routeros/6.40.7/chr-6.40.7.img.zip' 12/04/2018 17:58:14: Mikrotik CHR (img): Replacing {sha256} in '{sha256}' with '9164c1977296ccd92f6267c2be3091b9916dfceab9d8082b25ecd435a4350474' 12/04/2018 17:58:14: Mikrotik CHR (img): Failed, Could not find file 'D:\Unduhan\Jaringan\Mikrotik\Bugfix\chr-6.40.7.img.zip'. Hash matched, I manually multiple check with one listed on the download site. Look at the last line. I don't understand. Why is ketarin trying to find a remote file that has not been downloaded locally? Link to comment Share on other sites More sharing options...
Yuri-Tech Posted April 13, 2018 Report Share Posted April 13, 2018 I'm less familiar with the process but it seems it is trying to find the local file to hash and compare it. Does this file exists in this folder? "D:\Unduhan\Jaringan\Mikrotik\Bugfix\chr-6.40.7.img.zip" Link to comment Share on other sites More sharing options...
shawn Posted April 13, 2018 Report Share Posted April 13, 2018 @soeka the log you posted and the config you posted are not the same. There's no way that the config you shared ("Mikrotik ARM (all)") would get that file, since it never references the Bugfix folder. Most likely there is an issue with your "bugfix" config and that's the one that's having problems. I suspect that the folder "D:\Unduhan\Jaringan\Mikrotik\Bugfix" just needs to be created so that Ketarin can write your file to it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now