Bug 587628

Summary: No archives appear on Linux
Product: [NTS - Systems] Support Advisor Feedback Service Reporter: Jason Record <jason.record>
Component: View - ArchiveAssignee: Forgotten User ryjehfA1Aq <forgotten_ryjehfA1Aq>
Status: RESOLVED FIXED QA Contact: Mike Francis <mike.francis>
Severity: Critical    
Priority: P1 - Urgent    
Version: 2.0 (beta)   
Target Milestone: 2.0   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: nsaLog.txt from failed archive run
connections file from failed archive run

Description Jason Record 2010-03-11 20:09:24 UTC
Run an analysis with the client on Linux to a linux server. The analysis completes successfully, but never shows up in the archives tab. No additional entries in the .supportAdvisor/config/connections.xml.
Comment 1 Jason Record 2010-03-11 20:27:19 UTC
This is for a single server connection, not group connections.
Comment 2 Jason Record 2010-03-11 20:33:46 UTC
Zen archive appeared in archives tab, but supportconfig archives do not.
Comment 4 Aaron Burgemeister 2010-03-11 23:12:32 UTC
As an update after I ran my second scan (and therefore had two archives, one on two separate boxes) the archive for the second box showed up, even after restarting NSA 2 (rev 9).  After getting a third archive captured the second and third both show up (though the first does not).
Comment 5 Mike Francis 2010-03-16 02:02:34 UTC
Have seen issue first hand, however am unable to duplicate.
Please attempt to duplicate with debug log turned on, dup issue and send in log.

Enable log in NSA settings, then restart client
Log will be written to ~userHome/.supportAdvisor/nsalog.txt
Comment 6 Jason Record 2010-03-16 03:22:20 UTC
Created attachment 348546 [details]
nsaLog.txt from failed archive run
Comment 7 Jason Record 2010-03-16 03:23:06 UTC
Created attachment 348547 [details]
connections file from failed archive run
Comment 8 Jason Record 2010-03-16 03:24:18 UTC
Files attached. I ran the 2.0.0_rev9 client on SLED11 against the local loopback ip address.
Comment 9 Mike Francis 2010-03-16 14:04:16 UTC
connections.xml is not being updated with information about regarding archive file.

Root cause:
This is only happening on connection id's that don't have a full ip address range.
That connection id should be sent from nsaEngine with number padding.
Example:
151.155.241.197:22 sent as 151155241197_22  (fine)

This problem:
151.155.241.97 is being sent as 
15115524197_22 (wrong) should be sent as
151155241097_22

Have only verified that this is the case on connection ID's received in CompressMessageHandler in completion of a supportconfig gathering task.

nsaEngine message sent across bridge:
sendMessage: Compress: 1`~0`~nts_15115524118_22_1268747639682.tgz`~C:\Users\mike\.supportAdvisor\nsaarchive\`~1268747639682`~15115524118_22
Comment 10 Mike Francis 2010-03-16 15:25:36 UTC
fixed in nsaAIR connectionIDConverter rev 2189
Comment 11 Mike Francis 2010-03-16 15:25:56 UTC
fixed