14 Replies Latest reply on Aug 21, 2014 3:45 PM by Bill Robinson

    what is STDERR?

      We are running BSA & Agent version 8.3.02. Several of our servers are getting the error " Received messages on STDERR for command. Treating STDERR as error, reset item return to failure" What does this meean and how to fix it?

        • 1. Re: what is STDERR?
          Bill Robinson

          Standard streams - Wikipedia, the free encyclopedia

           

          it means some output of the command went to stderr, meaning there was an error or something being treated as an error.

           

          can you attach the log that shows these messages in context ?

          • 2. Re: what is STDERR?

            Hope this helps.

             

             

             

            05/10/14 07:26:53.465 INFO     bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] [stdout: 2]         

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254363.1>IF ERRORLEVEL 1 GOTO ERRPATCHEND1

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254363.1>"C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254363.1\CL5.exe" 2097157 1 "Sat May 10 07:26:29 EDT 2014" "" "stPackager" Windows6.1-2008-R2-SP1-KB2876331-x64.msu MS13-089

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254363.1>"C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254363.1\Windows6.1-KB2876331-x64.msu" /quiet /norestart 

             

            05/10/14 07:26:54.448 INFO     bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] [stdout: 2]         

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254363.1>SET LASTERR=2359302

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254363.1>IF 2359302 EQU 3010 (

            SET REBOOTREQ=1 

            "C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254363.1\CL5.exe" 2097418 1 MS13-089 "Sat May 10 07:26:29 EDT 2014" "" Windows6.1-2008-R2-SP1-KB2876331-x64.msu "2-task.xml" 0

            )  ELSE (IF 2359302 EQU 0 ("C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254363.1\CL5.exe" 2097418 1 MS13-089 "Sat May 10 07:26:29 EDT 2014" "" Windows6.1-2008-R2-SP1-KB2876331-x64.msu "2-task.xml" 0 )  ELSE ("C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254363.1\CL5.exe" 2097418 1 MS13-089 "Sat May 10 07:26:29 EDT 2014" "" Windows6.1-2008-R2-SP1-KB2876331-x64.msu "2-task.xml" 0 ) )

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254363.1>Set PATCHPROCESSED=1

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254363.1>IF 1 == 0 GOTO EOFDEPLOYMENT

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254363.1>IF 1 == 1 ren "C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254363.1\2.bat" "2.bat.his"

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254363.1>Exit 2359302

             

            05/10/14 07:26:54.448 DEBUG    bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] In RunProcess: exitCode = 2359302

            05/10/14 07:26:54.448 WARN     bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Command returned code 2359302, treating return code as warning

            05/10/14 07:26:54.448 ERROR    bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Received messages on STDERR for command. Treating STDERR as error, reset item return to failure

            05/10/14 07:26:54.448 DEBUG    bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] chdir to PkgDir: 'C:\'

            05/10/14 07:26:54.463 WARN     bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] ActionOnFailure = Continue. Continuing deploy job

            05/10/14 07:26:54.463 DEBUG    bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Storing software payload for rollback

            05/10/14 07:26:54.635 DEBUG    bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Finished with asset

            05/10/14 07:26:54.635 DEBUG    bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Removing asset: 2

            05/10/14 07:26:54.666 DEBUG    bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Consolidating rollback file to bldeploy.xml

            05/10/14 07:26:54.666 DEBUG    bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Applying parent first id = 3

            05/10/14 07:26:54.666 INFO     bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Processing asset HOTFIX2

            05/10/14 07:26:54.666 DEBUG    bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Starting the asset

            05/10/14 07:26:54.791 DEBUG    bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] chdir to PkgDir: 'C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\/254727.1'

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.791 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - m_shavlikMSOfficeParam:: 2097418

            05/10/14 07:26:54.806 DEBUG    bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] exeFullPath = (null), CmdLine = "C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\/254727.1\bldeploycmd.3.bat", workingDir = NULL

            05/10/14 07:26:54.931 INFO     bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] [stdout: 3]         

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>chcp 1252  1>NUL

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>Setlocal

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>Set RETURNCODE=0 

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>Set Rename=1

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>Set PATHTOFIXES=C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254727.1\

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>Set HFOAIPDir=5ABC7004-OAIP

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>Set PATCHPROCESSED=0

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>Set REBOOTREQ=0

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>set LSFN=Windows6.1-KB2868626-x64.msu

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>"C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254727.1\CL5.exe" 2097174 "C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254727.1\Windows6.1-KB2868626-x64.msu"

             

            05/10/14 07:26:54.931 WARN     bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] [stderr: 3]    'chcp' is not recognized as an internal or external command,

            operable program or batch file.

             

            05/10/14 07:26:55.040 INFO     bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] [stdout: 3]         

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>IF ERRORLEVEL 1 GOTO ERRPATCHEND1

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>"C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254727.1\CL5.exe" 2097157 1 "Sat May 10 07:26:29 EDT 2014" "" "stPackager" Windows6.1-2008-R2-SP1-KB2868626-x64.msu MS13-095

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>"C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254727.1\Windows6.1-KB2868626-x64.msu" /quiet /norestart 

             

            05/10/14 07:26:58.535 INFO     bldeploy - [3][Windows6.1-2008-R2-SP1-KB2868626-x64.msu-MS13-095-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] [stdout: 3]         

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>SET LASTERR=2359302

             

             

            C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\254727.1>IF 2359302 EQU 3010 (

            SET REBOOTREQ=1 

            "C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254727.1\CL5.exe" 2097418 1 MS13-095 "Sat May 10 07:26:29 EDT 2014" "" Windows6.1-2008-R2-SP1-KB2868626-x64.msu "3-task.xml" 0

            )  ELSE (IF 2359302 EQU 0 ("C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254727.1\CL5.exe" 2097418 1 MS13-095 "Sat May 10 07:26:29 EDT 2014" "" Windows6.1-2008-R2-SP1-KB2868626-x64.msu "3-task.xml" 0 )  ELSE ("C:\temp\stage\b75c2e7d669b3f5cba106f9ba2c0c926\\254727.1\CL5.exe" 2097418 1 MS13-095 "Sat May 10 07:26:29 EDT 2014" "" Windows6.1-2008-R2-SP1-KB2868626-x64.msu "3-task.xml" 0 ) )

            • 3. Re: what is STDERR?
              Davorin Stevanovic

              Basically this is your error:

               

              05/10/14 07:26:54.448 WARN     bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Command returned code 2359302, treating return code as warning

              05/10/14 07:26:54.448 ERROR    bldeploy - [2][Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1] Received messages on STDERR for command. Treating STDERR as error, reset item return to failure

               

              did you maybe installed this patch earlier and then again run PAJ with remediation and in the mean time you did not reboot the target?

               

              Error: 2359302 means 0x00240006 WU_S_ALREADY_INSTALLED The update to be installed is already installed on the system

               

              Could you please Live browse the target server and check if patch is already installed there.

              1 of 1 people found this helpful
              • 4. Re: what is STDERR?
                Bill Robinson

                to add to what davorin said, the return code of the install command for Windows6.1-2008-R2-SP1-KB2876331-x64.msu-MS13-089-en-WINDOWS SERVER 2008 R2 ENTERPRISE (X64)-SP1 is non-zero.

                 

                anything other than a 0 return code from a command executed by bladelogic (bldeploy) is treated as an error unless the return code overrides have been set (for example - for a microsoft patch a return code of 3010 means the patch installed but a reboot is required, so while that is not 0, it can be treated as ok)

                 

                so your patch threw an error, and that is the reason for the error message.  davorin indicated what might have caused the error.

                1 of 1 people found this helpful
                • 5. Re: what is STDERR?

                  if the patch is already installed, is there a way for BladeLogic to intake it as a warning instead of an error?

                  • 6. Re: what is STDERR?
                    Bill Robinson

                    it would depend on the error code – if that error code only means the patch is already installed we could maybe add that to the return code overrides for warnings.  In the patch global config in bsa , on the windows tab there is a line for the ‘patch deploy warning return codes’ that you would add this code to and then run the cuj.

                    • 7. Re: what is STDERR?

                      Ok. This is what we already have in the PGC.

                      • 8. Re: what is STDERR?

                        See attachment picture.

                        • 9. Re: what is STDERR?
                          Bill Robinson

                          I don’t see the picture.  Also, can you attach the entire bldeploy log? (use the adv editor)

                          • 11. Re: what is STDERR?

                            Hi Eric,

                             

                            The bldeploy log have Exit Code 1618 or

                             

                            1618 means - Another installation is already in progress. Complete that installation before proceeding with this install.

                             

                            Win32 System error codes

                             

                            2359302 - Bill and Davorin already provided the solution for 2359302.


                            -Chetan

                            • 13. Re: what is STDERR?
                              Mohit Mohan

                              what does below warning means?

                               

                              08/16/14 12:47:12.363 WARN     bldeploy - [1][Package_2.29.13.3842] [stderr: 1]       Package - Previous Version:[2.29.13.3450] <-> New Version:[2.29.13.
                              3842]

                              08/16/14 12:47:12.363 DEBUG    bldeploy - [1][Package_2.29.13.3842] In RunProcess: exitCode = 0
                              08/16/14 12:47:12.363 INFO     bldeploy - [1][Package_2.29.13.3842] Received messages on STDERR for command. Treating STDERR as warning

                               


                              • 14. Re: what is STDERR?
                                Bill Robinson

                                Can you attach the entire bldeploy log ?