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

OD6.0.1 redeploys files always?

Adam Stoller

**** Lengthy Post ****

I've got a case open with Support (been open for about a month now, just added some more info to it) but I'm curious if anyone else has seen the same odd behavior. [Todd - the case number is 1212906 in case you want to help push things along...]
Using OD 6.0.1 on Solaris [8 or 9] with a semi-complex [multi-pathSpecification] remoteDiff deployment configuration file, I find that a number of files which are unchanged and which *do* exist in both source and target directories (on a loop-back-deployment) continually get deployed every time the deployment is run.

Below is a slightly abridged / slightly annotated transcript of the latest experience:

~ > cd /usr/app/iwov/od/OpenDeployNG/log
log > iwodcmd -v; uname -a
Version 6.0.1.0.0 Build 41860 Interwoven 20041018
SunOS xxxxxxxxx 5.9 Generic_117171-12 sun4u sparc SUNW,Sun-Fire-880
#### $IWHOME represents the TeamSite [6.5] installation directory
#### ~/IWHOME represents a symlink into a workarea used to version/maintain the custom files
log > ls -l $IWHOME/httpd/iw-bin/HispanicFileCheck.cgi ~/IWHOME/httpd/iw-bin/HispanicFileCheck.cgi
-rw-r--r--   1 astoller IAS         3443 Jan 25 18:37 /export/home/astoller/IWHOME/httpd/iw-bin/HispanicFileCheck.cgi
-rwxr-xr-x   1 rcatabay staff       3443 Jan 25 18:37 /usr/app/iwov/teamsite/httpd/iw-bin/HispanicFileCheck.cgi
log > sum $IWHOME/httpd/iw-bin/HispanicFileCheck.cgi ~/IWHOME/httpd/iw-bin/HispanicFileCheck.cgi
16456 7 /usr/app/iwov/teamsite/httpd/iw-bin/HispanicFileCheck.cgi
16456 7 /export/home/astoller/IWHOME/httpd/iw-bin/HispanicFileCheck.cgi
log > foreach i (0 1 2 3)
foreach? iwodcmd start code_install -inst RUN_$i
foreach? end
...
-- Start deployment code_installRUN_0.
-- Start deployment code_installRUN_1.
-- Start deployment code_installRUN_2.
-- Start deployment code_installRUN_3.
...
log > ls ~/IWHOME/httpd/iw-bin/export/home/astoller/IWHOME/httpd/iw-bin:
HispanicFileCheck.cgi       ed_co_browser.cgi
change_password.cgi         ed_co_gen_to_prev.cgi
change_password.ex          ed_co_prepopulate_meta.cgi
confirm.cgi                 ed_co_save_selection.cgi
delete.sh*                  edit_attributes.cgi
doe_deleteMetadata.cgi      iwwft_instantiator.cgi*
doe_delete_files.cgi        meta_copy.cgi
doe_generic.cgi             meta_copy_identifier.cgi
doe_move_files.cgi          meta_copy_title.cgi
doe_unlock_files.cgi        meta_help.cgi
doed_cm_preview.cgi         meta_read_user_prefs.cgi
doed_cm_verify_subnav.cgi   meta_term_assignment.cgi
doed_co_browser.cgi         meta_verify_entries.cgi
doed_co_select_subnav.cgi   metadelete.cgi
doed_select_office.cgi      process.cgi
doed_subnav_validator.cgi   touch.cgi#### Note: there are 32 files in this directory
log > egrep "HispanicFileCheck.cgi|doed_cm_preview.cgi" *RUN* | grep reason | grep OK
src.code_installRUN_0.IWHOME.xxxxxxxx.to.mylocalhost.log:LIB: 2005-01-26 07:20:05  Sending [./HispanicFileCheck.cgi]  [reason missing-in-dest] -- OK
src.code_installRUN_1.IWHOME.xxxxxxxx.to.mylocalhost.log:LIB: 2005-01-26 07:20:16  Sending [./HispanicFileCheck.cgi]  [reason missing-in-dest] -- OK
src.code_installRUN_2.IWHOME.xxxxxxxx.to.mylocalhost.log:LIB: 2005-01-26 07:20:29  Sending [./HispanicFileCheck.cgi]  [reason missing-in-dest] -- OK
src.code_installRUN_3.IWHOME.xxxxxxxx.to.mylocalhost.log:LIB: 2005-01-26 07:20:44  Sending [./HispanicFileCheck.cgi]  [reason missing-in-dest] -- OK
#### The file was there before and after every run of this
#### deployment, it never changed - why does it think it's "missing-in-dest"?
log > ls -l $IWHOME/httpd/iw-bin/HispanicFileCheck.cgi ~/IWHOME/httpd/iw-bin/HispanicFileCheck.cgi
-rw-r--r--   1 astoller IAS         3443 Jan 25 18:37 /export/home/astoller/IWHOME/httpd/iw-bin/HispanicFileCheck.cgi
-rwxr-xr-x   1 rcatabay staff       3443 Jan 25 18:37 /usr/app/iwov/teamsite/httpd/iw-bin/HispanicFileCheck.cgi
log > sum $IWHOME/httpd/iw-bin/HispanicFileCheck.cgi ~/IWHOME/httpd/iw-bin/HispanicFileCheck.cgi
16456 7 /usr/app/iwov/teamsite/httpd/iw-bin/HispanicFileCheck.cgi
16456 7 /export/home/astoller/IWHOME/httpd/iw-bin/HispanicFileCheck.cgi
log > ls -l $IWHOME/httpd/iw-bin/doed_cm_preview.cgi ~/IWHOME/httpd/iw-bin/doed_cm_preview.cgi
-rw-r--r--   1 astoller IAS         8443 Jan 25 18:37 /export/home/astoller/IWHOME/httpd/iw-bin/doed_cm_preview.cgi
-rwxr-xr-x   1 rcatabay staff       8443 Jan 25 18:37 /usr/app/iwov/teamsite/httpd/iw-bin/doed_cm_preview.cgi
log > grep "Files deployed" *RUN*
rcv.code_installRUN_0.IWHOME.xxxxxxxx.to.mylocalhost.logirectories deployed :    0      Files deployed :   29   Links deployed :    0
rcv.code_installRUN_1.IWHOME.xxxxxxxx.to.mylocalhost.logirectories deployed :    0      Files deployed :   29   Links deployed :    0
rcv.code_installRUN_2.IWHOME.xxxxxxxx.to.mylocalhost.logirectories deployed :    0      Files deployed :   29   Links deployed :    0
rcv.code_installRUN_3.IWHOME.xxxxxxxx.to.mylocalhost.logirectories deployed :    0      Files deployed :   29   Links deployed :    0
src.code_installRUN_0.IWHOME.xxxxxxxx.to.mylocalhost.logirectories deployed :    0      Files deployed :   29   Links deployed :    0
src.code_installRUN_1.IWHOME.xxxxxxxx.to.mylocalhost.logirectories deployed :    0      Files deployed :   29   Links deployed :    0
src.code_installRUN_2.IWHOME.xxxxxxxx.to.mylocalhost.logirectories deployed :    0      Files deployed :   29   Links deployed :    0
src.code_installRUN_3.IWHOME.xxxxxxxx.to.mylocalhost.logirectories deployed :    0      Files deployed :   29   Links deployed :    0

