Need a HOWTO: Troubleshoot a failed deployment

I'm not really an OD admin guy, but I've been thrust into it and I'd appreciate some advice on how to troubleshoot a failed deployment. We have several deployments fail each day for seemingly no reason that I can fathom. If I retry the failed deployment about 15 minutes later it works fine. I've attached the two logs which seem to be identical to me except that one has this:

Directories deployed : 0 Files deployed : 0 Links deployed : 0
Directories failed : 0 Files failed : 1 Links failed : 0
Directories deleted : 0 Files deleted : 0 Links deleted : 0

and the other has this:

Directories deployed : 0 Files deployed : 1 Links deployed : 0
Directories failed : 0 Files failed : 0 Links failed : 0
Directories deleted : 0 Files deleted : 0 Links deleted : 0

How do you find out the specific reason why a file failed? And why would it fail, but then work 15 minutes later? Thanks for reading.

Find more posts tagged with

Comments

Adam Stoller

I'm not really an OD admin guy, but I've been thrust into it and I'd appreciate some advice on how to troubleshoot a failed deployment. We have several deployments fail each day for seemingly no reason that I can fathom. If I retry the failed deployment about 15 minutes later it works fine. I've attached the two logs which seem to be identical to me except that one has this:

Directories deployed : 0 Files deployed : 0 Links deployed : 0
Directories failed : 0 Files failed : 1 Links failed : 0
Directories deleted : 0 Files deleted : 0 Links deleted : 0

and the other has this:

Directories deployed : 0 Files deployed : 1 Links deployed : 0
Directories failed : 0 Files failed : 0 Links failed : 0
Directories deleted : 0 Files deleted : 0 Links deleted : 0

How do you find out the specific reason why a file failed? And why would it fail, but then work 15 minutes later? Thanks for reading.

You should probably look at the receiver side logs too - but given that you're deploying into what looks like an IIS directory (d:\inetpub\...) there's a chance that IIS has a lock on the file - you could try bumping up the svrTryInterval (currently set to 15) and svrTryCount (currently set to 10) and/or you could try setting the svrTryDisableOverwrite (defaults to "no") and/or the rmReadOnly (defaults to "no") transferRules settings.

Lex

You should probably look at the receiver side logs too - but given that you're deploying into what looks like an IIS directory (d:\inetpub\...) there's a chance that IIS has a lock on the file - you could try bumping up the svrTryInterval (currently set to 15) and svrTryCount (currently set to 10) and/or you could try setting the svrTryDisableOverwrite (defaults to "no") and/or the rmReadOnly (defaults to "no") transferRules settings.

Thanks, you've given me several things to try so hopefully I can get this figured out.

Lex

I tried the suggestions for changes to the actual deployment script, but we are still seeing failed deployments with regularity. I personally don't have permissions on the servers where these files are deployed, but I asked the guy who does to pull some of the OD receiver logs for the failures. I've attached a snippet from one such log. It looks to me like there is some type of file locking going on, but I thought I'd post the snippet here to get confirmation from those who might know better than I. Thanks.

Adam Stoller

I tried the suggestions for changes to the actual deployment script, but we are still seeing failed deployments with regularity. I personally don't have permissions on the servers where these files are deployed, but I asked the guy who does to pull some of the OD receiver logs for the failures. I've attached a snippet from one such log. It looks to me like there is some type of file locking going on, but I thought I'd post the snippet here to get confirmation from those who might know better than I. Thanks.

errno=5 is obviously the significant error.
On my Unix system that corresponds to EIO (Input/Output error) which could be pretty much anything, so it's not a lot of help.

I suggest you search for "errno=5" string both here on DevNet and on the Support site - because it seems to ring a bell to me - but I don't remember what it is, and I don't feel like searching for it for you ;-)

Lex

errno=5 is obviously the significant error.
On my Unix system that corresponds to EIO (Input/Output error) which could be pretty much anything, so it's not a lot of help.

I suggest you search for "errno=5" string both here on DevNet and on the Support site - because it seems to ring a bell to me - but I don't remember what it is, and I don't feel like searching for it for you ;-)

Bah...I should have done that first anyways. Thanks for the prompt. I found a couple threads on the issue, but I've already tried the rmReadOnly="yes" with no effect. One thread died with no resolution posted so I've revived that to see if the original poster found an answer. I think it's going to come down to me getting access to that server so I can do some troubleshooting.