Common Error Messages

Common Error Messages, Alphabetically Listed

"Add profile was selected without selecting what distro to use. Add --cobbler-use-distro or --cobbler-from-distro."

You specified to add a profile to cobbler, but without specifying a distro to add the profile to. As you may know, Cobbler distro's may have profiles, and profiles always have a distro.

"anaconda-runtime not installed; not setting up mediacheck"

Anaconda-runtime is not installed on the host system. Although very unlikely if you're just using yum to manage all packages, this could happen. Install anaconda-runtime with:

# yum -y install anaconda-runtime

"An error occured extracting the release files: %s"

As the message says, the release files could not be copied. The rest of the error message (where the %s is now), should be pretty indicative as to where the actual error is. If you get this error, let us know and we'll tell you what you need to do to solve it, and describe it here or work around it in Revisor.

"A network device with the name %s already exists.  Please choose another device name"

"Another application is running which is accessing software information."

"Bind-mounting '%s' to '%s' failed"

A bind mount is used to mount certain filesystems and directories in the livecd tree while it's building. Maybe the directory on which we want to bind mount doesn't exist. %s has more details

"Cannot access %s, please check the permissions so we can try again."

"Cannot find anaconda-runtime in /usr/lib/anaconda-runtime"

"Cannot fork process showing help, please use %s%s"

"Cannot setup installation target. Aborting."

"Cannot show Help in CLI mode, use %s%s"

"Configuration file '%s', section '%s' does not have the mandatory 'main' option"

"copy_dir '%s' not accessible"

"Copy of %s failed: %s"

"Could not handle the kickstart data or something... Log a bug"

"Could not read configuration file %s"

"Delta image creation specified, but no delta module found. Install revisor-delta."

"Did not succeed in adding in all required packages"

"Directory %s could not be created. Aborting"

"Error: Cannot create destination dir %s"

"Error: Cannot recreate destination dir %s"

"Error: Cannot remove destination dir %s"

"Error creating ext3 filesystem"

"Error downloading packages"

"Error encountered during installation of the software you selected:"

"Errors were encountered while downloading packages: %s"

"Errors where encountered while downloading package headers:"

"Failed create build directory in /var/tmp: %s"

"Failed to allocate loop device for '%s'"

"Failed to build transaction : %s"

"Failed to execute %%post script with '%s' : %s"

"Failed to find group '%s' : %s"

"Failed to find loop device associated with '%s' from '/sbin/losetup -a'"

"Failed to find package '%s' : %s"

"Failed to loopback mount squashfs.img from '%s' : %s"

"Failed to loopback mount '%s' : %s"

"Failed to mount '%s' to '%s'"

"Failed to parse kickstart file '%s' : %s"

"Failed to read kickstart file '%s' : %s"

"File %s is not accessible."

"Invalid model. Please choose a valid model."

"Invalid model %s, configuration file %s not readable"

"Invalid model %s, no configuration file %s"

"Invalid model specified: %s does not exist in %s"

"Kickstart file %s fails to load"

"Kickstart file %s fails to load, continuing with defaults"

"Kickstart file %s not accessible."

"No --device specified with network kickstart command"

"No installation media type selected, select at least one type of installation media."

"No IP address and/or netmask specified with static "

"No kernels installed: /lib/modules is empty"

"No kickstart file specified"

"No live media type selected, select at least one type of live media."

"No media selected. Please select at least one media type to compose."

"No media specified"

"No media types selected, select at least one media type."

"No model specified."

"No Package Matching (...)"

You get a message saying there is no package matching <name-of-package>, but it isn't fatal. This is caused by selecting a package for inclusion in the transaction, while it is not in the list of available packages. Some of the packages you select are actually selected by group (in kickstart you could have configured @gnome-desktop in the package manifest, for example), and using comps.xml from the repositories loaded, this group stands for certain packages; regardless of these packages being available in the repositories.

"No package named %s available to be installed: %s"

"No packages or groups specified"

"No repositories specified"

"No such package %s from group %s"

"No such package %s to remove"

"Not building delta for %s of type %s"

"Not creating a DVD ISO Image, Installation Media fits on a CD"

You may have selected to create a CD as well as a DVD, but as the installation media fits on a single CD, there is no need to also create a DVD.

"No utility media type selected, select at least one type of utility media."

"No virtualization media type selected, select at least one type of virtualization media."

"Package hard link failed, trying symlink for: %s"

"Package link failed: %s: %s"

"Package %s not added because we don't like it being added"

"Package %s not excluded because we don't like it being excluded"

"Package %s not included because we don't like it being included"

"Package %s was not marked in group %s"

"Please select a root password."

"Revisor Cobbler plugin options specified, but no cobbler module was found. Install revisor-cobbler."

"Root passwords do not match."

"'%s' is not a valid live CD ISO : os.img doesn't exist"

"'%s' is not a valid live CD ISO : squashfs.img doesn't exist"

"%s is not a valid Revisor configuration file"

"Specifying a Cobbler server is only supported for read-only actions. Currently, --cobbler-use-distro and --cobbler-use-profile."

"%s%s%s is a mount, trying to unmount"

"%s%s%s is not a mount"

"%s. This is a required package."

"The configured model does not have the mandatory 'main' configuration directive."

"The directories Revisor uses in %s already exist. This could possibly hold data from a previous run. Please remove or move them to a safe location. Then confirm to continue. If you do not move or remove the files, Revisor will simply delete them"

"The distro '%s' does not exist."

"The 'main' option configuration directive has a non-accessible file: "

"The profile '%s' does not exist."

"These passwords do not match"

"The updates.img %s is not accessible."

"This tool has to run with root privileges. Aborting"

"To be able to create a delta, you need to generate a new ISO image. Add --cd, --dvd or --unified."

"Unable to build transaction"

"Unable to find a suitable mirror."

"Unable to open %s: %s"

"Unable to resolve dependencies for some packages selected:"

"Unable to retrieve software information. This could be caused by not having a network connection available."

This is actually a bogus message; It doesn't really concern network connectivity although it is one of the most frequently occuring causes of not being able to load the repository metadata. Other causes of not being able to load the repository metadata are:

• The revisor configuration file you are using in /etc/revisor/conf.d has variables that are not expanded: $releasever, $basearch, $arch amongst others.
• The specified URL (baseurl or mirrorlist) cannot be reached (proxy? typo?) or, in case of a mirrorlist, returns an empty list.

Troubleshooting:

You can use the revisor configuration file with yum by running just:

$ yum -c /etc/revisor/conf.d/path/to/conf

and to increase verbosity, use:

$ yum -d 9 -c /etc/revisor/conf.d/path/to/conf

"Unable to unmount %s%s%s with error: Please resolve the issue and continue."

"Unable to unmount %s%s with error: Please resolve the issue and continue."

"Unresolvable dependency %s %s %s in %s.%s"

Updates.img is only usable with installation media. Please remove --updates-img or also build installation media."

"You have not selected any of the basic repositories. Please make sure that one of 'fedora', 'core', 'base' or 'development', or an equivalent repository has been configured"

"You may be using an old configuration file, since there is a 'pungi' configuration directive in %s"

"You should really select a more complex root password."

"yum.YumBase.doConfigSetup failed, probably an invalid configuration file %s"