No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Log Reference

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document supports all the logs of device, including the parameters, meaning, possible causes and solution.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ENGINE/3/MODFAIL

ENGINE/3/MODFAIL

Message

ENGINE/3/MODFAIL(l): Failed to process the module. (SyslogId=[syslog-id], Reason=[reason])

Description

Failed to install or uninstall the module.

Parameters

Parameter Name Parameter Meaning
syslog-id

Log ID

reason

Cause of the module processing failure:

  1. Can't start install because engine is not run

  2. Can't start install because engine is not ready

  3. Can't start install because compile is busy, compile flag value is [value]

    value is an integer ranging from 0 to 9.

  4. Can't start install because module has been installed

  5. Install module [module-name] failed

    module-name can be set to FTF or URLF.

  6. Can't start uninstall because engine is not run

  7. Can't start uninstall because engine is not ready

  8. Can't start uninstall because compile is busy, compile flag value is [value]

    value is an integer ranging from 0 to 9.

  9. Can't start uninstall because module is not been installed

  10. Uninstall module [module-name] failed

    module-name can be set to FTF or URLF.

  11. Module [module-name] state is [state], can not [action] on slot [slot-id] cpu [cpu-id]

    [module-name] can be set to FTF or URLF.

    [state] can be set to IDLE, INSTALL_START, INSTALL_REQ_CFG, INSTALL_START_COMPILE, INSTALL_FAILED, INSTALL_DONE, UNINSTALL_START, UNINSTALL_START_COMPILE, UNINSTALL_COMPILE_OK, UNINSTALL_FAILED, or UNINSTALL_DONE.

    [action] can be set to INSTALL or UNINSTALL.

    [slot-id] should be set to the slot number of the engine.

    [slot-id] should be set to the CPU ID of the engine.

  12. Module [module-name] [action] failed on slot [slot-id] cpu [cpu-id]

    [module-name] can be set to FTF or URLF.

    [action] can be set to INSTALL or UNINSTALL.

    [slot-id] should be set to the slot number of the engine.

    [slot-id] should be set to the CPU ID of the engine.

  13. Start compile failed when [action] module slot [slot-id] cpu [cpu-id]

    [action] can be set to INSTALL or UNINSTALL.

    [slot-id] should be set to the slot number of the engine.

    [slot-id] should be set to the CPU ID of the engine.

  14. Compile failed when [action] module slot [slot-id] cpu [cpu-id]

    [action] can be set to INSTALL or UNINSTALL.

    [slot-id] should be set to the slot number of the engine.

    [slot-id] should be set to the CPU ID of the engine.

  15. Process timeout when [action] module on slot [slot-id] cpu [cpu-id]

    [action] can be set to INSTALL or UNINSTALL.

    [slot-id] should be set to the slot number of the engine.

    [slot-id] should be set to the CPU ID of the engine.

  16. In the virtual system [virtual-system-name], the profile of [module-name] is referenced by the security policy.

    [virtual-system-name] should be set to the name of the virtual system.

    [module-name] can be set to FTF or URLF.

Possible Causes

Cause 1: The installation failed because the engine was unavailable.

Cause 2: The installation failed because the engine initialization was not completed.

Cause 3: The installation failed because the engine was being compiled.

Cause 4: The installation failed because the engine had been installed.

Cause 5: Failed to install the module.

Cause 6: The uninstallation failed because the engine was unavailable.

Cause 7: The uninstallation failed because the engine initialization was not completed.

Cause 8: The uninstallation failed because the engine was being compiled.

Cause 9: The uninstallation failed because the engine was not installed.

Cause 10: Failed to uninstall the module.

Cause 11: The module worked improperly and cannot execute the installation or uninstallation operation.

Cause 12: The module failed the installation or uninstallation on the SPU.

Cause 13: Failed to start compiling.

Cause 14: Compiling failed.

Cause 15: Processing timed out.

Cause 16: The profile has been referenced in a security policy.

Procedure

  1. Give suggestions based on log causes.

    1. Run the display engine information command to view the engine status.

    2. Run the display engine information command to view the engine status.

    3. Run the display engine information command to view the engine status.

    4. This log message is informational only, and no action is required.

    5. Try again later. If the fault persists, contact technical support personnel.

    6. Run the display engine information command to view the engine status.

    7. Run the display engine information command to view the engine status.

    8. Run the display engine information command to view the engine status.

    9. This log message is informational only, and no action is required.

    10. Try again later. If the fault persists, contact technical support personnel.

    11. Try again later. If the fault persists, contact technical support personnel.

    12. Try again later. If the fault persists, contact technical support personnel.

    13. Rectify the fault based on the message that is displayed on the device.

    14. Rectify the fault based on the message that is displayed on the device.

    15. Try again later. If the fault persists, contact technical support personnel.

    16. Unbind the profile from the security policy and try again.

Translation
Download
Updated: 2019-05-29

Document ID: EDOC1000097209

Views: 69709

Downloads: 181

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next