Opendeploy stalls during deployment

Okay, I have had an odd occurrence today and was wondering if anyone can shed some light on it.

When publishing a couple of files to one of our sites something glitched and the OpenDeploy sender crashed, leaving the receiver stuck in between the process with .iwnew and .iwold files/folders. Not usually a problem,we restarted both sender and receiver which usually fixes up everything.

Not this time. The .iwnew files/folders were gone, but the .iwold ones were still there. I was able to delete them manually from the server (which you don't normally have permissions for when it has frozen) Also every publishing job for that site got to "Deploy Submitted content" and stalled. On the webserver where the file was delivered an .iwold file was created and that is where it stopped. On the teamsite end it stayed at "Deploy Submitted content" and didn't move.

I could publish to other sites on the same server, I could publish to other servers, but not the affected sites (there were two of them).

We shut down and restarted the Open deploy receiver again figuring the problem was on that end, no joy, so we rebooted the entire web server. The problem kept happening.

I tried publishing to the affected sites from the test teamsite server, that was successful.

On the prod teamsite server we tried an iwreset -a, still no luck, stopped and restarted teamsite and opendeploy, again nothing.

Eventually I rebooted the entire server and we can now publish again, but the .iwold files from the earlier attempts had to be manually removed.

Has anyone had a similar problem and were you able to solve it without doing a complete reboot ?

The part I don't understand is why rebooting the sender fixed it, if the files were getting stuck on the receiver.

Thanks

ps. We are using OpenDeploy 6.0.0 and TS 6.1.0 SP1 (upgrading soon)

Find more posts tagged with

Comments

dhayalan

I am facing the same problem. In transitional deployment, the .iwold files were created once if large size files were deployed to the target server. I am able to delete this manually. but this is happening every time. Smiley Sad

Can any one help on this.

Rick Poulin

You have to help a little bit here.. Share some log files, and specify your TS and OD versions. If you're actually on OD6.0 and TS6.1 like the post you resurrected, the answer should be painfully obvious.

Adam Stoller

I am facing the same problem. In transitional deployment, the .iwold files were created once if large size files were deployed to the target server. I am able to delete this manually. but this is happening every time.

Can any one help on this.

The post you followed-up on is only about 6 years old.
The question your asking is a bit vague (not: it's "transactional" not "transitional")

A transactional deployment will always create a .iwold and .iwnew copy of the files being deployed - upon successful completion of the deployment, both should have been cleaned up. Upon failure, and successful completion of "rollback", both should be cleaned up too.

The only time you should end up with such files lingering around is if the deployment process was aborted in a non-graceful fashion, preventing the normal and/or rollback completion.

The other thing that you should be careful of, and which might cause these files to linger, is if you have concurrent transactional deployments to the same target area -- there are settings you should make in the base and receiver configuration files to serialize concurrent transactional deployments to prevent that from happening. This is documented in the manuals and several threads in the forum.