Having looked at the logs, I can tell you that three of the files being deployed are from/for a different directory - which means that 26 of the 32 files in the directory I showed above are constantly being deployed for, as far as I can tell, no reason.
The relevant portion of the deployment configuration file follows:<deploymentConfiguration>
...
<definition name="IWHOME">
<source>
<iwStore>
<remoteDiff area="/default/main/IWHOME/STAGING">
...
<pathSpecification>
<path name="./httpd/iw-bin"/>
<targetRules area="/usr/app/iwov/teamsite/httpd/iw-bin">
<filters>
<includePattern regex="/doed_"/>
</filters>
<permissionRules file="0755"
directory="0755"
user="rcatabay"
group="staff"/>
<transferRules doDeletes="yes"/>
</targetRules>
</pathSpecification>
...
</remoteDiff>
</iwStore>
</source>

<target>
<targetFilesystem area="***OVERRIDDEN***"/>
<comparisonRules ignoreModes="yes"
ignoreUser="yes"
ignoreGroup="yes"
dateDifferent="yes"/>
<permissionRules file="0644"
directory="0755"
user="rcatabay"
group="staff"/>
<transferRules doDeletes="no"/>
<replicationFarmLink>
<internal name="MYFARMNAME"/>
</replicationFarmLink>
</target>
</definition>
...
</deploymentConfiguration>

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Adam Stoller

No takers?
I haven't gotten a response from Support yet either ... sigh

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

13adam13

In reply to:

Having looked at the logs, I can tell you that three of the files being deployed are from/for a different directory - which means that 26 of the 32 files in the directory I showed above are constantly being deployed for, as far as I can tell, no reason.

