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

Opendeploy not overwritting

System

Hi,

I have a problem with opendeploy not overwritting existing file on our opendeploy receiver.
Some of the files will get a extension iwtmp behind.
Example
======
I deploy "helloworld.xml"(already exist in receiver) into my receiver but over at my receiver end i get "helloworld.xml.iwtmp" ..it is not overwritting ..This looks to me like a tmp file creating by opendeploy..I dun get a ny error deploying.Only notice this when we browse through the physical path.
What could be the problem?

Thank You

Find more posts tagged with

Comments

Adam Stoller

Hi,

I have a problem with opendeploy not overwritting existing file on our opendeploy receiver.
Some of the files will get a extension iwtmp behind.
Example
======
I deploy "helloworld.xml"(already exist in receiver) into my receiver but over at my receiver end i get "helloworld.xml.iwtmp" ..it is not overwritting ..This looks to me like a tmp file creating by opendeploy..I dun get a ny error deploying.Only notice this when we browse through the physical path.
What could be the problem?

Thank You

Please provide more detail:

There may be more - but the above are good for a start.

Migrateduser

Fish's questions are a good start but the very first thing I might check is to see if the files being overwritten can be done so by whomever owns the OD process on the receiver (probably root or Administrator but some folks have it set up differently).

Migrateduser

Fish's questions are a good start but the very first thing I might check is to see if the files being overwritten can be done so by whomever owns the OD process on the receiver (probably root or Administrator but some folks have it set up differently).

I notice after i restarted the system(receiver)..the problem is solve temporary .....

Migrateduser

[QUOTE=ghoti]Please provide more detail:

Is there any information in the log files to indicate why it's failing?ans:I have attach the log with the error message in the last 3 line,i couldnt understand the error message.Thank You

13adam13

Perhaps you are having problems with the readonly flag that can be set on a windows system.

Are either of the files indicated here being marked readonly on the target machine?
c:\interwoven\opendeployng\tmp\internet\Systemtaxonomy\relation-taxonomy.xml
c:\interwoven\opendeployng\tmp\internet\Systemtaxonomy\relation-taxonomy.xml.iwtmp

Migrateduser

Perhaps you are having problems with the readonly flag that can be set on a windows system.

Are either of the files indicated here being marked readonly on the target machine?
c:\interwoven\opendeployng\tmp\internet\Systemtaxonomy\relation-taxonomy.xml
c:\interwoven\opendeployng\tmp\internet\Systemtaxonomy\relation-taxonomy.xml.iwtmp

======================================================
None of the files is being marked as read only .The weird thing is this problem is temporary solved when i restart the receiver,and delete away the *iwtmp file and re deploy again..But it will come back again in a day or two.Is this a Bug, cause i am also experiencing this problem on our live server(which is a receiver).

Adam Stoller

[QUOTE=Leoh]

Given that OD is one of the easier programs to install - I'd suggest having the Receiver un-installed and then re-installed by someone logged in as "Administrator" - and then see if the problem persists.

Migrateduser

[QUOTE=ghoti]With respect to the third question I'd recommend that you spend a bit more time reading the manuals that come with OpenDeploy / EasyDeploy and search for the term "transactional" - however, I guess I'll assume that the answer is "no".

With respect to the last question, looking at the excerpt of the logfile you posted, it shows that at least two files (20060719105336.aspx, relation-contenttype) were processed in the same directory (c:\interwoven\opendeployng\tmp\internet\Systemtaxonomy\) without any problem - and it was only the third file (relation-taxonomy.xml) in that directory that ran into problems.

At least in the log you posted, it appears that the temporary file for the third file to be deployed already existed when the deployment began, and that for some reason OD was unable to remove it or overwrite it, which caused OD to error our (understandably).

Errno 13 is generally defined as EACCES / Permission Denied - which brings up the questions of:

sorry,is "iwodnonroot" a service name?I installed opendeploy using administrator,i have the same problem with another receiver.....

Adam Stoller

sorry,is "iwodnonroot" a service name?
I installed opendeploy using administrator,i have the same problem with another receiver.....

iwodnonroot is a utility you can run after having installed OD as root (or Administrator) that causes the server process to be run as the specified user rather than root (or Administrator) and when run in this mode puts additional constraints on what can be specified in the deployment configuration file (e.g. you cannot explicitly set ownership on deployed files and directories other than for the non-root user / group using a specified directive - read the manuals for more information).

Given that you haven't done this, and that you did install OD (on both sides?) as Administrator then the remaining probabilities are that the file is somehow being held locked / readonly on the receiver - usually by some (other) process that runs on the receiver. There are several deployment configuration options one can use to try to deal with this:

Read the manuals for more information about these settings, and hopefully one (or more) of them will help you get rid of the problem.

Migrateduser

[QUOTE=ghoti]iwodnonroot is a utility you can run after having installed OD as root (or Administrator) that causes the server process to be run as the specified user rather than root (or Administrator) and when run in this mode puts additional constraints on what can be specified in the deployment configuration file (e.g. you cannot explicitly set ownership on deployed files and directories other than for the non-root user / group using a specified directive - read the manuals for more information).

Given that you haven't done this, and that you did install OD (on both sides?) as Administrator then the remaining probabilities are that the file is somehow being held locked / readonly on the receiver - usually by some (other) process that runs on the receiver. There are several deployment configuration options one can use to try to deal with this:

we will try it out ,thanks

studentsummary.rptdesign

s1.xml