Failed to initialize log level based on config.xml in /etc/cma.d (Client tasks fails on Linux)

Technical Articles ID: KB95289
Last Modified: 2022-02-10 17:37:27 Etc/GMT

Environment

McAfee Agent 5.x.x
Linux - supported platforms

For environment information, see KB51573 - Supported platforms for McAfee Agent 5.x.

Problem

All client tasks fail. You see this problem with either a deployment or update task.

NOTE: This issue isn’t related to a problem with the agent-server communication interval (ASCI).

The MASVC.log and McScript logs record the errors below (/var/McAfee/agent/logs). The MASVC log shows that ASCI is working:

ahclient.Info: Agent is connecting to ePO server
ahclient.Info: Initiating spipe connection to site https://10.x.x.x:443/spipe/pkg?AgentGuid={cbd5469a-9389-11eb-1019-000d3aa04c07}&Source=Agent_3.0.0.
curl.Info: Before Encoding URL:https://10.x.x.x:443/spipe/pkg?AgentGuid={cbd5469a-9389-11eb-1019-000d3aa04c07}&Source=Agent_3.0.0, After Encoding URL:https://10.x.x.x:443/spipe/pkg?AgentGuid=%7Bcbd5469a-9389-11eb-1019-000d3aa04c07%7D&Source=Agent_3.0.0
ahclient.Info: connection initiated to site https://10.x.x.x:443/spipe/pkg?AgentGuid={cbd5469a-9389-11eb-1019-000d3aa04c07}&Source=Agent_3.0.0.
ahclient.Info: Network library rc = <1008>, Agent handler reports response code <200>.
ahclient.Info: Agent handler reports spipe package received. response code 200.
ahclient.Info: Spipe connection response received, network return code = 1008, response code 200.
policy.Info: Agent received POLICY package from ePO server
policy.Info: Loaded data looks fine, proceed further to update the database
ahclient.Info: Agent communication session closed

NOTE: Even though the ASCI is working, after you run the command cmdagent -p to initiate an ASCI, you see the 507 error below:

[root@SGPRGC109384 tmp]# /opt/McAfee/agent/bin/cmdagent -p
cmdagent.Error: Failed to get ma info, error code <507>.
cmdagent.Error: Get agent mode failed. Operation failed

The MASVC.log records the errors:

property.Info: Property collection 2022-01-20 12:02:56.847 (106461.106461) ioservice.Info: IO service received the message.
event.Error: Low disk space in agent data path. Minimum free disk space required = 500 MB, free disk space available = 16 MB.
event.Error: Custom event can't be saved, err = <28>.
msgbus.Info: File watcher callback invoked on broker config change, file name </var/McAfee/agent/.msgbus/config.ini>
msgbus.Info: File watcher callback invoked on broker config change, file name </var/McAfee/agent/.msgbus/config.ini>
msgbus.Info: File watcher callback invoked on broker config change, file name </var/McAfee/agent/.msgbus/config.ini>
scheduler.Info: The task ma.policy.enforce.timeout.task.name is successful
scheduler.Info: Next time(local) of task ma.policy.enforce.timeout.task.name: 2022-01-20 14:02:56
msgbus.Info: Received Timer event to read msgbus config file
msgbus.Warning: Broker information is not available, rc <1>
msgbus.Info: msgbus connectvity status : Disconnected
msgbus.Info: Removed file watcher on broker config file </var/McAfee/agent/.msgbus/config.ini>
msgbus.Info: Added file watcher on broker config file </var/McAfee/agent/.msgbus/config.ini>

You see the errors below in the Mcscript.log when an Update task is received:

NOTE: At each update attempt where you see the error, it stops initializing. This issue occurs because the symbolic link isn’t in sync.

