1 2 Previous Next 15 Replies Latest reply on Oct 30, 2017 7:47 AM by Steffen Kreis

    Unable to setup git-repo on a local fileserver agent

    Steffen Kreis

      Hi,

       

      we are doing quite some change sin our architecture at the moment.

      So one thing we are looking at is moving the FileServer and Patch-Repos to an NFS share that gets mounted to all of our AppServers.

       

      We are then looking at setting up two agents per AppServer. One for the management of the AppServer (bound to its external IP) and the other one for the FileServer+Patch traffic (bound only to localhost).

      We then point the Patch Payload and the FileServer location to "blfs" which is an /etc/hosts entry on all of the AppServer to 127.0.0.1.

       

      For the setup of the two agents we are following the docs from here How to configure two RSCD agents on a single host - BMC Server Automation 8.9

       

      So also like in the docs the fs-agent always maps all its connections to a user called "blfsuser" which has read/write access to the NFS shares.

       

      So far so good.

       

      We started to relocate the Patch-Payload in the first stepo and this seems to be working fine. Every AppServer talks to the "local" Payload directory through its own local fs-rscd.

       

      I am now trying to re-locate our git repository to the same share, since this is located on the single FileServer host we are running with up until today.

       

      Unfortunately i am getting the fooliwng error when i try to specify the new "Local Repo Details" in the Infrastructure Management.

       

      "git --version: Command not found"

       

      Git is of course in place.

       

      Checking the rscd.log from the FileServer-Agent that was used here it all looks fine:

       

      12/02/16 11:18:26.800 INFO rscd -  127.0.0.1 28895 54730/54730 (MYROLE:MYUSER): nexec: /opt/bmc/bladelogic/NSH/bin/nexec blfs git --version
      12/02/16 11:18:26.805 INFO1rscd -  127.0.0.1 28895 54730/54730 (MYROLE:MYUSER): nexec: > 01010 Execute remote command: "git --version"

       

      So the agent correctly receives the the "call" from the localhost address it is bound to and shows no other error.

       

      I checked the AppServer.log of the console instance i am connected against and it shows me this:

       

      [02 Dec 2016 10:29:11,721] [Client-Connections-Thread-9] [INFO] [MYUSER:MYROLE:MYDESKTOPIP] [Client] Executing command : /opt/bmc/bladelogic/NSH/bin/nexec blfs   "git --version"

      [02 Dec 2016 10:29:11,747] [Client-Connections-Thread-9] [INFO] [MYUSER:MYROLE:MYDESKTOPIP] [Client] Started pid 26115: /opt/bmc/bladelogic/NSH/bin/nexec blfs   "git --version"

      [02 Dec 2016 10:29:11,874] [Nsh-Proxy-Thread-48] [INFO] [MYUSER:MYROLE:APPSERVERIP] [BLSSOPROXY] Connecting to blfs

      [02 Dec 2016 10:29:12,052] [WaitForProcessThread-PID-26115-88] [INFO] [MYUSER:MYROLE:MYDESKTOPIP] [Client] Process finished: 26115

      [02 Dec 2016 10:29:12,053] [Nsh-Proxy-Thread-47] [INFO] [MYUSER:MYROLE:APPSERVERIP] [BLSSOPROXY] copy data stop: Connection closed

      [02 Dec 2016 10:29:12,055] [Client-Connections-Thread-9] [ERROR] [MYUSER:MYROLE:MYDESKTOPIP] [Client] ERROR while executing cmd  "git --version"  return Code is 127

      error Stream is git --version: Command not found

       

      output stream is

      [02 Dec 2016 09:55:07,753] [Scheduled-System-Tasks-Thread-3] [INFO] [System:System:] [Memory Monitor] Total JVM (B): 1567621120,Free JVM (B): 546424904,Used JVM (B): 1021196216,VSize (B): 8274857984,RSS (B): 1609035776,Used File Descriptors: 301,Used NSH Proxy Threads: 0/50,Used Client Connections: 5/200,DB Client-Connection-Pool: 2/1/1/100/75/25,DB Job-Connection-Pool: 1/1/0/2/1/1,DB General-Connection-Pool: 3/2/1/50/37/13

       

       

      I have also registered the "blfs" server object in the console and ran an NSH script against it including the command "nexec blfs git --version" and it runs fine.

       

      Info    Fri, 02 Dec 2016 11:26:20    git version 1.9.4

      Info    Fri, 02 Dec 2016 11:26:20    Exit Code 0

       

       

      Is anybody running a similiar setup without issues or has any clue what is wrong here ?

       

      Cheers

      Steffen

        1 2 Previous Next