Arerror.log shows “Failed to install artifact: <Install Path>\ARSystem\Conf\org.apache.felix.fileinstall-deploy.cfg" causes Atrium Core and IT Service Management Installs/Upgrades to Fail.

Version 3
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System Server


    APPLIES TO:

    Remedy AR System Server, Atrium CMDB, IT Service Management 9.0 or higher.



    PROBLEM:

    Arerror.log shows “Failed to install artifact: <Install Path>\ARSystem\Conf\org.apache.felix.fileinstall-deploy.cfg".  This can cause the Assignment Engine and certain components of Atrium Core to fail during install, upgrade, or patch.
    This can negatively impact the functionality of components of the Remedy system such as Assignment Engine, CMDB, and ITSM applications.
    Apache Felix File Install is a directory based OSGi management agent. It uses a directory in the file system to install and start a bundle when it is first placed there. It updates the bundle when you update the bundle file in the directory and, when the file is deleted, it will stop and uninstall the bundle.  In the Remedy system, this directory is the “<Install Path>\ARSystem\Deploy” folder.

    CAUSE

    When the Apache Felix File Install agent starts with the Remedy AR System Server it initializes using the fileinstall-deploy.cfg file, then scans the “<Install Path>\ARSystem\Conf” directory to gather other system parameters.  It then monitors the Deploy folder to install and start bundles that are placed there.

       
    1. If there are any parameters found in the Conf directory, like a random .txt file, then the Felix agent might not be to parse the file and initialization of the agent will fail.
    2.  
    3. If the files found in the Deploy folder are conflicted or missing, then the Felix agent wont have anything to do.

     


    SOLUTION:

    To resolve the issue of the Felix File Installer agent initialization, please follow these steps:

       
    1. Please ensure that the “<Install Path>\ARSystem\Conf” does not have any additional files included in it.  Including backup files.  This directory should not be used for storing anything outside of the normal AR System Server.  Please refer to a working environment or backup.
       To resolve the issue of the Felix File Installer agent not deploying the correct components, please follow these steps:  
       
    1. Please ensure that the “<Install Path>\ARSystem\Deploy” folder has the necessary binaries inside.  These could include the following     
           
      1. Assignment Engine (com.bmc.arsys.assignmentEngine-9.1.07-SNAPSHOT.jar)
      2.    
      3. Atrium CMDB (cmdb-9.1.07-SNAPSHOT.jar, cmdb-rest-9.1.07-SNAPSHOT.jar, and cmdb-services-9.1.07-SNAPSHOT.jar)
      4.    
      5. Other components.
      6.   
    2.  
    3. Also please ensure that any old version of these files are either deleted or removed from this directory as only the files for your current version are necessary.
    4.  
    5. If you do not have any files present in this folder, you can manually copy them from one of the following sources:     
           
      1. The installer’s files.
      2.    
      3. A recent patch/hotfix that has these files (not all patches and hotfixes will update these files).
      4.    
      5. A working server.
      6.    
      7. A backup.
      8.   
      
    How to enable additional logging:
    If the above steps do not resolve your issue then please complete the following steps to enable advanced logging for the Felix Agent:  
       
    1. Open the “org.apache.felix.fileinstall-deploy.cfg” found in the Conf directory.
    2.  
    3. Update the following 2 lines to the value “4”     
           
      1. felix.fileinstall.log.level
      2.    
      3. felix.fileinstall.debug
      4.   
    4.  
    5. Save the org.apache.felix.fileinstall-deploy.cfg file.
    6.  
    7. Open the “logback_server.xml” found in the Conf directory.
    8.  
    9. Search for “arerrorlogger” in the file, and change to debug.
    10.  
    11. Save the logback_server.xml file.
    12.  
    13. Now restart the Remedy AR System Server and reproduce the errors.
    14.  
    15. The new logging should appear in arerror.log.
    16.  
    17. You can examine these to troubleshoot them.
    18.  
    19. Run the Log Zipper Utility.     
           
      1. https://communities.bmc.com/docs/DOC-61580
      2.   
    20.  
    21. Create a BMC Support Case and attach the output from the Log Zipper Utility.

     


    Article Number:

    000149971


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles