On 03/23/11 12:23 PM, David Giroux wrote:
Hello,
I'm setting up a local repository origin from the repository ISO images
from the Solaris 11 Express download URL on OTN.
The local repository build went smoothly (no errors indicated). My
clients can search for package, they see package info fine.
But I noticed that quite a few on the IPS packages have "Invalid content
path- chash failure" errors when I try to do installs.
When I configure the AI service, I noticed that when my AI clients try
to load the entire/babel_install package groups they start spitting out
the same "Invalid content path- chash failure" errors and the AI install
aborts.
Does anyone have any experience with this problem? How do I fix it?
Here are the commands I used to build the local repository and AI
service. The AI default manifest (demo_manifest.xml) and an AI failure
message snapshot are attached.
The errors you're seeing would indicate to me one of a few possible
failures:
* the storage device for the repository is faulty and is providing
corrupted data to clients
* there's a severe network data corruption issue
* there's some other hardware failure on either the client or the server
causing this problem
Have you tried this install process on other clients using the same
repository server?
Have you tried using NFS access instead of HTTP access to the repository
in question?
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
