Solved! Go to Solution.
Hi Chris,
Rebooting the machine will kill all the preexisting process on the mac machine.
yes the issue won't occur again, assuming 4684 is applied to ePO , even if the work-around to change the update task to MEDDAT only for ENSM is not applied.
Regards,
Gururaj.m.d
Do you know if a reboot terminates any Mue_InUse sessions?
This is assuming 4684 is applied to ePO so the issue won't occur again, even if the work-around to change the update task to MEDDAT only for ENSM is not applied.
I don't have a Mac to test a reboot on, but I am getting reports of this issue occurring and would like to know if suggesting a reboot will be good enough now I have AMCore 4684 available
Hi Chris,
Rebooting the machine will kill all the preexisting process on the mac machine.
yes the issue won't occur again, assuming 4684 is applied to ePO , even if the work-around to change the update task to MEDDAT only for ENSM is not applied.
Regards,
Gururaj.m.d
We have this problem on all our linux system.
The problem has been solved by the last amcore and the task update modification but it create some oversizing backup files on several server.
/var/McAfee/agent/logs/McScript_b*.log
This situation has caused the stopped of update DAT by a lack of space.
Hello lichar23,
When the process Mue_InUse runs continuously, it keeps logging under McScript log. Hence the size of the log is big.
You can remove the McScript backup log just by running rm command and make some free space.
You're right, if the /var/ doesn't have the recommend disk space, DAT updates will fail.
Refer -> https://kc.mcafee.com/corporate/index?page=content&id=KB91276&locale=en_US
Thanks,
Aravind K
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA