is SKIPPED a bad thing in a deployment?

hello one of our deployments failed, and i can't see an explanaition, but in the log file of the src i see alot of:
LIB: 2006-11-21 13:10:15 delete .\com\commercial\c-program-ppv-432.html [reason missing-in-src] -- SKIPPED

i never seen this SKIPPED before in other logs, so is this a reason to fail? or is it an OK thing for OD to do?
we are on OD 5.6 w2k

thank you.

Find more posts tagged with

Comments

Adam Stoller

hello one of our deployments failed, and i can't see an explanaition, but in the log file of the src i see alot of:
LIB: 2006-11-21 13:10:15 delete .\com\commercial\c-program-ppv-432.html [reason missing-in-src] -- SKIPPED

i never seen this SKIPPED before in other logs, so is this a reason to fail? or is it an OK thing for OD to do?
we are on OD 5.6 w2k

thank you.

This is okay - you'll generally see this if the deployment was running in simulated / dontDo mode - are you sure you're looking at the log for the failed deployment?

CRB

yes i am looking at the log files of the sender and i attached the last part of the deployment log to both servers and the deployment job file. it says one directory failed, but i dont knwo why, i hope you can tell from the little info i put on the logs. i havent got the rcvr logs yet.

CRB

the complet log file from the sender is 650K byte and it has alot of SKIPPED things.. like 70% of the log file, just says that "skipped"... i can send itfrom a private email if anybody needs it

nipper

Skipped is fine. It happens when you do a date different deployment and have do deletes turn off. It says something like: deleting foo.html (missing in source) skipped...

Per your issue there is something wrong on the receiver. Get the receiver logs and post them. I say the sender logs and the receiver config file

CRB

this is what i was told from poeple who are watching the boxes: told me that it’s related to some temporary directories which perhaps don’t get deleted from previous deployments. (They said they have the extension “iwnew”.)

and i am about to get the rcvr logs soon, and yes the dodelete is turned off, this is what it s in the deployment job file:

doDeletes="no"
dontDo="no"
rmReadOnly="yes"
preserveAcls="no"
svrTryCount="2"
svrTryInterval="30"
/>
what do i need to change to delete the files with iwnew extensions?

Adam Stoller

this is what i was told from poeple who are watching the boxes: told me that it’s related to some temporary directories which perhaps don’t get deleted from previous deployments. (They said they have the extension “iwnew”.)

and i am about to get the rcvr logs soon, and yes the dodelete is turned off, this is what it s in the deployment job file:

doDeletes="no"
dontDo="no"
rmReadOnly="yes"
preserveAcls="no"
svrTryCount="2"
svrTryInterval="30"
/>
what do i need to change to delete the files with iwnew extensions?

The .iwnew extensions are, I believe, due to running a deployment with the transaction="yes" attribute set - and normally (if everything works) the .iwnew files and/or directories would end up replacing the files and directories of the same name without the extension (I could provide a more detailed description of what's involved here - but you can also read the manuals and other threads on transactional deployments).

Unfortunately - at some point in time - one (or more) of these transactional deployments failed - and while the failure is supposed to result in a rollback (which is supposed to include the removal of all the .iwnew files and directories) it is possible that the rollback failed as well (perhaps one or the other of the servers was shut-down, network glitch, whatever) - so these files and directories with the .iwnew extension are left lying around.

You could write a perl script to find and remove all these files, or you can use the built-in mechanisms on Windows to find and remove them. OpenDeploy won't remove them until/unless it overwrites them with another fresh deployment (and it might actually just move them aside and then back again, so I wouldn't count on that to clean it up). Basically, it's a manual effort that hopefully doesn't need to be done too frequently. If it is, then there is something wrong and that would need to be investigated.