cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 11 of 17

Re: Linux (RHEL 7) Agent not responding

Jump to solution

No, you don't need to do that.  In the MA product guide, there are instructions for changing the agent from unmanaged to managed mode. 

https://docs.mcafee.com/bundle/agent-5.6.x-product-guide/page/GUID-CF5406D8-3F89-4DB3-BA50-07BFC0935...

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Highlighted

Re: Linux (RHEL 7) Agent not responding

Jump to solution

I ended up uninstalling it.  This time I was able to deploy the agent from the ePO server.

./cmdagent -i
Component: McAfee Agent
AgentMode: 1
Version: 5.6.5.165
GUID: d3a54248-f817-11ea-169f-005056b5ebe2
TenantId: N/A
LogLocation: /var/McAfee/agent/logs
InstallLocation: /opt/McAfee/agent
CryptoMode: 0
DataLocation: /var/McAfee/agent
EpoServerList: IP|HOSTNAME| FQDN
EpoPortList: 443
EpoServerLastUsed: IP
LastASCTime: 20200916062820
LastPolicyUpdateTime: 20200916062820
EpoVersion: 5.9.1
ServerId: 8B80FAC4-E895-4AD6-8725-BE592ED9422E

However when I tried to deploy the ENS modules (TP and FW) in the server log it shows:

Wake up agent on IP address IP...
20200916063043 E #07228 NAIMSERV naSPIPE.cpp(338): Failed to connect to IP:591, network error was 10061
20200916063044 E #07228 NAIMSERV naSPIPE.cpp(338): Failed to connect to IP:591, network error was 10061
20200916063044 I #07228 NAIMSERV Wake up agent on DNS name FQDN...
20200916063045 E #07228 NAIMSERV naSPIPE.cpp(338): Failed to connect to FQDN:591, network error was 10061
20200916063046 E #07228 NAIMSERV naSPIPE.cpp(338): Failed to connect to FQDN:591, network error was 10061
20200916063046 I #07228 NAIMSERV Wake up agent on NetBIOS name HOSTNAME...
20200916063047 E #07228 NAIMSERV naSPIPE.cpp(338): Failed to connect to HOSTNAME:591, network error was 10061
20200916063048 E #07228 NAIMSERV naSPIPE.cpp(338): Failed to connect to HOSTNAME:591, network error was 10061
20200916063048 E #07228 NAIMSERV AgentWakeup.cpp(206): Server failed to wake up HOSTNAME, detailed error = -999
20200916063129 I #06060 NAIMSERV Received [PolicyManifestRequest] from HOSTNAME:{D3A54248-F817-11EA-169F-005056B5EBE2}
20200916063129 I #06060 NAIMSERV Processed [PolicyManifestRequest] from HOSTNAME:{D3A54248-F817-11EA-169F-005056B5EBE2} in 31ms
20200916063129 I #06060 NAIMSERV Signing agent response package with key H4AZ+S3dHCOcJBY32De1UeqL7ybsrumIss+ZAzO0OUo=
20200916063129 I #06060 MOD_EPO epo request processed, rc=0, session ID=30437, session time=47ms
20200916063224 E #06772 NAIMSERV PushAgent.cpp(488): Timeout waiting for external process to finish.
20200916063224 E #06772 NAIMSERV PushAgent.cpp(590): Unable to copy C:\Windows\TEMP\mfe599801265.tmp\install.sh to HOSTNAME, invocation of pscp failed, err=-2147024638
20200916063224 E #06772 NAIMSERV PushAgent.cpp(681): Push Agent Installation Program to HOSTNAME failed, will not retry
20200916063406 I #05256 EPODAL Label cache cleaned; oldsize=46, newsize=0
20200916063406 I #05256 NAIMSERV Reloading tag cache, tid=0

Not sure why I could deploy the agent, but now can't deploy the modules.

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 13 of 17

Re: Linux (RHEL 7) Agent not responding

Jump to solution

Does epo show the agent communicating properly?  If so, use a client task, not a run client task now or anything else, but an assigned client task to install the threat prevention modules.  

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

Highlighted

Re: Linux (RHEL 7) Agent not responding

Jump to solution

that worked.  Not sure why a run task would not. 

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 15 of 17

Re: Linux (RHEL 7) Agent not responding

Jump to solution

Run client task now depends on wakeups to work as well as datachannel communication being successful, which is different than normal asci.  So it is easy for a client task to work where a run client task now would fail.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Highlighted

Re: Linux (RHEL 7) Agent not responding

Jump to solution

service ma restart
McAfee Agent service is not running.

[root@hostname]# service ma status

McAfee agent service is not running.
McAfee common services is not running.
McAfee compat service is not running.

 

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 17 of 17

Re: Linux (RHEL 7) Agent not responding

Jump to solution

To remove also the firewall module, follow this doc.

 
Once you do, restart the machine if possible, then reinstall the agent and verify it is working properly before reinstalling ENS.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community