[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 03, 2000 4:55 PM
To: [EMAIL PROTECTED]
Subject: Re: Server not responding... Need help
Thanks Seth,
I talked to tivoli and they gave me 3.7.3.6 and the server is now up and
running but why the crash out of no wher. I now have a huge core dump to
pour
Seth,
I'm of the same mentality; if it aint broke... why fix it.
I'd still like to know what caused it.
-
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
Hello everyone,
I've hit a situation I've never encountered before. My TSM server(rs6000 70 v3.7 had
crashed yesterday. We restarted it and it comes backup but will not allow an sessions
to be established with it.
I'm getting ans1017e messages and ans8023e messages. Thes messages state there
Healy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 03, 2000 2:04 PM
To: [EMAIL PROTECTED]
Subject: Server not responding... Need help
Hello everyone,
I've hit a situation I've never encountered before. My TSM server(rs6000 70
v3.7 had crashed yesterday. We restarted it and it comes backup
I'm getting ans1017e messages and ans8023e messages.
Jim - The 8023 says you can't establish an admin session.
I would try starting the server interactively, in the
foreground, and see what Activity Log messages are produced.
You might also do an errpt to see if anything there, or if
a
James,
you can kill restart the TSM server -- sometimes this will get the
TCP/IP port back. Otherwise you need to reset the system.
Steffan
James Healy wrote:
Hello everyone,
I've hit a situation I've never encountered before. My TSM server(rs6000 70 v3.7 had
crashed yesterday. We
I had a very similar exprience (except I did a normal halt) and ended up
having to recycle the AIX system. With the server not running, ports 1500
and 1580 were showing in use (aixnetstat -a | grep 1500, if I remember
correctly), and my SysAdmin (who, in my opinion, sits at the right hand of
the
Thanks Seth,
I talked to tivoli and they gave me 3.7.3.6 and the server is now up and running but
why the crash out of no wher. I now have a huge core dump to pour over. Almost looks
like it was a memory allocation problem from early peeks at the dump. Anyone else hit
this and actually come
