11 Replies Latest reply on May 8, 2015 8:14 AM by Cody Dean

    RSCD agent does not start.

    Team Fujitsu

      Hi All

       

      I have one trouble.

      Although RSCD agent is installed successfully in Windows Server 2003 R2(x86), the agent does not start.

       

      Do you know what is wrong?

      Or

      Do you have any workaround?

       

      If you know anything, please tell me.

       

      - Here is rscdsvc.log. -

      10/17/13 11:28:25.727 DEBUG    rscdsvc - RSCDsvc::Run: Service started

      10/17/13 11:28:25.727 DEBUG    rscdsvc - RSCDsvc::Run: HealthCheck options: Check(NoCheck) Freq (60000 ms) MaxRestarts(50)

      10/17/13 11:28:25.727 DEBUG    rscdsvc - HandleAgentStart: Top

      10/17/13 11:28:25.727 INFO     rscdsvc - HandleAgentStart: Agent process started ("C:\Program Files\BMC Software\BladeLogic\RSCD\/RSCD.exe")

      10/17/13 11:28:41.618 ERROR    rscdsvc -  1007server1 1212 SYSTEM (Not_available): (Not_available): ACNP_Open: No Agent Control Pipe detected, Service manager cannot control agent: The system cannot find the file specified.

      10/17/13 11:28:41.618 ERROR    rscdsvc - HandleAgentStart: Agent process may have failed to start, Check for Agent hung processes or Agent resources still in use, consier reboot

      10/17/13 11:28:41.618 DEBUG    rscdsvc - ManageAgent: Type of loop - before wait agent(68)

      10/17/13 11:28:41.618 ERROR    rscdsvc - ManageAgent: Agent down hard thread(68)

      10/17/13 11:28:41.618 DEBUG    rscdsvc - RSCDsvc is not reporting itself as paused.

      10/17/13 11:28:41.618 ERROR    rscdsvc - ManageAgent: Agent being restarted - count=1

      10/17/13 11:28:43.618 DEBUG    rscdsvc - HandleAgentStart: Top

      10/17/13 11:28:43.618 INFO     rscdsvc - HandleAgentStart: Agent process started ("C:\Program Files\BMC Software\BladeLogic\RSCD\/RSCD.exe" -r -R)

      10/17/13 11:28:59.243 ERROR    rscdsvc -  1007server1 1212 SYSTEM (Not_available): (Not_available): ACNP_Open: No Agent Control Pipe detected, Service manager cannot control agent: The system cannot find the file specified.

      10/17/13 11:28:59.243 ERROR    rscdsvc - HandleAgentStart: Agent process may have failed to start, Check for Agent hung processes or Agent resources still in use, consier reboot

      10/17/13 11:28:59.243 DEBUG    rscdsvc - ManageAgent: Type of loop - before wait agent(68)

      10/17/13 11:28:59.243 ERROR    rscdsvc - ManageAgent: Agent down hard thread(68)

      10/17/13 11:28:59.243 DEBUG    rscdsvc - RSCDsvc is not reporting itself as paused.

      10/17/13 11:28:59.243 ERROR    rscdsvc - ManageAgent: Agent being restarted - count=2

      10/17/13 11:29:01.243 DEBUG    rscdsvc - HandleAgentStart: Top

      10/17/13 11:29:01.243 INFO     rscdsvc - HandleAgentStart: Agent process started ("C:\Program Files\BMC Software\BladeLogic\RSCD\/RSCD.exe" -r -R)

      10/17/13 11:29:16.993 ERROR    rscdsvc -  1007server1 1212 SYSTEM (Not_available): (Not_available): ACNP_Open: No Agent Control Pipe detected, Service manager cannot control agent: The system cannot find the file specified.

      10/17/13 11:29:16.993 ERROR    rscdsvc - HandleAgentStart: Agent process may have failed to start, Check for Agent hung processes or Agent resources still in use, consier reboot

       

      - In rscdsvc.log, I got this repeatedly for many times. -

       

      10/17/13 11:42:49.139 DEBUG    rscdsvc - ManageAgent: Type of loop - before wait agent(68)

      10/17/13 11:42:49.139 ERROR    rscdsvc - ManageAgent: Agent down hard thread(68)

      10/17/13 11:42:49.139 DEBUG    rscdsvc - RSCDsvc is not reporting itself as paused.

      10/17/13 11:42:49.139 ERROR    rscdsvc - ManageAgent: Agent being restarted - count=49

      10/17/13 11:42:51.139 DEBUG    rscdsvc - HandleAgentStart: Top

      10/17/13 11:42:51.139 INFO     rscdsvc - HandleAgentStart: Agent process started ("C:\Program Files\BMC Software\BladeLogic\RSCD\/RSCD.exe" -r -R)

      10/17/13 11:43:06.764 ERROR    rscdsvc -  1007server1 1212 SYSTEM (Not_available): (Not_available): ACNP_Open: No Agent Control Pipe detected, Service manager cannot control agent: The system cannot find the file specified.

      10/17/13 11:43:06.764 ERROR    rscdsvc - HandleAgentStart: Agent process may have failed to start, Check for Agent hung processes or Agent resources still in use, consier reboot

      10/17/13 11:43:06.764 DEBUG    rscdsvc - ManageAgent: Type of loop - before wait agent(68)

      10/17/13 11:43:06.764 ERROR    rscdsvc - ManageAgent: Agent down hard thread(68)

      10/17/13 11:43:06.764 DEBUG    rscdsvc - RSCDsvc is not reporting itself as paused.

      10/17/13 11:43:06.764 ERROR    rscdsvc - ManageAgent: Agent being restarted - count=50

      10/17/13 11:43:08.764 DEBUG    rscdsvc - HandleAgentStart: Top

      10/17/13 11:43:08.764 INFO     rscdsvc - HandleAgentStart: Agent process started ("C:\Program Files\BMC Software\BladeLogic\RSCD\/RSCD.exe" -r -R)

      10/17/13 11:43:24.389 ERROR    rscdsvc -  1007server1 1212 SYSTEM (Not_available): (Not_available): ACNP_Open: No Agent Control Pipe detected, Service manager cannot control agent: The system cannot find the file specified.

      10/17/13 11:43:24.389 ERROR    rscdsvc - HandleAgentStart: Agent process may have failed to start, Check for Agent hung processes or Agent resources still in use, consier reboot

      10/17/13 11:43:24.389 DEBUG    rscdsvc - ManageAgent: Type of loop - before wait agent(68)

      10/17/13 11:43:24.389 ERROR    rscdsvc - ManageAgent: Agent down hard thread(68)

      10/17/13 11:43:24.389 DEBUG    rscdsvc - RSCDsvc is not reporting itself as paused.

      10/17/13 11:43:24.389 ERROR    rscdsvc - ManageAgent: Agent failed after 50 restarts. Exiting

      10/17/13 11:43:24.389 INFO     rscdsvc - RSCDsvc::Run: Service stopped

        • 1. Re: RSCD agent does not start.

          which version of RSCD ? there was a known issue with one !

          • 2. Re: RSCD agent does not start.

            This has been fixed in BSA 8.0 SP10. What version of BSA are you using ?

             

            Regards

            • 3. Re: RSCD agent does not start.
              Team Fujitsu

              Thank you for your replies.

               

              Agent version is 8.3.01.160.

              It seems that VL differs from KA374411.

              • 4. Re: RSCD agent does not start.
                Siddu angadi

                is it one agent giving the proble? or many?

                 

                Thanks

                Siddu

                • 5. Re: RSCD agent does not start.
                  Siddu angadi

                  Hi,

                   

                  Is the Bladalogicuser account created ? if yes, check is it locked or not?

                   

                  Thanks

                  Siddu

                  • 6. Re: RSCD agent does not start.
                    Team Fujitsu

                    Hello Siddu-san

                     

                    It has occurred in two agents of many servers.

                    BladeLogicRSCD account is not created.

                     

                    - Here is rscd.log -

                    bcae8a01157eb359f021 0000000001 10/17/13 11:43:11.030 INFO     rscd -  1007server1 1676 SYSTEM (Not_available): (Not_available): FIPS Enabled

                    fbe6b8afd4b7bfd3e10c 0000000002 10/17/13 11:43:11.045 INFO     rscd -  1007server1 1676 SYSTEM (Not_available): (Not_available): Agent version is 8.3.01.160

                    a4b07581fddb8cc7a8e2 0000000003 10/17/13 11:43:11.045 INFO     rscd -  1007server1 1676 SYSTEM (Not_available): (Not_available): The operation completed successfully

                    16e05caa7c54cf630105 0000000004 10/17/13 11:43:11.045 INFO     rscd -  1007server1 1676 SYSTEM (Not_available): (Not_available): Platform Details: x86;1007server1;5.2;WindowsNT;3790;x86

                    03b0b41d3a2db069562b 0000000005 10/17/13 11:43:11.045 INFO     rscd -  1007server1 1676 SYSTEM (Not_available): (Not_available): Main: **** RSCD started (app) ****

                    2e3531db1be26ab36acd 0000000006 10/17/13 11:43:11.061 INFO2    rscd -  1007server1 1676 SYSTEM (Not_available): (Not_available): Main: Valid CM/NSH License.

                    0180c16c286e20f207f0 0000000007 10/17/13 11:43:11.108 DEBUG    rscd -  1007server1 3248 SYSTEM (Not_available): (Not_available): listen_thread Top

                     

                    Thanks.

                    • 7. Re: RSCD agent does not start.
                      Siddu angadi

                      This is same issue as:

                       

                      https://communities.bmc.com/thread/68108?start=15&tstart=0

                       

                      Try explore this and apply the fix. Still it does not work.  Then reinstall the agent with Full Amdinistration preveiligies.

                      Thanks

                      Siddu

                      • 8. Re: RSCD agent does not start.
                        Siddu angadi

                        Below is the consolidated conversation for thread 68108:

                         

                        ######################################################

                         

                        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa ?

                         

                        Check this KB- https://kb.bmc.com/infocenter/index?page=content&id=KA307612&actp=search&publishedview=true&viewlocale=en_US for the correct values and other steps mentioned here.

                         

                        Also, can you take a screenshot of the following and attach here?

                         

                        Go to services.msc-> BladeLogic RSCD Service-> Double click the services-> Dependencies tab.

                         

                        #######################################################

                         

                        This is the error:

                        "The Server service is not started. (Could not determine if this is a domain controller. Expect failures in user privilege mapping mode.)


                        With the new version (I believe starting 8.1.x) you need to have Server service running on the target for the BladeLogic RSCD Agent to work. The Netlogon service is also required to be running if the target is a DC.
                        You can use this command to set the dependency on the BladeLogic RSCD Agent, so that it does not attempt to start before time, provided that you do a lot of reboots:


                        On DC:
                        sc config RSCDsvc depend= Netlogon/LanmanServer


                        On non-DC (or you could just use the syntax above, if you do not have Netlogon disabled due to other policies):
                        sc config RSCDsvc depend= LanmanServer

                        ###########################################################

                         

                        In addition to my original post, make sure that Server and Netlogon services are not disabled - set them to Automatic. These need to be started prior to BladeLogic RSCD Agent account can start.

                         

                        Deleting the BladeLogicRSCD account would have resolved possible another followup issue, where the account is getting locked. So in the end this is the procedure that you should do:

                         

                        - Make sure the BladeLogic RSCD Agent is stopeed

                        - If BladeLogicRSCD account is locked - unlock it (or delete it, as it will be recreated)

                        - Make sure that Server and Netlogon services are set to Automatic (for now start them manually, but the 'automatic' startup will ensure they start after system reboot)

                        - Run this to set the Server and Netlogon services dependencies for BladeLogic RSCD Agent:

                        sc config RSCDsvc depend= Netlogon/LanmanServer

                        - Start BladeLogic RSCD Agent manually this time (but in the future, it will be started after the dependent services have started)

                         

                        BladeLogicRSCD account should be created this time around and stay around.

                         

                        ###########################################################

                         

                        netstat -o showed a pid using port 4750.

                        Restarted that service and RSCD.

                         

                        telnet *** 4750 works!

                         

                        ######################################################

                        • 9. Re: RSCD agent does not start.
                          Team Fujitsu

                          Hi all,

                           

                          Thank you for many advices.

                          I have a little progress.

                          I found rscd installer does not create exports, secures, users.local on C:\Windows\rsc.

                          After I myself create 3 files manually, rscd starts successfully.


                          However, even if I repeat rscd install and uninstall several times, the installer has never created the 3 files.

                          Do you know anything about the cause of this trouble?


                          Here is msi.log

                          (For more details, see to attachment, sorry that it is mixed Japanese)

                          Taking a look at the log, there are some warning messages.

                          But, the installation finished successfully.

                          ---

                          <<<< BMC_LOG_MESSAGE >>>>  INFO: Creating configuration files in: C:\WINDOWS\rsc\

                          <<<< BMC_LOG_MESSAGE>>>>  WARNING: The file
                          C:\WINDOWS\system32\config\SYSTEM~1\LOCALS~1\Temp\secure does not exist.

                          <<<< BMC_LOG_MESSAGE>>>>  WARNING: The file C:\WINDOWS\system32\config\SYSTEM~1\LOCALS~1\Temp\exports does not exist.

                          <<<< BMC_LOG_MESSAGE>>>>  WARNING: The file C:\WINDOWS\system32\config\SYSTEM~1\LOCALS~1\Temp\users.local does not exist.

                          --

                          • 10. Re: RSCD agent does not start.
                            sourav halder

                            This works for me

                             

                              Agent Release   : 8.3.03.170

                             

                            - Make sure the BladeLogic RSCD Agent is stopeed

                            - If BladeLogicRSCD account is locked - unlock it (or delete it, as it will be recreated)

                            - Make sure that Server and Netlogon services are set to Automatic (for now start them manually, but the 'automatic' startup will ensure they start after system reboot)

                            - Run this to set the Server and Netlogon services dependencies for BladeLogic RSCD Agent:

                            sc config RSCDsvc depend= Netlogon/LanmanServer

                            - Start BladeLogic RSCD Agent manually this time (but in the future, it will be started after the dependent services have started)

                             

                            BladeLogicRSCD account should be created this time around and stay around.

                            • 11. Re: RSCD agent does not start.
                              Cody Dean

                              Good Morning,

                              We actually had this happen on some of our 2003 servers and didn't discover a solution until two days ago.  It's been happening a while and only effected a certain group of servers for us. 

                              The solution was as follows:

                              1. Uninstall RSCD Agent

                              2. Remove any BladelogicRSCD user profiles that might exist (and directories from C:\Documents and Settings)

                              3. Reboot

                              4. Login to the box using the /admin switch (from mstsc, to login as console)

                              5  Install the RSCD agent. 

                               

                              The /admin switch is what seemed to make it be able to create the user for us.