search cancel

NFA Pumplog shows 404 error


Article ID: 253885


Updated On:


CA Network Flow Analysis (NetQos / NFA)


The Pumplog*.log file on the NFA Console shows errors similar to the following   

at NetQoS.FilePump.SourceManager.Start()
10:29:15 2 - Pump::SourceManager - :
NQS_FIP_00200: Error retrieving http://<IPADDRESS>:8080/getFiles?do=files&mask=NFMInput/*.*
NetQoS.FilePump.i18nFilePumpException: NQS_FIP_00200: Error retrieving http://<IPADDRESS>:8080/getFiles?do=files&mask=NFMInput/*.* ---> System.Net.WebException: The remote server returned an error: (404) Not Found.
   at System.Net.HttpWebRequest.GetResponse()
   at NetQoS.FilePump.ManagementServer.Execute(Uri uri, String& responseString)
   --- End of inner exception stack trace ---
   at NetQoS.FilePump.ManagementServer.Execute(Uri uri, String& responseString)
   at NetQoS.FilePump.ManagementServer.ListFiles(String path, String filePattern)
   at NetQoS.FilePump.SourceManager.Start()







A 404 error connecting to the Harvester means that the File Server service on the Harvester is not reachable on port 8080.


Restart  the "CA NFA File Server" service on the Harvester. If this fails to start, check the fileserver-wrapper.log in the Netflow\logs directory on the harvester. If you see an error similar to the following:

 Harvester: publishFlowStatWS(): Caught exception: Address already in use

STATUS | wrapper  | 2022/11/08 11:53:39 | <-- Wrapper Stopped


Then there is probably some other application causing a conflict on port 8080. Stop the conflicting application and restart the NFA File Server service.

Additional Information

If there are thousands of files backed up in 



These files can be deleted. The longer the pump service us unable to connect, the more files will back up in NFMInput.