1 Reply Latest reply on Apr 18, 2013 5:56 AM by Edwin Lindeman

    Advanced Repeater Staging Issues

    Edwin Lindeman

      We're having some weird sporadic issues using our Advanced Repeaters(more often than sporadic).  When we attempt to deploy a package to remote servers we're getting some errors in our deploy jobs at the staging part.


      Error     Apr 15, 2013 4:05:19 PM     /bin/bash: /opt/bmc/bladelogic/advancedrepeater/tuner/bin/runchannel: No such file or directory  If we try the same job again the job goes through successfully  to the Commit portion. However sometimes we have to attempt more than once to make it a success.   While doing some research we looked at the job logs and during the same time saw this error.



      [Deploy] com.bladelogic.om.infra.mfw.util.NotFoundException: Could not find automation principal with the '4' ID. com.bladelogic.om.infra.mfw.util.BlException: com.bladelogic.om.infra.mfw.util.NotFoundException: Could not find automation principal with the '4' ID.      at com.bladelogic.om.infra.app.service.file.FileManagerServiceImpl.loadFileServer(FileManagerServiceImpl.java:383)      at com.bladelogic.om.infra.app.service.file.FileManagerServiceImpl.getFileServer(FileManagerServiceImpl.java:342)      at com.bladelogic.om.infra.app.service.file.mbt.FileserverToRepeaterAccessImpl.publish(FileserverToRepeaterAccessImpl.java:165)      at com.bladelogic.om.deploy.model.job.AdvanceRepeaterPublishWorkItemImpl.execute(AdvanceRepeaterPublishWorkItemImpl.java:133)      at com.bladelogic.om.infra.app.service.workitem.WorkItem.doExecute(WorkItem.java:114)      at com.bladelogic.om.infra.app.service.workitem.thread.WorkItemThread.execute(WorkItemThread.java:176)      at com.bladelogic.om.infra.app.service.workitem.thread.WorkItemThread.execute(WorkItemThread.java:51)      at com.bladelogic.om.infra.app.service.thread.BlBlockingThread.run(BlBlockingThread.java:95) Caused by: com.bladelogic.om.infra.mfw.util.NotFoundException: Could not find automation principal with the '4' ID.      at com.bladelogic.om.infra.model.rbac.ImpersonationServiceImpl.findById(ImpersonationServiceImpl.java:245)      at com.bladelogic.om.infra.app.service.file.AppFileServerImpl.loadMrbaApName(AppFileServerImpl.java:121)      at com.bladelogic.om.infra.app.service.file.AppFileServerImpl.(AppFileServerImpl.java:81)      at com.bladelogic.om.infra.app.service.file.AppFileServerFactory.findFileServerById(AppFileServerFactory.java:93)      at com.bladelogic.om.infra.app.service.file.FileManagerServiceImpl.loadFileServer(FileManagerServiceImpl.java:377)      ... 7 more



      Its causing the developers headaches cause they are deploying their code multiple times throughout the day and having to keep re-running the same job till it succeeds is causing them to slow down.


      Any help on this would be appreciated.

        • 1. Re: Advanced Repeater Staging Issues
          Edwin Lindeman

          UPDATE:   So while looking at the Properties of the Advanced Repeater nothing looked out of place. But I did see the credentials were using the Default credentials per Documentation


          Specifies the automation principal is used to access and configure the advanced file server.

          Select an Automation Principal from the drop-down list.

          • If you have not changed any credential during the installation or post-installation procedures, select "Default". This default automation principal matches the built-in administrator credential.
          • If you specified a custom user/password combination during installation or in the post-install procedure, select the automation principal that was created for that user/password combination. This credential is needed by BMC Server Automation to access and configure the Advanced Repeater server.

          During our installation we left as default.


          Instead of using the "Default" credentials we specifically pointed to the Automation Principal BSA created during installation.


          So this resolved our Java errors and the developer hasn't seen any sporadic errors with his deployments. We'll keep an eye on this and if we should see weird issues again will update this POST.


          Thank you