OD slow - files modified by root in GUI

One of our branches is having problems doing deployments. It is taking about 5 times longer than it used to. Previous to this problem, some of the site content was deleted and we recreated the site from the most recent edition. Now in the TeamSite GUI, in the workare it is showing all files as still being edited and all files show modified by root instead of the owner of the workarea. Also have been getting some lstat errors during deploy. Any ideas on why the deploy is taking so long and what can we do to resolve it?

Find more posts tagged with

Comments

Migrateduser

most likely the issue is in TeamSite and not OD. If you are doing a directory comparison deployment based on date modified then the fact that you say that all files are being listed as modified by "root" would cause OD to believe that it needs to transfer all of the files from the source and overwrite the target files (which will take longer than just transfering the files that have really changed).

Usually when you see that every file in the source is listed as modified it means that someone either touched all files in their workarea and submitted or there may have been some software/script that changed the modification time on the files (some backup software has been known to do this and gnu tar will do this if you do not tell it to do otherwise).

lamock

Any suggestions to resolving this beyond manually going into each of the 4000+ files and re-saving so the permissions are correct? Any help is greatly appreciated!!

Adam Stoller

Make sure you have a well configured submit.cfg file.
Submit all the files that appear modified
Do a deployment (this will take time if there were a lot of files)
Do another deployment after the first one (this should be relatively quick as no files should get deployed).

If the second deployment is still deploying files, then you will probably have to post (as an attachment) the deployment config file and potentially some of the log files.

Also - are you really deploying from the workarea? or are you deploying from staging or an edition?

However, If the files in the workarea continue to mysteriously (?) show up as modified - then you need to determine what is causing that to occur.

--fish
(Interwoven Senior Technical Consultant)