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 Failure

System

Hello there,

I am running into some weird Open Deploy error problem.

OD Base OS version - Solaris 10
OD Base version - 7.3.2
OD Receiver OS version - RED HAT 6
OD Receiver version - 7.2.1

Simple open deploy is failing to deploy the content. Once the base initiates the flow the receiver returns nack and base just stops an processing and the deployment fails.

1) We have checked the OD user (with which OD is running at receiver end) is able to write the file on the target directory. No permission issues.
2) The receiver xml entries are proper, with similar setting the deployment works on other server.
3) We have checked the license and it's a valid license on receiver and base both side.
4) We have tried remote diff and file based deployment and both fails with same error.

Now I will list the errors we see.

1) Error on receiver side:
2014-03-06 09:12:17.328 GMT-0800 serverLog [ReThread-0] - ENG: Rcvr send verson string, rc=1
2014-03-06 09:12:17.329 GMT-0800 serverLog [ReThread-0] - ENG: Rcvr: sender-version=7.3.2.0.0 receiver-version=7.2.1.0.0
2014-03-06 09:12:17.388 GMT-0800 serverLog [ReThread-0] - ENG: Receiver is version slave
2014-03-06 09:12:17.438 GMT-0800 serverLog [ReThread-0] - ENG: ***ERROR - Check the filepath. Filepath might have exceeded maximum path length //OpenDeployNG/log/LiveSite/r
cv.test.MYDEFINITIONNAME.LiveSiteDEVRuntime.log
2014-03-06 09:12:17.438 GMT-0800 serverLog [ReThread-0] - ENG: ***ERROR - Exception accessing //OpenDeployNG/log/LiveSite/rcv.test.MYDEFINITIONNAME.LiveSiteDEVRuntime.logen
_US.iso88591
2014-03-06 09:12:17.553 GMT-0800 serverLog [ReThread-0] - ENG: Rcvr sent nack, rc=1
2014-03-06 09:13:57.298 GMT-0800 serverLog [ReThread-0] - ENG: Rcvr got request to receive a deployment.
2014-03-06 09:13:57.298 GMT-0800 serverLog [ReThread-0] - ENG: Rcvr OpenDeploy Version is 7.2.1.0.0

2014-03-06 09:13:58.744 GMT-0800 serverLog [ReThread-0] - ENG: Rcvr received base version string
2014-03-06 09:13:59.443 GMT-0800 serverLog [ReThread-0] - ENG: ***ERROR - Rcvr read deployment attributes got null, exiting

2) Error on Base Side:
ENG: Thread-57 Sender-side handshake timeout = 120 secs
ENG: Thread-57 Send version string to receiver, RC = 13
ENG: Thread-57 Send attributes to receiver, RC = 1
ENG: Thread-57 Read attributes from receiver.
ENG: Thread-57 sender-version=7.3.2.0.0 receiver-version=7.2.1.0.0
ENG: Thread-57 Sender is version master
ENG: Thread-57 Sender compatible with receiver: version down-rev
ENG: Thread-57 ***ERROR - Receiver didn't reply with ack, it replied: nack:7.2.1.0.0
ENG: Thread-57 exiting setup
ENG: Thread-57 entering awaiting-cleanup
ENG: previousPhaseStr:setup
ENG: currentPhaseStr:awaiting-cleanup
ENG: Thread-57 exiting awaiting-cleanup
ENG: Thread-57 entering cleanup
ENG: Thread-57 exiting cleanup
ENG: Thread-57 entering task-failed
ENG: Thread-57 still waiting for 0

So the root cause starts with following error on receiver side
2014-03-06 09:12:17.438 GMT-0800 serverLog [ReThread-0] - ENG: ***ERROR - Exception accessing //OpenDeployNG/log/LiveSite/rcv.test.MYDEFINITIONNAME.LiveSiteDEVRuntime.logen
_US.iso88591

then receiver send nack to base and says got deployment attributes null, base sees the nack response and the deployment fails completely.

I am not able to comprehend what does this error mean. I have seen the file paths for od much longer than the one which is failing.
2014-03-06 09:12:17.438 GMT-0800 serverLog [ReThread-0] - ENG: ***ERROR - Check the filepath. Filepath might have exceeded maximum path length //OpenDeployNG/log/LiveSite/r
cv.test.MYDEFINITIONNAME.LiveSiteDEVRuntime.log
2014-03-06 09:12:17.438 GMT-0800 serverLog [ReThread-0] - ENG: ***ERROR - Exception accessing //OpenDeployNG/log/LiveSite/rcv.test.MYDEFINITIONNAME.LiveSiteDEVRuntime.logen
_US.iso88591

Any suggestions will be appreciated.

Thanks
Rajesh

Find more posts tagged with

Comments

Adam Stoller

Check with Support - there was a brief period where OD failed to properly do up-rev and/or down-rev deployments - for which a patch was created. This sounds like what you're running into.

I don't recall which versions were involved (hence it would be a good idea to contact Support)

Migrateduser

Hi All,

I wanted to post the solution we found for the problem. It is pretty much weird but it resolved our problem.

OD was running as a non root user. This non root user is shared with other applications running on the machine. During OD startup, it was setting the following parameter which was restricting the length of the file names created by OD.
JAVA_TOOL_OPTIONS: -Dfile.encoding=en_US.iso88591

When we set this parameter as null then OD works fine otherwise causes failures.

Thanks

SaiDeen

Hi All,

We are using multi-tier deployment and the log permisson for the LSCS servers Opendeploy logs were changed to 002.

We are deploying from Base ==> Staging ==> 4 LSCS and 4 LSDS servers.

But some times, the log permission for the OpenDeploy Logs(only LSCS deployment logs) were changed to 002.

It happens randomly and we are not able to figureout the root cause.

2015-11-02 16:14:16.326 GMT+0800 serverLog [ReThread-0] - ENG: ***ERROR - Check the filepath. Filepath might have exceeded maximum path length /app/teamsite/iw-home/OpenDeployNG/log/lscs/rcv.teamsite-areadiff-relay.LSCSRuntimeRelay.Staging_server.to.LSCS_SERVER_1.log
2015-11-02 16:14:16.326 GMT+0800 serverLog [ReThread-0] - ENG: ***ERROR - Exception accessing /app/teamsite/iw-home/OpenDeployNG/log/lscs/rcv.teamsite-areadiff-relay.LSCSRuntimeRelay.Staging_server.to.LSCS_SERVER_1.log/app/teamsite/iw-home/OpenDeployNG/log/lscs/rcv.teamsite-areadiff-relay.LSCSRuntimeRelay.Staging_server.to.LSCS_SERVER_1.log (Permission denied)

Our OD is running as non-root and OD version of 7.3.1.

Could any one help on this?

Adam Stoller

Is OpenDeploy running as 'root' on all servers?

Check 'root's (or whatever account is being used's) umask. It is possible that someone set the default umask [for root or whomever] differently so that when a new log file is created it gets the different permissions.

SaiDeen

Hi Ghoti,

Thanks for the reply.

The Opendeploy(Staging and LSCS) is running in owner_ID but TeamSite Base is running in root.

Adam Stoller

Did you check the umask value for "owner_ID" on [all] the receivers?

SaiDeen

0022 is the permission for the all the folders.

Adam Stoller

I didn't ask you about the permission on the folders - I asked you about the umask of the account.

The easiest way to determine that is to login as that account, or login as root and do a sudo su - account and then type umask and see what comes back.

SaiDeen

Thanks all for the valuable replies. The issue is fixed.

The issue is due to the log file which got apppended in the same file name and this make the log to change the permission.