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; } } }

failed to deploy directory?

CRB

hello all, we are on OD 5.6 on w2k.
we had a deployment that was running to two receivers at the same time, and it seems one of them fails and caused the roll back.
i said one of them, just bc i only found an error in one of the logs not in the other. but i couldnt tell what kind of error this is, can anybodyhelp me here?

thank you, any ideas to point me to the source of the problem will be very appreciated.

so far i only have the logs from the src and i got this much:
------------------------------------------
ENG: 2006-12-06 22:31:20 MST GMT-07:00 Thread-25 entering awaiting-commit

ENG: 2006-12-06 22:31:20 MST GMT-07:00 Thread-25 still waiting for 0

ENG: 2006-12-06 22:31:20 MST GMT-07:00 Thread-25 exiting awaiting-commit

ENG: 2006-12-06 22:31:20 MST GMT-07:00 Thread-25 entering commit

LIB: 2006-12-06 22:31:20 COMMITTING Transactional Deployment
LIB: (3) 2006-12-06 22:31:24 failed target name from receiver E:\inetpub\wwwroot\dorissrvc\images\IRD-screenshots\DTV_HR20\Impulse_Pay_Per_View__IPPV_
LIB: 2006-12-06 22:31:24 Receiver-ERROR: ERROR: commit-failed.
LIB: 2006-12-06 22:31:24 ERROR: Failed to deploy local_directory[.] of area[Y:\default\main\DORIS\doris_static\EDITION\ed_2414]
LIB: 2006-12-06 22:31:24 ERROR: Failed 1 of 1 local_directories
ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-25 After COMMIT, res=-1

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-25 exiting commit

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-25 entering awaiting-rollback

ENG: 2006-12-06 22:0031:24 MST GMT-07:00 Thread-25 still waiting for 0
--------------------------------------------

and but the second log i got:
----------------------------------------
LIB: (3) 2006-12-06 22:31:19 Received 'get' request for (.\srvc\howto\IRD-databases\DTV_HR20.txt)
LIB: 2006-12-06 22:31:19 Sending [.\srvc\howto\IRD-databases\DTV_HR20.txt] [reason src-is-newer] -- OK
ENG: 2006-12-06 22:31:19 MST GMT-07:00 Thread-26 After PRECOMMIT, res=0

ENG: 2006-12-06 22:31:19 MST GMT-07:00 Thread-26 exiting dotask

ENG: 2006-12-06 22:31:19 MST GMT-07:00 Thread-26 entering awaiting-commit

ENG: 2006-12-06 22:31:20 MST GMT-07:00 Thread-26 still waiting for 1

ENG: 2006-12-06 22:31:20 MST GMT-07:00 Thread-26 exiting awaiting-commit

ENG: 2006-12-06 22:31:20 MST GMT-07:00 Thread-26 entering commit

LIB: 2006-12-06 22:31:20 COMMITTING Transactional Deployment
LIB: 2006-12-06 22:31:24 Deploying local_directory[.] of area[Y:\default\main\DORIS\doris_static\EDITION\ed_2414] was UNENCRYPTED
ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-26 After COMMIT, res=0

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-26 exiting commit

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-26 entering awaiting-cleanup

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-26 still waiting for 1

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-26In MicroDeploy commit false

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-26In MicroDeploy commit 11

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-26In MicroDeploy commit 0

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Result after commit 0

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-26 exiting awaiting-cleanup

ENG: 2006-12-06 22:31:24 MST GMT-07:00 Thread-26 entering cleanup

LIB: 2006-12-06 22:31:24 ROLLBACK Transactional Deployment
ENG: 2006-12-06 22:31:27 MST GMT-07:00 Thread-26 After ROLLBACK, res=0

ENG: 2006-12-06 22:31:27 MST GMT-07:00 Thread-26 exiting cleanup

ENG: 2006-12-06 22:31:27 MST GMT-07:00 Thread-26 entering task-failed

ENG: 2006-12-06 22:31:28 MST GMT-07:00 Thread-26 still waiting for 1

ENG: 2006-12-06 22:31:28 MST GMT-07:00 Thread-26 exiting task-failed

Find more posts tagged with

Comments

iw_store

1. Check whether that receiver has desired directory structure.

2. Check you configuration file whether it properly matches path between source and destination

Rohan_t1

Chris,

We are also facing similar issue. Did you manage to find a solution for this?

-Rohan

yogesh_agrawal

can you post the receiver logs of failed receiver?

Rohan_t1

Thanks
I will get the receiver logs as soon as i can. Any other suggestion?

Adam Stoller

...
LIB: 2006-12-06 22:31:20 COMMITTING Transactional Deployment
LIB: (3) 2006-12-06 22:31:24 failed target name from receiver E:\inetpub\wwwroot\dorissrvc\images\IRD-screenshots\DTV_HR20\Impulse_Pay_Per_View__IPPV_
LIB: 2006-12-06 22:31:24 Receiver-ERROR: ERROR: commit-failed.
LIB: 2006-12-06 22:31:24 ERROR: Failed to deploy local_directory[.] of area[Y:\default\main\DORIS\doris_static\EDITION\ed_2414 ]
LIB: 2006-12-06 22:31:24 ERROR: Failed 1 of 1 local_directories
...

In answer to one of your questions - if a transactional deployment fails to deploy on any one of its "legs" in a fan-out (and there is no quorum set) - then all "legs" of the fan-out will be rolled back. That is why you may not see any error in the other log files.

Regarding the error messages above, it would appear you're using IIS on Windows - IIS is notorious for locking files and preventing them from being replaced. Sometimes it is a temporary thing, sometimes it is a more permanent thing.

There are a number of deployment configuration options related to this (search the forums, read the manual) for either trying to explicitly remove read-only files, trying multiple times to deploy the file, waiting between multiple tries, etc. Sometimes these options will work.

If you cannot get them to work, then you need a DNR script on the target side to run before the deployment that stops IIS and then another DNR script on the target side after the deployment that starts IIS. This is usually the least desirable solution because it represents an explicit disruption of service on your web site.

Another possibility to upgrade to the latest version of OpenDeploy (currently 6.2.0 Patch 1) and enable the transient_directory feature - which would allow transactional deployments to create their temporary files and directories (*.iwold, *.iwnew) in a distinct directory root from where the actual content lives - which might alleviate some or all of the problem without having to resort to stopping / starting IIS.

As noted - the receiver-side log of the actual failed deployment should provide at least a little bit more information about the cause of failure.