Mark Black wrote:
Hi Maurice
To recap your email:
1. The package.lst has the correct entries
2. You saw "No route to host messages"
3. You saw "Erased: Packagename" messages in some log file
4. When running cfmsync -u the log shows the repo IP missing
For item 1:
Check the contents of /depot/repos/1001
It must contain all the rpm's listed in the package.lst.
It does.
On the nodes truncate the /opt/kusu/etc/package.lst file
e.g. # cat /dev/null > /opt/kusu/etc/package.lst
Then run cfmsync -p
That should trigger a retry of the package install.
We will try that. In other words just make the package.lst file an empty
file?
For item 2:
For the no route to host messages, I'm not sure why you are seeing this.
Is there anything unusual in the web servers access_log, or error_log.
We will check. I am not sure what would be "unusual".
Should we just post the contents of those 2 files in response?
For item 3:
If this is the yum.log, this can happen if you have the components
selected in ngedit, but the repo does not have them.
Ngedit will mark then for removal, because the repository did not
contain them, and the next time cfmsync -p is run the packages will be
removed.
It's important to run "repoman -u -r ..." before ngedit.
OK, can do. Will try again.
Is the logging level we are providing sufficient?
4. We logged this one a while ago, but have not had time to look at
it. It's slated to be addressed before the final release.
How could yum work if it does not get a repo path?
--
With our best regards,
//Maurice W. Hilarius Telephone: 01-780-456-9771/
/Hard Data Ltd. /
/11060 - 166 Avenue/
/Edmonton, AB, Canada /
/ T5X 1Y3/
/
_______________________________________________
Kusu-users mailing list
[email protected]
http://mail.osgdc.org/mailman/listinfo/kusu-users
