I have this node (W2K - 5.2.3.4 client) that has been having issues with
session hangs/terminations/restarts !
One think I have noticed about this node is the TCPIP information that the
TSM server records, is confusing.
By this I mean that when I check the details for this node, is says the IP
address is 192.168.131.1.
However, when I check the activity log, it records the IP address as
128.172.8.65, which is the correct address.
It should not be using the 192.168 address (this is a DIEBOLD system and
it uses the private address to communicate with other DIEBOLD servers) and
there isn't a TCPNODEADDRESS statement to tell it otherwise ?
Why am I getting this misleading information ?
While on this topic (since this box is having issues), any suggestions on
what I can do about the hangs/restarts.
The only clues I have are these from the DSMERROR.LOG:
11/09/2004 10:07:56 ANS1005E TCP/IP read error on socket = 1140, errno =
10054, reason : 'An existing connection was forcibly closed by the remote
host.'.
11/09/2004 10:07:56 ANS1809W Session is lost; initializing session reopen
procedure.
11/09/2004 10:07:56 ANS1809W Session is lost; initializing session reopen
procedure.
11/09/2004 10:08:11 ANS1811S TSM session could not be reestablished.
11/09/2004 10:09:52 sessSendVerb: Error sending Verb, rc: -50
11/09/2004 10:09:52 ANS1809W Session is lost; initializing session reopen
procedure.
11/09/2004 10:09:52 ANS1809W Session is lost; initializing session reopen
procedure.
11/09/2004 10:10:07 ANS1810E TSM session has been reestablished.
11/09/2004 10:10:08 ANS1999E Incremental processing of '\\db\d$' stopped.
11/09/2004 10:10:09 ANS1369E Session Rejected: The session was canceled by
the server administrator.
11/09/2004 10:10:09 ANS1512E Scheduled event 'DIEBOLD' failed. Return
code = 12.
I can't find anything in the server log around this time, to address the
"forcibly closed" message. The only thing I have near this time is the
session ending stats:
11/9/2004 10:02:17 AM ANR0406I Session 2056 started for node DIEBOLD-DB1
(WinNT) (BPX-Tcp/Ip 128.172.8.65(2748)).
11/9/2004 10:02:18 AM ANR0403I Session 2019 ended for node DIEBOLD-DB1
(WinNT).
11/9/2004 10:02:19 AM ANE4952I (Session: 2056, Node: DIEBOLD-DB1) Total
number of objects inspected: 21,989
11/9/2004 10:02:19 AM ANE4954I (Session: 2056, Node: DIEBOLD-DB1) Total
number of objects backed up: 93
11/9/2004 10:02:19 AM ANE4958I (Session: 2056, Node: DIEBOLD-DB1) Total
number of objects updated: 0
11/9/2004 10:02:19 AM ANE4960I (Session: 2056, Node: DIEBOLD-DB1) Total
number of objects rebound: 0
11/9/2004 10:02:19 AM ANE4957I (Session: 2056, Node: DIEBOLD-DB1) Total
number of objects deleted: 0
11/9/2004 10:02:19 AM ANE4970I (Session: 2056, Node: DIEBOLD-DB1) Total
number of objects expired: 2
11/9/2004 10:02:19 AM ANE4959I (Session: 2056, Node: DIEBOLD-DB1) Total
number of objects failed: 0
11/9/2004 10:02:19 AM ANE4961I (Session: 2056, Node: DIEBOLD-DB1) Total
number of bytes transferred: 4.85 GB
11/9/2004 10:02:19 AM ANE4963I (Session: 2056, Node: DIEBOLD-DB1) Data
transfer time: 3,810.96 sec
11/9/2004 10:02:19 AM ANE4966I (Session: 2056, Node: DIEBOLD-DB1) Network
data transfer rate: 1,335.07 KB/sec
11/9/2004 10:02:19 AM ANE4967I (Session: 2056, Node: DIEBOLD-DB1)
Aggregate data transfer rate: 1,119.25 KB/sec
11/9/2004 10:02:19 AM ANE4968I (Session: 2056, Node: DIEBOLD-DB1) Objects
compressed by: 29%
11/9/2004 10:02:19 AM ANE4964I (Session: 2056, Node: DIEBOLD-DB1) Elapsed
processing time: 01:15:45
FYI/FWIW, we have been having these (and other) issues on this box, for a
while. The client was downlevel and one of the errors we were seeing was
tagged by an apar and listed as being targeted/fixed in 5.2.3.4. So we
upgraded the client, but it doesn't seem to have fixed this problem !
|
