cancel
Showing results for 
Search instead for 
Did you mean: 
HS
Level 8
Report Inappropriate Content
Message 1 of 4

McAfee Agent for linux failed collection

Jump to solution

Hi,

I'm making a POC with McAfee products for Linux.

I'm facing some issues with McAfee Agent 5.6.1.157 for Linux.

After install the file installdeb.sh the log don't show up errors. But from ePO console I don't have proprieties from the machine, just the MA showing as installed. If I force communication from endpoint works fine but there is no info getting to the ePO...  

Any idea what could be missing?

 

ubuntu specs:

distributor id: Ubuntu
Description: Ubuntu 18.10
Release: 18.10
Codename: cosmic

 

I attach MA logs

 

2019-07-18 08:29:30.409 (1261.1261) publisher.Info: message will be sent after <0> seconds.
2019-07-18 08:29:30.409 (1261.1261) policy.Info: Enforcing Policies for EPOAGENT3000
2019-07-18 08:29:30.409 (1261.1261) policy.Info: Agent finished Enforcing policies
2019-07-18 08:29:30.409 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 08:29:30.410 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 08:29:30.417 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 08:30:52.790 (1261.1261) svcmgr.Info: Get the subscribers list for input topic name <dxl.subscribe.*>
2019-07-18 08:33:59.798 (1261.1261) scheduler.Info: Scheduler: Invoking task [ma.event.priority.event.send.task.name]...
2019-07-18 08:33:59.798 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name becomes active
2019-07-18 08:33:59.801 (1261.1261) event.Info: Agent is looking for events to upload
2019-07-18 08:34:00.800 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name is successful
2019-07-18 08:34:00.800 (1261.1261) scheduler.Info: Next time(local) of task ma.event.priority.event.send.task.name: 2019-07-18 08:38:59
2019-07-18 08:37:18.710 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:37:18.710 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:37:18.710 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:37:18.710 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:37:18.710 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:37:18.731 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 08:38:14.313 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:14.313 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:14.313 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:14.313 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:14.313 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:14.327 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 08:38:14.329 (1261.1261) event.Info: Agent is looking for events to upload
2019-07-18 08:38:14.329 (1261.1261) event.Info: Agent did not find any events to upload
2019-07-18 08:38:38.280 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:38.280 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:38.280 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:38.280 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:38.280 (1261.1261) msgbus.Warning: hash comparisons match failed
2019-07-18 08:38:38.297 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 08:38:38.308 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 08:38:59.822 (1261.1261) scheduler.Info: Scheduler: Invoking task [ma.event.priority.event.send.task.name]...
2019-07-18 08:38:59.822 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name becomes active
2019-07-18 08:38:59.823 (1261.1261) event.Info: Agent is looking for events to upload
2019-07-18 08:39:00.824 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name is successful
2019-07-18 08:39:00.824 (1261.1261) scheduler.Info: Next time(local) of task ma.event.priority.event.send.task.name: 2019-07-18 08:43:59
2019-07-18 08:43:59.845 (1261.1261) scheduler.Info: Scheduler: Invoking task [ma.event.priority.event.send.task.name]...
2019-07-18 08:43:59.845 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name becomes active
2019-07-18 08:43:59.846 (1261.1261) event.Info: Agent is looking for events to upload
2019-07-18 08:44:00.847 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name is successful
2019-07-18 08:44:00.847 (1261.1261) scheduler.Info: Next time(local) of task ma.event.priority.event.send.task.name: 2019-07-18 08:48:59
2019-07-18 08:45:52.806 (1261.1261) svcmgr.Info: Get the subscribers list for input topic name <dxl.subscribe.*>
2019-07-18 08:48:59.848 (1261.1261) scheduler.Info: Scheduler: Invoking task [ma.event.priority.event.send.task.name]...
2019-07-18 08:48:59.848 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name becomes active
2019-07-18 08:48:59.849 (1261.1261) event.Info: Agent is looking for events to upload
2019-07-18 08:49:00.850 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name is successful
2019-07-18 08:49:00.850 (1261.1261) scheduler.Info: Next time(local) of task ma.event.priority.event.send.task.name: 2019-07-18 08:53:59
2019-07-18 08:53:59.865 (1261.1261) scheduler.Info: Scheduler: Invoking task [ma.event.priority.event.send.task.name]...
2019-07-18 08:53:59.865 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name becomes active
2019-07-18 08:53:59.866 (1261.1261) event.Info: Agent is looking for events to upload
2019-07-18 08:54:00.868 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name is successful
2019-07-18 08:54:00.869 (1261.1261) scheduler.Info: Next time(local) of task ma.event.priority.event.send.task.name: 2019-07-18 08:58:59
2019-07-18 08:58:59.891 (1261.1261) scheduler.Info: Scheduler: Invoking task [ma.event.priority.event.send.task.name]...
2019-07-18 08:58:59.891 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name becomes active
2019-07-18 08:58:59.892 (1261.1261) event.Info: Agent is looking for events to upload
2019-07-18 08:59:00.893 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name is successful
2019-07-18 08:59:00.893 (1261.1261) scheduler.Info: Next time(local) of task ma.event.priority.event.send.task.name: 2019-07-18 09:03:59
2019-07-18 09:00:52.822 (1261.1261) svcmgr.Info: Get the subscribers list for input topic name <dxl.subscribe.*>
2019-07-18 09:03:08.735 (1261.1261) scheduler.Info: Scheduler: Invoking task [ma.policy.enforce.timeout.task.name]...
2019-07-18 09:03:08.735 (1261.1261) scheduler.Info: The task ma.policy.enforce.timeout.task.name becomes active
2019-07-18 09:03:08.735 (1261.1261) io.service.Info: Next policy enforcement in 60 minutes
2019-07-18 09:03:08.738 (1261.1261) policy.Info: Enforcing policies
2019-07-18 09:03:08.738 (1261.1261) publisher.Info: message will be sent after <0> seconds.
2019-07-18 09:03:08.738 (1261.1261) policy.Info: Enforcing Policies for EPOAGENT3000
2019-07-18 09:03:08.738 (1261.1261) policy.Info: Agent finished Enforcing policies
2019-07-18 09:03:08.762 (1261.1261) nameservice.Info: Writing broker info in file
2019-07-18 09:03:08.780 (1261.1261) scheduler.Info: Next time(local) of task ma.superagent.repo.purge.task.name: 2019-08-17 09:03:08
2019-07-18 09:03:08.780 (1261.1261) scheduler.Info: The task ma.superagent.repo.purge.task.name is modified
2019-07-18 09:03:08.781 (1261.1261) event.Info: Enforcing event service policy.
2019-07-18 09:03:08.781 (1261.1261) policybag.Warning: returning default policy for section=EventService , key=EventFreeDiskSpaceThresholdPercentage , value=5
2019-07-18 09:03:08.781 (1261.1261) policybag.Warning: returning default policy for section=EventService , key=EventFreeDiskSpaceThreshold , value=500
2019-07-18 09:03:08.781 (1261.1261) event.Info: Publishing event filter.
2019-07-18 09:03:08.781 (1261.1261) event.Info: eventpolicies.ini writing into disk path(/var/McAfee/agent/data/eventpolicies.ini)
2019-07-18 09:03:08.781 (1261.1261) policybag.Warning: returning default policy for section=AMPQ , key=AMPQ_ENABLED , value=1
2019-07-18 09:03:18.803 (1261.1261) reporank.Info: Policy change as got from Configurator <0>
2019-07-18 09:03:18.803 (1261.1261) ContribManagerService.Info: Configuring Contrib manager service
2019-07-18 09:03:18.803 (1261.1261) ContribManagerService.Info: Verify client extension version against manifest.
2019-07-18 09:03:18.803 (1261.1261) ContribManagerService.Info: Matching client extensions are installed. No remediation action will be initiated.
2019-07-18 09:03:18.810 (1261.1261) ContribManagerService.Info: Client Extensions are installed properly.
2019-07-18 09:03:18.810 (1261.1261) ContribManager.Info: Configuring contrib manager
2019-07-18 09:03:18.810 (1261.1261) ContribManager.Info: Configuring Configuration plugin
2019-07-18 09:03:18.810 (1261.1261) ContribManager.Info: Finished configuring service Configuration.
2019-07-18 09:03:18.814 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 09:03:18.815 (1261.1261) scheduler.Info: The task ma.policy.enforce.timeout.task.name is successful
2019-07-18 09:03:18.815 (1261.1261) scheduler.Info: Next time(local) of task ma.policy.enforce.timeout.task.name: 2019-07-18 10:03:29
2019-07-18 09:03:18.826 (1261.1261) msgbus.Info: File watcher callback invoked on broker config change, file name
2019-07-18 09:03:18.826 (1261.1261) msgbus.Info: File watcher callback invoked on broker config change, file name
2019-07-18 09:03:18.826 (1261.1261) msgbus.Info: File watcher callback invoked on broker config change, file name
2019-07-18 09:03:19.826 (1261.1261) msgbus.Info: Received Timer event to read msgbus config file
2019-07-18 09:03:34.749 (1261.1261) scheduler.Info: Scheduler: Invoking task [ma.property.collect.timeout.task.name]...
2019-07-18 09:03:34.749 (1261.1261) scheduler.Info: The task ma.property.collect.timeout.task.name becomes active
2019-07-18 09:03:34.752 (1261.1261) property.Info: Collecting Properties
2019-07-18 09:03:34.753 (1261.1261) publisher.Info: message will be sent after <0> seconds.
2019-07-18 09:03:34.753 (1261.1261) property.Info: Property collection session initiated for PropsVersion with session id 163.
2019-07-18 09:03:54.777 (1261.1261) policybag.Warning: returning default policy for section=General , key=ePOMaxChars , value=128
2019-07-18 09:03:54.783 (1261.1261) property.Info: Properties received from EPOAGENT3000 provider
2019-07-18 09:03:54.785 (1261.1261) property.Info: Properties received from SYSPROPS1000 provider
2019-07-18 09:03:54.785 (1261.1261) scheduler.Info: The task ma.property.collect.timeout.task.name is successful
2019-07-18 09:03:54.785 (1261.1261) scheduler.Info: Next time(local) of task ma.property.collect.timeout.task.name: 2019-07-18 10:03:55
2019-07-18 09:03:54.799 (1261.1261) property.Info: Properties received from DXL_____1000 provider
2019-07-18 09:03:54.799 (1261.1261) property.Info: Finished Collecting Properties
2019-07-18 09:03:54.799 (1261.1261) property.Warning: Property collection session timed out
2019-07-18 09:03:54.801 (1261.1261) property.Info: Agent started performing ASCI
2019-07-18 09:03:54.802 (1261.1261) ahclient.Info: Scheduling spipe connection with "immediate" priority.
2019-07-18 09:03:54.802 (1261.1261) ahclient.Info: Start processing spipe connection request.
2019-07-18 09:03:54.804 (1261.1261) property.Info: Agent is sending PROPS VERSION package to ePO server
2019-07-18 09:03:54.804 (1261.1261) DataChannel.Manager.Info: DataChannel Service ignoring decoration of SPIPE package for : { PropsVersion }
2019-07-18 09:03:54.807 (1261.1261) ahclient.Info: Agent communication session started
2019-07-18 09:03:54.807 (1261.1261) ahclient.Info: Agent is connecting to ePO server
2019-07-18 09:03:54.807 (1261.1261) ahclient.Info: Initiating spipe connection to site https://192.168.114.146:443/spipe/pkg?AgentGuid={49bd0140-a932-11e9-1427-000c29ff4f37}&Source=Agent_....
2019-07-18 09:03:54.807 (1261.1261) ahclient.Info: connection initiated to site https://192.168.114.146:443/spipe/pkg?AgentGuid={49bd0140-a932-11e9-1427-000c29ff4f37}&Source=Agent_....
2019-07-18 09:03:55.015 (1261.1261) ahclient.Info: Network library rc = <1008>, Agent handler reports response code <202>.
2019-07-18 09:03:55.015 (1261.1261) ahclient.Info: Agent handler doesn't have anything to send. response code 202.
2019-07-18 09:03:55.015 (1261.1261) ahclient.Info: Spipe connection response received, network return code = 1008, response code 202.
2019-07-18 09:03:55.015 (1261.1261) property.Info: Package uploaded to ePO Server successfully
2019-07-18 09:03:55.018 (1261.1261) xml_generator.Info: ma_property_xml_generator_save_props_to_datastore
2019-07-18 09:03:55.025 (1261.1261) property.Info: Published property collect and send status message
2019-07-18 09:03:55.025 (1261.1261) ahclient.Info: Agent communication session closed
2019-07-18 09:03:55.028 (1261.1261) io.service.Info: Next collect and send properties in 60 minutes and 0 seconds.
2019-07-18 09:03:55.031 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 09:03:55.031 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 09:03:55.032 (1261.1261) ahclient.Info: Scheduling spipe connection with "immediate" priority.
2019-07-18 09:03:55.033 (1261.1261) event.Info: Agent is looking for events to upload
2019-07-18 09:03:55.033 (1261.1261) event.Info: Agent did not find any events to upload
2019-07-18 09:03:55.033 (1261.1261) ahclient.Info: Start processing spipe connection request.
2019-07-18 09:03:55.035 (1261.1261) DataChannel.Manager.Info: DataChannel Service ignoring decoration of SPIPE package for : { PolicyManifestRequest }
2019-07-18 09:03:55.036 (1261.1261) ahclient.Info: Agent communication session started
2019-07-18 09:03:55.036 (1261.1261) ahclient.Info: Agent is connecting to ePO server
2019-07-18 09:03:55.036 (1261.1261) ahclient.Info: Initiating spipe connection to site https://192.168.114.146:443/spipe/pkg?AgentGuid={49bd0140-a932-11e9-1427-000c29ff4f37}&Source=Agent_....
2019-07-18 09:03:55.036 (1261.1261) ahclient.Info: connection initiated to site https://192.168.114.146:443/spipe/pkg?AgentGuid={49bd0140-a932-11e9-1427-000c29ff4f37}&Source=Agent_....
2019-07-18 09:03:55.141 (1261.1261) ahclient.Info: Network library rc = <1008>, Agent handler reports response code <200>.
2019-07-18 09:03:55.141 (1261.1261) ahclient.Info: Agent handler reports spipe package received. response code 200.
2019-07-18 09:03:55.141 (1261.1261) ahclient.Info: Spipe connection response received, network return code = 1008, response code 200.
2019-07-18 09:03:55.142 (1261.1261) policy.Info: Agent received POLICY package from ePO server
2019-07-18 09:03:55.147 (1261.1261) ahclient.Info: Agent communication session closed
2019-07-18 09:03:55.165 (1261.1261) ioservice.Info: Refreshed the policy bag.
2019-07-18 09:03:55.168 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 09:03:55.168 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 09:03:55.170 (1261.1261) ioservice.Info: IO service received the message.
2019-07-18 09:03:59.898 (1261.1261) scheduler.Info: Scheduler: Invoking task [ma.event.priority.event.send.task.name]...
2019-07-18 09:03:59.898 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name becomes active
2019-07-18 09:03:59.898 (1261.1261) event.Info: Agent is looking for events to upload
2019-07-18 09:04:00.899 (1261.1261) scheduler.Info: The task ma.event.priority.event.send.task.name is successful
2019-07-18 09:04:00.899 (1261.1261) scheduler.Info: Next time(local) of task ma.event.priority.event.send.task.name: 2019-07-18 09:08:59</dxl.subscribe.*></dxl.subscribe.*></dxl.subscribe.*>

