Bug #3042
closed
NLSRC is unable to fetch status in large topology after first run
Added by Vince Lehman almost 10 years ago.
Updated almost 8 years ago.
Description
Currently, when NLSRC is used to fetch the LSDB status on a large topology, the first run successfully returns the LSDB dataset. On subsequent runs, NLSRC hangs and fails to fetch the dataset.
I ran nlsrc status today on titan. First time I got the status back. But on second time instead of hanging it gave me the error:
Request timed out (code: 2, error: Error while decoding segment: TLV length exceeds buffer length)
Then on third time (and for subsequent times) it hanged.
Issuing the command nlsrc status for the second time results in the following error in the logs:
20150814160918871 DEBUG: [LsdbDatasetInterestHandler] Received malformed interest: /localhost/nlsr/lsdb/adjacencies/%FD%00%00%01O.%0BH%E1/%00%01%8B
20150814160918880 DEBUG: [LsdbDatasetInterestHandler] Received malformed interest: /localhost/nlsr/lsdb/adjacencies/%FD%00%00%01O.%0BH%E1/%00%01%8C
20150814160918888 DEBUG: [LsdbDatasetInterestHandler] Received malformed interest: /localhost/nlsr/lsdb/adjacencies/%FD%00%00%01O.%0BH%E1/%00%01%8D
20150814160918896 DEBUG: [LsdbDatasetInterestHandler] Received malformed interest: /localhost/nlsr/lsdb/adjacencies/%FD%00%00%01O.%0BH%E1/%00%01%8E
20150814160918905 DEBUG: [LsdbDatasetInterestHandler] Received malformed interest: /localhost/nlsr/lsdb/adjacencies/%FD%00%00%01O.%0BH%E1/%00%01%8F
- Status changed from New to Closed
Error appears to have been resolved at some point, as evidenced by its absence.
Also available in: Atom
PDF