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 Crashes ?

sahu

OD 6.2
Windows 2k3

We are deploying content to around 200 receivers but most of the time it crashes.

How can i improve this

-any windows Vitual memory changes require ?
-OD conf file modification require ?
-OD upgrade ?

Experts what is the best way to resovle this ?

Find more posts tagged with

Comments

Bhargav Coca

OD 6.2
Windows 2k3

We are deploying content to around 200 receivers but most of the time it crashes.

How can i improve this

-any windows Vitual memory changes require ?
-OD conf file modification require ?
-OD upgrade ?

Experts what is the best way to resovle this ?

What kind of deployment are you doing? i.e. Comparing filesystems or compring tamsite areas or filelist based. You might want to post your config file.

What does the log file says when it fails?

Thanks

sahu

We are using Comparing filesystems and OD restarted automatically when it fails

Adam Stoller

Do you have sufficient disk space and RAM on all the Receivers (and the Base Server)?

Are the OpenDeploy log files rotating correctly (there used to be a problem on Windows when one of the log files grew to 5 GB (or was it only MB?) but I don't recall the details right now. However, make sure all the log files within ODHOME/log/ appear to be properly rotating after reaching whatever is set as the max size - if you see any log files that don't appear to be rotating, and which have reached around 5 GB/MB - stop the OD service, rename the log file, and the restart the OD service and see if that fixes things [for a while]

nipper

I think the log issue was 2GB, not 5 GB.

Also are you doing any fanout deployments or just straight to 200 servers ? The latter is just plain stupid, especially for a compare filesystem deployment.

Consider buying more senders and doing fanouts, as well as changing to a filelist deployment.

sahu

Log files are properly rotating, i can say it is not log file related issue.

We are just doing straight to 200 servers deployment.

2017-03-24 09_10_07-OS BIRT - VMware Workstation.png

2017-03-24 09_08_37-OS BIRT - VMware Workstation.png

2017-03-24 09_10_47-OS BIRT - VMware Workstation.png

2017-03-24 09_11_25-OS BIRT - VMware Workstation.png

Adam Stoller

Log files are properly rotating, i can say it is not log file related issue.

We are just doing straight to 200 servers deployment.

Is this a single fan-out from one base server to 200 receivers?
Are all the receivers on the same LAN and/or WAN? (if not, you might want to consider routed or tiered deployments)
Have you verified the disk space and memory (on both base and receiver) and inodes on the base server (200 deployment fan-out uses 400+ inodes for the log files)

Bhargav Coca

There is no way that you gonna debug this keeping 200 servers in one deployment. i strongly suggest to break it down like 100 each and try it. If there are any network issues you will understand them better.

As guys here suggested, change your deployment to filebased and see deployment for 100 servers to begin with then Increment it by 50 and see that it doesn't choke again.

Did you talk to support, see what they say.

Thanks