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

OD read-only issue

fbuno

Trying to do a deployment and got this error:

LIB: 2008-05-30 11:12:06 ERROR: MoveFile Failed while moving from (d:\web\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl.iwtmp) to (D:\web\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl), errno=5
LIB 00023: 2008-05-30 11:12:06 ERROR: Could not rename (d:\web\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl.iwtmp) to (D:\web\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl)
LIB 00017: 2008-05-30 11:12:06 ERROR: Could not get file data(.\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl) from socket.
LIB: (3) id=m8 2008-05-30 11:12:06 directive[reason src-is-newer]

The issue seems to be overwriting files with a read-only flag. Is there a way to configure the OD conf file to deploy over read-only files?

Find more posts tagged with

Comments

ISCBorisB

Trying to do a deployment and got this error:

LIB: 2008-05-30 11:12:06 ERROR: MoveFile Failed while moving from (d:\web\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl.iwtmp) to (D:\web\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl), errno=5
LIB 00023: 2008-05-30 11:12:06 ERROR: Could not rename (d:\web\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl.iwtmp) to (D:\web\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl)
LIB 00017: 2008-05-30 11:12:06 ERROR: Could not get file data(.\superstore\pages\Homepages\Inc\footers\E\usingFavourites.xsl) from socket.
LIB: (3) id=m8 2008-05-30 11:12:06 directive[reason src-is-newer]

The issue seems to be overwriting files with a read-only flag. Is there a way to configure the OD conf file to deploy over read-only files?

Transfer Rules, rmReadOnly="yes". Note that it's Windows-only setting

fbuno

Many thanks

Vijay_K

I am facing the same read-only issue, however its an Unix environment.
Is there a way to achieve the same In UNIX environment?

I am working on 7.1.0 version of Teamsite and OD.

Adam Stoller

I am facing the same read-only issue, however its an Unix environment.
Is there a way to achieve the same In UNIX environment?

I am working on 7.1.0 version of Teamsite and OD.

Are you running OD as root or non-root?
Are you getting errors in the logs? If so - please post the relevant information.

Vijay_K

OD is running as root on the server .

PFA the receiver log file that contains the error.

The files which could not be deleted have the 444 perm set to it.

Rick Poulin

You're wondering why you can't delete files you don't have write access to? Or are you wondering why the perm is set to 444 in the first place?

Since the former should be self-explanatory for anybody familiar with a unix platform, the latter can be fixed by using the <permissionRules> tag in your OD conf -- make sure to specify a appropriate u/g owners and a mask that allows write access to at least the owner. Obviously, your current perms mask will have to be rectified by root (or sudo) before you can delete those problem files.

Vijay_K

I would like to know why the permission is set to 444 even though I have given the permissionRules tag to set the permissions.

I have attached my deployment configuration file and the dnr script file that basically cuts an edition before deployment and after deployment and sets the appropriate groups on the deployed folders.

The dnr script is called before and after deploymnent also works as expected.But the deployment shows the status "Completed with Errors" because of this read-only issue.

Any pointers will be greatly appreciated.

Pawan

Can you please confirm if the directory permission, user and group are set correctly and it is only the file permission which is screwed up? Please check the submit.cfg file as well for any entry of the target workarea.

Vijay_K

Yes the folder permissions are set correctly.Its only the file permissions that is causing the issue.Also we have not configured anything in the submit.cfg file.