14 Replies Latest reply on May 12, 2011 9:38 PM by edwin miller

    failure when running sox compliance against solaris 10

      Info  May 5, 2011 4:18:26 PM  saving results for job

      Info  May 5, 2011 4:18:26 PM  The job 'testcom6320blade' has failed

      Info  May 5, 2011 4:17:28 PM  Started running the job 'testcom6320blade' with priority 'NORMAL' on application server 'lxrp930_job01'(2,002,000)

      Info  May 5, 2011 4:17:28 PM  creating work item for component SOX Data Security Standard - Solaris10 (10.20.11.104)

      Info  May 5, 2011 4:17:29 PM  Executing work item Compliance Job:testcom6320blade; Template:SOX Data Security Standard - Solaris10; Component:SOX Data Security Standard - Solaris10 (10.20.11.104); Server:10.20.11.104; on application server: lxrp930_job01

      Info  May 5, 2011 4:17:31 PM  Compliance execution started for component: SOX Data Security Standard - Solaris10 (10.20.11.104)

      Error May 5, 2011 4:18:26 PM  com.bladelogic.om.infra.app.collector.AssetCollectionException: sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      sort: cannot stat temporary directory /var/tmp//installjvaaf6: No such file or directory

      (component=SOX Data Security Standard - Solaris10 (10.20.11.104), selector=Extended Object:BL-LXO User Accounts and Environment Configuration)

       

      This same process runs fine against linux boxes, also I can nsh and do other menu items to the server without problem.

        • 1. failure when running sox compliance against solaris 10
          Bill Robinson

          as the user you are mapped to on the target can you run:

           

          set | grep installjvaa6

          and/or

          env | grep installjvaa6

           

          and see if that dir is being used in any of the env variables ?

          • 2. failure when running sox compliance against solaris 10

            10% set | grep installjvaa6

            10%

             

            No result

             

            By the way I went into the rscd server and cleaned up the environment a big

            The shell was changed from sh from ksh and also renamed .profile

             

            After doing this the compliance still failed buy I got much further in the run see logs below

             

            from debug on app server

             

            11 10:32:55,280] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Checking RBAC access for object type id = 4003 and auth enum = 16 on object name = Running Processes

            [10 May 2011 10:32:55,280] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] get Entries From Agent:/opt/bmc/BladeLogic/8.0/NSH/tmp/WorkItem-Thread-71305037975280.ini

            [10 May 2011 10:32:55,280] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Couldn't find proxy server for servername= 10.20.11.104

            [10 May 2011 10:32:55,280] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] NSHExec: about to run cmd: nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"

            [10 May 2011 10:32:55,281] [WorkItem-Thread-7] [INFO] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Executing command : nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"

            [10 May 2011 10:32:55,281] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] About to exec(nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"): pid=-1

            [10 May 2011 10:32:55,445] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] exec(nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"): pid=5950

            [10 May 2011 10:32:55,446] [WorkItem-Thread-7] [INFO] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Started pid 5950: nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"

            [10 May 2011 10:32:55,446] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] About to wait for process with pid:5950

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [FINE] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Pid 5950 finished with exit code 127

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Joining stream threads for process with pid:5950

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Stream threads finished for process with pid:5950

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] NSHExec is Complete

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [FINE] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Releasing resources for process with pid:5950

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Freeing process handle

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Freed process handle

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closing stdin

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closed stdin

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closing stdout

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closed stdout

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closing stderr

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closed stderr

            [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [FINE] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Released resources for process with pid:5950

            [10 May 2011 10:32:55,558] [WorkItem-Thread-7] [INFO] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] com.bladelogic.om.infra.app.collector.AssetCollectionException: nsh:1: connection refused: //blfs/bladelogic/blstorage/extended_objects/running_processes.nsh

            (component=SOX Data Security Standard - Solaris10 (10.20.11.104), selector=Extended Object:Running Processes)

            [10 May 2011 10:32:55,558] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] com.bladelogic.om.infra.app.service.workitem.event.WorkItemFinishedEvent@208ff1a2

            [10 May 2011 10:32:55,559] [Job-Execution-1] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] execution thread processing events: 1

            [10 May 2011 10:32:55,559] [Job-Execution-1] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] execution thread processing results: 0

            [10 May 2011 10:32:55,559] [Job-Execution-1] [DEBUG] [::] [] Removing session for thread : Job-Execution-1

             

            from export

             

             

            "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:31:28 AM",creating work item for component SOX Data Security Standard - Solaris10 (10.20.11.104) "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:31:29 AM",Executing work item Compliance Job:compliance10.20.11.104; Template:SOX Data Security Standard - Solaris10; Component:SOX Data Security Standard - Solaris10 (10.20.11.104); Server:10.20.11.104;  on application server: lxrp930_job01 SOX Data Security Standard - Solaris10 (10.20.11.104) (),Info,"May 10, 2011 9:31:30 AM",Compliance execution started for component: SOX Data Security Standard - Solaris10 (10.20.11.104) SOX Data Security Standard - Solaris10 (10.20.11.104) (),Error,"May 10, 2011 9:32:55 AM","com.bladelogic.om.infra.app.collector.AssetCollectionException: nsh:1: connection refused: //blfs/bladelogic/blstorage/extended_objects/running_processes.nsh

            (component=SOX Data Security Standard - Solaris10 (10.20.11.104), selector=Extended Object:Running Processes)"

            "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:32:55 AM",saving results for job "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:32:55 AM",The job 'compliance10.20.11.104' has failed

            • 3. failure when running sox compliance against solaris 10

              the problem now is

              connection refused: //blfs/bladelogic/blstorage/extended_objects/running_processes.nsh

               
              from debug
              
              11 10:32:55,280] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Checking RBAC access for object type id = 4003 and auth enum = 16 on object name = Running Processes
              [10 May 2011 10:32:55,280] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] get Entries From Agent:/opt/bmc/BladeLogic/8.0/NSH/tmp/WorkItem-Thread-71305037975280.ini
              [10 May 2011 10:32:55,280] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Couldn't find proxy server for servername= 10.20.11.104
              [10 May 2011 10:32:55,280] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] NSHExec: about to run cmd: nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"
              [10 May 2011 10:32:55,281] [WorkItem-Thread-7] [INFO] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Executing command : nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"
              [10 May 2011 10:32:55,281] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] About to exec(nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"): pid=-1
              [10 May 2011 10:32:55,445] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] exec(nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"): pid=5950
              [10 May 2011 10:32:55,446] [WorkItem-Thread-7] [INFO] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Started pid 5950: nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"
              [10 May 2011 10:32:55,446] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] About to wait for process with pid:5950
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [FINE] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Pid 5950 finished with exit code 127
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Joining stream threads for process with pid:5950
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Stream threads finished for process with pid:5950
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] NSHExec is Complete
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [FINE] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Releasing resources for process with pid:5950
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Freeing process handle
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Freed process handle
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closing stdin
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closed stdin
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closing stdout
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closed stdout
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closing stderr
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Closed stderr
              [10 May 2011 10:32:55,555] [WorkItem-Thread-7] [FINE] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] Released resources for process with pid:5950
              [10 May 2011 10:32:55,558] [WorkItem-Thread-7] [INFO] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] com.bladelogic.om.infra.app.collector.AssetCollectionException: nsh:1: connection refused: //blfs/bladelogic/blstorage/extended_objects/running_processes.nsh
              (component=SOX Data Security Standard - Solaris10 (10.20.11.104), selector=Extended Object:Running Processes)
              [10 May 2011 10:32:55,558] [WorkItem-Thread-7] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] com.bladelogic.om.infra.app.service.workitem.event.WorkItemFinishedEvent@208ff1a2
              [10 May 2011 10:32:55,559] [Job-Execution-1] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] execution thread processing events: 1
              [10 May 2011 10:32:55,559] [Job-Execution-1] [DEBUG] [exm40828@CORP.PAETEC.COM:BLAdmins:] [Compliance] execution thread processing results: 0
              [10 May 2011 10:32:55,559] [Job-Execution-1] [DEBUG] [::] [] Removing session for thread : Job-Execution-1
              
              from export
              
              
              "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:31:28 AM",creating work item for component SOX Data Security Standard - Solaris10 (10.20.11.104) "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:31:29 AM",Executing work item Compliance Job:compliance10.20.11.104; Template:SOX Data Security Standard - Solaris10; Component:SOX Data Security Standard - Solaris10 (10.20.11.104); Server:10.20.11.104;  on application server: lxrp930_job01 SOX Data Security Standard - Solaris10 (10.20.11.104) (),Info,"May 10, 2011 9:31:30 AM",Compliance execution started for component: SOX Data Security Standard - Solaris10 (10.20.11.104) SOX Data Security Standard - Solaris10 (10.20.11.104) (),Error,"May 10, 2011 9:32:55 AM","com.bladelogic.om.infra.app.collector.AssetCollectionException: nsh:1: connection refused: //blfs/bladelogic/blstorage/extended_objects/running_processes.nsh
              (component=SOX Data Security Standard - Solaris10 (10.20.11.104), selector=Extended Object:Running Processes)"
              "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:32:55 AM",saving results for job "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:32:55 AM",The job 'compliance10.20.11.104' has failed
              
              
              
              • 4. Re: failure when running sox compliance against solaris 10

                10% set | grep installjvaa6

                10%

                 

                No result

                 

                By the way I went into the rscd server and cleaned up the environment a big

                The shell was changed from sh from ksh and also renamed .profile

                 

                After doing this the compliance still failed buy I got much further in the run see logs below

                 

                from debug on app server

                 

                11 10:32:55,280] exm40828@CORP.PAETEC.COM:BLAdmins: Checking RBAC access for object type id = 4003 and auth enum = 16 on object name = Running Processes

                exm40828@CORP.PAETEC.COM:BLAdmins: get Entries From Agent:/opt/bmc/BladeLogic/8.0/NSH/tmp/WorkItem-Thread-71305037975280.ini

                exm40828@CORP.PAETEC.COM:BLAdmins: Couldn't find proxy server for servername= 10.20.11.104

                exm40828@CORP.PAETEC.COM:BLAdmins: NSHExec: about to run cmd: nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"

                exm40828@CORP.PAETEC.COM:BLAdmins: Executing command : nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"

                exm40828@CORP.PAETEC.COM:BLAdmins: About to exec(nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"): pid=-1

                exm40828@CORP.PAETEC.COM:BLAdmins: exec(nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"): pid=5950

                exm40828@CORP.PAETEC.COM:BLAdmins: Started pid 5950: nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"

                exm40828@CORP.PAETEC.COM:BLAdmins: About to wait for process with pid:5950

                exm40828@CORP.PAETEC.COM:BLAdmins: Pid 5950 finished with exit code 127

                exm40828@CORP.PAETEC.COM:BLAdmins: Joining stream threads for process with pid:5950

                exm40828@CORP.PAETEC.COM:BLAdmins: Stream threads finished for process with pid:5950

                exm40828@CORP.PAETEC.COM:BLAdmins: NSHExec is Complete

                exm40828@CORP.PAETEC.COM:BLAdmins: Releasing resources for process with pid:5950

                exm40828@CORP.PAETEC.COM:BLAdmins: Freeing process handle

                exm40828@CORP.PAETEC.COM:BLAdmins: Freed process handle

                exm40828@CORP.PAETEC.COM:BLAdmins: Closing stdin

                exm40828@CORP.PAETEC.COM:BLAdmins: Closed stdin

                exm40828@CORP.PAETEC.COM:BLAdmins: Closing stdout

                exm40828@CORP.PAETEC.COM:BLAdmins: Closed stdout

                exm40828@CORP.PAETEC.COM:BLAdmins: Closing stderr

                exm40828@CORP.PAETEC.COM:BLAdmins: Closed stderr

                exm40828@CORP.PAETEC.COM:BLAdmins: Released resources for process with pid:5950

                exm40828@CORP.PAETEC.COM:BLAdmins: com.bladelogic.om.infra.app.collector.AssetCollectionException: nsh:1: connection refused: //blfs/bladelogic/blstorage/extended_objects/running_processes.nsh

                (component=SOX Data Security Standard - Solaris10 (10.20.11.104), selector=Extended Object:Running Processes)

                exm40828@CORP.PAETEC.COM:BLAdmins: com.bladelogic.om.infra.app.service.workitem.event.WorkItemFinishedEvent@208ff1a2

                exm40828@CORP.PAETEC.COM:BLAdmins: execution thread processing events: 1

                exm40828@CORP.PAETEC.COM:BLAdmins: execution thread processing results: 0

                [] Removing session for thread : Job-Execution-1

                 

                from export

                 

                 

                "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:31:28 AM",creating work item for component SOX Data Security Standard - Solaris10 (10.20.11.104) "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:31:29 AM",Executing work item Compliance Job:compliance10.20.11.104; Template:SOX Data Security Standard - Solaris10; Component:SOX Data Security Standard - Solaris10 (10.20.11.104); Server:10.20.11.104;  on application server: lxrp930_job01 SOX Data Security Standard - Solaris10 (10.20.11.104) (),Info,"May 10, 2011 9:31:30 AM",Compliance execution started for component: SOX Data Security Standard - Solaris10 (10.20.11.104) SOX Data Security Standard - Solaris10 (10.20.11.104) (),Error,"May 10, 2011 9:32:55 AM","com.bladelogic.om.infra.app.collector.AssetCollectionException: nsh:1: connection refused: //blfs/bladelogic/blstorage/extended_objects/running_processes.nsh

                (component=SOX Data Security Standard - Solaris10 (10.20.11.104), selector=Extended Object:Running Processes)"

                "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:32:55 AM",saving results for job "Run at May 10, 2011 9:31:27 AM",Info,"May 10, 2011 9:32:55 AM",The job 'compliance10.20.11.104' has failed

                • 5. failure when running sox compliance against solaris 10
                  Bill Robinson

                  does the role:user running the job have access to the file server?

                  • 6. Re: failure when running sox compliance against solaris 10

                    </PROCESSES>

                    -bash-3.2$ ls -ltr running_processes.nsh

                    -rwxr-xr-x 1 blfs blfs 1535 Jul 27  2010 running_processes.nsh

                    -bash-3.2$ id

                    uid=159451(exm40828) gid=101(avahi-autoipd) groups=101(avahi-autoipd)

                    -bash-3.2$

                     

                    It seems to run fine from unix shell as exm40828

                    • 7. Re: failure when running sox compliance against solaris 10

                      -bash-3.2$ ls -ltr running_processes.nsh

                      -rwxr-xr-x 1 blfs blfs 1535 Jul 27  2010 running_processes.nsh

                      -bash-3.2$ id

                      uid=159451(exm40828) gid=101(avahi-autoipd) groups=101(avahi-autoipd)

                      -bash-3.2$ ls -ltr running_processes.nsh

                      -rwxr-xr-x 1 blfs blfs 1535 Jul 27  2010 running_processes.nsh

                      -bash-3.2$ id

                      uid=159451(exm40828) gid=101(avahi-autoipd) groups=101(avahi-autoipd)

                       

                       

                      exm40828 runs the running_processes.nsh script just fine from the shell

                       

                      =======================================

                       

                      also ran from "nsh here"  shell on gui

                       

                      cp'ed the script to /tmp on 10.20.11.104

                      then cd to //10.20.11.104/tmp

                      ./running_processes.nsh

                      and it ran fine

                      • 8. Re: failure when running sox compliance against solaris 10
                        Bill Robinson

                        What’s in the rsc files on the file server?

                         

                        Does the role running the job have access through the file server agent to that file ?

                        • 9. Re: failure when running sox compliance against solaris 10

                          If I go to a unix shell and do nsh then run the following it works fine

                           

                          nsh -c "//blfsprod/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"

                           

                          if I run

                           

                          -bash-3.2$ nsh -c "//blfs/bladelogic/blstorage/extended_objects/running_processes.nsh" "10.20.11.104"

                          nsh:1: connection refused: //blfs/bladelogic/blstorage/extended_objects/running_processes.nsh

                          -bash-3.2$

                           

                          Where does it define the host to use for extended objects?

                          • 10. Re: failure when running sox compliance against solaris 10
                            Bill Robinson

                            what is the difference between blfs and blfsprod?

                            • 11. Re: failure when running sox compliance against solaris 10

                              On my app server there is a mount nfs  mount to a blfsprod

                              # df -h

                              blfsprod:/bladelogic  247G  142G   93G  61% /bladelogic

                               

                              looking at my /etc/hosts file it is actually an alias for lxrp935

                               

                              # cat /etc/hosts

                              1. Do not remove the following line, or various programs

                              2. that require network functionality will fail.

                              127.0.0.1       localhost.localdomain localhost blfs

                              ::1             localhost6.localdomain6 localhost6

                              10.35.25.46     lxrp930 lxrp930.corp.paetec.com

                              10.35.25.53     lxrp935 lxrp935.corp.paetec.com blfs blfsprod

                              10.20.11.104    edsbox

                               

                              As far as I can tell blfs does not exist as a server

                              • 12. Re: failure when running sox compliance against solaris 10

                                I confirmed thru ./br/blappconf

                                 

                                That my File Server is defined as blfsprod mapped tp /bladelogic/blstorage/

                                • 13. Re: failure when running sox compliance against solaris 10
                                  Bill Robinson

                                  Go into the config object dictionary, or the specific component template and change the path for the eo

                                  • 14. Re: failure when running sox compliance against solaris 10

                                    well figured out yesterday the fix for the problem from TS: turns out our app server was configured with a rscd for the file server that was down, as soon as i ran the startup script the nsh could get to the the

                                    //blfs/bladelogic/blstorage/extended_objects/running_processes.nsh

                                    and compliance ran to completion without error.

                                     

                                    really new to the product so i didn't see the obvious

                                     

                                    app server has 2 instances of rscd running on for the server itself , the other for the file storage

                                    1 of 1 people found this helpful