1 Solution

Accepted Solutions
Highlighted
HS
Level 8
Report Inappropriate Content
Message 3 of 4

Re: McAfee Agent for linux failed collection

Jump to solution

Hi,
thanks for your reply.

I've resolved this issue. In ePO console I was getting the error "An error occurred while retrieving the requested data".

SQL version is 2012 and compatibility Level Value shown is  SQL 2012 (110), so it wasn't from sql compatibility level.

I install Upgrade 2 on my ePO and issue is resolved.

You can follow the solution:

https://kc.mcafee.com/corporate/index?page=content&id=KB90876

Thank you for your help and hints

3 Replies
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: McAfee Agent for linux failed collection

Jump to solution

What specific info is missing?  According to your log, it is only enforcing policies for the agent, so it would only show the agent installed.  Do you have a task to push out ens for Linux or whatever point products you are using?  Are you attempting to install supported versions of the products?  For example, only 10.6.x  is supported on that OS build.  The communication to epo shows fine, no errors.

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
HS
Level 8
Report Inappropriate Content
Message 3 of 4

Re: McAfee Agent for linux failed collection

Jump to solution

Hi,
thanks for your reply.

I've resolved this issue. In ePO console I was getting the error "An error occurred while retrieving the requested data".

SQL version is 2012 and compatibility Level Value shown is  SQL 2012 (110), so it wasn't from sql compatibility level.

I install Upgrade 2 on my ePO and issue is resolved.

You can follow the solution:

https://kc.mcafee.com/corporate/index?page=content&id=KB90876

Thank you for your help and hints

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 4 of 4

Re: McAfee Agent for linux failed collection

Jump to solution

Good deal!

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?

More McAfee Tools to Help You

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