Troubleshooting
Problem
Scheduled backups do not start in the given time window if sessioinitiation is set to "serveronly". Instead error messages ANS1814E and ANS1815E are returned.
Symptom
If the Tivoli Storage Manager node and server are configured for having the session started only by the server (sessioninitiation set to "serveronly" on both node and server), the scheduled backups may fail with the following errors:
- In the dsmerror.log from the client:
SendStartOp: Received rc: -50 trying to receive ConfirmResp verb
ANS1814E Unable to start the scheduled event 'EVENT1'
ANS1815E Either the window has elapsed or the schedule has been deleted
- In the activity log from the server:
ANR0406I Session 381838 started for node NODE1 (WinNT) (Tcp/Ip). ANR0480W Session 381840 for node NODE1 (WinNT) terminated -
connection with client severed.
ANR0480W Session 381838 for node NODE1 (WinNT) terminated -
connection with client severed.
Cause
The main cause is due to firewall rules blocking the communication from the Tivoli Storage Manager server to the Tivoli Storage Manager client node.
Diagnosing The Problem
The issue can be analyzed gathering two concurrent traces both on client side (traceflag service) and server (traceflag session sessiond tcp).
Analyzing the traces, the following messages related to the dropped communication can be seen:
In the client trace:
[005008] [4404] : ..\..\common\com\commtcp.cpp(2099): ANS1005I TCP/IP read
error on socket = 1636, errno = 10054, reason : 'A existing connection was forcibly closed by the remote host.'
[005008] [4404] : ..\..\common\com\session.cpp(1519): Recv Verb:
[005008] [4404] : ..\..\common\com\session.cpp(1521): ...error-1
[005008] [4404] : ..\..\common\com\session.cpp(1522): sessRecvVerb: Error -50 from call to 'readRtn'. [005008] [4404] : ..\..\common\com\session.cpp(4682): sessClose: Transitioning: sSignedOn state ===> sInit state
The Server trace shows the session is terminated while the server was trying to send the ConfirmResp verb:
963476][smutil.c][15824][SmInMediaWait]:Evaluating session
NODE1(687483).
[963476][smutil.c][15860][SmInMediaWait]:Reporting False -
in False, out False,
mediaWaitList 0 and bfHandle 1179c2578 for NODE1(687483).
[963504][smutil.c][15824][SmInMediaWait]:Evaluating session
NODE1(687483).
[963504][smutil.c][15860][SmInMediaWait]:Reporting False -
in False, out False,
mediaWaitList 0 and bfHandle 1179c2578 for NODE1(687483).
[smexec.c][3348][smEndMessage]:Session 687483 for
NODE1 ending with termReason 1. :
Resolving The Problem
From the messages in the traces is clear that there is something closing the connection.
The most probable cause for errno 10054 is a firewall rule that is blocking the communication from the server to the client.
Contact the Firewall Administrator to open the communication ports between the server and the client.
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21679326