Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Date different missing recently submitted files ?
nipper
This has happened maybe 3-4 times in the last 6 months.
Normal deployments are scheduled. We also have an emergency deployment that takes submits the content and then kicks off an ipl to run iwodstart.
Ran this weekend, file submitted & deployemnt kicked off. However the newly submitted file was not deployed. No mention of the file at all in the OD log. I rechecked the source and destionation, no problems with going back (target was older).
So my guess is that OD started BEFORE the changes were reflected in the Staging area.
Is this a known problem ?
I am in the process of rewriting this to a file list deployment, even though that means we could deploy an untested config.
(A and B were changed & tested but only B was part of the file list)
If it is a known possibility, how long is a good time to wait ? If the file is not reflected in Staging at iwodstart time, could a file list have the same problem ?
Andy
Find more posts tagged with
Comments
gwen1
Are you on Solaris? If so, we had that problem as well... needed to deploy from /.iwmnt instead of /iwmnt. There were several articles regarding this problem on the support site. This does though add to the time deployments take, so may not be an option if you are comparing files.
nipper
thanks Gwen, I forgot about the caching mount point that is probably it. I will check out the support site.
Andy
Migrateduser
Please take a look at p. 24 in the OD 5.6 Release Notes (Nov 2003 edition). There you'll find the latest write-up on limitations when using varous TeamSite path prefixes.
Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
cc preview.png
Adam Stoller
We just got bit by this at our project with a custom CGI that performs deletions and then deployments.
IMO - iwsubmit should be provided another flag option - which basically says "do not return status until the changes have been migrated to the caching mount-point"
In lieu of that, while deploying from /.iwmnt worked for our OpenDeploy deployment, it seemed to break our DataDeploy DNR. We didn't have time to investigate in depth, so we went with a poor-man's solution: Wrote a loop within the CGI that checks to make sure all the files that should have been removed from staging are in fact gone from /default/.../STAGING before it kicks off the deployment. Not elegant, but functional.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com