Toutes les tâches client échouent. Vous voyez ce problème avec une tâche de déploiement ou de mise à jour.
Remarque: Ce problème n’est pas lié à un problème lié à l’intervalle de communication agent-serveur (ASCI).
Les journaux
MASVC. log et mcscript enregistrent les erreurs ci-dessous (
/var/McAfee/agent/logs ). Le
Journal MASVC indique que l’intervalle de communication agent-serveur fonctionne :
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
Remarque : De même si l’intervalle de communication agent-serveur fonctionne, une fois que vous avez exécuté la commande cmdagent -p pour initier un intervalle ASCI, l’erreur 507 ci-dessous s’affiche :
[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
Le
MASVC.log enregistre les erreurs :
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>
Les erreurs ci-dessous s’affichent dans lors de la
Mcscript.log réception d’une tâche de
mise à jour :
Remarque : lors de chaque tentative de mise à jour où vous voyez l’erreur, l’initialisation de l’erreur est interrompue. Ce problème se produit car le lien symbolique n’est pas synchronisé.
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
Le
McScript_deploy .log enregistre la même erreur lorsqu’une tâche de déploiement de produits est lancée :
[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