1 2 Previous Next 15 Replies Latest reply on Oct 6, 2016 10:42 AM by Santhosh Kurimilla

    verify fails but live browse works

    Raja Mohan

      hi, I have a solaris server that I am able to live browse successfully to file system, processes, system info ... but verify fails, unix groups, unix users etc. This is a Solaris 10 server on bsa 8.3.02. Any thoughts?

        • 1. Re: verify fails but live browse works
          Santosh Kothuru

          You can try to run "Update Server Properties" job and check the status.

          • 2. Re: verify fails but live browse works
            Geeta Gokhale

            Also please post logs here.

            • 3. Re: verify fails but live browse works
              Santhosh Kurimilla

              You may need to Right click on the server -> Administration Task -> Distribution Configuration Objects.

              You will be prompted with New Job window Name it, and select the required COs as shown in the screen capture.Distribute CO.JPG

              • 4. Re: verify fails but live browse works
                Jim Wilson

                Before doing that, get data to show what is happening.

                 

                1. Define "fail" of verify.  How do you know it failed? What error do you see?

                2. Collect details - get the RSCD log from the target

                3. Collect more details - set the RSCD on the target to debug logging level.  Repeat the activities (Verify, Live Browse Unix Users, also run agentinfo).  Get the new RSCD log and the reset to info1 logging.

                 

                RSCD Debug Logging:

                 

                Modify the log4crc.txt in /etc/rsc on the target

                 

                Change the line :

                <category name="rscd" priority="info1" appender="/opt/bmc/bladelogic/NSH/log/rscd.log" debugappender="stderr"/>

                to

                <category name="rscd" priority="debug" appender="/opt/bmc/bladelogic/NSH/log/rscd.log" debugappender="stderr"/>

                 

                Restart the RSCD Agent

                Reproduce the problem

                • 5. Re: verify fails but live browse works
                  Santhosh Kurimilla

                  I was under impression the issue might be as shown below (he is not able to view the options Unix users, Unix Groups):

                  browse.jpg

                  • 6. Re: verify fails but live browse works
                    Bill Robinson

                    you should never have to deploy the built-in COs to a target.

                     

                    if the appserver version does not match the target agent version, and the appserver does not have the CO verion(s) present on the target agent(s) then you will not see the COs in live browse (CO = UnixUsers, UnixGroups, Daemons, etc)

                    • 7. Re: verify fails but live browse works
                      Raja Mohan

                      Jim Wilson get "failed to connect" error on port 4750. Notice on the logs when tried

                       

                      "TLS setup failed for agent: Protool mismatch. Check that client and server "secure" files match. Exiting and terminating connection."

                       

                      My question, how does livebrowse to a filesystem works without an issue when all other functions seem to fail? does it use different method?

                      • 8. Re: verify fails but live browse works
                        Raja Mohan

                        rscd agent is running, listening on port

                         

                        ps -ef |grep rsc[dw]

                            root  8474  8472   0   Mar 28 ?           0:00 bin/rscd

                            root  8472     1   0   Mar 28 ?           0:00 bin/rscd

                            root  8473  8472   0   Mar 28 ?           0:00 bin/rscd

                         

                        pfiles /proc/* 2>/dev/null | nawk '/^[0-9]*:/ { pid=$0 } /port: 4750$/ { printf("%s %s\n",pid,$0);}'

                        8474:   bin/rscd        sockname: AF_INET 0.0.0.0  port: 4750

                         

                        Refresh server properties job runs every 6 hours and it fails with the same "connect" error for that particular server.

                        • 9. Re: verify fails but live browse works
                          Jim Wilson

                          Raja Mohan wrote:

                           

                          My question, how does livebrowse to a filesystem works without an issue when all other functions seem to fail? does it use different method?

                          Yes.

                          Please post the RSCD log

                          • 10. Re: verify fails but live browse works
                            richard mcleod

                            Do you have separate config/app servers? What's in the exports file on the target?

                            • 11. Re: verify fails but live browse works
                              Mike Reider

                              Im seeing a similar issue on one of our mannaged servers. If i right click > Verify, it will hang indefinitely up to a point where I have to kill the console. If I browse it, theres no issues. Not seeing errors in rscd.log

                              • 12. Re: verify fails but live browse works
                                Bill Robinson

                                what version of bsa?

                                using a socks proxy?

                                using a nsh proxy?

                                what's in the agent log when the hang happens?

                                put the rscd log on the target in debug mode if you can to capture that.

                                • 13. Re: verify fails but live browse works
                                  Mike Reider

                                  our bsa is 851 patch 4, no sox proxy, no nsh proxy. Our appservers are using a load balancer, but in this case im logging in directly to 1 of the appservers, not using LB.

                                   

                                  [root@ulvclird1 /]# tail -f /opt/bmc/bladelogic/NSH/log/rscd.log

                                  76206e5fea5dfa3880fc 0000002493 07/02/15 13:46:27.241 INFO     rscd -  ulvclird1 4956 -1/-1 (Not_available): (Not_available): Getting network interfaces details

                                  47d0ab175a8172bf72d8 0000002494 07/02/15 13:46:27.242 INFO     rscd -  ulvclird1 4956 -1/-1 (Not_available): (Not_available): Got network interfaces details: 2 entries

                                  033d1da06b377c3a5385 0000002495 07/02/15 13:46:48.116 ERROR    rscd -  ulvclird1 2624 -1/-1 (Not_available): (Not_available): SSL_read (Error on socket: 'Connection reset by peer')

                                  358ea328ea71d216f796 0000002496 07/02/15 13:46:48.117 ERROR    rscd -  ulvclird1 2624 -1/-1 (Not_available): (Not_available): SSL_write (Error on socket: 'Broken pipe')

                                  b49caeea9f7bf385fc76 0000002497 07/02/15 13:46:48.278 ERROR    rscd -  ulvclird1 2624 -1/-1 (Not_available): (Not_available): SSL error : s3_pkt.c:781 error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry

                                  6db594824824482f638c 0000002498 07/02/15 13:46:48.278 ERROR    rscd -  ulvclird1 2624 -1/-1 (Not_available): (Not_available): SSL_write

                                  • 14. Re: verify fails but live browse works
                                    Mike Reider

                                    also the agent ver matches teh app server, secure files and users files look ok and consistent w other hosts

                                     

                                    whats weird is that i can browse the server, the agent is up but its just the Verify call thats hanging it (or when a job tries to execute against it, the job will hang). The it cant be port 4750 issue.

                                    1 2 Previous Next