ARServer service cannot be started

Version 2
    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


    APPLIES TO:

    ARServer



    PROBLEM:

    ARServer cannot be started on Linux environment. Following error found in armonitor.conf file.

    <MNTR> <TNAME: main > <INFO > <ARMonitorDaemon > < ARMonitorDaemon.java:138 > /* Tue Jul 03 18 11:08:44.0088 */ ****************************************************************************************** <MNTR> <TNAME: main > <INFO > <ARMonitorDaemon > < ARMonitorDaemon.java:139 > /* Tue Jul 03 18 11:08:44.0093 */ Initializing ARMonitor Version 9.1.00 201512160229 <MNTR> <TNAME: main > <INFO > <ARMonitorDaemon > < ARMonitorDaemon.java:140 > /* Tue Jul 03 18 11:08:44.0093 */ ****************************************************************************************** <MNTR> <TNAME: main > <INFO > <ProcessController > < ProcessController.java:74 > /* Tue Jul 03 18 11:10:50.0278 */ Initializing ProcessController, to start and monitor all the processes listed in armonitor configuration file. <MNTR> <TNAME: main > <DEBUG> <ARMonitorProperties > < ARMonitorProperties.java:439 > /* Tue Jul 03 18 11:10:50.0279 */ For Linux-based OS, armonitor.conf is located at '/etc/arsystem/<AR_SERVER_ID>/armonitor.conf', the <AR_SERVER_ID> is configured in configuration and script file '<AR_SERVER_HOME>/bin/arsystem', so read the server_name from file arsystem first and then look for armonitor.conf. <MNTR> <TNAME: main > <INFO > <ProcessController > < ProcessController.java:225 > /* Tue Jul 03 18 11:10:50.0300 */ Read and start all processes listed in armonitor.conf. <MNTR> <TNAME: main > <INFO > <ProcessController > < ProcessController.java:231 > /* Tue Jul 03 18 11:10:50.0300 */ Starting Server-Process : /usr/java_x64/jdk1.8.0_60/jre/bin/java -jar /arsys/ARSystem/bin/arserver.jar -s i-7s5c0t0a -i /arsys/ARSystem -l /etc/arsystem/i-7s5c0t0a <MNTR> <TNAME: main > <DEBUG> <ProcessMonitor > < ProcessMonitor.java:404 > /* Tue Jul 03 18 11:10:50.0301 */ The process is not Running - [ ARSERVER ] <MNTR> <TNAME: main > <INFO > <ProcessMonitor > < ProcessMonitor.java:157 > /* Tue Jul 03 18 11:10:50.0302 */ ProcessMonitor starting process [ ARSERVER ]. <MNTR> <TNAME: main > <DEBUG> <ProcessMonitor > < ProcessMonitor.java:167 > /* Tue Jul 03 18 11:10:50.0302 */ Process commands List - [/usr/java_x64/jdk1.8.0_60/jre/bin/java, -jar, /arsys/ARSystem/bin/arserver.jar, -s, i-7s5c0t0a, -i, /arsys/ARSystem, -l, /etc/arsystem/i-7s5c0t0a] <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1 > < ProcessMonitor.java:198 > /* Tue Jul 03 18 11:10:55.0314 */ Server Statup Notification Port [ARSERVERPORT] :41501 <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1 > < ProcessMonitor.java:198 > /* Tue Jul 03 18 11:10:55.0314 */ Tue Jul 03 11:10:55.260 2018 RestApiActivator:starting bundle... <MNTR> <TNAME: main > <INFO > <ARServerStartupListener > <ARServerStartupListener.java:87 > /* Tue Jul 03 18 11:10:55.0315 */ Server port socket listener initializing.. <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1 > < ProcessMonitor.java:198 > /* Tue Jul 03 18 11:10:55.0766 */ Tue Jul 03 11:10:55.766 2018 Registering Restful servlet container... <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1 > < ProcessMonitor.java:198 > /* Tue Jul 03 18 11:10:56.0993 */ Tue Jul 03 11:10:56.993 2018 Registered Restful servlet container with the base URI as "/api" <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1 > < ProcessMonitor.java:198 > /* Tue Jul 03 18 11:10:56.0995 */ Tue Jul 03 11:10:56.995 2018 Restapi bundle started. <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1 > < ProcessMonitor.java:198 > /* Tue Jul 03 18 11:10:58.0059 */ Registering CMDB REST API @ /cmdb ... <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1 > < ProcessMonitor.java:198 > /* Tue Jul 03 18 11:10:58.0261 */ Registered CMDB REST API <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1 > < ProcessMonitor.java:198 > /* Tue Jul 03 18 11:20:51.0838 */ Tue Jul 03 11:20:51.836 2018 Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.bmc.arsys.messaging, config=bundleentry://160.fwk1456208737/OSGI-INF/blueprint/application_context.xml)) <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1 > < ProcessMonitor.java:198 > /* Tue Jul 03 18 11:20:51.0839 */ org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'localBroker' defined in OSGi resource[bundleentry://160.fwk1456208737/OSGI-INF/blueprint/application_context.xml|bnd.id=160|bnd.sym=com.bmc.arsys.messaging]: Invocation of init method failed; nested exception is java.io.IOException: Failed to bind to server socket: tcp://<server>:61617?wireFormat.maxInactivityDurationInitalDelay=120000 due to: java.net.BindException: Cannot assign requested address
      
    In arerror.log file, following entries are logged  
    Thu Sep 20 17:41:06.643 2018 Error encountered in bundle: com.bmc.arsys.messaging Thu Sep 20 17:41:06.671 2018 Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.bmc.arsys.messaging, config=bundleentry://158.fwk288665596/OSGI-INF/blueprint/application_context.xml)) Thu Sep 20 17:41:06.676 2018 Unable to create application context for [com.bmc.arsys.messaging], unsatisfied dependencies: none Thu Sep 20 17:41:06.686 2018 Stopserver.await: accept Thu Sep 20 17:41:06.697 2018 TID 100 initTransport Normal ARServer shutdown process Initiated.
      
    In ardebug log file, following entries are logged  
    Thu Sep 20 17:41:06.671 2018 org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'localBroker' defined in OSGi resource[bundleentry://158.fwk288665596/OSGI-INF/blueprint/application_context.xml|bnd.id=158|bnd.sym=com.bmc.arsys.messaging]: Invocation of init method failed; nested exception is java.io.IOException: Failed to bind to server socket: tcp://<servername>:61617?wireFormat.maxInactivityDurationInitalDelay=120000&wireFormat.maxInactivityDuration=30000 due to: java.net.BindException: Cannot assign requested address at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1572) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:539) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:755) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:762) at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60) at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325) at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85) at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290) at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Failed to bind to server socket: tcp://<servername>:61617?wireFormat.maxInactivityDurationInitalDelay=120000&wireFormat.maxInactivityDuration=30000 due to: java.net.BindException: Cannot assign requested address

     


    CAUSE:

    incorrect parameters in ar.conf file


    SOLUTION:

    Found following parameters are enabled in ar.conf file:

    Rejected-By-Others-Interval:
    Approval-Web-Doc-Dir:

    Comment out these two parameters in ar.conf file

    clean out all files in folders below.
     

      BMC Software\ARSystem\activemq-data\
    BMC Software\ARSystem\bundle-cache\
      
    Restart AR Server 

     


    Article Number:

    000155303


    Article Type:

    Solutions to a Product Problem



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