On Thu, Feb 04, 2016 at 02:52:40PM -0800, CLOSE Dave wrote: > The subject message sometimes appears on the installation source entry > from anaconda. But I have never been able to find a good way to learn > just what the error is. Sure, sometimes it's obvious: the URL is wrong. > But other times everything seems to be correct but still the error > persists. I'm looking for a checklist of possible causes or a log entry > that corresponds to the problem. > > In my present effort, I'm attempting to use a local mirror of the > fedora-updates repository (in addition to local mirrors of the fedora > and other repositories). I believe the mirror is correct and complete. > The machine being installed has no trouble accessing the repo from an F2 > shell while anaconda is running. Looking through the anaconda logs, I > find lots of references to the updates repository but no errors. > > What can cause this error message? And how do I find out what caused it > in this instance? The first place to start is with the packaging.log in /tmp/, but it can be hard to track down since there are so many different things that could cause connection problems. You're serving your own repo in this case, how are you doing that? dnf/rpm need the repository server to support partial file requests in order for it to work. Apache, lighttpd, nginx all work fine for this but simpler servers (eg. the python SimpleHTTPServer) don't and would result in cmdline use of wget working but actual installation failing. -- Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT) _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
