Description

This article explains why the IDP SigDB update is failing with the error and how to fix it:

checksum of the file FILENAME in device node is not matching with SD pushed file to device and failed even after 2 retries.


Symptoms

This is a BUG after installing SD 23.1 Hotpatch v8:

 

While checking netconf traces, we observed that even though Node 1 was the primary, SD uploaded the SigDB file on Node 0.
Apr 7 13:59:36 [NETCONF] - [56934] Incoming: <rpc message-id="1"><file-put><filename>node0:/var/db/idpd/nsm-download/libidp-detector.so.tgz.v</filename><encoding>base64</encoding><permission>0644</permission><delete-if-exist/><file-contents>

After uploading the file on Node 0, SD attempted to verify the checksum on Node 1.
Since Node 1 did not have the downloaded file, the checksum validation failed.

Apr 4 15:23:25 [NETCONF] - [45227] Incoming: <?xml version="1.0" encoding="UTF-8"?><rpc message-id="1"><get-checksum-information><path>/var/db/idpd/nsm-download/libidp-detector.so.tgz.v</path></get-checksum-information></rpc>

]]>]]>

Apr 4 15:23:25 [NETCONF] - [45227] Outgoing: <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/22.4R0/junos" message-id="1">

Apr 4 15:23:25 [NETCONF] - [45227] Outgoing: <checksum-information>

Apr 4 15:23:25 [NETCONF] - [45227] Outgoing: <file-checksum>

Apr 4 15:23:25 [NETCONF] - [45227] Outgoing: <rpc-error>

Apr 4 15:23:25 [NETCONF] - [45227] Outgoing: <error-type>protocol</error-type>

Apr 4 15:23:25 [NETCONF] - [45227] Outgoing: <error-tag>operation-failed</error-tag>

Apr 4 15:23:25 [NETCONF] - [45227] Outgoing: <error-severity>error</error-severity>

Apr 4 15:23:25 [NETCONF] - [45227] Outgoing: <error-message>

Apr 4 15:23:25 [NETCONF] - [45227] Outgoing: md5: /var/db/idpd/nsm-download/libidp-detector.so.tgz.v: No such file or directory

 

Root Cause:

 

While copying the files, SD is using "node0" for primary device and "node1" for secondary device.

 

When fail over happens in device, Primary node becomes secondary and secondary node becomes primary node.

 

Before failover:

 

Primary:node0

Secondary:node1

 

After Failover:

 

Primary:node1

Secondary:node0

 

SD asked to copy files to Primary node for "node0", since node0 is a secondary node, the files will be copied to the secondary, but check Sum Validation is performed for Primary node.

This is the reason for IDP installation failure.

Solution

Workaround or Temporary fix:


Failover the primary back to node 0


Solution or Permanent fix:


Install SD 23.1 Hotpatch v9

Modification History

2025-07-17 : Article Created