Random policy error....

[jmercier]

Situation....

we have 11 mac labs... 21 mac each labs...
2 of those labs are brand new imac with Fusion drive

we have 1 policy very simple running at startup and than another one also on startup to delete and reinstall printer queue.

randomly, every morning at 7 when all computers boot up at the same time, i have between 2 and 7 computers that have this error : Error: Could not mount a distribution point. : on my printer policy only...

What is weird, it's only with my fusion imac i have those errors... never on the other standard iMac...

The errors comes random, on those 2 labs with fusion, not always same machine... but always on the same policies... but the policy works in all other labs...

[tomt]

Could you stagger the start up times of each lab by a few minutes? Maybe the server connection is being overloaded.

[donmontalvo]

We're seeing this in our environment too, doesn't seem to be consistent. JSS is on Xserve, 8.64 with mix of 10.6/7/8 Macs, DPs are on NAS. Mounts fine in Finder, but not consistenty through Casper.

Error: Could not mount a distribution point.

We are migrating from a single Xserve to a multi-tiered, clustered, load balanced environment, so hopefully this issue won't follow us during migration.

Don

[CGundersen]

Ditto on this error ... we've been receiving it for a while. We have been getting the error while on 8.6x and continue to with 8.71. Our prod environment is not optimally setup (JSS not under load balancer yet), but we do have 10 distro points (XServes/10.7.5/AFP) in our data center to spread the load. I can consistently mount any given distro point at time of error with ease. Hopefully my request for additional resources (physical hardware for distros and vm's for JSS instances) will be approved and any resource questions/issues with be answered then.

[ctangora]

Can you call the policy with the verbose tag?

We see this error occasionally, but the policy would continue and run fine. Turns out that two policies were running at the same time, so the distribution point wasn't re-mounted. The error is true, it didn't mount the drive, but it could have been better stated that it already was mounted.

Your mileage may vary, but the verbose tag helped us figure out what our issue was. May help with yours.