Solved! Go to Solution.
Hello @nicksullivan
Thank you for your post here. There are two part tho this post. Firstly why this error is coming. For this I would need to know the exact build version of MOVE and also need the MOVE Debug enabled log when issue got re-produced. Both 4.6 and 4.8 had similar entries but for completely different reason. This I can only verify by having the full build and the Logs.
Secondly regarding the SVA-Manger handling this situation. SVA-Manager will assign a new SVM/OSS to the clients only if current SVM/OSS is not reachable. Here network connection is absolutely in connected state between Client to existing OSS and to SVA-Manager. Hence SVA-Manager not getting a signal that current OSS needs to be replaced by a new one. Here OSS server is not able to access the files from RAM Drive causing the scan flood within the scanning network and resulting into OSS high CPU/Hung.
Now thee could be multiple reason behind not able to read files from RAM Disk which needs to be looked at from the Debug enabled MER log and I can confirm. Please IM me the Debug enabled MER log.
Follow the article https://kc.mcafee.com/corporate/index?page=content&id=KB87799 to enable the Debug in OSS.
Hello @nicksullivan
Thank you for your post here. There are two part tho this post. Firstly why this error is coming. For this I would need to know the exact build version of MOVE and also need the MOVE Debug enabled log when issue got re-produced. Both 4.6 and 4.8 had similar entries but for completely different reason. This I can only verify by having the full build and the Logs.
Secondly regarding the SVA-Manger handling this situation. SVA-Manager will assign a new SVM/OSS to the clients only if current SVM/OSS is not reachable. Here network connection is absolutely in connected state between Client to existing OSS and to SVA-Manager. Hence SVA-Manager not getting a signal that current OSS needs to be replaced by a new one. Here OSS server is not able to access the files from RAM Drive causing the scan flood within the scanning network and resulting into OSS high CPU/Hung.
Now thee could be multiple reason behind not able to read files from RAM Disk which needs to be looked at from the Debug enabled MER log and I can confirm. Please IM me the Debug enabled MER log.
Follow the article https://kc.mcafee.com/corporate/index?page=content&id=KB87799 to enable the Debug in OSS.
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA