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 Error 28?

djo2112

This is OD 6.2 Admin running on an IIS W2K3 server with an OD 6.1 receiver running on an IIS W2K3 server.
The pertinent OD log info is below:

SRC:
LIB: (3) 2009-07-07 09:43:48 Received 'get' request for (.\html\glossary\actualremaininghours.html)
LIB: 2009-07-07 09:43:48 Receiver-ERROR: ERROR: DoCopying() failed, check target log.

RCV:
LIB: (3) id=m373 2009-07-07 09:43:47 directive[get .\html\glossary\actualremaininghours.html]
LIB: id=m373 2009-07-07 09:43:47 Receiving item(.\html\glossary\actualremaininghours.html)
LIB: (3) id=m373 2009-07-07 09:43:47 dir for tempfile [e:\rushmore\ownersweb-web\smp\cms\sitehelp\html.iwnew\glossary]
LIB: (3) id=m373 2009-07-07 09:43:47 -- Processing file(e:\rushmore\ownersweb-web\smp\cms\sitehelp\html.iwnew\glossary\actualremaininghours.html)
LIB: (3) id=m373 2009-07-07 09:43:47 file created[e:\rushmore\ownersweb-web\smp\cms\sitehelp\html.iwnew\glossary\actualremaininghours.html.iwtmp]
LIB: 2009-07-07 09:43:47 00028LIB 00017: 2009-07-07 09:43:47 ERROR: Could not get file data(.\html\glossary\actualremaininghours.html) from socket.
LIB: 2009-07-07 09:43:47 ERROR: DoCopying() failed, check target log.

The deployment works up until this folder (\html\glossary) is encountered. I am making the assumption that the error number is 28. If I did proper research, error 28 is out of disk space. The web server has gigs of space so I discounted that as the root issue. I checked the permissions on the folder and sub-folder structure to make sure there weren't Windows permission issues there. As an extra added debug, I deleted the entire \html folder on the web server and received the same error in the same place. I have the following in the deployment filter set:
[html]

[/html]
There are other subfolders for this website with similar scripts so I'm confident that I'm not doing anything exotic.

Does anyone have any additional debug direction they can point me in?
Thanks.

-Oz

Find more posts tagged with

Comments

CRB

This is OD 6.2 Admin running on an IIS W2K3 server with an OD 6.1 receiver running on an IIS W2K3 server.

LIB: 2009-07-07 09:43:47 ERROR: DoCopying() failed, check target log.

The deployment works up until this folder (\html\glossary) is encountered. I am making the assumption that the error number is 28. If I did proper research, error 28 is out of disk space. The web server has gigs of space so I discounted that as the root issue. I checked the permissions on the folder and sub-folder structure to make sure there weren't Windows permission issues there. As an extra added debug, I deleted the entire \html folder on the web server and received the same error in the same place. I have the following in the deployment filter set:

-Oz

this is most likely a disk space issue on target, opendeploy needs 2 to 3 times the size of the deployment it is handling. so if your deployment updates the entire site, then you will need 2 to 3 times the size of your site as available disk space. also check if there is enough disk space for the logs.

sniv

Hey...

Yes major Possible causes for this issue is less space on receiver side.

It looks like destination(receiver) volume did not have enough temp space for a deployment

Also some more possible causes for this issue:

1) This is the error where it cannot write to the destination.
A transactional deployment required 3x the content size being deployed.

2)File is corrupted, Try deleting the file on the base and deploy again.

3) Permissions issue at minimum, read permissions are required. If file is read-only on receiver, use rmReadOnly=”yes” attribute in target rules in the deployment configuration.

Also check if any cron job is interfere with OD deployments. If yes Once try disabling that cron job.

Regards!
Vinayak

djo2112

Chris & Vinayak,

These are all excellent suggestions!

Again, I am not considering disk space an issue as I have a deployment content size of 9MB and 56GB of available space. It is a transactional deployment and we're in the 3x size spec.

The rmReadOnly flag is correctly set for Windows (Yes) in the depoyment configuration.

In my original post, I noted that I deleted the entire content folder on the web server and redeployed with no luck. I too assumed it was some type of corruption.

I am interperting the issue is on the sender because according to the log the get request is received.

Back to the drawing board and thank you for the suggestions!

-Oz

CRB

this might not be related but it would be worth it to check if you have anti-virus or some kinda of process that is running and might take the lock of a file while your deployment is running?

i remember having similar issue, but we ended up rebuilding the server before we determining a root cause.

djo2112

We use Trend-Micro stuff but apparently the DMZ web box is taking these changes while this non-DMZ box is not taking the changes. This is a fan-out deployment to 2 servers.

This is the old: "This has been working for a long time and we don't know what changed" scenario.

Needle in a hay stack, it is. :-)

-Oz

djo2112

I wanted to make sure I followed up on this issue in case anyone else encountered. I solved it by changing the

preserveAcls="no"

attribute in the transfer file rules. I was confident it wasn't a disk space issue.

I'm not exactly sure why this flag was checked to begin with however, it has been there for quite some time. Also, all of my other configuration scripts (13) for this web site had a similar setting and worked.

Hope this helps!

-Oz