On Mon, 25 Aug 2008 14:08:59 +0200, Colin Allinson <[EMAIL PROTECTED] m> wrote:
>Over the weekend a LAN problem resulted in TCPIP getting hung up on 3 of >our systems and a recycle of TCPIP was necessary to resolve the issue. > >On 2 of the systems we had no issue but, on a 3rd, we had a subsequent >issue with NAMESRV needing a separate manual recycle of that server. > >When I look at the console of TCPIP startup I see :- > > DTCIPI030W StartANewLife: Victim NAMESRV, reason "Restarting you >because TCP/IP has been restarted" > HCPLGA054E Already logged on disconnected > >and, sure enough, NAMESRV was not restarted. I see the same for all 3 >systems but, I guess, NAMESRV survived without problems on the other 2 b ut >got hung up on this system. > >This leads me to the following questions:- >- Should TCPIP force it's application servers before starting them - and , >if so, what might I have configured incorrectly? >- If not, what would be the best place to insert commands to force these >off when TCPIP is started to ensure a clean start up? > > >Colin Allinson > >Amadeus Data Processing GmbH > We ran into a similar problem, but the guest was SSLSERV. We IPLed VM. Th en Dennis noticed he had forgotten some beta service for SSLSERV so he #CP EXT TCPIP. TCPIP ca me down after bringing down it's guests. SSLSERV was shut down but (because it is a Linux guest? ) it did not log off. When TCPIP came back up it tried to AUTOLOG SSLSERV but failed because SSLSERV was still logged on. We are planning to open an incident, but I don't see it open yet. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
