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

DD 6.1 /.iwmnt bug

Bill Klish

OpenDeploy 6.1
Solaris 2.9

We just installed 6.1 and I was doing some testing on a legacy deployment script that works in OD 6.0.2. The script has a definition which uses the dbLoader capability. The deployment returns success, and no errors were found in the logs, however, the database deployment never occurred, nor is there any trace of it in the log files (src or rcv).

Upon further inspection, I noticed the following in the src..log file:

ENG: 2006-07-27 17:15:40 CDT GMT-05:00 Prefix /.iwmnt not permitted in src area path /.iwmnt/default/main/branch1/WORKAREA/en_US. Use /iwmnt instead.

After making this change, the database deployment suddenly activated.

It would be helpful to return this as an error in the log and a failure for the opendeploy process. Otherwise, you may spend time trying to figure out what is wrong.

Find more posts tagged with

Comments

jed

OpenDeploy 6.1
Solaris 2.9

We just installed 6.1 and I was doing some testing on a legacy deployment script that works in OD 6.0.2. The script has a definition which uses the dbLoader capability. The deployment returns success, and no errors were found in the logs, however, the database deployment never occurred, nor is there any trace of it in the log files (src or rcv).

Upon further inspection, I noticed the following in the src..log file:

ENG: 2006-07-27 17:15:40 CDT GMT-05:00 Prefix /.iwmnt not permitted in src area path /.iwmnt/default/main/branch1/WORKAREA/en_US. Use /iwmnt instead.

After making this change, the database deployment suddenly activated.

It would be helpful to return this as an error in the log and a failure for the opendeploy process. Otherwise, you may spend time trying to figure out what is wrong.

Yikes! I guess I will not be upgrading any time soon.

When dbLoader first came out, the lack of /.iwmnt support was a bug which was fixed in a subsequent patch/sp release. When we first transitioned to db loader, we were forced to use "/iwmnt" which caused caching issues and failed/invalid deployments during content creates/deletes. The original bug was #59330. Maybe the cacheing issues are resolved? If not, a sleep statement will be your best friend Smiley Happy

If you do use /iwmnt, watch out for this in your log file:

LIB: 2005-02-28 13:57:27 Sending [./servers/highend/e10000/images/foo.jpg] [reason file_list] LIB: 2005-02-28 13:57:27
ERROR: Could not open file (/default/main/www.sun.com/web_site/en/servers/STAGING/servers/highend/e10000/images/foo.jpg) to send over.
LIB: 2005-02-28 13:57:27 ERROR: File(/default/main/www.sun.com/web_site/en/servers/STAGING/servers/highend/e10000/images/foo.jpg) failure: bytes-read=0 bytes-expected=0.
LIB: 2005-02-28 13:57:27 ERROR:

Bill Klish

Haven't seen that issue yet, but I will let you know if I do. I suppose I should open a support case and reference your bug that appears to have not made it into the 6.1 code line.

jed

Haven't seen that issue yet, but I will let you know if I do. I suppose I should open a support case and reference your bug that appears to have not made it into the 6.1 code line.

Any update on this? Is it a bug or a "feature" Smiley Happy

Bill Klish

I have been absolutely swamped. It's on my list for next week, along with real-update not working Smiley Happy

jed

I just upgraded a dev server to 6.1 and spent a few hours tracing down why DD's were not working. It appears the /.iwmnt issue is still present. Time to file a bug Smiley Sad

Migrateduser

I just upgraded a dev server to 6.1 and spent a few hours tracing down why DD's were not working. It appears the /.iwmnt issue is still present. Time to file a bug

anyone know if this is still an issue (or have a workaround).. I am using Version 6.1.1.0.0 Build 68182 Interwoven 20070917 with all the patches and seem to be having the same issues with datadeploy described here. I tried /.iwmnt but its ignored as described above.

I either get this:

--------------------
LIB: (3) id=m1475 2007-12-17 21:50:09 -- Processing file(/opt/OpenDeployNG/tmp/website/publish/templatedata/category/content
/data/menu_applications/applications_landing_page_513682_513681_eng.base)
LIB: (3) id=m1475 2007-12-17 21:50:09 file created[/opt/OpenDeployNG/tmp/website/publish/templatedata/category/content/data/
menu_applications/applications_landing_page_513682_513681_eng.base.iwtmp]
LIB: 2007-12-17 21:50:09 ERROR: Failed transferring contents of (./templatedata/category/content/data/menu_applications/appl
ications_landing_page_513682_513681_eng.base)
LIB 00017: 2007-12-17 21:50:09 ERROR: Could not get file data(templatedata/category/content/data/menu_applications/applicati
ons_landing_page_513682_513681_eng.base).
LIB: 2007-12-17 21:50:09 ERROR: deploy-failed.
LIB: 2007-12-17 21:50:09 ERROR: Failed deploying filelist[0]
LIB: 2007-12-17 21:50:09 ERROR: Failed 1 of 1 filelists

---------------------------------

-- OR when trying to deploy a delete

--------

ERROR: Could not open file (/default/main/production/STAGING/templatedata/category/content/data/menu_applications/application
s_landing_page_513682_513681_eng.base) to send over.
LIB 00032: 2007-12-17 21:50:09 ERROR: File(/default/main/production/STAGING/templatedata/category/content/data/menu_applicat
ions/applications_landing_page_513682_513681_eng.base) failure: bytes-read=0 bytes-expected=0.

----------------------------

If I hit retry, it usually goes thru..

any thoughts?

jed

anyone know if this is still an issue (or have a workaround).. I am using Version 6.1.1.0.0 Build 68182 Interwoven 20070917 with all the patches and seem to be having the same issues with datadeploy described here. I tried /.iwmnt but its ignored as described above.

No fix yet Smiley Sad

I have an open case regarding this issue and:
"Our engineering confirmed this to be a regression bug and they are working on the fix. We currently are targeting to have the fix in OD6.2.0 which is projected in Q3/Q4."

Looks like they will miss that date.

I do not have the corresponding bug number, but my active case # for this issue is: 00716124 Referencing that might save you some time.

nipper

Are you sure ? Bug 61363 is listed as fixed in the OD 6.2 release which is out.

Migrateduser

Are you sure ? Bug 61363 is listed as fixed in the OD 6.2 release which is out.

where do you see it listed as fixed? I am looking thru the 6.2 release notes now and only see 1 bug listed as resolved (and it has nothing to do with this issue)

nipper

where do you see it listed as fixed? I am looking thru the 6.2 release notes now and only see 1 bug listed as resolved (and it has nothing to do with this issue)

I just did. trust me. Smiley Wink

Migrateduser

I just did. trust me.

I must be slow today (and most days).. you mean like you tried it an it works now? or you see it documented somewhere.. cause if its documented, I can suggest to my client to do the upgrade from 6.1.1 to 6.2.0

jed

Are you sure ? Bug 61363 is listed as fixed in the OD 6.2 release which is out.

Whoops! I did not notice 6.2 was out.