9 Replies Latest reply on Feb 2, 2012 5:16 PM by Edwin Lindeman

    Failed to send TLS marker

    Mike Reider

      Hi all, I am running a file deploy job according to page 65 of BL 8.0 Install guide, to upgrade existing RSCD agents from 7.2 to 8.0

       

      the job runs ok all the way up to teh post commands, it copies the RSCD installer, the .iss, and at the post commands I'm getting this from the Job results log,

       

       

      Job Name,"RSCD800 Upgrade - Run at Apr 14, 2011 12:32:47 PM"
      Start Time,Apr 14, 2011 12:32:47 PM
      End Time,Apr 14, 2011 12:33:41 PM

      Status,Completed Successfully

      Participant,Type,Date,Message
      "Run at Apr 14, 2011 12:32:47 PM",Info,Apr 14, 2011 12:32:47 PM,"Started running the job 'RSCD800 Upgrade' on application server 'JobServer01'(2,002,242)"
      "Run at Apr 14, 2011 12:32:47 PM",Info,Apr 14, 2011 12:32:48 PM,Executing work item File Deploy Job:RSCD800 Upgrade; Server:rosetstbl76ts01;  on application server: JobServer01


      rosetstbl76ts01,Info,Apr 14, 2011 12:32:56 PM,Copy //rosetstbl76ts01/C/Temp/upgrade_v800/RSCD800-814-W32.EXE -> /c/temp/RSCD800-814-W32.EXE ... Done


      rosetstbl76ts01,Info,Apr 14, 2011 12:32:58 PM,Copy //rosetstbl76ts01/C/Temp/upgrade_v800/RSCD_upgrade.iss -> /c/temp/RSCD_upgrade.iss ... Done

      rosetstbl76ts01,Info,Apr 14, 2011 12:33:27 PM,+ /c/temp/job_2400130.3_postcmd.bat

      rosetstbl76ts01,Error,Apr 14, 2011 12:33:39 PM,Failed to send TLS marker
      rosetstbl76ts01,Info,Apr 14, 2011 12:33:40 PM,Exit Code 0
      rosetstbl76ts01,Error,Apr 14, 2011 12:33:40 PM,//rosetstbl76ts01/c/: Connection refused


      "Run at Apr 14, 2011 12:32:47 PM",Info,Apr 14, 2011 12:33:41 PM,The job 'RSCD800 Upgrade' has succeeded

       

      It says its 'succeeded' but upgrade never occurs.

       

      I'm running this job from a terminal server which has NSH proxy enabled, heres the secure file on this terminal server. I'm wondering if TLS marker is related to our NSH proxy settings.

       

      secure

      #
      #  Copyright (c) 2001-2005 BladeLogic, Inc.
      #       -- All Rights Reserved --
      #
      # The information in this file determines what encryption and authentication
      # parameters should be used by the RSCD Agent and the Network Shell utilities.
      #
      # Please read the BladeLogicAdministration.pdf or "secure" man page for details
      # on how to use this file.
      #
       

      #NSH Proxy
      rscd:port=4750:protocol=5:tls_mode=encryption_only:encryption=tls
      default:port=4750:protocol=5:tls_mode=encryption_only:encryption=tls:appserver_host=rosetstbl76ap01:appserver_port=9833:appserver_protocol=sso

      proxy:auth_profiles_file=/C/Program Files/BMC

      Software/bladelogic/8.0/NSH/br/authenticationProfiles.xml:auth_profile=AuthServer01:appserver_protocol=ssoproxy

        • 1. Failed to send TLS marker
          Bill Robinson

          The nsh proxy settings are for your client, not the appserver right?

           

          If so, those should have no effect on the job running.

           

          what is the post-install command that you are using?

           

          if you run the commands in the post-install on the target, is the upgrade successful ?

           

          is this happening on all targets or only some ?

          • 2. Re: Failed to send TLS marker
            Mike Reider

            hi Bill, the posted nsh settings are on terminal server console,not app server.

             

            this is the post install command Im running

             

            "C:\Program Files\BladeLogic\RSC\agentctl" -b exec C:\tmp\RSCD800-814-W32.EXE -a -s -f1C:\tmp\v3.iss

             

            If I run this command on target server from the target's command prompt, it runs the installation OK

             

            when I run this command in deploy job I get this error (I can browse the target servers files from teh console, so it cant be a credential issue)

             

             

            Participant,Type,Date,Message

            "Run at Apr 14, 2011 2:22:27 PM",Info,Apr 14, 2011 2:22:27 PM,"Started running the job 'RSCD800 Upgrade' on application server 'JobServer01'(2,002,242)"

            "Run at Apr 14, 2011 2:22:27 PM",Info,Apr 14, 2011 2:22:28 PM,Executing work item File Deploy Job:RSCD800 Upgrade; Server:rosetstbl76ts01;  on application server: JobServer01

            rosetstbl76ts01,Info,Apr 14, 2011 2:22:30 PM,Copy //rosetstbl76ts01/C/Temp/upgrade_v800/RSCD800-814-W32.EXE -> /c/tmp/RSCD800-814-W32.EXE ... Done

            rosetstbl76ts01,Info,Apr 14, 2011 2:22:30 PM,Copy //rosetstbl76ts01/C/Temp/v3.iss -> /c/tmp/v3.iss ... Done

            rosetstbl76ts01,Info,Apr 14, 2011 2:22:31 PM,+ /c/tmp/job_2400130.5_postcmd.bat

            rosetstbl76ts01,Error,Apr 14, 2011 2:22:36 PM,SSL_connect2

            rosetstbl76ts01,Error,Apr 14, 2011 2:22:36 PM,SSL_connect

            rosetstbl76ts01,Error,Apr 14, 2011 2:22:36 PM,//rosetstbl76ts01/c/: Error in TLS protocol

            rosetstbl76ts01,Info,Apr 14, 2011 2:22:38 PM,Exit Code 0

            rosetstbl76ts01,Error,Apr 14, 2011 2:22:38 PM,//rosetstbl76ts01/c/: Connection refused

            "Run at Apr 14, 2011 2:22:27 PM",Info,Apr 14, 2011 2:22:38 PM,The job 'RSCD800 Upgrade' has succeeded

             

            • 3. Re: Failed to send TLS marker
              Mike Reider

              it looks like its copying both the installer and .iss correctly to the target server.

               

              it also creates a NSH and BAT file, which contain the post install command. Its failing right as tries to run the .bat

               

              error: SSL_connect

              SSL_connect2

               

              error in TLS protocol

               

              If I run this .bat file manually on target, it installs new agent correctly.

              • 4. Re: Failed to send TLS marker
                Mike Reider

                after talking with support it turns out the culprit was the .iss file.

                 

                the TLS and SSL errors were to be expected, since the File Deploy job kicks off the post command .bat and then stops the agent, which causes these 'errors'.

                 

                the problem was the ISS file, if you open the setup.log file (in deployment folder on target machine), look at the Response result code, if its anything other than zero, its something with the installer or ISS file

                 

                mine was like this

                 

                 

                 

                [ResponseResult]

                ResultCode=-3

                 

                 

                this happens when you are recording the .iss during the initial install, the program runs to InstallShield, and its at the last screen that says you have been succesfully upgraded or installed. If you move that iss file out from its original location, without closing that last Installshield screen, the iss is gona be screwed up.

                 

                I regenerated it again, closing all screens, then reran the job and itt upgraded OK.

                • 5. Re: Failed to send TLS marker
                  Edwin Lindeman

                  I'm getting the same error and I made sure all my screens are closed during the initial install and after I run the deploy file job on the target my ResultCode=0.    Any thoughts?  This is going from 8.1 to 8.1 SP3  Regards

                  • 6. Re: Failed to send TLS marker
                    Bill Robinson

                    can you post the full job run log? and the agent isn't upgraded ?

                    • 7. Re: Failed to send TLS marker
                      Edwin Lindeman

                      Yes the agent is getting upgrade I just didn't know if those errors would cause me issues down the road. I can navigate and live browse the server with no issues.....below is the log

                       

                      Job Name,"AgentUpgrade - Run at Feb 2, 2012 3:45:23 PM" Start Time,Feb 2, 2012 3:45:23 PM End Time,Feb 2, 2012 3:45:44 PM Status,Completed Successfully  Participant,Type,Date,Message "Run at Feb 2, 2012 3:45:23 PM",Info,"Feb 2, 2012 3:45:23 PM",Started running the job 'AgentUpgrade' with priority 'NORMAL' on application server 'BBSA642012'(1) "Run at Feb 2, 2012 3:45:23 PM",Info,"Feb 2, 2012 3:45:24 PM",Executing work item File Deploy Job:AgentUpgrade; Server:Test2;  on application server: BBSA642012 Test2,Info,"Feb 2, 2012 3:45:36 PM",Copy //Test2/C/Windows/Temp/rscd.exe -> /tmp/blade/rscd.exe ... Done Test2,Info,"Feb 2, 2012 3:45:37 PM",Copy //Test2/C/Windows/Temp/rscd.iss -> /tmp/blade/rscd.iss ... Done Test2,Info,"Feb 2, 2012 3:45:37 PM",+ /tmp/blade/job_1819.14_postcmd.bat Test2,Error,"Feb 2, 2012 3:45:42 PM",Failed to send TLS marker Test2,Error,"Feb 2, 2012 3:45:42 PM",SSL_connect2 Test2,Error,"Feb 2, 2012 3:45:42 PM",SSL_connect Test2,Error,"Feb 2, 2012 3:45:42 PM",//192.168.3.20/c/: Error in TLS protocol Test2,Error,"Feb 2, 2012 3:45:43 PM",//192.168.3.20/c/: Operation not permitted Test2,Info,"Feb 2, 2012 3:45:43 PM",Exit Code 0 "Run at Feb 2, 2012 3:45:23 PM",Info,"Feb 2, 2012 3:45:44 PM",The job 'AgentUpgrade' has succeeded

                      • 8. Re: Failed to send TLS marker
                        Bill Robinson

                        the tls errors are usually ok, it's from when the agent is restarted for the upgrade.

                        • 9. Re: Failed to send TLS marker
                          Edwin Lindeman

                          thank you for the verification.