2 Replies Latest reply on Jul 19, 2010 5:45 AM by Carmine Buono

    BL8 ssl_write error

      Hi all,

      I've this problem (there is also a ticket): when opening a nsh shell with "nexec" command (nexec -i hostname su), if idle for some minutes it falls with error "ssl_write".

       

      The Appserver is BL8.

      The RSCD Agent is 8 version.

      NSH is trought nsh proxy.

      There is not Load balancer.

       

       

      In this environment there is an BL7.4.5 up and running that does not present this issue.

       

       

      Anyone had the some issue?

       

      Thanks...CArmine

        • 1. Re: BL8 ssl_write error

          I know that from 7.6 too ...

          Either "read error " or "write error".

          And the nexec sometimes cannot be simply killed, but runs on the AppServer with high CPU load!

          • 2. Re: BL8 ssl_write error

            Yes, on the client there is the samme issue about CPU load.

            The problem is really strange...

             

             

            09:47:33.283050 IP RSCD_TARGET_local_.ssad > NSH_SERVER_PROXY_.38615: P 2158:2211(53) ack 583 win 317 <nop,nop,timestamp 3870718450 670732288>
            09:47:33.283056 IP NSH_SERVER_PROXY_.38615 > RSCD_TARGET_local_.ssad: . ack 2211 win 215 <nop,nop,timestamp 670732361 3870718450>
            09:47:33.284107 IP RSCD_TARGET_local_.ssad > NSH_SERVER_PROXY_.38615: P 2211:2280(69) ack 583 win 317 <nop,nop,timestamp 3870718450 670732361>
            09:47:33.284112 IP NSH_SERVER_PROXY_.38615 > RSCD_TARGET_local_.ssad: . ack 2280 win 215 <nop,nop,timestamp 670732362 3870718450>
            09:54:35.968408 IP NSH_SERVER_PROXY_.38615 > RSCD_TARGET_local_.ssad: F 583:583(0) ack 2280 win 215 <nop,nop,timestamp 671155112 3870718450>
            09:54:35.971461 IP RSCD_TARGET_local_.ssad > NSH_SERVER_PROXY_.38615: P 2280:2365(85) ack 584 win 317 <nop,nop,timestamp 3871161550 671155112>
            09:54:35.971485 IP NSH_SERVER_PROXY_.38615 > RSCD_TARGET_local_.ssad: R 3840293082:3840293082(0) win 0

             

            Proxy sends a FIN ack (is out of sequence?... ) to the target that sends an ack... but the Proxy socket is already close, because I see a Reset!!!

             

            I don't think to a problem about the tcp stack, but...

             

             

            Ciao...CArmine