2022-01-31 07:04:01 [96801] (16384) [ScrptMain] [I] START [/opt/McAfee/agent/bin/Mue_InUse -script /var/McAfee/agent/update/UpdateMain.McS -id 1640062907 -localeid 0409 -logfile /var/McAfee/agent/logs/McScript.log -parent FRAMEWORK -initiator 1 -installdir /opt/McAfee/agent//lib -taskid 6895]
2022-01-31 07:04:01 [96801] (16384) [LogLvl] [I] Initializing log level based on config.xml in /etc/cma.d
2022-01-31 07:04:01 [96801] (16384) [LogLvl] [I] Failed to initialize log level based on config.xml in /etc/cma.d. Using default configuration.
2022-01-31 07:04:01 [96801] (16384) [MueEep] [I] Initializing MUE EEP Script ID = 1640062907

2022-01-31 08:00:01 [98306] (16384) [ScrptMain] [I] START [/opt/McAfee/agent/bin/Mue_InUse -script /var/McAfee/agent/update/UpdateMain.McS -id 894815115 -localeid 0409 -logfile /var/McAfee/agent/logs/McScript.log -parent FRAMEWORK -initiator 1 -installdir /opt/McAfee/agent//lib -taskid 6892]
2022-01-31 08:00:01 [98306] (16384) [LogLvl] [I] Initializing log level based on config.xml in /etc/cma.d
2022-01-31 08:00:01 [98306] (16384) [LogLvl] [I] Failed to initialize log level based on config.xml in /etc/cma.d. Using default configuration.
2022-01-31 08:00:01 [98306] (16384) [MueEep] [I] Initializing MUE EEP Script ID = 894815115

The McScript_deploy.log records the same error when a Product Deployment task is initiated:

[ScrptMain] [I] START [/opt/McAfee/agent/bin/Mue_InUse -script /var/McAfee/agent/update/InstallMain.McS -id 715767777 -localeid 0409 -logfile /var/McAfee/agent/logs/McScript_deploy.log -parent FRAMEWORK -initiator 4 -installdir /opt/McAfee/agent//lib -taskid 3]
[LogLvl] [I] Initializing log level based on config.xml in /etc/cma.d
[LogLvl] [I] Failed to initialize log level based on config.xml in /etc/cma.d. Using default configuration.
[MueEep] [I] Initializing MUE EEP Script ID = 715767777
[crypto] [I] Crypto logger used <0x9f82938>
[crypto] [I] Key imported successfully and recognized in RSA format
[crypto] [I] Key imported successfully and recognized in RSA format
[msgbus] [I] Added file watcher on broker config file </var/McAfee/agent/.msgbus/config.ini>
[msgbus] [I] msgbus connectvity status : Connected
[msgbus] [I] hash comparisons match failed
[msgbus] [I] hash comparisons match failed
[ma_client] [I] ma client is started

Cause

The Linux system is low on disk space. This issue leads to the config.xml file and config.ini file becoming blank:

Config.ini (/var/McAfee/agent/.msgbus/config.ini)

To check file size through ssh, run the commands below:

[root@SGPRGC109384 /]# ls -l /var/McAfee/agent/.msgbus/config.ini

Output

-rw-r--r--. 1 root root 0 JAN 20 12:24 /var/McAfee/agent/.msgbus/config.ini
[root@SGPRGC109384 /]#

Config.xml (/etc/ma.d/EPOAGENT3000/config.xml)

To check file size through ssh, run the command below:

[root@SGPRGC109384 tmp]# ls -l /etc/ma.d/EPOAGENT3000/

NOTE: The output shows zero (0).

total 4
-rw-r--r--. 1 root root 0 JAN 20 12:24 config.xml
lrwxrwxrwx. 1 root root JAN 20 12:24 EPOAGENT3000 -> /etc/ma.d/EPOAGENT3000

Solution

To resolve the issue, remove McAfee Agent, and then install McAfee Agent manually:

Remove McAfee Agent:
1. Log on to the non-Windows system.
2. Run the command below on a Linux system to uninstall McAfee Agent:
  
  NOTE: The system user must be root user or root permissions user. To confirm that the correct user is logged in, the displayed prompt is the # sign.
  
  /opt/McAfee/agent/scripts/uninstall.sh
3. You can also use the commands below to remove individual packages:
  
  IMPORTANT: Run the commands below in the listed order.
  
  rpm -e MFEdx
  
  rpm -e MFEcma
  
  rpm -e MFErt
Other resources:
- For more information about these commands, see the McAfee Agent 5.7.x Installation Guide
- KB75550 - How to manually remove McAfee Agent 5.x for Linux

Install McAfee Agent manually by copying the install.sh from ePO using the winscp tool:

Before you copy the install.sh from ePO to the problem Linux system, change the Transfer Settings to Binary.

NOTE: Binary is the default setting. This setting helps to copy the binaries of the sh script successfully while copying the file.
1. Copy the agent install.sh package to a temporary folder on the Linux system. For details, see the McAfee Agent Installation Guide.
2. Run the command below to add the execute permissions for the install.sh:
  
  sudo chmod +x install.sh
3. Run the command below to install McAfee Agent through install.sh:
  
  sudo install.sh -i
  
  NOTE: If you want the installation details to be saved to a log, add the switch as shown below:
  
  sudo install.sh -i > /tmp/MA_install.log

Related Information

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Failed to initialize log level based on config.xml in /etc/cma.d (Client tasks fails on Linux)

Environment

Problem

Cause

Solution

Related Information

Affected Products

Languages:

Title

Title

Knowledge Center

Failed to initialize log level based on config.xml in /etc/cma.d (Client tasks fails on Linux)

Environment

Problem

Cause

Solution

Related Information

Affected Products

Languages:

Choose your region

Title

Title