nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Open deploy failed ...Sender-side handshake timeout

Lal

Hi,

I am getting this error when we are doing an open deploy to production nodes.

Could you please throw lights on this,

Warm Regards
lal

######################

######################

ENG: 2009-10-15 13:03:59 UTC GMT+00:00 Thread-3574 Connecting to host=10.59.229.130 port=20014

ENG: 2009-10-15 13:03:59 UTC GMT+00:00 Thread-3574 Sender Side timeout = 0

ENG: 2009-10-15 13:03:59 UTC GMT+00:00 Thread-3574 Buffer Size 4000
ENG: 2009-10-15 13:03:59 UTC GMT+00:00 Thread-3574 After Connect RC = 0
ENG: 2009-10-15 13:03:59 UTC GMT+00:00 Thread-3574 Sender-side handshake timeout = 120 secs
ENG: 2009-10-15 13:03:59 UTC GMT+00:00 Thread-3574 Send version string to receiver, RC = 13
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 Thread-3574 ***ERROR - Send attributes to receiver got RC = -1
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 Thread-3574 exiting setup
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 Thread-3574 entering awaiting-cleanup
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 previousPhaseStr:setup
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 currentPhaseStr:awaiting-cleanup
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 Thread-3574 exiting awaiting-cleanup
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 Thread-3574 entering cleanup
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 Thread-3574 exiting cleanup
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 Thread-3574 entering task-failed

############

ENG: 2009-10-15 13:09:36 UTC GMT+00:00 Thread-3635 Connecting to host=itseelm-ax4019.ikea.com port=20014

ENG: 2009-10-15 13:09:36 UTC GMT+00:00 Thread-3635 Sender Side timeout = 0

ENG: 2009-10-15 13:09:36 UTC GMT+00:00 Thread-3635 Buffer Size 4000
ENG: 2009-10-15 13:09:36 UTC GMT+00:00 Thread-3635 After Connect RC = 0
ENG: 2009-10-15 13:09:36 UTC GMT+00:00 Thread-3635 Sender-side handshake timeout = 120 secs
ENG: 2009-10-15 13:09:36 UTC GMT+00:00 Thread-3635 Send version string to receiver, RC = 13
ENG: 2009-10-15 13:11:36 UTC GMT+00:00 Thread-3635 ***ERROR - Send attributes to receiver got RC = -1
ENG: 2009-10-15 13:11:36 UTC GMT+00:00 Thread-3635 exiting setup
ENG: 2009-10-15 13:11:36 UTC GMT+00:00 Thread-3635 entering awaiting-cleanup
ENG: 2009-10-15 13:11:36 UTC GMT+00:00 previousPhaseStr:setup
ENG: 2009-10-15 13:11:36 UTC GMT+00:00 currentPhaseStr:awaiting-cleanup
ENG: 2009-10-15 13:11:36 UTC GMT+00:00 Thread-3635 exiting awaiting-cleanup
ENG: 2009-10-15 13:11:36 UTC GMT+00:00 Thread-3635 entering cleanup
ENG: 2009-10-15 13:11:36 UTC GMT+00:00 Thread-3635 exiting cleanup
ENG: 2009-10-15 13:11:36 UTC GMT+00:00 Thread-3635 entering task-failed

Find more posts tagged with

Comments

ISCBorisB

Note that your problem is probably not a Time-out, that was just a regular info message (what your time-out has been set to).

If I were you I would've checked standard things first. Make sure that the Receiver is up, listening on the expected Port,
Fire Walls allow the connection etc. Providing all that is taken care of you will have to analyze OD Receiver Logs to see
what's causing the failure

Lal

Thnaks Boris,

I verified all except the od receiver logs, I will do that and come back if I get some more info on this,

Lal

Adam Stoller

\ENG: 2009-10-15 13:03:59 UTC GMT+00:00 Thread-3574 Send version string to receiver, RC = 13
ENG: 2009-10-15 13:05:59 UTC GMT+00:00 Thread-3574 ***ERROR - Send attributes to receiver got RC = -1

I'm not positive about this, but I think the "RC = 13" is the error code received from the receiver - which, if it's using standard error code values would be EACCES - or Permission Denied.

Check to make sure the receivers are running, and if so, who they are running as (are the receivers Unix or Windows?), and whether there's any aspect of the network configuration between sender and receiver that might be doing some sort of authentication check (??), or just get together with your local network administrator so that they can examine the traffic when you attempt to perform the deployment.

Lal

Hi Ghoti,

Today i was able to get access to the od logs of target nodes.
This is the error which I could see there, any thoughts on this?

2009-10-19 14:23:57 IWDeploySock::WriteString ERROR: Sending (2) bytes of string data to remote.
2009-10-19 14:23:57 ERROR: outer-loop send failure, fd=86, err=32 [Unknown socket error]

Note: Both the src and target nodes,version is the same,

nipper

OK, 1st question, is this a basic sender -> receiver or is it a more complicated fan out ? The error implies the receiver could not send information, which could mean it cannot pass the files downstream in a fan out deployment.

I also have seen where the fire wall is open in one direction only, so the sender can send information to the receiver but the replies are blocked. OD requires two way communications.

HTH

me

Lal

Hi,

This is not a fan-out deployment, it is a non-transactional simple deployment Only,

nipper

Then have someone log on the receiver and try to telnet to the OD sender on the appropriate port (should be 20014)

ISCBorisB

Hi,

This is not a fan-out deployment, it is a non-transactional simple deployment Only,

How consistent is the problem? Does it happen always, sometimes, randomly? Does it go away at least temporarily when you restart
Target OD Receiver(s)? What IS your receiver, Unix/Linux or Windows?

Quite possibly 'err 32' denotes generic Socket "Broken Pipe" Error, it may be caused by various Network conditions like overload,
*stuck* OD receiver process and so on

Lal

Hi,

When we restart the problem may not be there..but after some time it will start again..

receiver is on AIX server,

ISCBorisB

Hi,

When we restart the problem may not be there..but after some time it will start again..

receiver is on AIX server,

Contact Support. We have no way of knowing what and why deteriorates in your Environments over time

Pawan

Hi,

When we restart the problem may not be there..but after some time it will start again..

receiver is on AIX server,

Check your OD.log on the receiver side which should mention the deployment details after which this problem may be occurring. We had a similar problem with OD6.1.1 on AIX box which goes away after restarting OD services on receiver.