Ok tried that and that didn't seem to cause it to build/rebuild /var/rhn/cache/repodata/* It searched for cache in the /var/log/rhn/rhn_taskomatic_daemon.log and didn't see much, so not sure if more debug logging I can do ? Is there a command that will rebuild the cache that I could try running manually? So as it stands right now, the packages show up in the channel via the web, and on the system, and from the web I can download them, but when I try and yum install them on the system it gets a 404 not found error.
Dan On May 11, 2010, at 5:17 AM, James Hogarth wrote: >> >> No, spacewalk-repo-sync pushes packages directly to database nad >> filesystem (thus must be run on spacewalk server locally) while rhnpush >> uses XMLRPC API and can be run from another box. >> > > Ah so that could be a useful debug step for him... > > If rhnpush uploads the packages and the repo metadata generation gets > triggered then there is an issue with spacealk-repo-sync specifically > for him but if the packages load and the metadata still doesn't get > generated looks more like an oracle/taskomatic possible issue. > > Thanks for that - filed away in that cobwebbed mind of mine for > debugging uses if I have problems here in the future ;) > > James > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