can you provide a list of the files that are not being deployed each time. That might shed some more light on it.

--Adam Wilson
Senior Programmer

Adam Stoller

If you mean - do they have white-space or other non alphanumeric (including '-' and '_') characters in the paths or filenames - no - everything is named fairly straight forward, as can be seen in my previous post where: doed_cm_preview.cgi does not get deployed redundently, but HispanicFileCheck.cgi gets deployed every time.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

13adam13

Actually, I wanted to see what files were not being deployed, but based on the numbers, I would bet that the files not deployed are:
doed_cm_preview.cgi
doed_cm_verify_subnav.cgi
doed_co_browser.cg
doed_co_select_subnav.cgi
doed_select_office.cgi
doed_subnav_validator.cgi

those were ommitted because of your filter.

The only thing I can think of is that it appears that the system cannot read the directory that you are deploying to. Perhaps the perms on the folder itself are 644? This could, depending on who your ODReciever is running as, keep OD from reading the contents of the directory, and cause it to blindly write the files every time.

--Adam Wilson
Senior Programmer

Adam Stoller

...
those were ommitted because of your filter.

Hmm - well I had kind of forgotten about that filter - but the reason for it was that I only wanted files beginning with "doed_" to be considered for deletion - but apparently it has the adverse affect of saying that any other file will always be deployed -- does that make sense? Is there some other way (that I'm not currently seeing) to say:
deploy all files in this source directory, but only delete files in the target directory if they don't exist in the source area and [dont] match this pattern?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

13adam13

If your rcvr is running as root, then you can disregard this whole post.

Otherwise, I think that you took away from my post the wrong idea (at least, not the idea I meant, anyways). Looking at your configuration, I think you did everything right, to accomplish what you would have expected.

The only thing that I can think of that would result in your results, is if the rcvr cannot read the directory.

Imagine, if you will, that you are on a Unix box, as UserA. UserA does not have "search" rights on folder asdf.
When you do an ls -l asdf, the result is nothing. I think this is similar to what the RCVR is doing. Then, it compares that to the BASE directory tree, where an ls -l asdf results in a directory listing of all your files.
Then, the BASE compares nothing to the source tree and says, look, I need to send all of these files, except what matches the filter.
So, it sends all the files. Now, not being able to search a directory in Unix does not mean that you cannot write to it, so the BASE says rcp BASE:asdf/FileA RCVR:asdf/FileA.

It would do this everytime, because no matter how many times it puts the file there, when it does an ls on the dir, it sees nothing and thinks that it is not there.

--Adam Wilson
Senior Programmer

Adam Stoller

Here's my problem with the access theory - given the following:[NEW_PROD-TS] ~ > ll -d {$STG,$IWHOME}/httpd/iw-bin
dr-xr-xr-x 2 rcatabay staff 512 Jan 27 15:13 /default/main/IWHOME/STAGING/httpd/iw-bin
drwxrwxr-x 2 root daemon 3584 Jan 28 16:57 /usr/app/iwov/teamsite/httpd/iw-bin
[NEW_PROD-TS] ~ > ll {$STG,$IWHOME}/httpd/iw-bin/{edit_attributes.cgi,doed_cm_touch.cgi}
-r--r--r-- 1 astoller IAS 6323 Jan 25 18:37 /default/main/IWHOME/STAGING/httpd/iw-bin/edit_attributes.cgi
-rwxr-xr-x 1 rcatabay staff 6323 Jan 25 18:37 /usr/app/iwov/teamsite/httpd/iw-bin/edit_attributes.cgi
-r-xr-xr-x 1 astoller staff 2983 Jan 27 15:13 /default/main/IWHOME/STAGING/httpd/iw-bin/doed_cm_touch.cgi
-rwxr-xr-x 1 rcatabay staff 2983 Jan 27 15:13 /usr/app/iwov/teamsite/httpd/iw-bin/doed_cm_touch.cgi
[NEW_PROD-TS] ~ > id -a
uid=2072(astoller) gid=135(IAS) groups=135(IAS),10(staff)If I keep just the filter on the target side, edit_attributes.cgi gets deployed each time, while doed_cm_touch.cgi only gets deployed when actually modified on the source side.

File Access:

Directory Access:

By my way of thinking - it should either work consistantly or fail consistantly - and thus far, the absence of the inclusion filter on the source side is the "cause" of the alway-deploy problem --- except that it's not the solution I want as I mentioned in my previous post.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com