Hash Mismatch Troubleshooting
There are scenarios where file contents may appear to be identical but the hash calculation is resulting in mismatched values.
In the example below, there are non-printable characters present that can't be seen with a file diff.
$ diff SampleAuditFileRouteLink.txt SampleAuditFileCustomer.txt
2c2
< 8005551213,QR760,bdc1126e1780e076cde352f37e0fb48823605a78
---
> 8005551213,QR760,bdc1126e1780e076cde352f37e0fb48823605a78
A tool to generate a hex dump of the database file can be used to determine non-printable characters. Comparing the hex dump files between the RouteLink Client and RouteLink Server can highlight the issue.
Contact Somos support at routelinkhelp@somos.com for a RouteLink Server database prefix file.
For example, the Linux utility command "od" was used on the above files. The bytes in red are the hexadecimal values of each byte in the file. The difference between the two files is highlighted to show there is an extra space at the end of the second line in the customer output file.
$ diff RLClient-HEX.txt RLServer-HEX.txt
8c8
Disclaimer: Any images in this article are intended to be used as a guide for educational purposes only and they may differ slightly from the Production Environment.