Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 587772 Details for
Bug 826634
Install continues even though rpmdb gets corrupted
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
File: anaconda-tb-3_2T7_
anaconda-tb-3_2T7_ (text/plain), 951.79 KB, created by
John Dennis
on 2012-05-30 16:17:59 UTC
(
hide
)
Description:
File: anaconda-tb-3_2T7_
Filename:
MIME Type:
Creator:
John Dennis
Created:
2012-05-30 16:17:59 UTC
Size:
951.79 KB
patch
obsolete
>anaconda 17.29 exception report >Traceback (most recent call first): > File "/usr/lib/python2.7/site-packages/pyanaconda/iutil.py", line 181, in execWithRedirect > raise RuntimeError, errstr > File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 1830, in install > env_prune=['MALLOC_PERTURB_']) > File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 1843, in write > self.install() > File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 2392, in writeBootloader > anaconda.bootloader.write() > File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 383, in dispatch > self.dir = self.steps[self.step].target(self.anaconda) > File "/usr/lib/python2.7/site-packages/pyanaconda/text.py", line 507, in run > self.anaconda.dispatch.dispatch() > File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 326, in run > self.anaconda.intf.run(self.anaconda) > File "/usr/sbin/anaconda", line 863, in <module> > anaconda.dispatch.run() >RuntimeError: Error running grub2-install: No such file or directory > >Local variables in innermost frame: >stderrclose: <function <lambda> at 0xb447d764> >stdinclose: <function <lambda> at 0xb447d764> >proc_std: <tee(Thread-111, stopped -1237763264)> >errstr: Error running grub2-install: No such file or directory >stdoutclose: <function <lambda> at 0xb447d684> >perrout: 40 >chroot: <function chroot at 0xb73526f4> >stdout: 37 >pstdout: 38 >var: MALLOC_PERTURB_ >orig_stdout: /dev/tty5 >env: {'ksdevice': 'link', 'LC_NUMERIC': 'C', 'LC_ALL': 'C', 'PYTHONPATH': '/tmp/updates', 'LVM_SUPPRESS_FD_WARNINGS': '1', 'GCONF_GLOBAL_LOCKS': '1', 'HOME': '/tmp', 'PIXMAPPATH': '/tmp/updates/pixmaps/:/tmp/updates/:/tmp/product/pixmaps/:/tmp/product/:pixmaps/:/usr/share/anaconda/pixmaps/:/usr/share/pixmaps/:/usr/share/anaconda/:/usr/share/python-meh/:/usr/share/icons/Fedora/48x48/apps/', 'PATH': '/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin:/sbin:/usr/sbin', 'LANG': 'en_US.UTF-8', 'TERM': 'linux', 'TZ': 'America/New_York', 'XAUTHORITY': '/root/.Xauthority', 'GLADEPATH': '/tmp/updates/:/tmp/updates/data/ui/:ui/:/usr/share/anaconda/ui/:/usr/share/python-meh/', 'SHLVL': '0', 'LIBUSER_CONF': '/tmp/libuser.aw7iHh', 'ks': 'http://10.16.78.1/cblr/svc/op/ks/profile/Fedora-17-i386-freeipa', 'PWD': '/', 'MALLOC_CHECK_': '2', 'dhcpclass': 'ipa-lab-vms', 'method': 'http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/'} >perrin: 41 >argv: ['--no-floppy', '/dev/sda'] >e: [Errno 2] No such file or directory >env_prune: ['MALLOC_PERTURB_'] >stdin: 0 >proc_err: <tee(Thread-112, stopped -1229370560)> >command: grub2-install >stderr: 37 >pstdin: 39 >root: /mnt/sysimage > > >Anaconda instance, containing members: >_instClass: DefaultInstall instance, containing members: >_intf: InstallInterface instance, containing members: > _intf.screen: SnackScreen instance, containing members: > _intf.screen.width: 80 > _intf.screen.height: 25 > _intf._initLabelAnswers: {} > _intf.instProgress: None > _intf._warnedUnusedRaidMembers: [] > _intf.anaconda: Already dumped (Anaconda instance) > _intf._inconsistentLVMAnswers: {} >updateSrc: None >firewall: Firewall instance, containing members: > firewall.portlist: [22:tcp] > firewall.servicelist: [] > firewall.trustdevs: [] > firewall.enabled: True >keyboard: Keyboard instance, containing members: > keyboard.config: [['KEYTABLE="us"\n', 'KEYTABLE', 'us'] >, ['MODEL="pc105+inet"\n', 'MODEL', 'pc105+inet'] >, ['LAYOUT="us"\n', 'LAYOUT', 'us'] >] > keyboard.type: PC > keyboard._mods: KeyboardModels instance, containing members: > keyboard._mods._modelDict: Skipped > keyboard.beenset: 1 >clearPartTypeSystem: None >dispatch: Skipped >upgradeRoot: None >_platform: X86 instance, containing members: > _platform.anaconda: Already dumped (Anaconda instance) >id: None >rescue: False >_instLanguage: Language instance, containing members: > _instLanguage.info: Skipped > _instLanguage.nativeLangNames: Skipped > _instLanguage._instLang: en_US.UTF-8 > _instLanguage.displayMode: t > _instLanguage._systemLang: en_US.UTF-8 > _instLanguage._default: en_US.UTF-8 > _instLanguage.localeInfo: Skipped >mediaDevice: None >upgrade: False >_network: Network instance, containing members: > _network.netdevices: {'eth0': IPV6INIT="yes" >UUID="06561c93-5dda-4a00-8956-fda8958a799a" >DHCPCLASS="ipa-lab-vms" >NM_CONTROLLED="yes" >NETBOOT="yes" >HWADDR="00:16:3e:55:f8:21" >BOOTPROTO="dhcp" >DEVICE="eth0" >DNS1="10.16.255.2" >TYPE="Ethernet" >ONBOOT="yes" >NAME="Boot Disk" > >} > _network.ksdevice: eth0 > _network.hostname: unused >methodstr: http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/ >proxyPassword: None >desktop: Desktop instance, containing members: > desktop.info: {} > desktop.runlevel: 3 >rootParts: None >canReIPL: False >xdriver: None >stage2: None >rescue_mount: True >_bootloader: GRUB2 instance, containing members: > _bootloader.encrypted_password: > _bootloader.console_options: > _bootloader.console: > _bootloader.errors: [] > _bootloader.skip_bootloader: False > _bootloader.warnings: [] > _bootloader.chain_images: [] > _bootloader.stage2_is_preferred_stage1: False > _bootloader._drives: [existing 5120MB disk sda (0) with existing msdos disklabel >, existing 4064MB lvmlv vg_root-lv_root (12) with existing ext4 filesystem mounted at / >] > _bootloader.storage: Storage instance, containing members: > _bootloader.storage.clearPartChoice: None > _bootloader.storage._intf: None > _bootloader.storage._platform: None > _bootloader.storage.eddDict: {} > _bootloader.storage.anaconda: Already dumped (Anaconda instance) > _bootloader.storage.dasd: DASD instance, containing members: > _bootloader.storage.dasd.dasdfmt: /sbin/dasdfmt > _bootloader.storage.dasd.commonArgv: [-y, -d, cdl, -b, 4096] > _bootloader.storage.dasd.started: True > _bootloader.storage.dasd.totalCylinders: 0 > _bootloader.storage.dasd._maxFormatJobs: 0 > _bootloader.storage.dasd._devices: [] > _bootloader.storage.dasd._completedCylinders: 0.0 > _bootloader.storage.dasd._dasdlist: [] > _bootloader.storage.autoPartEscrowCert: None > _bootloader.storage.autoPartAddBackupPassphrase: False > _bootloader.storage.escrowCertificates: {} > _bootloader.storage.fsset: FSSet instance, containing members: > _bootloader.storage.fsset.origFStab: None > _bootloader.storage.fsset._usb: NoDevice instance, containing members: > _bootloader.storage.fsset._usb._model: > _bootloader.storage.fsset._usb.controllable: True > _bootloader.storage.fsset._usb.major: 0 > _bootloader.storage.fsset._usb.kids: 0 > _bootloader.storage.fsset._usb._partedDevice: None > _bootloader.storage.fsset._usb.uuid: None > _bootloader.storage.fsset._usb.exists: True > _bootloader.storage.fsset._usb.fstabComment: > _bootloader.storage.fsset._usb._format: USBFS instance, containing members: > _bootloader.storage.fsset._usb._format.uuid: None > _bootloader.storage.fsset._usb._format.exists: True > _bootloader.storage.fsset._usb._format._mountpoint: None > _bootloader.storage.fsset._usb._format._majorminor: None > _bootloader.storage.fsset._usb._format._minInstanceSize: None > _bootloader.storage.fsset._usb._format._mountType: usbfs > _bootloader.storage.fsset._usb._format.fsprofile: None > _bootloader.storage.fsset._usb._format.label: None > _bootloader.storage.fsset._usb._format._targetSize: 0 > _bootloader.storage.fsset._usb._format._size: 0 > _bootloader.storage.fsset._usb._format.mountopts: None > _bootloader.storage.fsset._usb._format.mountpoint: /proc/bus/usb > _bootloader.storage.fsset._usb._format._migrate: False > _bootloader.storage.fsset._usb._format._device: usbfs > _bootloader.storage.fsset._usb.sysfsPath: > _bootloader.storage.fsset._usb._vendor: > _bootloader.storage.fsset._usb._name: usbfs > _bootloader.storage.fsset._usb._targetSize: 0 > _bootloader.storage.fsset._usb.protected: False > _bootloader.storage.fsset._usb.parents: [] > _bootloader.storage.fsset._usb.originalFormat: Already dumped (USBFS instance) > _bootloader.storage.fsset._usb.bus: > _bootloader.storage.fsset._usb._size: 0 > _bootloader.storage.fsset._usb._serial: None > _bootloader.storage.fsset._usb.id: 19 > _bootloader.storage.fsset._usb.minor: 0 > _bootloader.storage.fsset.devicetree: DeviceTree instance, containing members: > _bootloader.storage.fsset.devicetree.clearPartType: 1 > _bootloader.storage.fsset.devicetree.intf: Already dumped (InstallInterface instance) > _bootloader.storage.fsset.devicetree.populated: True > _bootloader.storage.fsset.devicetree.names: [sda, loop0, /run/initramfs/tmp/curl_fetch_url1/squashfs.img, loop1, /LiveOS/rootfs.img, loop2, /overlay (deleted), loop3, loop4, loop5, loop6, loop7, live-rw, pv.01, vg_root, vg_root-lv_swap, vg_root-lv_root] > _bootloader.storage.fsset.devicetree.liveBackingDevice: None > _bootloader.storage.fsset.devicetree.zeroMbr: True > _bootloader.storage.fsset.devicetree.dasd: Already dumped (DASD instance) > _bootloader.storage.fsset.devicetree._cleanup: False > _bootloader.storage.fsset.devicetree.clearPartDisks: [] > _bootloader.storage.fsset.devicetree.iscsi: iscsi instance, containing members: > _bootloader.storage.fsset.devicetree.iscsi.started: False > _bootloader.storage.fsset.devicetree.iscsi.initiatorSet: False > _bootloader.storage.fsset.devicetree.iscsi.nodes: [] > _bootloader.storage.fsset.devicetree.iscsi.ibftNodes: [] > _bootloader.storage.fsset.devicetree.iscsi._initiator: > _bootloader.storage.fsset.devicetree.platform: X86 instance, containing members: > _bootloader.storage.fsset.devicetree.platform.anaconda: None > _bootloader.storage.fsset.devicetree.exclusiveDisks: [] > _bootloader.storage.fsset.devicetree.unusedRaidMembers: [] > _bootloader.storage.fsset.devicetree.mpathFriendlyNames: True > _bootloader.storage.fsset.devicetree.topology: MultipathTopology instance, containing members: > _bootloader.storage.fsset.devicetree.topology._multipaths: [] > _bootloader.storage.fsset.devicetree.topology._nondisks: [] > _bootloader.storage.fsset.devicetree.topology._devmap: {'dm-0': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/virtual/block/dm-0 > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/virtual/block/dm-0 > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/dm-0 > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: dm-0 > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: 0 >, 'sda': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/sda > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: sda > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: None >, 'loop3': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/virtual/block/loop3 > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/virtual/block/loop3 > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/loop3 > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: loop3 > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: 3 >, 'loop2': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/virtual/block/loop2 > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/virtual/block/loop2 > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/loop2 > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: loop2 > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: 2 >, 'loop1': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/virtual/block/loop1 > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/virtual/block/loop1 > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/loop1 > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: loop1 > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: 1 >, 'loop0': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/virtual/block/loop0 > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/virtual/block/loop0 > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/loop0 > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: loop0 > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: 0 >, 'loop7': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/virtual/block/loop7 > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/virtual/block/loop7 > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/loop7 > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: loop7 > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: 7 >, 'loop6': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/virtual/block/loop6 > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/virtual/block/loop6 > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/loop6 > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: loop6 > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: 6 >, 'loop5': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/virtual/block/loop5 > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/virtual/block/loop5 > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/loop5 > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: loop5 > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: 5 >, 'loop4': UdevDevice instance, containing members: > _bootloader.storage.fsset.devicetree.topology._devmap.subsystem: block > _bootloader.storage.fsset.devicetree.topology._devmap.syspath: /sys/devices/virtual/block/loop4 > _bootloader.storage.fsset.devicetree.topology._devmap.devpath: /devices/virtual/block/loop4 > _bootloader.storage.fsset.devicetree.topology._devmap.devnode: /dev/loop4 > _bootloader.storage.fsset.devicetree.topology._devmap.sysname: loop4 > _bootloader.storage.fsset.devicetree.topology._devmap.devtype: disk > _bootloader.storage.fsset.devicetree.topology._devmap.sysnum: 4 >} > _bootloader.storage.fsset.devicetree.topology._devices: [Already dumped (UdevDevice instance) >, Already dumped (UdevDevice instance) >, Already dumped (UdevDevice instance) >, Already dumped (UdevDevice instance) >, Already dumped (UdevDevice instance) >, Already dumped (UdevDevice instance) >, Already dumped (UdevDevice instance) >, Already dumped (UdevDevice instance) >, Already dumped (UdevDevice instance) >, Already dumped (UdevDevice instance) >] > _bootloader.storage.fsset.devicetree.topology._singlepaths: [sda, loop0, loop1, loop2, loop3, loop4, loop5, loop6, loop7, dm-0] > _bootloader.storage.fsset.devicetree.topology._mpath_topology: {} > _bootloader.storage.fsset.devicetree._ignoredDisks: [loop3, loop4, loop5, loop6, loop7] > _bootloader.storage.fsset.devicetree._actions: [ActionDestroyFormat instance, containing members: > device: Already dumped (DiskDevice instance) > origFormat: non-existent None > id: 0 >, ActionCreateFormat instance, containing members: > device: Already dumped (DiskDevice instance) > origFormat: existing None > id: 1 >, ActionCreateDevice instance, containing members: > device: existing 1MB partition sda1 (8) with non-existent biosboot > id: 2 >, ActionCreateDevice instance, containing members: > device: existing 5118MB partition sda2 (9) with existing lvmpv > id: 4 >, ActionCreateFormat instance, containing members: > device: Already dumped (PartitionDevice instance) > origFormat: non-existent None > id: 5 >, ActionCreateDevice instance, containing members: > device: existing 5088MB lvmvg vg_root (10) > id: 6 >, ActionCreateDevice instance, containing members: > device: Already dumped (LVMLogicalVolumeDevice instance) > id: 9 >, ActionCreateFormat instance, containing members: > device: Already dumped (LVMLogicalVolumeDevice instance) > origFormat: non-existent None > id: 10 >, ActionCreateDevice instance, containing members: > device: existing 1024MB lvmlv vg_root-lv_swap (11) with existing swap > id: 7 >, ActionCreateFormat instance, containing members: > device: Already dumped (LVMLogicalVolumeDevice instance) > origFormat: non-existent None > id: 8 >, ActionCreateFormat instance, containing members: > device: Already dumped (PartitionDevice instance) > origFormat: non-existent None > id: 3 >] > _bootloader.storage.fsset.devicetree.reinitializeDisks: True > _bootloader.storage.fsset.devicetree._devices: [Already dumped (DiskDevice instance) >, FileDevice instance, containing members: > _model: > controllable: False > major: 0 > kids: 1 > _partedDevice: parted.Device instance -- > model: path: /run/initramfs/tmp/curl_fetch_url1/squashfs.img type: 5 > sectorSize: 512 physicalSectorSize: 512 > length: 294064 openCount: 0 readOnly: False > externalMode: False dirty: False bootDirty: False > host: 13107 did: 13107 busy: False > hardwareGeometry: (2297, 4, 32) biosGeometry: (2297, 4, 32) > PedDevice: <_ped.Device object at 0xb6ef038c> > uuid: None > exists: True > fstabComment: > _format: existing None > sysfsPath: > _vendor: > _name: /run/initramfs/tmp/curl_fetch_url1/squashfs.img > _targetSize: 0 > protected: False > parents: [] > originalFormat: Already dumped (DeviceFormat instance) > bus: > _size: 143.5859375 > _serial: None > id: 1 > minor: 0 >, LoopDevice instance, containing members: > _model: > controllable: False > major: 0 > kids: 0 > _partedDevice: parted.Device instance -- > model: path: /dev/loop0 type: 5 > sectorSize: 512 physicalSectorSize: 512 > length: 294064 openCount: 0 readOnly: False > externalMode: False dirty: False bootDirty: False > host: 13107 did: 13107 busy: False > hardwareGeometry: (2297, 4, 32) biosGeometry: (2297, 4, 32) > PedDevice: <_ped.Device object at 0xb6ef03ec> > uuid: None > exists: True > fstabComment: > _format: existing None > sysfsPath: > _vendor: > _name: loop0 > _targetSize: 0 > protected: False > parents: [Already dumped (FileDevice instance) >] > originalFormat: Already dumped (DeviceFormat instance) > bus: > _size: 0 > _serial: None > id: 2 > minor: 0 >, FileDevice instance, containing members: > _model: > controllable: False > major: 0 > kids: 1 > _partedDevice: None > uuid: None > exists: True > fstabComment: > _format: existing None > sysfsPath: > _vendor: > _name: /LiveOS/rootfs.img > _targetSize: 0 > protected: False > parents: [] > originalFormat: Already dumped (DeviceFormat instance) > bus: > _size: 0 > _serial: None > id: 3 > minor: 0 >, LoopDevice instance, containing members: > _model: > controllable: False > major: 0 > kids: 0 > _partedDevice: None > uuid: None > exists: True > fstabComment: > _format: Ext4FS instance, containing members: > _format.uuid: 1c95f55c-e231-4409-a46c-5f985cb07a01 > _format.exists: True > _format._mountpoint: None > _format._majorminor: None > _format._minInstanceSize: 0 > _format._mountType: ext4 > _format.fsprofile: None > _format.label: Anaconda > _format._targetSize: 2048.0 > _format._size: 2048.0 > _format.mountopts: None > _format.mountpoint: None > _format._migrate: False > _format._device: /dev/loop1 > sysfsPath: > _vendor: > _name: loop1 > _targetSize: 0 > protected: False > parents: [Already dumped (FileDevice instance) >] > originalFormat: Already dumped (Ext4FS instance) > bus: > _size: 0 > _serial: None > id: 4 > minor: 0 >, FileDevice instance, containing members: > _model: > controllable: False > major: 0 > kids: 1 > _partedDevice: None > uuid: None > exists: True > fstabComment: > _format: existing None > sysfsPath: > _vendor: > _name: /overlay (deleted) > _targetSize: 0 > protected: False > parents: [] > originalFormat: Already dumped (DeviceFormat instance) > bus: > _size: 0 > _serial: None > id: 5 > minor: 0 >, LoopDevice instance, containing members: > _model: > controllable: False > major: 0 > kids: 1 > _partedDevice: None > uuid: None > exists: True > fstabComment: > _format: existing None > sysfsPath: > _vendor: > _name: loop2 > _targetSize: 0 > protected: False > parents: [Already dumped (FileDevice instance) >] > originalFormat: Already dumped (DeviceFormat instance) > bus: > _size: 0 > _serial: None > id: 6 > minor: 0 >, existing 2048MB dm live-rw (7) with existing ext4 filesystem >, Already dumped (PartitionDevice instance) >, Already dumped (PartitionDevice instance) >, Already dumped (LVMVolumeGroupDevice instance) >, Already dumped (LVMLogicalVolumeDevice instance) >, Already dumped (LVMLogicalVolumeDevice instance) >] > _bootloader.storage.fsset.devicetree.protectedDevNames: [] > _bootloader.storage.fsset.devicetree.diskImages: {} > _bootloader.storage.fsset.devicetree.protectedDevSpecs: [] > _bootloader.storage.fsset.preserveLines: [] > _bootloader.storage.fsset._devshm: NoDevice instance, containing members: > _bootloader.storage.fsset._devshm._model: > _bootloader.storage.fsset._devshm.controllable: True > _bootloader.storage.fsset._devshm.major: 0 > _bootloader.storage.fsset._devshm.kids: 0 > _bootloader.storage.fsset._devshm._partedDevice: None > _bootloader.storage.fsset._devshm.uuid: None > _bootloader.storage.fsset._devshm.exists: True > _bootloader.storage.fsset._devshm.fstabComment: > _bootloader.storage.fsset._devshm._format: TmpFS instance, containing members: > _bootloader.storage.fsset._devshm._format.uuid: None > _bootloader.storage.fsset._devshm._format.exists: True > _bootloader.storage.fsset._devshm._format._mountpoint: /mnt/sysimage/dev/shm > _bootloader.storage.fsset._devshm._format._majorminor: None > _bootloader.storage.fsset._devshm._format._minInstanceSize: None > _bootloader.storage.fsset._devshm._format._mountType: tmpfs > _bootloader.storage.fsset._devshm._format.fsprofile: None > _bootloader.storage.fsset._devshm._format.label: None > _bootloader.storage.fsset._devshm._format._targetSize: 0 > _bootloader.storage.fsset._devshm._format._size: 0 > _bootloader.storage.fsset._devshm._format.mountopts: None > _bootloader.storage.fsset._devshm._format.mountpoint: /dev/shm > _bootloader.storage.fsset._devshm._format._migrate: False > _bootloader.storage.fsset._devshm._format._device: tmpfs > _bootloader.storage.fsset._devshm.sysfsPath: > _bootloader.storage.fsset._devshm._vendor: > _bootloader.storage.fsset._devshm._name: tmpfs > _bootloader.storage.fsset._devshm._targetSize: 0 > _bootloader.storage.fsset._devshm.protected: False > _bootloader.storage.fsset._devshm.parents: [] > _bootloader.storage.fsset._devshm.originalFormat: Already dumped (TmpFS instance) > _bootloader.storage.fsset._devshm.bus: > _bootloader.storage.fsset._devshm._size: 0 > _bootloader.storage.fsset._devshm._serial: None > _bootloader.storage.fsset._devshm.id: 14 > _bootloader.storage.fsset._devshm.minor: 0 > _bootloader.storage.fsset._dev: DirectoryDevice instance, containing members: > _bootloader.storage.fsset._dev._model: > _bootloader.storage.fsset._dev.controllable: True > _bootloader.storage.fsset._dev.major: 0 > _bootloader.storage.fsset._dev.kids: 0 > _bootloader.storage.fsset._dev._partedDevice: None > _bootloader.storage.fsset._dev.uuid: None > _bootloader.storage.fsset._dev.exists: True > _bootloader.storage.fsset._dev.fstabComment: > _bootloader.storage.fsset._dev._format: BindFS instance, containing members: > _bootloader.storage.fsset._dev._format.uuid: None > _bootloader.storage.fsset._dev._format.exists: True > _bootloader.storage.fsset._dev._format._mountpoint: /mnt/sysimage/dev > _bootloader.storage.fsset._dev._format._majorminor: None > _bootloader.storage.fsset._dev._format._minInstanceSize: None > _bootloader.storage.fsset._dev._format._mountType: bind > _bootloader.storage.fsset._dev._format.fsprofile: None > _bootloader.storage.fsset._dev._format.label: None > _bootloader.storage.fsset._dev._format._targetSize: None > _bootloader.storage.fsset._dev._format._size: None > _bootloader.storage.fsset._dev._format.mountopts: None > _bootloader.storage.fsset._dev._format.mountpoint: /dev > _bootloader.storage.fsset._dev._format._migrate: False > _bootloader.storage.fsset._dev._format._device: /dev > _bootloader.storage.fsset._dev.sysfsPath: > _bootloader.storage.fsset._dev._vendor: > _bootloader.storage.fsset._dev._name: /dev > _bootloader.storage.fsset._dev._targetSize: 0 > _bootloader.storage.fsset._dev.protected: False > _bootloader.storage.fsset._dev.parents: [] > _bootloader.storage.fsset._dev.originalFormat: Already dumped (BindFS instance) > _bootloader.storage.fsset._dev.bus: > _bootloader.storage.fsset._dev._size: 0 > _bootloader.storage.fsset._dev._serial: None > _bootloader.storage.fsset._dev.id: 13 > _bootloader.storage.fsset._dev.minor: 0 > _bootloader.storage.fsset.blkidTab: None > _bootloader.storage.fsset._proc: NoDevice instance, containing members: > _bootloader.storage.fsset._proc._model: > _bootloader.storage.fsset._proc.controllable: True > _bootloader.storage.fsset._proc.major: 0 > _bootloader.storage.fsset._proc.kids: 0 > _bootloader.storage.fsset._proc._partedDevice: None > _bootloader.storage.fsset._proc.uuid: None > _bootloader.storage.fsset._proc.exists: True > _bootloader.storage.fsset._proc.fstabComment: > _bootloader.storage.fsset._proc._format: ProcFS instance, containing members: > _bootloader.storage.fsset._proc._format.uuid: None > _bootloader.storage.fsset._proc._format.exists: True > _bootloader.storage.fsset._proc._format._mountpoint: /mnt/sysimage/proc > _bootloader.storage.fsset._proc._format._majorminor: None > _bootloader.storage.fsset._proc._format._minInstanceSize: None > _bootloader.storage.fsset._proc._format._mountType: proc > _bootloader.storage.fsset._proc._format.fsprofile: None > _bootloader.storage.fsset._proc._format.label: None > _bootloader.storage.fsset._proc._format._targetSize: 0 > _bootloader.storage.fsset._proc._format._size: 0 > _bootloader.storage.fsset._proc._format.mountopts: None > _bootloader.storage.fsset._proc._format.mountpoint: /proc > _bootloader.storage.fsset._proc._format._migrate: False > _bootloader.storage.fsset._proc._format._device: proc > _bootloader.storage.fsset._proc.sysfsPath: > _bootloader.storage.fsset._proc._vendor: > _bootloader.storage.fsset._proc._name: proc > _bootloader.storage.fsset._proc._targetSize: 0 > _bootloader.storage.fsset._proc.protected: False > _bootloader.storage.fsset._proc.parents: [] > _bootloader.storage.fsset._proc.originalFormat: Already dumped (ProcFS instance) > _bootloader.storage.fsset._proc.bus: > _bootloader.storage.fsset._proc._size: 0 > _bootloader.storage.fsset._proc._serial: None > _bootloader.storage.fsset._proc.id: 17 > _bootloader.storage.fsset._proc.minor: 0 > _bootloader.storage.fsset.active: True > _bootloader.storage.fsset.cryptTab: CryptTab instance, containing members: > _bootloader.storage.fsset.cryptTab.devicetree: Already dumped (DeviceTree instance) > _bootloader.storage.fsset.cryptTab.blkidTab: None > _bootloader.storage.fsset.cryptTab.chroot: > _bootloader.storage.fsset.cryptTab.mappings: {} > _bootloader.storage.fsset._devpts: NoDevice instance, containing members: > _bootloader.storage.fsset._devpts._model: > _bootloader.storage.fsset._devpts.controllable: True > _bootloader.storage.fsset._devpts.major: 0 > _bootloader.storage.fsset._devpts.kids: 0 > _bootloader.storage.fsset._devpts._partedDevice: None > _bootloader.storage.fsset._devpts.uuid: None > _bootloader.storage.fsset._devpts.exists: True > _bootloader.storage.fsset._devpts.fstabComment: > _bootloader.storage.fsset._devpts._format: DevPtsFS instance, containing members: > _bootloader.storage.fsset._devpts._format.uuid: None > _bootloader.storage.fsset._devpts._format.exists: True > _bootloader.storage.fsset._devpts._format._mountpoint: /mnt/sysimage/dev/pts > _bootloader.storage.fsset._devpts._format._majorminor: None > _bootloader.storage.fsset._devpts._format._minInstanceSize: None > _bootloader.storage.fsset._devpts._format._mountType: devpts > _bootloader.storage.fsset._devpts._format.fsprofile: None > _bootloader.storage.fsset._devpts._format.label: None > _bootloader.storage.fsset._devpts._format._targetSize: 0 > _bootloader.storage.fsset._devpts._format._size: 0 > _bootloader.storage.fsset._devpts._format.mountopts: None > _bootloader.storage.fsset._devpts._format.mountpoint: /dev/pts > _bootloader.storage.fsset._devpts._format._migrate: False > _bootloader.storage.fsset._devpts._format._device: devpts > _bootloader.storage.fsset._devpts.sysfsPath: > _bootloader.storage.fsset._devpts._vendor: > _bootloader.storage.fsset._devpts._name: devpts > _bootloader.storage.fsset._devpts._targetSize: 0 > _bootloader.storage.fsset._devpts.protected: False > _bootloader.storage.fsset._devpts.parents: [] > _bootloader.storage.fsset._devpts.originalFormat: Already dumped (DevPtsFS instance) > _bootloader.storage.fsset._devpts.bus: > _bootloader.storage.fsset._devpts._size: 0 > _bootloader.storage.fsset._devpts._serial: None > _bootloader.storage.fsset._devpts.id: 15 > _bootloader.storage.fsset._devpts.minor: 0 > _bootloader.storage.fsset._sysfs: NoDevice instance, containing members: > _bootloader.storage.fsset._sysfs._model: > _bootloader.storage.fsset._sysfs.controllable: True > _bootloader.storage.fsset._sysfs.major: 0 > _bootloader.storage.fsset._sysfs.kids: 0 > _bootloader.storage.fsset._sysfs._partedDevice: None > _bootloader.storage.fsset._sysfs.uuid: None > _bootloader.storage.fsset._sysfs.exists: True > _bootloader.storage.fsset._sysfs.fstabComment: > _bootloader.storage.fsset._sysfs._format: SysFS instance, containing members: > _bootloader.storage.fsset._sysfs._format.uuid: None > _bootloader.storage.fsset._sysfs._format.exists: True > _bootloader.storage.fsset._sysfs._format._mountpoint: /mnt/sysimage/sys > _bootloader.storage.fsset._sysfs._format._majorminor: None > _bootloader.storage.fsset._sysfs._format._minInstanceSize: None > _bootloader.storage.fsset._sysfs._format._mountType: sysfs > _bootloader.storage.fsset._sysfs._format.fsprofile: None > _bootloader.storage.fsset._sysfs._format.label: None > _bootloader.storage.fsset._sysfs._format._targetSize: 0 > _bootloader.storage.fsset._sysfs._format._size: 0 > _bootloader.storage.fsset._sysfs._format.mountopts: None > _bootloader.storage.fsset._sysfs._format.mountpoint: /sys > _bootloader.storage.fsset._sysfs._format._migrate: False > _bootloader.storage.fsset._sysfs._format._device: sysfs > _bootloader.storage.fsset._sysfs.sysfsPath: > _bootloader.storage.fsset._sysfs._vendor: > _bootloader.storage.fsset._sysfs._name: sysfs > _bootloader.storage.fsset._sysfs._targetSize: 0 > _bootloader.storage.fsset._sysfs.protected: False > _bootloader.storage.fsset._sysfs.parents: [] > _bootloader.storage.fsset._sysfs.originalFormat: Already dumped (SysFS instance) > _bootloader.storage.fsset._sysfs.bus: > _bootloader.storage.fsset._sysfs._size: 0 > _bootloader.storage.fsset._sysfs._serial: None > _bootloader.storage.fsset._sysfs.id: 16 > _bootloader.storage.fsset._sysfs.minor: 0 > _bootloader.storage.fsset._selinux: NoDevice instance, containing members: > _bootloader.storage.fsset._selinux._model: > _bootloader.storage.fsset._selinux.controllable: True > _bootloader.storage.fsset._selinux.major: 0 > _bootloader.storage.fsset._selinux.kids: 0 > _bootloader.storage.fsset._selinux._partedDevice: None > _bootloader.storage.fsset._selinux.uuid: None > _bootloader.storage.fsset._selinux.exists: True > _bootloader.storage.fsset._selinux.fstabComment: > _bootloader.storage.fsset._selinux._format: SELinuxFS instance, containing members: > _bootloader.storage.fsset._selinux._format.uuid: None > _bootloader.storage.fsset._selinux._format.exists: True > _bootloader.storage.fsset._selinux._format._mountpoint: /mnt/sysimage/sys/fs/selinux > _bootloader.storage.fsset._selinux._format._majorminor: None > _bootloader.storage.fsset._selinux._format._minInstanceSize: None > _bootloader.storage.fsset._selinux._format._mountType: selinuxfs > _bootloader.storage.fsset._selinux._format.fsprofile: None > _bootloader.storage.fsset._selinux._format.label: None > _bootloader.storage.fsset._selinux._format._targetSize: 0 > _bootloader.storage.fsset._selinux._format._size: 0 > _bootloader.storage.fsset._selinux._format.mountopts: None > _bootloader.storage.fsset._selinux._format.mountpoint: /sys/fs/selinux > _bootloader.storage.fsset._selinux._format._migrate: False > _bootloader.storage.fsset._selinux._format._device: selinuxfs > _bootloader.storage.fsset._selinux.sysfsPath: > _bootloader.storage.fsset._selinux._vendor: > _bootloader.storage.fsset._selinux._name: selinuxfs > _bootloader.storage.fsset._selinux._targetSize: 0 > _bootloader.storage.fsset._selinux.protected: False > _bootloader.storage.fsset._selinux.parents: [] > _bootloader.storage.fsset._selinux.originalFormat: Already dumped (SELinuxFS instance) > _bootloader.storage.fsset._selinux.bus: > _bootloader.storage.fsset._selinux._size: 0 > _bootloader.storage.fsset._selinux._serial: None > _bootloader.storage.fsset._selinux.id: 18 > _bootloader.storage.fsset._selinux.minor: 0 > _bootloader.storage.config: StorageDiscoveryConfig instance, containing members: > _bootloader.storage.config.clearPartType: 1 > _bootloader.storage.config.ignoredDisks: [] > _bootloader.storage.config.protectedDevSpecs: [] > _bootloader.storage.config.reinitializeDisks: True > _bootloader.storage.config.ignoreDiskInteractive: False > _bootloader.storage.config.exclusiveDisks: [] > _bootloader.storage.config.zeroMbr: True > _bootloader.storage.config.diskImages: {} > _bootloader.storage.config.clearPartDisks: [] > _bootloader.storage.config.mpathFriendlyNames: True > _bootloader.storage.autoPartType: 2 > _bootloader.storage.zfcp: ZFCP instance, containing members: > _bootloader.storage.zfcp.down: False > _bootloader.storage.zfcp.hasReadConfig: True > _bootloader.storage.zfcp.intf: Already dumped (InstallInterface instance) > _bootloader.storage.zfcp.fcpdevs: set([]) > _bootloader.storage.devicetree: Already dumped (DeviceTree instance) > _bootloader.storage.defaultFSType: ext4 > _bootloader.storage._dumpFile: /tmp/storage.state > _bootloader.storage.services: set([]) > _bootloader.storage.shrinkPartitions: {} > _bootloader.storage.encryptionPassphrase: None > _bootloader.storage.encryptionRetrofit: False > _bootloader.storage._nextID: 1 > _bootloader.storage.fcoe: fcoe instance, containing members: > _bootloader.storage.fcoe.started: True > _bootloader.storage.fcoe.nics: [] > _bootloader.storage.fcoe.lldpadStarted: False > _bootloader.storage.autoPartitionRequests: [PartSpec instance (0xb6f9c6ac) -- > mountpoint = / lv = True singlePV = False btrfs = True > weight = 0 fstype = ext4 encrypted = True > size = 1024 maxSize = 51200 grow = True > >, PartSpec instance (0xb6f9c72c) -- > mountpoint = /home lv = True singlePV = False btrfs = True > weight = 0 fstype = ext4 encrypted = True > size = 500 maxSize = None grow = True > >, PartSpec instance (0xb6f9c7ac) -- > mountpoint = /boot lv = False singlePV = False btrfs = False > weight = 2000 fstype = ext4 encrypted = False > size = 500 maxSize = None grow = False > >, PartSpec instance (0xb582df6c) -- > mountpoint = None lv = False singlePV = False btrfs = False > weight = 5000 fstype = biosboot encrypted = False > size = 1 maxSize = None grow = False > >, PartSpec instance (0xb582df4c) -- > mountpoint = None lv = True singlePV = False btrfs = False > weight = 0 fstype = swap encrypted = True > size = 1008 maxSize = 2016 grow = True > >] > _bootloader.storage.doAutoPart: False > _bootloader.storage.iscsi: Already dumped (iscsi instance) > _bootloader.storage.encryptedAutoPart: False > _bootloader._update_only: False > _bootloader._default_image: LinuxBootLoaderImage instance, containing members: > _bootloader._default_image.short_label: linux > _bootloader._default_image.label: Fedora > _bootloader._default_image._initrd: None > _bootloader._default_image.version: 3.3.7-1.fc17.i686.PAE > _bootloader._default_image._kernel: None > _bootloader._default_image.device: Already dumped (LVMLogicalVolumeDevice instance) > _bootloader.stage1_drive: Already dumped (DiskDevice instance) > _bootloader._stage1_device: Already dumped (DiskDevice instance) > _bootloader._drive_order: [] > _bootloader._timeout: None > _bootloader.password: None > _bootloader.dracut_args: rd.md=0 LANG=en_US.UTF-8 rd.lvm.lv=vg_root/lv_swap KEYTABLE=us SYSFONT=True rd.luks=0 rd.lvm.lv=vg_root/lv_root rd.dm=0 > _bootloader.boot_args: rd.md=0 LANG=en_US.UTF-8 rd.lvm.lv=vg_root/lv_swap KEYTABLE=us SYSFONT=True rd.luks=0 rd.lvm.lv=vg_root/lv_root rd.dm=0 > _bootloader._trusted_boot: False > _bootloader.linux_images: [] >_timezone: Timezone instance, containing members: > _timezone.utc: True > _timezone.tz: America/New_York >displayMode: t >simpleFilter: True >ksdata: Skipped >proxy: None >_users: Users instance, containing members: > _users.admin: <Admin object at 0xb7435338> > _users.rootPassword: Skipped > _users.anaconda: Already dumped (Anaconda instance) >extraModules: [] >mehConfig: Config instance, containing members: > mehConfig.programName: anaconda > mehConfig.programVersion: 17.29 > mehConfig.attrSkipList: [backend.ayum, backend.dlpkgs, accounts, bootloader.password, comps, dispatch, hdList, ksdata, instLanguage.font, instLanguage.kbd, instLanguage.info, instLanguage.localeInfo, instLanguage.nativeLangNames, instLanguage.tz, keyboard._mods._modelDict, keyboard.modelDict, storage.encryptionPassphrase, users.rootPassword, tmpData, intf.icw.buff, intf.icw.currentWindow.storage.encryptionPassphrase, intf.icw.stockButtons] > mehConfig.localSkipList: [passphrase, password] > mehConfig.fileList: [/tmp/anaconda.log, /tmp/program.log, /tmp/storage.log, /tmp/ifcfg.log, /tmp/yum.log, /mnt/sysimage/root/install.log, /mnt/sysimage/root/upgrade.log, /proc/cmdline, /tmp/syslog, /run/install/ks.cfg] >_backend: YumBackend instance, containing members: > _backend.modeText: %s Installing %s > > _backend.instPath: /mnt/sysimage > _backend.supportsPackageSelection: True > _backend.totalSize: 1470466 > _backend.dlpkgs: Skipped > _backend.skipFormatRoot: False > _backend.instLog: <closed file '/mnt/sysimage/root/install.log', mode 'w+' at 0xb444ecd8> > _backend.supportsUpgrades: True > _backend.anaconda: Already dumped (Anaconda instance) > _backend.ayum: Skipped > _backend.totalFiles: 83738 >clearPartTypeSelection: None >isHeadless: False >reIPLMessage: None >_storage: Already dumped (Storage instance) >dir: 1 >security: Security instance, containing members: > security.selinux: 1 > security.auth: --useshadow --enablemd5 >opts: {'noipv6': False, 'noipv4': False, 'updateSrc': None, 'keymap': None, 'selinux': True, 'module': [], 'syslog': None, 'images': [], 'serial': False, 'dmraid': True, 'virtpconsole': None, 'memcheck': True, 'iscsi': False, 'ksfile': '/run/install/ks.cfg', 'kbdtype': None, 'runres': None, 'xdriver': None, 'display_mode': 't', 'stage2': None, 'method': 'http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/', 'vncpassword': '', 'vnc': False, 'rescue': False, 'noverifyssl': False, 'autostep': False, 'proxy': None, 'dlabel': False, 'vncconnect': None, 'lang': '', 'liveinst': False, 'loglevel': None, 'isHeadless': False, 'rescue_nomount': False, 'proxyAuth': None, 'mpath': True, 'ibft': True, 'debug': False, 'nofb': None, 'targetArch': None} >proxyUsername: None > > >/tmp/anaconda.log: >15:39:09,993 INFO anaconda: /usr/sbin/anaconda 17.29 >15:39:13,659 INFO anaconda: 1048576 kB (1024 MB) are available >15:39:13,659 INFO anaconda: check_memory(): total:1024, needed:512, graphical:512 >15:39:13,685 INFO anaconda: anaconda called with cmdline = ['/usr/sbin/anaconda'] >15:39:13,689 INFO anaconda: Default encoding = utf-8 >15:39:13,808 INFO anaconda: Running kickstart %%pre script(s) >15:39:13,811 INFO anaconda.stdout: Running pre-installation scripts >15:39:14,007 INFO anaconda: All kickstart %%pre script(s) have been run >15:39:14,101 INFO anaconda: ISCSID is /sbin/iscsid >15:39:14,108 INFO anaconda: no initiator set >15:39:14,435 INFO anaconda: No FCoE EDD info found: No FCoE boot disk information is found in EDD! >15:39:14,438 INFO anaconda: no /etc/zfcp.conf; not configuring zfcp >15:39:14,803 INFO anaconda: kickstart forcing text mode >15:39:14,805 INFO anaconda: Display mode = t >15:39:14,809 INFO anaconda: 1048576 kB (1024 MB) are available >15:39:14,809 INFO anaconda: check_memory(): total:1024, needed:512, graphical:512 >15:39:15,082 INFO anaconda: using only installclass _Fedora >15:39:15,084 INFO anaconda: Detected 1008M of memory >15:39:15,085 INFO anaconda: Swap attempt of 1008M to 2016M >15:39:15,187 INFO anaconda: dispatch: resetting to the first step. >15:39:15,189 INFO anaconda: dispatch: moving (1) to step sshd >15:39:15,190 DEBUG anaconda: dispatch: sshd is a direct step >15:39:15,191 INFO anaconda: sshd: not enabled, skipping. >15:39:15,192 INFO anaconda: created new libuser.conf at /tmp/libuser.aw7iHh with instPath="/mnt/sysimage" >15:39:15,193 INFO anaconda: dispatch: leaving (1) step sshd >15:39:15,193 INFO anaconda: dispatch: moving (1) to step kickstart >15:39:15,193 DEBUG anaconda: dispatch: kickstart is a direct step >15:39:15,263 INFO anaconda: no initiator set >15:39:15,628 DEBUG anaconda: required disklabel type for sda (1) is None >15:39:15,631 DEBUG anaconda: default disklabel type for sda is msdos >15:39:15,635 DEBUG anaconda: selecting msdos disklabel for sda based on size >15:39:16,892 DEBUG anaconda: required disklabel type for sda (1) is None >15:39:16,894 DEBUG anaconda: default disklabel type for sda is msdos >15:39:16,897 DEBUG anaconda: selecting msdos disklabel for sda based on size >15:39:18,217 INFO anaconda: set timezone: America/New_York, utc: 0 >15:39:18,218 INFO anaconda: set timezone: America/New_York, utc: 1 >15:39:18,270 INFO anaconda: dispatch: leaving (1) step kickstart >15:39:18,271 INFO anaconda: dispatch: moving (1) to step setuptime >15:39:18,271 DEBUG anaconda: dispatch: setuptime is a direct step >11:39:19,003 INFO anaconda: dispatch: leaving (1) step setuptime >11:39:19,006 INFO anaconda: dispatch: moving (1) to step autopartitionexecute >11:39:19,006 DEBUG anaconda: dispatch: autopartitionexecute is a direct step >11:39:19,122 INFO anaconda: dispatch: leaving (1) step autopartitionexecute >11:39:19,122 INFO anaconda: dispatch: moving (1) to step storagedone >11:39:19,123 DEBUG anaconda: dispatch: storagedone is a direct step >11:39:19,123 INFO anaconda: dispatch: leaving (1) step storagedone >11:39:19,124 INFO anaconda: dispatch: moving (1) to step enablefilesystems >11:39:19,124 DEBUG anaconda: dispatch: enablefilesystems is a direct step >11:39:20,463 DEBUG anaconda: notifying kernel of 'change' event on device /sys/class/block/sda2 >11:39:24,693 DEBUG anaconda: notifying kernel of 'change' event on device /sys/class/block/dm-1 >11:39:25,600 DEBUG anaconda: notifying kernel of 'change' event on device /sys/class/block/dm-2 >11:39:26,462 DEBUG anaconda: isys.py:mount()- going to mount /dev/mapper/vg_root-lv_root on /mnt/sysimage as ext4 with options defaults >11:39:26,582 DEBUG anaconda: isys.py:mount()- going to mount /dev on /mnt/sysimage/dev as bind with options defaults,bind >11:39:26,621 DEBUG anaconda: isys.py:mount()- going to mount devpts on /mnt/sysimage/dev/pts as devpts with options gid=5,mode=620 >11:39:26,654 DEBUG anaconda: isys.py:mount()- going to mount tmpfs on /mnt/sysimage/dev/shm as tmpfs with options defaults >11:39:26,686 INFO anaconda: failed to get default SELinux context for /proc: [Errno 2] No such file or directory >11:39:26,689 DEBUG anaconda: isys.py:mount()- going to mount proc on /mnt/sysimage/proc as proc with options defaults >11:39:26,709 INFO anaconda: failed to get default SELinux context for /proc: [Errno 2] No such file or directory >11:39:26,779 DEBUG anaconda: isys.py:mount()- going to mount sysfs on /mnt/sysimage/sys as sysfs with options defaults >11:39:26,812 DEBUG anaconda: isys.py:mount()- going to mount selinuxfs on /mnt/sysimage/sys/fs/selinux as selinuxfs with options defaults >11:39:26,833 INFO anaconda: failed to set SELinux context for /mnt/sysimage/sys/fs/selinux: [Errno 95] Operation not supported >11:39:26,838 INFO anaconda: dispatch: leaving (1) step enablefilesystems >11:39:26,840 INFO anaconda: dispatch: moving (1) to step reposetup >11:39:26,841 DEBUG anaconda: dispatch: reposetup is a direct step >11:39:26,845 DEBUG anaconda: enabling new callback mode >11:39:27,390 INFO anaconda: Error downloading treeinfo: [Errno 14] HTTP Error 404 - Not Found : http://download.bos.redhat.com/pub/fedora/linux/releases/17/Fedora/source/SRPMS//treeinfo >11:39:27,608 INFO anaconda: Error downloading treeinfo: [Errno 14] HTTP Error 404 - Not Found : http://download.bos.redhat.com/pub/fedora/linux/updates/17/i386//treeinfo >11:39:27,713 INFO anaconda: Error downloading treeinfo: [Errno 14] HTTP Error 404 - Not Found : http://download.bos.redhat.com/pub/fedora/linux/releases/17/Everything/i386/debug//treeinfo >11:39:27,715 INFO anaconda: added repository Fedora-17-SRPM with URL http://download.bos.redhat.com/pub/fedora/linux/releases/17/Fedora/source/SRPMS/ >11:39:27,716 INFO anaconda: added repository Fedora-17-i386-Everything with URL http://download.bos.redhat.com/pub/fedora/linux/releases/17/Everything/i386/os/ >11:39:27,717 INFO anaconda: added repository Fedora-17-i386-updates with URL http://download.bos.redhat.com/pub/fedora/linux/updates/17/i386/ >11:39:27,717 INFO anaconda: added repository Fedora-17-i386-debuginfo with URL http://download.bos.redhat.com/pub/fedora/linux/releases/17/Everything/i386/debug/ >11:39:27,852 DEBUG anaconda: Grabbing http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/repodata/repomd.xml >11:39:27,976 DEBUG anaconda: Grabbing http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/repodata/7ccd9374ffa3a0c8a6c497252e9120aefc4748a89fe5532af814ef1c76aced54-primary.sqlite.bz2 >11:39:30,977 DEBUG anaconda: Grabbing http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/repodata/e0a7c23e8f77d20bbbf1dcddab6f8b13a7744e8da0df85175e93e0ffbf7518fa-Fedora-17-comps.xml.gz >11:39:49,251 DEBUG anaconda: Grabbing http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/repodata/767f84f69c06ee9b14da2cc3ece4532520bd65969f4d8849852db692bbe57bc3-Fedora-17-comps.xml >11:40:01,614 INFO anaconda: dispatch: leaving (1) step reposetup >11:40:01,616 INFO anaconda: dispatch: moving (1) to step basepkgsel >11:40:01,617 DEBUG anaconda: dispatch: basepkgsel is a direct step >11:40:11,064 WARN anaconda: not adding Base group >11:40:25,905 INFO anaconda: dispatch: leaving (1) step basepkgsel >11:40:25,907 INFO anaconda: dispatch: moving (1) to step postselection >11:40:25,908 DEBUG anaconda: dispatch: postselection is a direct step >11:40:25,914 INFO anaconda: selected kernel-PAE package for kernel >11:40:28,148 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/fcoe/fcoe.ko >11:40:28,149 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/fcoe/libfcoe.ko >11:40:28,150 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/libfc/libfc.ko >11:40:28,152 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/scsi_transport_fc.ko >11:40:28,152 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/scsi_tgt.ko >11:40:28,152 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/i2c/busses/i2c-piix4.ko >11:40:28,152 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/virtio/virtio_balloon.ko >11:40:28,152 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/i2c/i2c-core.ko >11:40:28,152 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/net/ethernet/realtek/8139too.ko >11:40:28,153 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/net/ethernet/realtek/8139cp.ko >11:40:28,153 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/net/mii.ko >11:40:28,153 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/net/sunrpc/sunrpc.ko >11:40:28,153 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/xts.ko >11:40:28,153 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/lrw.ko >11:40:28,153 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/gf128mul.ko >11:40:28,156 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/sha256_generic.ko >11:40:28,156 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/dm-crypt.ko >11:40:28,156 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/dm-round-robin.ko >11:40:28,157 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/dm-multipath.ko >11:40:28,158 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/linear.ko >11:40:28,159 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/raid10.ko >11:40:28,160 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/raid456.ko >11:40:28,162 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_raid6_recov.ko >11:40:28,163 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_memcpy.ko >11:40:28,164 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_pq.ko >11:40:28,166 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/lib/raid6/raid6_pq.ko >11:40:28,167 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_xor.ko >11:40:28,168 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/xor.ko >11:40:28,169 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_tx.ko >11:40:28,170 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/raid1.ko >11:40:28,172 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/raid0.ko >11:40:28,173 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/firmware/iscsi_ibft.ko >11:40:28,174 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/iscsi_boot_sysfs.ko >11:40:28,175 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/firmware/edd.ko >11:40:28,177 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/block/floppy.ko >11:40:28,178 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/device_handler/scsi_dh_rdac.ko >11:40:28,179 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/device_handler/scsi_dh_hp_sw.ko >11:40:28,180 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/device_handler/scsi_dh_emc.ko >11:40:28,182 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko >11:40:28,183 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/iscsi_tcp.ko >11:40:28,184 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/libiscsi_tcp.ko >11:40:28,185 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/libiscsi.ko >11:40:28,187 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/scsi_transport_iscsi.ko >11:40:28,188 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/fs/squashfs/squashfs.ko >11:40:28,189 DEBUG anaconda: Checking for DUD module /lib/modules/3.3.4-5.fc17.i686/kernel/fs/cramfs/cramfs.ko >11:40:28,191 DEBUG anaconda: selecting kernel-PAE-devel >11:41:19,447 INFO anaconda: dispatch: leaving (1) step postselection >11:41:19,449 INFO anaconda: dispatch: moving (1) to step install >11:41:19,453 INFO anaconda: dispatch: leaving (1) step install >11:41:19,455 INFO anaconda: dispatch: moving (1) to step preinstallconfig >11:41:19,457 DEBUG anaconda: dispatch: preinstallconfig is a direct step >11:41:19,619 INFO anaconda: Backend logger started. >11:41:19,632 INFO anaconda: copy_to_sysimage: source '/etc/multipath/wwids' does not exist. >11:41:19,633 INFO anaconda: copy_to_sysimage: source '/etc/multipath/bindings' does not exist. >11:41:19,652 INFO anaconda: copy_to_sysimage: source '/etc/multipath/wwids' does not exist. >11:41:19,652 INFO anaconda: copy_to_sysimage: source '/etc/multipath/bindings' does not exist. >11:41:19,654 INFO anaconda: dispatch: leaving (1) step preinstallconfig >11:41:19,654 INFO anaconda: dispatch: moving (1) to step installpackages >11:41:19,654 DEBUG anaconda: dispatch: installpackages is a direct step >11:41:19,655 INFO anaconda: Preparing to install packages >11:55:38,202 INFO anaconda: dispatch: leaving (1) step installpackages >11:55:38,207 INFO anaconda: dispatch: moving (1) to step postinstallconfig >11:55:38,208 DEBUG anaconda: dispatch: postinstallconfig is a direct step >11:55:38,244 INFO anaconda: Backend logger stopped. >11:55:38,259 INFO anaconda: dispatch: leaving (1) step postinstallconfig >11:55:38,261 INFO anaconda: dispatch: moving (1) to step writeconfig >11:55:38,262 DEBUG anaconda: dispatch: writeconfig is a direct step >11:55:38,263 INFO anaconda: Writing main configuration >11:55:38,283 INFO anaconda: removing libuser.conf at /tmp/libuser.aw7iHh >11:55:38,283 INFO anaconda: created new libuser.conf at /tmp/libuser.aw7iHh with instPath="/mnt/sysimage" >11:55:38,755 ERR anaconda: Error running /usr/sbin/lokkit: No such file or directory >11:55:38,761 ERR anaconda: lokkit run failed: Error running /usr/sbin/lokkit: No such file or directory >11:55:39,034 ERR anaconda: Error running /usr/sbin/lokkit: No such file or directory >11:55:39,040 ERR anaconda: lokkit run failed: Error running /usr/sbin/lokkit: No such file or directory >11:55:39,043 INFO anaconda: dispatch: leaving (1) step writeconfig >11:55:39,045 INFO anaconda: dispatch: moving (1) to step firstboot >11:55:39,045 DEBUG anaconda: dispatch: firstboot is a direct step >11:55:39,046 INFO anaconda: dispatch: leaving (1) step firstboot >11:55:39,046 INFO anaconda: dispatch: moving (1) to step instbootloader >11:55:39,046 DEBUG anaconda: dispatch: instbootloader is a direct step >11:55:39,634 ERR anaconda: Error running grub2-install: No such file or directory > > >/tmp/program.log: >15:39:12,106 INFO program: Running... localedef -i en_US -f UTF-8 en_US.UTF-8 >15:39:13,814 INFO program: Running... /bin/sh /tmp/ks-script-_j4a7U >15:39:13,845 ERR program: exec 1>/tmp/ks-pre.log 2>&1 >15:39:13,851 ERR program: + exec >15:39:14,037 INFO program: Running... udevadm trigger --action=change --subsystem-match=block >15:39:14,111 INFO program: Running... modprobe fcoe >15:39:14,279 INFO program: Running... /usr/libexec/fcoe/fcoe_edd.sh -i >15:39:14,427 INFO program: No FCoE boot disk information is found in EDD! >15:39:14,441 INFO program: Running... modprobe scsi_wait_scan >15:39:14,483 INFO program: Running... rmmod scsi_wait_scan >15:39:14,514 INFO program: Running... udevadm settle --timeout=300 >15:39:14,673 INFO program: Running... multipath -d >15:39:14,721 INFO program: Running... multipath -ll >15:39:15,193 INFO program: Running... udevadm trigger --action=change --subsystem-match=block >15:39:15,279 INFO program: Running... modprobe scsi_wait_scan >15:39:15,327 INFO program: Running... rmmod scsi_wait_scan >15:39:15,360 INFO program: Running... udevadm settle --timeout=300 >15:39:15,466 INFO program: Running... multipath -d >15:39:15,520 INFO program: Running... multipath -ll >15:39:15,749 INFO program: Running... losetup -j /run/initramfs/tmp/curl_fetch_url1/squashfs.img >15:39:15,780 INFO program: /dev/loop0: [0016]:10809 (/run/initramfs/tmp/curl_fetch_url1/squashfs.img) >15:39:15,791 INFO program: Running... losetup -j /run/initramfs/tmp/curl_fetch_url1/squashfs.img >15:39:15,809 INFO program: /dev/loop0: [0016]:10809 (/run/initramfs/tmp/curl_fetch_url1/squashfs.img) >15:39:15,838 INFO program: Running... losetup -j /run/initramfs/tmp/curl_fetch_url1/squashfs.img >15:39:15,863 INFO program: /dev/loop0: [0016]:10809 (/run/initramfs/tmp/curl_fetch_url1/squashfs.img) >15:39:15,871 INFO program: Running... losetup -j /run/initramfs/tmp/curl_fetch_url1/squashfs.img >15:39:15,889 INFO program: /dev/loop0: [0016]:10809 (/run/initramfs/tmp/curl_fetch_url1/squashfs.img) >15:39:15,951 INFO program: Running... dumpe2fs -h /dev/loop1 >15:39:15,979 INFO program: Filesystem volume name: Anaconda >15:39:15,983 INFO program: Last mounted on: / >15:39:15,984 INFO program: Filesystem UUID: 1c95f55c-e231-4409-a46c-5f985cb07a01 >15:39:15,985 INFO program: Filesystem magic number: 0xEF53 >15:39:15,985 INFO program: Filesystem revision #: 1 (dynamic) >15:39:15,985 INFO program: Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super huge_file uninit_bg dir_nlink extra_isize >15:39:15,985 INFO program: Filesystem flags: signed_directory_hash >15:39:15,985 INFO program: Default mount options: user_xattr acl >15:39:15,986 INFO program: Filesystem state: clean >15:39:15,986 INFO program: Errors behavior: Continue >15:39:15,986 INFO program: Filesystem OS type: Linux >15:39:15,986 INFO program: Inode count: 131072 >15:39:15,986 INFO program: Block count: 2097152 >15:39:15,986 INFO program: Reserved block count: 0 >15:39:15,986 INFO program: Free blocks: 1603427 >15:39:15,988 INFO program: Free inodes: 108443 >15:39:15,989 INFO program: First block: 1 >15:39:15,989 INFO program: Block size: 1024 >15:39:15,990 INFO program: Fragment size: 1024 >15:39:15,991 INFO program: Reserved GDT blocks: 256 >15:39:15,992 INFO program: Blocks per group: 8192 >15:39:15,993 INFO program: Fragments per group: 8192 >15:39:15,995 INFO program: Inodes per group: 512 >15:39:15,996 INFO program: Inode blocks per group: 128 >15:39:15,997 INFO program: Flex block group size: 16 >15:39:15,999 INFO program: Filesystem created: Tue May 22 20:52:33 2012 >15:39:16,000 INFO program: Last mount time: Tue May 22 20:52:48 2012 >15:39:16,001 INFO program: Last write time: Tue May 22 20:53:01 2012 >15:39:16,002 INFO program: Mount count: 2 >15:39:16,003 INFO program: Maximum mount count: -1 >15:39:16,004 INFO program: Last checked: Tue May 22 20:52:33 2012 >15:39:16,006 INFO program: Check interval: 0 (<none>) >15:39:16,007 INFO program: Lifetime writes: 32 MB >15:39:16,008 INFO program: Reserved blocks uid: 0 (user root) >15:39:16,009 INFO program: Reserved blocks gid: 0 (group root) >15:39:16,010 INFO program: First inode: 11 >15:39:16,011 INFO program: Inode size: 256 >15:39:16,013 INFO program: Required extra isize: 28 >15:39:16,014 INFO program: Desired extra isize: 28 >15:39:16,015 INFO program: Journal inode: 8 >15:39:16,016 INFO program: Default directory hash: half_md4 >15:39:16,017 INFO program: Directory Hash Seed: 0d7e1567-3da8-4376-858b-4beeae3ed182 >15:39:16,018 INFO program: Journal backup: inode blocks >15:39:16,019 INFO program: Journal features: (none) >15:39:16,021 INFO program: Journal size: 32M >15:39:16,022 INFO program: Journal length: 32768 >15:39:16,023 INFO program: Journal sequence: 0x0000000b >15:39:16,024 INFO program: Journal start: 0 >15:39:16,025 INFO program: >15:39:16,027 ERR program: dumpe2fs 1.42 (29-Nov-2011) >15:39:16,029 INFO program: Running... dumpe2fs -h /dev/loop1 >15:39:16,062 INFO program: Filesystem volume name: Anaconda >15:39:16,066 INFO program: Last mounted on: / >15:39:16,067 INFO program: Filesystem UUID: 1c95f55c-e231-4409-a46c-5f985cb07a01 >15:39:16,068 INFO program: Filesystem magic number: 0xEF53 >15:39:16,068 INFO program: Filesystem revision #: 1 (dynamic) >15:39:16,068 INFO program: Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super huge_file uninit_bg dir_nlink extra_isize >15:39:16,068 INFO program: Filesystem flags: signed_directory_hash >15:39:16,068 INFO program: Default mount options: user_xattr acl >15:39:16,069 INFO program: Filesystem state: clean >15:39:16,069 INFO program: Errors behavior: Continue >15:39:16,069 INFO program: Filesystem OS type: Linux >15:39:16,069 INFO program: Inode count: 131072 >15:39:16,069 INFO program: Block count: 2097152 >15:39:16,069 INFO program: Reserved block count: 0 >15:39:16,069 INFO program: Free blocks: 1603427 >15:39:16,073 INFO program: Free inodes: 108443 >15:39:16,073 INFO program: First block: 1 >15:39:16,073 INFO program: Block size: 1024 >15:39:16,074 INFO program: Fragment size: 1024 >15:39:16,075 INFO program: Reserved GDT blocks: 256 >15:39:16,076 INFO program: Blocks per group: 8192 >15:39:16,077 INFO program: Fragments per group: 8192 >15:39:16,078 INFO program: Inodes per group: 512 >15:39:16,080 INFO program: Inode blocks per group: 128 >15:39:16,082 INFO program: Flex block group size: 16 >15:39:16,083 INFO program: Filesystem created: Tue May 22 20:52:33 2012 >15:39:16,084 INFO program: Last mount time: Tue May 22 20:52:48 2012 >15:39:16,085 INFO program: Last write time: Tue May 22 20:53:01 2012 >15:39:16,086 INFO program: Mount count: 2 >15:39:16,087 INFO program: Maximum mount count: -1 >15:39:16,089 INFO program: Last checked: Tue May 22 20:52:33 2012 >15:39:16,090 INFO program: Check interval: 0 (<none>) >15:39:16,092 INFO program: Lifetime writes: 32 MB >15:39:16,094 INFO program: Reserved blocks uid: 0 (user root) >15:39:16,095 INFO program: Reserved blocks gid: 0 (group root) >15:39:16,096 INFO program: First inode: 11 >15:39:16,098 INFO program: Inode size: 256 >15:39:16,100 INFO program: Required extra isize: 28 >15:39:16,101 INFO program: Desired extra isize: 28 >15:39:16,102 INFO program: Journal inode: 8 >15:39:16,103 INFO program: Default directory hash: half_md4 >15:39:16,104 INFO program: Directory Hash Seed: 0d7e1567-3da8-4376-858b-4beeae3ed182 >15:39:16,105 INFO program: Journal backup: inode blocks >15:39:16,106 INFO program: Journal features: (none) >15:39:16,108 INFO program: Journal size: 32M >15:39:16,112 INFO program: Journal length: 32768 >15:39:16,114 INFO program: Journal sequence: 0x0000000b >15:39:16,115 INFO program: Journal start: 0 >15:39:16,116 INFO program: >15:39:16,117 ERR program: dumpe2fs 1.42 (29-Nov-2011) >15:39:16,119 INFO program: Running... resize2fs -P /dev/loop1 >15:39:16,163 INFO program: Couldn't find valid filesystem superblock. >15:39:16,167 ERR program: resize2fs 1.42 (29-Nov-2011) >15:39:16,168 ERR program: resize2fs: Device or resource busy while trying to open /dev/loop1 >15:39:16,279 INFO program: Running... modprobe scsi_wait_scan >15:39:16,309 INFO program: Running... rmmod scsi_wait_scan >15:39:16,340 INFO program: Running... udevadm settle --timeout=300 >15:39:16,464 INFO program: Running... dumpe2fs -h /dev/mapper/live-rw >15:39:16,491 INFO program: Filesystem volume name: Anaconda >15:39:16,494 INFO program: Last mounted on: / >15:39:16,495 INFO program: Filesystem UUID: 1c95f55c-e231-4409-a46c-5f985cb07a01 >15:39:16,496 INFO program: Filesystem magic number: 0xEF53 >15:39:16,497 INFO program: Filesystem revision #: 1 (dynamic) >15:39:16,497 INFO program: Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super huge_file uninit_bg dir_nlink extra_isize >15:39:16,497 INFO program: Filesystem flags: signed_directory_hash >15:39:16,497 INFO program: Default mount options: user_xattr acl >15:39:16,497 INFO program: Filesystem state: clean >15:39:16,497 INFO program: Errors behavior: Continue >15:39:16,497 INFO program: Filesystem OS type: Linux >15:39:16,498 INFO program: Inode count: 131072 >15:39:16,498 INFO program: Block count: 2097152 >15:39:16,498 INFO program: Reserved block count: 0 >15:39:16,498 INFO program: Free blocks: 1603427 >15:39:16,500 INFO program: Free inodes: 108443 >15:39:16,500 INFO program: First block: 1 >15:39:16,500 INFO program: Block size: 1024 >15:39:16,502 INFO program: Fragment size: 1024 >15:39:16,503 INFO program: Reserved GDT blocks: 256 >15:39:16,504 INFO program: Blocks per group: 8192 >15:39:16,505 INFO program: Fragments per group: 8192 >15:39:16,507 INFO program: Inodes per group: 512 >15:39:16,508 INFO program: Inode blocks per group: 128 >15:39:16,509 INFO program: Flex block group size: 16 >15:39:16,510 INFO program: Filesystem created: Tue May 22 20:52:33 2012 >15:39:16,512 INFO program: Last mount time: Wed May 30 15:39:02 2012 >15:39:16,513 INFO program: Last write time: Wed May 30 15:39:02 2012 >15:39:16,514 INFO program: Mount count: 3 >15:39:16,515 INFO program: Maximum mount count: -1 >15:39:16,516 INFO program: Last checked: Tue May 22 20:52:33 2012 >15:39:16,518 INFO program: Check interval: 0 (<none>) >15:39:16,519 INFO program: Lifetime writes: 32 MB >15:39:16,520 INFO program: Reserved blocks uid: 0 (user root) >15:39:16,521 INFO program: Reserved blocks gid: 0 (group root) >15:39:16,523 INFO program: First inode: 11 >15:39:16,524 INFO program: Inode size: 256 >15:39:16,525 INFO program: Required extra isize: 28 >15:39:16,526 INFO program: Desired extra isize: 28 >15:39:16,527 INFO program: Journal inode: 8 >15:39:16,528 INFO program: Default directory hash: half_md4 >15:39:16,529 INFO program: Directory Hash Seed: 0d7e1567-3da8-4376-858b-4beeae3ed182 >15:39:16,530 INFO program: Journal backup: inode blocks >15:39:16,532 INFO program: Journal features: (none) >15:39:16,533 INFO program: Journal size: 32M >15:39:16,534 INFO program: Journal length: 32768 >15:39:16,535 INFO program: Journal sequence: 0x0000000c >15:39:16,536 INFO program: Journal start: 1 >15:39:16,537 INFO program: >15:39:16,537 ERR program: dumpe2fs 1.42 (29-Nov-2011) >15:39:16,539 INFO program: Running... dumpe2fs -h /dev/mapper/live-rw >15:39:16,560 INFO program: Filesystem volume name: Anaconda >15:39:16,562 INFO program: Last mounted on: / >15:39:16,562 INFO program: Filesystem UUID: 1c95f55c-e231-4409-a46c-5f985cb07a01 >15:39:16,563 INFO program: Filesystem magic number: 0xEF53 >15:39:16,563 INFO program: Filesystem revision #: 1 (dynamic) >15:39:16,563 INFO program: Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super huge_file uninit_bg dir_nlink extra_isize >15:39:16,564 INFO program: Filesystem flags: signed_directory_hash >15:39:16,564 INFO program: Default mount options: user_xattr acl >15:39:16,565 INFO program: Filesystem state: clean >15:39:16,565 INFO program: Errors behavior: Continue >15:39:16,565 INFO program: Filesystem OS type: Linux >15:39:16,566 INFO program: Inode count: 131072 >15:39:16,566 INFO program: Block count: 2097152 >15:39:16,566 INFO program: Reserved block count: 0 >15:39:16,567 INFO program: Free blocks: 1603427 >15:39:16,567 INFO program: Free inodes: 108443 >15:39:16,567 INFO program: First block: 1 >15:39:16,568 INFO program: Block size: 1024 >15:39:16,568 INFO program: Fragment size: 1024 >15:39:16,568 INFO program: Reserved GDT blocks: 256 >15:39:16,569 INFO program: Blocks per group: 8192 >15:39:16,569 INFO program: Fragments per group: 8192 >15:39:16,569 INFO program: Inodes per group: 512 >15:39:16,569 INFO program: Inode blocks per group: 128 >15:39:16,570 INFO program: Flex block group size: 16 >15:39:16,570 INFO program: Filesystem created: Tue May 22 20:52:33 2012 >15:39:16,570 INFO program: Last mount time: Wed May 30 15:39:02 2012 >15:39:16,571 INFO program: Last write time: Wed May 30 15:39:02 2012 >15:39:16,571 INFO program: Mount count: 3 >15:39:16,571 INFO program: Maximum mount count: -1 >15:39:16,572 INFO program: Last checked: Tue May 22 20:52:33 2012 >15:39:16,572 INFO program: Check interval: 0 (<none>) >15:39:16,572 INFO program: Lifetime writes: 32 MB >15:39:16,573 INFO program: Reserved blocks uid: 0 (user root) >15:39:16,573 INFO program: Reserved blocks gid: 0 (group root) >15:39:16,573 INFO program: First inode: 11 >15:39:16,574 INFO program: Inode size: 256 >15:39:16,574 INFO program: Required extra isize: 28 >15:39:16,574 INFO program: Desired extra isize: 28 >15:39:16,575 INFO program: Journal inode: 8 >15:39:16,575 INFO program: Default directory hash: half_md4 >15:39:16,575 INFO program: Directory Hash Seed: 0d7e1567-3da8-4376-858b-4beeae3ed182 >15:39:16,576 INFO program: Journal backup: inode blocks >15:39:16,576 INFO program: Journal features: (none) >15:39:16,576 INFO program: Journal size: 32M >15:39:16,577 INFO program: Journal length: 32768 >15:39:16,577 INFO program: Journal sequence: 0x0000000c >15:39:16,577 INFO program: Journal start: 1 >15:39:16,578 INFO program: >15:39:16,578 ERR program: dumpe2fs 1.42 (29-Nov-2011) >15:39:16,580 INFO program: Running... resize2fs -P /dev/mapper/live-rw >15:39:16,600 INFO program: Estimated minimum size of the filesystem: 471747 >15:39:16,602 ERR program: resize2fs 1.42 (29-Nov-2011) >15:39:16,629 INFO program: Running... modprobe scsi_wait_scan >15:39:16,651 INFO program: Running... rmmod scsi_wait_scan >15:39:16,673 INFO program: Running... udevadm settle --timeout=300 >15:39:16,733 INFO program: Running... udevadm settle --timeout=300 >15:39:16,778 INFO program: Running... losetup -j /run/initramfs/tmp/curl_fetch_url1/squashfs.img >15:39:16,797 INFO program: /dev/loop0: [0016]:10809 (/run/initramfs/tmp/curl_fetch_url1/squashfs.img) >15:39:16,805 INFO program: Running... losetup -j /run/initramfs/tmp/curl_fetch_url1/squashfs.img >15:39:16,822 INFO program: /dev/loop0: [0016]:10809 (/run/initramfs/tmp/curl_fetch_url1/squashfs.img) >15:39:16,912 INFO program: Running... localedef -i en_US -f UTF-8 en_US.UTF-8 >11:39:18,275 INFO program: Running... /sbin/hwclock --hctosys -u >11:39:19,125 INFO program: Running... losetup -j /run/initramfs/tmp/curl_fetch_url1/squashfs.img >11:39:19,143 INFO program: /dev/loop0: [0016]:10809 (/run/initramfs/tmp/curl_fetch_url1/squashfs.img) >11:39:19,151 INFO program: Running... losetup -j /run/initramfs/tmp/curl_fetch_url1/squashfs.img >11:39:19,169 INFO program: /dev/loop0: [0016]:10809 (/run/initramfs/tmp/curl_fetch_url1/squashfs.img) >11:39:19,204 INFO program: Running... wipefs -a /dev/sda >11:39:19,246 INFO program: Running... udevadm settle --timeout=300 >11:39:19,322 INFO program: Running... udevadm settle --timeout=300 >11:39:19,366 INFO program: Running... udevadm settle --timeout=300 >11:39:19,457 INFO program: Running... udevadm settle --timeout=300 >11:39:19,520 INFO program: Running... udevadm settle --timeout=300 >11:39:19,574 INFO program: Running... udevadm settle --timeout=300 >11:39:19,658 INFO program: Running... udevadm settle --timeout=300 >11:39:19,739 INFO program: Running... wipefs -a /dev/sda1 >11:39:19,776 INFO program: Running... udevadm settle --timeout=300 >11:39:19,824 INFO program: Running... udevadm settle --timeout=300 >11:39:19,907 INFO program: Running... udevadm settle --timeout=300 >11:39:20,009 INFO program: Running... wipefs -a /dev/sda2 >11:39:20,062 INFO program: Running... udevadm settle --timeout=300 >11:39:20,112 INFO program: Running... udevadm settle --timeout=300 >11:39:20,229 INFO program: Running... wipefs -a /dev/sda2 >11:39:20,278 INFO program: Running... lvm pvcreate --config devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] } --dataalignment 1024k /dev/sda2 >11:39:20,452 INFO program: Physical volume "/dev/sda2" successfully created >11:39:20,456 ERR program: Writing physical volume data to disk "/dev/sda2" >11:39:20,473 INFO program: Running... udevadm settle --timeout=300 >11:39:20,580 INFO program: Running... udevadm settle --timeout=300 >11:39:20,646 INFO program: Running... lvm vgcreate -s 32m --config devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] } vg_root /dev/sda2 >11:39:20,829 INFO program: Volume group "vg_root" successfully created >11:39:20,860 INFO program: Running... udevadm settle --timeout=300 >11:39:20,911 INFO program: Running... udevadm settle --timeout=300 >11:39:20,981 INFO program: Running... lvm lvcreate -L 4064m -n lv_root --config devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] } vg_root >11:39:21,313 INFO program: Logical volume "lv_root" created >11:39:21,350 INFO program: Running... udevadm settle --timeout=300 >11:39:21,444 INFO program: Running... udevadm settle --timeout=300 >11:39:21,518 INFO program: Running... mke2fs -t ext4 /dev/mapper/vg_root-lv_root >11:39:24,654 INFO program: Filesystem label= >11:39:24,661 INFO program: OS type: Linux >11:39:24,662 INFO program: Block size=4096 (log=2) >11:39:24,664 INFO program: Fragment size=4096 (log=2) >11:39:24,664 INFO program: Stride=0 blocks, Stripe width=0 blocks >11:39:24,664 INFO program: 260096 inodes, 1040384 blocks >11:39:24,664 INFO program: 52019 blocks (5.00%) reserved for the super user >11:39:24,664 INFO program: First data block=0 >11:39:24,665 INFO program: Maximum filesystem blocks=1065353216 >11:39:24,665 INFO program: 32 block groups >11:39:24,665 INFO program: 32768 blocks per group, 32768 fragments per group >11:39:24,665 INFO program: 8128 inodes per group >11:39:24,665 INFO program: Superblock backups stored on blocks: >11:39:24,665 INFO program: 32768, 98304, 163840, 229376, 294912, 819200, 884736 >11:39:24,665 INFO program: >11:39:24,670 INFO program: Allocating group tables: 0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32 done >11:39:24,670 INFO program: Writing inode tables: 0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32 done >11:39:24,670 INFO program: Creating journal (16384 blocks): done >11:39:24,671 INFO program: Writing superblocks and filesystem accounting information: 0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32 done >11:39:24,674 INFO program: >11:39:24,676 ERR program: mke2fs 1.42 (29-Nov-2011) >11:39:24,704 INFO program: Running... udevadm settle --timeout=300 >11:39:24,834 INFO program: Running... udevadm settle --timeout=300 >11:39:24,921 INFO program: Running... lvm lvcreate -L 1024m -n lv_swap --config devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] } vg_root >11:39:25,278 INFO program: Logical volume "lv_swap" created >11:39:25,314 INFO program: Running... udevadm settle --timeout=300 >11:39:25,425 INFO program: Running... udevadm settle --timeout=300 >11:39:25,511 INFO program: Running... mkswap -f /dev/mapper/vg_root-lv_swap >11:39:25,580 INFO program: Setting up swapspace version 1, size = 1048572 KiB >11:39:25,586 INFO program: no label, UUID=8a574a39-166c-4e43-a996-710d4fe3650e >11:39:25,605 INFO program: Running... udevadm settle --timeout=300 >11:39:25,723 INFO program: Running... udevadm settle --timeout=300 >11:39:26,078 INFO program: Running... udevadm settle --timeout=300 >11:39:26,176 INFO program: Running... udevadm settle --timeout=300 >11:39:26,314 INFO program: Running... swapon /dev/mapper/vg_root-lv_swap >15:39:26,470 INFO program: Running... /bin/mount -n -t ext4 -o defaults /dev/mapper/vg_root-lv_root /mnt/sysimage >15:39:26,590 INFO program: Running... /bin/mount -n -t bind -o defaults,bind /dev /mnt/sysimage/dev >15:39:26,628 INFO program: Running... /bin/mount -n -t devpts -o gid=5,mode=620 /dev/devpts /mnt/sysimage/dev/pts >15:39:26,662 INFO program: Running... /bin/mount -n -t tmpfs -o defaults /dev/tmpfs /mnt/sysimage/dev/shm >15:39:26,697 INFO program: Running... /bin/mount -n -t proc -o defaults /dev/proc /mnt/sysimage/proc >15:39:26,787 INFO program: Running... /bin/mount -n -t sysfs -o defaults /dev/sysfs /mnt/sysimage/sys >15:39:26,820 INFO program: Running... /bin/mount -n -t selinuxfs -o defaults /dev/selinuxfs /mnt/sysimage/sys/fs/selinux >11:40:25,916 INFO program: Running... modinfo -F filename fcoe >11:40:25,988 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/fcoe/fcoe.ko >11:40:25,991 INFO program: Running... modinfo -F filename libfcoe >11:40:26,040 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/fcoe/libfcoe.ko >11:40:26,044 INFO program: Running... modinfo -F filename libfc >11:40:26,094 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/libfc/libfc.ko >11:40:26,097 INFO program: Running... modinfo -F filename scsi_transport_fc >11:40:26,146 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/scsi_transport_fc.ko >11:40:26,150 INFO program: Running... modinfo -F filename scsi_tgt >11:40:26,199 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/scsi_tgt.ko >11:40:26,202 INFO program: Running... modinfo -F filename i2c_piix4 >11:40:26,248 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/i2c/busses/i2c-piix4.ko >11:40:26,252 INFO program: Running... modinfo -F filename virtio_balloon >11:40:26,297 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/virtio/virtio_balloon.ko >11:40:26,301 INFO program: Running... modinfo -F filename i2c_core >11:40:26,346 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/i2c/i2c-core.ko >11:40:26,350 INFO program: Running... modinfo -F filename 8139too >11:40:26,395 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/net/ethernet/realtek/8139too.ko >11:40:26,399 INFO program: Running... modinfo -F filename 8139cp >11:40:26,442 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/net/ethernet/realtek/8139cp.ko >11:40:26,445 INFO program: Running... modinfo -F filename mii >11:40:26,488 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/net/mii.ko >11:40:26,492 INFO program: Running... modinfo -F filename sunrpc >11:40:26,536 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/net/sunrpc/sunrpc.ko >11:40:26,540 INFO program: Running... modinfo -F filename xts >11:40:26,585 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/xts.ko >11:40:26,589 INFO program: Running... modinfo -F filename lrw >11:40:26,633 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/lrw.ko >11:40:26,637 INFO program: Running... modinfo -F filename gf128mul >11:40:26,679 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/gf128mul.ko >11:40:26,683 INFO program: Running... modinfo -F filename sha256_generic >11:40:26,728 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/sha256_generic.ko >11:40:26,731 INFO program: Running... modinfo -F filename dm_crypt >11:40:26,777 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/dm-crypt.ko >11:40:26,781 INFO program: Running... modinfo -F filename dm_round_robin >11:40:26,826 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/dm-round-robin.ko >11:40:26,829 INFO program: Running... modinfo -F filename dm_multipath >11:40:26,872 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/dm-multipath.ko >11:40:26,876 INFO program: Running... modinfo -F filename linear >11:40:26,921 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/linear.ko >11:40:26,925 INFO program: Running... modinfo -F filename raid10 >11:40:26,971 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/raid10.ko >11:40:26,975 INFO program: Running... modinfo -F filename raid456 >11:40:27,020 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/raid456.ko >11:40:27,024 INFO program: Running... modinfo -F filename async_raid6_recov >11:40:27,069 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_raid6_recov.ko >11:40:27,072 INFO program: Running... modinfo -F filename async_memcpy >11:40:27,118 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_memcpy.ko >11:40:27,121 INFO program: Running... modinfo -F filename async_pq >11:40:27,167 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_pq.ko >11:40:27,171 INFO program: Running... modinfo -F filename raid6_pq >11:40:27,213 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/lib/raid6/raid6_pq.ko >11:40:27,217 INFO program: Running... modinfo -F filename async_xor >11:40:27,262 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_xor.ko >11:40:27,266 INFO program: Running... modinfo -F filename xor >11:40:27,311 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/xor.ko >11:40:27,315 INFO program: Running... modinfo -F filename async_tx >11:40:27,359 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/crypto/async_tx/async_tx.ko >11:40:27,363 INFO program: Running... modinfo -F filename raid1 >11:40:27,411 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/raid1.ko >11:40:27,415 INFO program: Running... modinfo -F filename raid0 >11:40:27,461 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/md/raid0.ko >11:40:27,465 INFO program: Running... modinfo -F filename iscsi_ibft >11:40:27,510 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/firmware/iscsi_ibft.ko >11:40:27,514 INFO program: Running... modinfo -F filename iscsi_boot_sysfs >11:40:27,558 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/iscsi_boot_sysfs.ko >11:40:27,562 INFO program: Running... modinfo -F filename edd >11:40:27,609 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/firmware/edd.ko >11:40:27,613 INFO program: Running... modinfo -F filename floppy >11:40:27,658 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/block/floppy.ko >11:40:27,661 INFO program: Running... modinfo -F filename scsi_dh_rdac >11:40:27,706 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/device_handler/scsi_dh_rdac.ko >11:40:27,709 INFO program: Running... modinfo -F filename scsi_dh_hp_sw >11:40:27,754 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/device_handler/scsi_dh_hp_sw.ko >11:40:27,758 INFO program: Running... modinfo -F filename scsi_dh_emc >11:40:27,801 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/device_handler/scsi_dh_emc.ko >11:40:27,804 INFO program: Running... modinfo -F filename scsi_dh_alua >11:40:27,850 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko >11:40:27,854 INFO program: Running... modinfo -F filename iscsi_tcp >11:40:27,899 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/iscsi_tcp.ko >11:40:27,902 INFO program: Running... modinfo -F filename libiscsi_tcp >11:40:27,948 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/libiscsi_tcp.ko >11:40:27,952 INFO program: Running... modinfo -F filename libiscsi >11:40:27,997 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/libiscsi.ko >11:40:28,001 INFO program: Running... modinfo -F filename scsi_transport_iscsi >11:40:28,046 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/drivers/scsi/scsi_transport_iscsi.ko >11:40:28,050 INFO program: Running... modinfo -F filename squashfs >11:40:28,095 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/fs/squashfs/squashfs.ko >11:40:28,099 INFO program: Running... modinfo -F filename cramfs >11:40:28,144 INFO program: /lib/modules/3.3.4-5.fc17.i686/kernel/fs/cramfs/cramfs.ko >11:41:19,459 INFO program: Running... /sbin/rsyslogd -c 4 -f /tmp/rsyslog_backend.conf -i /var/run/rsyslog_backend.pid >11:55:38,517 INFO program: Running... /usr/sbin/lokkit --selinux=enforcing >11:55:38,758 ERR program: Error running /usr/sbin/lokkit: No such file or directory >11:55:38,768 INFO program: Running... /usr/sbin/authconfig --update --nostart --useshadow --enablemd5 >11:55:38,918 INFO program: Running... /usr/sbin/lokkit --quiet --nostart -f --port=22:tcp >11:55:39,037 ERR program: Error running /usr/sbin/lokkit: No such file or directory >11:55:39,525 INFO program: Running... grub2-install --no-floppy /dev/sda >11:55:39,637 ERR program: Error running grub2-install: No such file or directory > > >/tmp/storage.log: >15:39:10,860 DEBUG storage: registered device format class PPCPRePBoot as prepboot >15:39:10,866 DEBUG storage: registered device format class DiskLabel as disklabel >15:39:10,868 DEBUG storage: registered device format class MDRaidMember as mdmember >15:39:10,870 DEBUG storage: registered device format class BIOSBoot as biosboot >15:39:10,872 DEBUG storage: registered device format class MultipathMember as multipath_member >15:39:10,916 DEBUG storage: registered device format class Ext2FS as ext2 >15:39:10,918 DEBUG storage: registered device format class Ext3FS as ext3 >15:39:10,919 DEBUG storage: registered device format class Ext4FS as ext4 >15:39:10,920 DEBUG storage: registered device format class FATFS as vfat >15:39:10,920 DEBUG storage: registered device format class EFIFS as efi >15:39:10,920 DEBUG storage: registered device format class BTRFS as btrfs >15:39:10,920 DEBUG storage: registered device format class GFS2 as gfs2 >15:39:10,921 DEBUG storage: registered device format class JFS as jfs >15:39:10,921 DEBUG storage: registered device format class ReiserFS as reiserfs >15:39:10,921 DEBUG storage: registered device format class XFS as xfs >15:39:10,921 DEBUG storage: registered device format class HFS as hfs >15:39:10,921 DEBUG storage: registered device format class AppleBootstrapFS as appleboot >15:39:10,921 DEBUG storage: registered device format class HFSPlus as hfs+ >15:39:10,922 DEBUG storage: registered device format class NTFS as ntfs >15:39:10,922 DEBUG storage: registered device format class NFS as nfs >15:39:10,925 DEBUG storage: registered device format class NFSv4 as nfs4 >15:39:10,925 DEBUG storage: registered device format class Iso9660FS as iso9660 >15:39:10,925 DEBUG storage: registered device format class NoDevFS as nodev >15:39:10,925 DEBUG storage: registered device format class DevPtsFS as devpts >15:39:10,927 DEBUG storage: registered device format class ProcFS as proc >15:39:10,928 DEBUG storage: registered device format class SysFS as sysfs >15:39:10,929 DEBUG storage: registered device format class TmpFS as tmpfs >15:39:10,931 DEBUG storage: registered device format class BindFS as bind >15:39:10,932 DEBUG storage: registered device format class SELinuxFS as selinuxfs >15:39:10,933 DEBUG storage: registered device format class USBFS as usbfs >15:39:10,936 DEBUG storage: registered device format class LVMPhysicalVolume as lvmpv >15:39:10,942 DEBUG storage: registered device format class SwapSpace as swap >15:39:11,041 DEBUG storage: registered device format class LUKS as luks >15:39:11,044 DEBUG storage: registered device format class DMRaidMember as dmraidmember >15:39:14,640 DEBUG storage: MultipathTopology._build_topology: >15:39:14,641 DEBUG storage: /etc/multipath.conf contents: >15:39:14,642 DEBUG storage: # multipath.conf written by anaconda >15:39:14,644 DEBUG storage: >15:39:14,644 DEBUG storage: defaults { >15:39:14,644 DEBUG storage: user_friendly_names yes >15:39:14,644 DEBUG storage: } >15:39:14,644 DEBUG storage: blacklist { >15:39:14,644 DEBUG storage: devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" >15:39:14,644 DEBUG storage: devnode "^hd[a-z]" >15:39:14,644 DEBUG storage: devnode "^dcssblk[0-9]*" >15:39:14,645 DEBUG storage: device { >15:39:14,645 DEBUG storage: vendor "DGC" >15:39:14,645 DEBUG storage: product "LUNZ" >15:39:14,645 DEBUG storage: } >15:39:14,649 DEBUG storage: device { >15:39:14,649 DEBUG storage: vendor "IBM" >15:39:14,649 DEBUG storage: product "S/390.*" >15:39:14,649 DEBUG storage: } >15:39:14,650 DEBUG storage: # don't count normal SATA devices as multipaths >15:39:14,651 DEBUG storage: device { >15:39:14,652 DEBUG storage: vendor "ATA" >15:39:14,654 DEBUG storage: } >15:39:14,655 DEBUG storage: # don't count 3ware devices as multipaths >15:39:14,656 DEBUG storage: device { >15:39:14,657 DEBUG storage: vendor "3ware" >15:39:14,658 DEBUG storage: } >15:39:14,660 DEBUG storage: device { >15:39:14,661 DEBUG storage: vendor "AMCC" >15:39:14,662 DEBUG storage: } >15:39:14,664 DEBUG storage: # nor highpoint devices >15:39:14,665 DEBUG storage: device { >15:39:14,666 DEBUG storage: vendor "HPT" >15:39:14,667 DEBUG storage: } >15:39:14,668 DEBUG storage: } >15:39:14,669 DEBUG storage: multipaths { >15:39:14,670 DEBUG storage: } >15:39:14,671 DEBUG storage: (end of /etc/multipath.conf) >15:39:14,755 INFO storage: MultipathTopology: found singlepath device: sda >15:39:14,758 INFO storage: MultipathTopology: found singlepath device: loop0 >15:39:14,760 INFO storage: MultipathTopology: found singlepath device: loop1 >15:39:14,761 INFO storage: MultipathTopology: found singlepath device: loop2 >15:39:14,761 INFO storage: MultipathTopology: found singlepath device: loop3 >15:39:14,761 INFO storage: MultipathTopology: found singlepath device: loop4 >15:39:14,762 INFO storage: MultipathTopology: found singlepath device: loop5 >15:39:14,762 INFO storage: MultipathTopology: found singlepath device: loop6 >15:39:14,762 INFO storage: MultipathTopology: found singlepath device: loop7 >15:39:14,762 INFO storage: MultipathTopology: found singlepath device: dm-0 >15:39:15,271 INFO storage: not going to create backup copy of non-existent /etc/mdadm.conf >15:39:15,275 INFO storage: DeviceTree.populate: ignoredDisks is [] ; exclusiveDisks is [] >15:39:15,430 DEBUG storage: MultipathTopology._build_topology: >15:39:15,433 DEBUG storage: /etc/multipath.conf contents: >15:39:15,434 DEBUG storage: # multipath.conf written by anaconda >15:39:15,435 DEBUG storage: >15:39:15,435 DEBUG storage: defaults { >15:39:15,435 DEBUG storage: user_friendly_names yes >15:39:15,435 DEBUG storage: } >15:39:15,436 DEBUG storage: blacklist { >15:39:15,436 DEBUG storage: devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" >15:39:15,436 DEBUG storage: devnode "^hd[a-z]" >15:39:15,436 DEBUG storage: devnode "^dcssblk[0-9]*" >15:39:15,436 DEBUG storage: device { >15:39:15,436 DEBUG storage: vendor "DGC" >15:39:15,436 DEBUG storage: product "LUNZ" >15:39:15,436 DEBUG storage: } >15:39:15,440 DEBUG storage: device { >15:39:15,440 DEBUG storage: vendor "IBM" >15:39:15,440 DEBUG storage: product "S/390.*" >15:39:15,441 DEBUG storage: } >15:39:15,442 DEBUG storage: # don't count normal SATA devices as multipaths >15:39:15,443 DEBUG storage: device { >15:39:15,445 DEBUG storage: vendor "ATA" >15:39:15,446 DEBUG storage: } >15:39:15,447 DEBUG storage: # don't count 3ware devices as multipaths >15:39:15,448 DEBUG storage: device { >15:39:15,450 DEBUG storage: vendor "3ware" >15:39:15,451 DEBUG storage: } >15:39:15,453 DEBUG storage: device { >15:39:15,454 DEBUG storage: vendor "AMCC" >15:39:15,455 DEBUG storage: } >15:39:15,456 DEBUG storage: # nor highpoint devices >15:39:15,457 DEBUG storage: device { >15:39:15,459 DEBUG storage: vendor "HPT" >15:39:15,461 DEBUG storage: } >15:39:15,462 DEBUG storage: } >15:39:15,463 DEBUG storage: multipaths { >15:39:15,464 DEBUG storage: } >15:39:15,465 DEBUG storage: (end of /etc/multipath.conf) >15:39:15,555 INFO storage: MultipathTopology: found singlepath device: sda >15:39:15,559 INFO storage: MultipathTopology: found singlepath device: loop0 >15:39:15,561 INFO storage: MultipathTopology: found singlepath device: loop1 >15:39:15,561 INFO storage: MultipathTopology: found singlepath device: loop2 >15:39:15,561 INFO storage: MultipathTopology: found singlepath device: loop3 >15:39:15,561 INFO storage: MultipathTopology: found singlepath device: loop4 >15:39:15,562 INFO storage: MultipathTopology: found singlepath device: loop5 >15:39:15,562 INFO storage: MultipathTopology: found singlepath device: loop6 >15:39:15,562 INFO storage: MultipathTopology: found singlepath device: loop7 >15:39:15,562 INFO storage: MultipathTopology: found singlepath device: dm-0 >15:39:15,563 INFO storage: devices to scan: ['sda', 'loop0', 'loop1', 'loop2', 'loop3', 'loop4', 'loop5', 'loop6', 'loop7', 'dm-0'] >15:39:15,577 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVLINKS': '/dev/disk/by-id/ata-QEMU_HARDDISK_QM00001', > 'DEVNAME': 'sda', > 'DEVPATH': '/devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda', > 'DEVTYPE': 'disk', > 'ID_ATA': '1', > 'ID_ATA_FEATURE_SET_SMART': '1', > 'ID_ATA_FEATURE_SET_SMART_ENABLED': '1', > 'ID_BUS': 'ata', > 'ID_MODEL': 'QEMU_HARDDISK', > 'ID_MODEL_ENC': 'QEMU\\x20HARDDISK\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20\\x20', > 'ID_REVISION': '0.12.1', > 'ID_SERIAL': 'QEMU_HARDDISK_QM00001', > 'ID_SERIAL_SHORT': 'QM00001', > 'ID_TYPE': 'disk', > 'MAJOR': '8', > 'MINOR': '0', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'TAGS': ':systemd:', > 'USEC_INITIALIZED': '123670788', > 'name': 'sda', > 'symlinks': ['/dev/disk/by-id/ata-QEMU_HARDDISK_QM00001'], > 'sysfs_path': '/devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda'} ; name: sda ; >15:39:15,578 INFO storage: scanning sda (/devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda)... >15:39:15,579 DEBUG storage: DeviceTree.getDeviceByName: name: sda ; >15:39:15,585 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:15,587 DEBUG storage: DeviceTree.addUdevDiskDevice: name: sda ; >15:39:15,592 INFO storage: sda is a disk >15:39:15,593 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:15,600 DEBUG storage: DiskDevice._setFormat: sda ; current: None ; type: None ; >15:39:15,602 INFO storage: added disk sda (id 0) to device tree >15:39:15,603 DEBUG storage: looking up parted Device: /dev/sda >15:39:15,612 DEBUG storage: DeviceTree.handleUdevDeviceFormat: name: sda ; >15:39:15,617 DEBUG storage: DeviceTree.handleUdevDiskLabelFormat: device: sda ; label_type: None ; >15:39:15,620 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:15,624 DEBUG storage: DiskDevice.setup: sda ; status: True ; controllable: True ; orig: False ; >15:39:15,640 DEBUG storage: DiskLabel.__init__: device: /dev/sda ; labelType: msdos ; exists: True ; >15:39:15,659 DEBUG storage: DiskLabel.__init__: device: /dev/sda ; labelType: msdos ; exists: False ; >15:39:15,663 DEBUG storage: DiskLabel.freshPartedDisk: device: /dev/sda ; labelType: msdos ; >15:39:15,670 DEBUG storage: Did not set pmbr_boot on parted.Disk instance -- > type: msdos primaryPartitionCount: 0 > lastPartitionNumber: -1 maxPrimaryPartitionCount: 4 > partitions: [] > device: <parted.device.Device object at 0xb5994f2c> > PedDisk: <_ped.Disk object at 0xb5994f8c> >15:39:15,673 DEBUG storage: getFormat('disklabel') returning DiskLabel instance >15:39:15,677 DEBUG storage: DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; >15:39:15,681 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:15,686 DEBUG storage: DiskDevice._setFormat: sda ; current: None ; type: None ; >15:39:15,690 INFO storage: registered action: [0] Destroy Format None on disk sda (id 0) >15:39:15,694 DEBUG storage: DeviceFormat.teardown: device: /dev/sda ; status: False ; type: None ; >15:39:15,700 DEBUG storage: DiskDevice._setFormat: sda ; current: None ; type: disklabel ; >15:39:15,701 INFO storage: registered action: [1] Create Format msdos disklabel on disk sda (id 0) >15:39:15,704 INFO storage: got device: DiskDevice instance (0xb59943ac) -- > name = sda status = True kids = 0 id = 0 > parents = [] > uuid = None size = 5120.0 > format = non-existent msdos disklabel > major = 8 minor = 0 exists = True protected = False > sysfs path = /devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda partedDevice = parted.Device instance -- > model: ATA QEMU HARDDISK path: /dev/sda type: 1 > sectorSize: 512 physicalSectorSize: 512 > length: 10485760 openCount: 0 readOnly: False > externalMode: False dirty: False bootDirty: False > host: 1 did: 0 busy: False > hardwareGeometry: (652, 255, 63) biosGeometry: (652, 255, 63) > PedDevice: <_ped.Device object at 0xb6f32e6c> > target size = 0 path = /dev/sda > format args = [] originalFormat = None removable = False partedDevice = <parted.device.Device object at 0xb5994acc> >15:39:15,707 INFO storage: got format: DiskLabel instance (0xb59c75ec) -- > type = disklabel name = partition table (MSDOS) status = False > device = /dev/sda uuid = None exists = False > options = None supported = False formattable = True resizable = False > type = msdos partition count = 0 sectorSize = 512 > align_offset = 0 align_grain = 2048 > partedDisk = parted.Disk instance -- > type: msdos primaryPartitionCount: 0 > lastPartitionNumber: -1 maxPrimaryPartitionCount: 4 > partitions: [] > device: <parted.device.Device object at 0xb5994f2c> > PedDisk: <_ped.Disk object at 0xb5994f8c> > origPartedDisk = <parted.disk.Disk object at 0xb5994eac> > partedDevice = parted.Device instance -- > model: ATA QEMU HARDDISK path: /dev/sda type: 1 > sectorSize: 512 physicalSectorSize: 512 > length: 10485760 openCount: 0 readOnly: False > externalMode: False dirty: False bootDirty: False > host: 1 did: 0 busy: False > hardwareGeometry: (652, 255, 63) biosGeometry: (652, 255, 63) > PedDevice: <_ped.Device object at 0xb5825c8c> > >15:39:15,710 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVNAME': 'loop0', > 'DEVPATH': '/devices/virtual/block/loop0', > 'DEVTYPE': 'disk', > 'ID_FS_TYPE': 'squashfs', > 'ID_FS_USAGE': 'filesystem', > 'ID_FS_VERSION': '1024.0', > 'MAJOR': '7', > 'MINOR': '0', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'USEC_INITIALIZED': '123535211', > 'name': 'loop0', > 'symlinks': [], > 'sysfs_path': '/devices/virtual/block/loop0'} ; name: loop0 ; >15:39:15,712 INFO storage: scanning loop0 (/devices/virtual/block/loop0)... >15:39:15,715 DEBUG storage: DeviceTree.getDeviceByName: name: loop0 ; >15:39:15,717 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:15,718 INFO storage: loop0 is a loop device >15:39:15,721 DEBUG storage: DeviceTree.addUdevLoopDevice: name: loop0 ; >15:39:15,723 DEBUG storage: DeviceTree.getDeviceByName: name: /run/initramfs/tmp/curl_fetch_url1/squashfs.img ; >15:39:15,726 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:15,727 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:15,730 DEBUG storage: FileDevice._setFormat: /run/initramfs/tmp/curl_fetch_url1/squashfs.img ; current: None ; type: None ; >15:39:15,731 INFO storage: added file /run/initramfs/tmp/curl_fetch_url1/squashfs.img (id 1) to device tree >15:39:15,734 DEBUG storage: FileDevice.addChild: kids: 0 ; name: /run/initramfs/tmp/curl_fetch_url1/squashfs.img ; >15:39:15,735 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:15,738 DEBUG storage: LoopDevice._setFormat: loop0 ; current: None ; type: None ; >15:39:15,740 INFO storage: added loop loop0 (id 2) to device tree >15:39:15,743 DEBUG storage: DeviceTree.handleUdevDeviceFormat: name: loop0 ; >15:39:15,744 DEBUG storage: DeviceTree.handleUdevDiskLabelFormat: device: loop0 ; label_type: None ; >15:39:15,745 DEBUG storage: getFormat('squashfs') returning DeviceFormat instance >15:39:15,789 DEBUG storage: LoopDevice.setup: loop0 ; status: True ; controllable: False ; orig: False ; >15:39:15,819 DEBUG storage: DiskLabel.__init__: device: /dev/loop0 ; labelType: None ; exists: True ; >15:39:15,829 WARN storage: disklabel detected but not usable on loop0 >15:39:15,831 INFO storage: type detected on 'loop0' is 'squashfs' >15:39:15,833 DEBUG storage: getFormat('squashfs') returning DeviceFormat instance >15:39:15,836 DEBUG storage: LoopDevice._setFormat: loop0 ; current: None ; type: None ; >15:39:15,867 DEBUG storage: looking up parted Device: /run/initramfs/tmp/curl_fetch_url1/squashfs.img >15:39:15,893 DEBUG storage: looking up parted Device: /dev/loop0 >15:39:15,896 INFO storage: got device: LoopDevice instance (0xb59c7f6c) -- > name = loop0 status = True kids = 0 id = 2 > parents = ['existing 143MB file /run/initramfs/tmp/curl_fetch_url1/squashfs.img (1)'] > uuid = None size = 143.5859375 > format = existing None > major = 0 minor = 0 exists = True protected = False > sysfs path = partedDevice = parted.Device instance -- > model: path: /dev/loop0 type: 5 > sectorSize: 512 physicalSectorSize: 512 > length: 294064 openCount: 0 readOnly: False > externalMode: False dirty: False bootDirty: False > host: 13107 did: 13107 busy: False > hardwareGeometry: (2297, 4, 32) biosGeometry: (2297, 4, 32) > PedDevice: <_ped.Device object at 0xb6ef03ec> > target size = 0 path = /dev/loop0 > format args = [] originalFormat = None >15:39:15,904 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVLINKS': '/dev/disk/by-label/Anaconda /dev/disk/by-uuid/1c95f55c-e231-4409-a46c-5f985cb07a01', > 'DEVNAME': 'loop1', > 'DEVPATH': '/devices/virtual/block/loop1', > 'DEVTYPE': 'disk', > 'ID_FS_LABEL': 'Anaconda', > 'ID_FS_LABEL_ENC': 'Anaconda', > 'ID_FS_TYPE': 'ext4', > 'ID_FS_USAGE': 'filesystem', > 'ID_FS_UUID': '1c95f55c-e231-4409-a46c-5f985cb07a01', > 'ID_FS_UUID_ENC': '1c95f55c-e231-4409-a46c-5f985cb07a01', > 'ID_FS_VERSION': '1.0', > 'MAJOR': '7', > 'MINOR': '1', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'USEC_INITIALIZED': '123535904', > 'name': 'loop1', > 'symlinks': ['/dev/disk/by-label/Anaconda', > '/dev/disk/by-uuid/1c95f55c-e231-4409-a46c-5f985cb07a01'], > 'sysfs_path': '/devices/virtual/block/loop1'} ; name: loop1 ; >15:39:15,906 INFO storage: scanning loop1 (/devices/virtual/block/loop1)... >15:39:15,909 DEBUG storage: DeviceTree.getDeviceByName: name: loop1 ; >15:39:15,911 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:15,913 INFO storage: loop1 is a loop device >15:39:15,918 DEBUG storage: DeviceTree.addUdevLoopDevice: name: loop1 ; >15:39:15,920 DEBUG storage: DeviceTree.getDeviceByName: name: /LiveOS/rootfs.img ; >15:39:15,922 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:15,924 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:15,928 DEBUG storage: FileDevice._setFormat: /LiveOS/rootfs.img ; current: None ; type: None ; >15:39:15,929 INFO storage: added file /LiveOS/rootfs.img (id 3) to device tree >15:39:15,932 DEBUG storage: FileDevice.addChild: kids: 0 ; name: /LiveOS/rootfs.img ; >15:39:15,933 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:15,936 DEBUG storage: LoopDevice._setFormat: loop1 ; current: None ; type: None ; >15:39:15,937 INFO storage: added loop loop1 (id 4) to device tree >15:39:15,939 DEBUG storage: DeviceTree.handleUdevDeviceFormat: name: loop1 ; >15:39:15,942 DEBUG storage: DeviceTree.handleUdevDiskLabelFormat: device: loop1 ; label_type: None ; >15:39:15,945 DEBUG storage: Ext4FS.supported: supported: True ; >15:39:15,947 DEBUG storage: getFormat('ext4') returning Ext4FS instance >15:39:15,948 DEBUG storage: device loop1 does not contain a disklabel >15:39:15,949 INFO storage: type detected on 'loop1' is 'ext4' >15:39:16,174 DEBUG storage: Ext4FS.supported: supported: True ; >15:39:16,177 DEBUG storage: getFormat('ext4') returning Ext4FS instance >15:39:16,180 DEBUG storage: LoopDevice._setFormat: loop1 ; current: None ; type: ext4 ; >15:39:16,183 INFO storage: got device: LoopDevice instance (0xb6ef2fec) -- > name = loop1 status = False kids = 0 id = 4 > parents = ['existing 0MB file /LiveOS/rootfs.img (3)'] > uuid = None size = 0 > format = existing ext4 filesystem > major = 0 minor = 0 exists = True protected = False > sysfs path = partedDevice = None > target size = 0 path = /dev/loop1 > format args = [] originalFormat = None >15:39:16,186 DEBUG storage: Ext4FS.supported: supported: True ; >15:39:16,188 INFO storage: got format: Ext4FS instance (0xb6ef24ac) -- > type = ext4 name = ext4 status = False > device = /dev/loop1 uuid = 1c95f55c-e231-4409-a46c-5f985cb07a01 exists = True > options = defaults supported = True formattable = True resizable = True > mountpoint = None mountopts = None > label = Anaconda size = 2048.0 targetSize = 2048.0 > >15:39:16,191 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVNAME': 'loop2', > 'DEVPATH': '/devices/virtual/block/loop2', > 'DEVTYPE': 'disk', > 'ID_FS_TYPE': 'DM_snapshot_cow', > 'ID_FS_USAGE': 'other', > 'MAJOR': '7', > 'MINOR': '2', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'USEC_INITIALIZED': '123545236', > 'name': 'loop2', > 'symlinks': [], > 'sysfs_path': '/devices/virtual/block/loop2'} ; name: loop2 ; >15:39:16,193 INFO storage: scanning loop2 (/devices/virtual/block/loop2)... >15:39:16,195 DEBUG storage: DeviceTree.getDeviceByName: name: loop2 ; >15:39:16,198 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:16,200 INFO storage: loop2 is a loop device >15:39:16,202 DEBUG storage: DeviceTree.addUdevLoopDevice: name: loop2 ; >15:39:16,205 DEBUG storage: DeviceTree.getDeviceByName: name: /overlay (deleted) ; >15:39:16,208 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:16,209 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:16,212 DEBUG storage: FileDevice._setFormat: /overlay (deleted) ; current: None ; type: None ; >15:39:16,214 INFO storage: added file /overlay (deleted) (id 5) to device tree >15:39:16,216 DEBUG storage: FileDevice.addChild: kids: 0 ; name: /overlay (deleted) ; >15:39:16,218 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:16,220 DEBUG storage: LoopDevice._setFormat: loop2 ; current: None ; type: None ; >15:39:16,222 INFO storage: added loop loop2 (id 6) to device tree >15:39:16,224 DEBUG storage: DeviceTree.handleUdevDeviceFormat: name: loop2 ; >15:39:16,227 DEBUG storage: DeviceTree.handleUdevDiskLabelFormat: device: loop2 ; label_type: None ; >15:39:16,228 DEBUG storage: getFormat('DM_snapshot_cow') returning DeviceFormat instance >15:39:16,230 DEBUG storage: LoopDevice.setup: loop2 ; status: False ; controllable: False ; orig: False ; >15:39:16,233 DEBUG storage: DiskLabel.__init__: device: /dev/loop2 ; labelType: None ; exists: True ; >15:39:16,242 WARN storage: disklabel detected but not usable on loop2 >15:39:16,244 INFO storage: type detected on 'loop2' is 'DM_snapshot_cow' >15:39:16,245 DEBUG storage: getFormat('DM_snapshot_cow') returning DeviceFormat instance >15:39:16,248 DEBUG storage: LoopDevice._setFormat: loop2 ; current: None ; type: None ; >15:39:16,250 INFO storage: got device: LoopDevice instance (0xb6ef416c) -- > name = loop2 status = False kids = 0 id = 6 > parents = ['existing 0MB file /overlay (deleted) (5)'] > uuid = None size = 0 > format = existing None > major = 0 minor = 0 exists = True protected = False > sysfs path = partedDevice = None > target size = 0 path = /dev/loop2 > format args = [] originalFormat = None >15:39:16,252 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVNAME': 'loop3', > 'DEVPATH': '/devices/virtual/block/loop3', > 'DEVTYPE': 'disk', > 'MAJOR': '7', > 'MINOR': '3', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'USEC_INITIALIZED': '123533614', > 'name': 'loop3', > 'symlinks': [], > 'sysfs_path': '/devices/virtual/block/loop3'} ; name: loop3 ; >15:39:16,253 INFO storage: ignoring loop3 (/devices/virtual/block/loop3) >15:39:16,253 DEBUG storage: lvm filter: adding loop3 to the reject list >15:39:16,259 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVNAME': 'loop4', > 'DEVPATH': '/devices/virtual/block/loop4', > 'DEVTYPE': 'disk', > 'MAJOR': '7', > 'MINOR': '4', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'USEC_INITIALIZED': '123500285', > 'name': 'loop4', > 'symlinks': [], > 'sysfs_path': '/devices/virtual/block/loop4'} ; name: loop4 ; >15:39:16,259 INFO storage: ignoring loop4 (/devices/virtual/block/loop4) >15:39:16,260 DEBUG storage: lvm filter: adding loop4 to the reject list >15:39:16,261 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVNAME': 'loop5', > 'DEVPATH': '/devices/virtual/block/loop5', > 'DEVTYPE': 'disk', > 'MAJOR': '7', > 'MINOR': '5', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'USEC_INITIALIZED': '123562440', > 'name': 'loop5', > 'symlinks': [], > 'sysfs_path': '/devices/virtual/block/loop5'} ; name: loop5 ; >15:39:16,265 INFO storage: ignoring loop5 (/devices/virtual/block/loop5) >15:39:16,266 DEBUG storage: lvm filter: adding loop5 to the reject list >15:39:16,267 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVNAME': 'loop6', > 'DEVPATH': '/devices/virtual/block/loop6', > 'DEVTYPE': 'disk', > 'MAJOR': '7', > 'MINOR': '6', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'USEC_INITIALIZED': '123504201', > 'name': 'loop6', > 'symlinks': [], > 'sysfs_path': '/devices/virtual/block/loop6'} ; name: loop6 ; >15:39:16,268 INFO storage: ignoring loop6 (/devices/virtual/block/loop6) >15:39:16,268 DEBUG storage: lvm filter: adding loop6 to the reject list >15:39:16,274 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVNAME': 'loop7', > 'DEVPATH': '/devices/virtual/block/loop7', > 'DEVTYPE': 'disk', > 'MAJOR': '7', > 'MINOR': '7', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'USEC_INITIALIZED': '123476057', > 'name': 'loop7', > 'symlinks': [], > 'sysfs_path': '/devices/virtual/block/loop7'} ; name: loop7 ; >15:39:16,274 INFO storage: ignoring loop7 (/devices/virtual/block/loop7) >15:39:16,274 DEBUG storage: lvm filter: adding loop7 to the reject list >15:39:16,274 DEBUG storage: Skipping a device mapper drive (dm-0) for now >15:39:16,403 INFO storage: devices to scan: ['dm-0'] >15:39:16,412 DEBUG storage: DeviceTree.addUdevDevice: info: {'ANACBIN': '/sbin', > 'DEVLINKS': '/dev/disk/by-id/dm-name-live-rw /dev/disk/by-label/Anaconda /dev/disk/by-uuid/1c95f55c-e231-4409-a46c-5f985cb07a01 /dev/mapper/live-rw', > 'DEVNAME': 'dm-0', > 'DEVPATH': '/devices/virtual/block/dm-0', > 'DEVTYPE': 'disk', > 'DM_NAME': 'live-rw', > 'DM_SBIN_PATH': '/sbin', > 'DM_SUSPENDED': '0', > 'DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG': '1', > 'DM_UDEV_PRIMARY_SOURCE_FLAG': '1', > 'DM_UDEV_RULES_VSN': '2', > 'ID_FS_LABEL': 'Anaconda', > 'ID_FS_LABEL_ENC': 'Anaconda', > 'ID_FS_TYPE': 'ext4', > 'ID_FS_USAGE': 'filesystem', > 'ID_FS_UUID': '1c95f55c-e231-4409-a46c-5f985cb07a01', > 'ID_FS_UUID_ENC': '1c95f55c-e231-4409-a46c-5f985cb07a01', > 'ID_FS_VERSION': '1.0', > 'MAJOR': '253', > 'MINOR': '0', > 'MPATH_SBIN_PATH': '/sbin', > 'SUBSYSTEM': 'block', > 'TAGS': ':systemd:', > 'USEC_INITIALIZED': '118815718', > 'name': 'dm-0', > 'symlinks': ['/dev/disk/by-id/dm-name-live-rw', > '/dev/disk/by-label/Anaconda', > '/dev/disk/by-uuid/1c95f55c-e231-4409-a46c-5f985cb07a01', > '/dev/mapper/live-rw'], > 'sysfs_path': '/devices/virtual/block/dm-0'} ; name: live-rw ; >15:39:16,413 INFO storage: scanning live-rw (/devices/virtual/block/dm-0)... >15:39:16,416 DEBUG storage: DeviceTree.getDeviceByName: name: live-rw ; >15:39:16,418 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:16,420 INFO storage: live-rw is a device-mapper device >15:39:16,422 DEBUG storage: DeviceTree.addUdevDMDevice: name: live-rw ; >15:39:16,425 DEBUG storage: DeviceTree.getDeviceByName: name: loop1 ; >15:39:16,429 DEBUG storage: DeviceTree.getDeviceByName returned existing 0MB loop loop1 (4) with existing ext4 filesystem >15:39:16,432 DEBUG storage: DeviceTree.getDeviceByName: name: loop2 ; >15:39:16,435 DEBUG storage: DeviceTree.getDeviceByName returned existing 0MB loop loop2 (6) >15:39:16,438 DEBUG storage: DeviceTree.getDeviceByName: name: live-rw ; >15:39:16,441 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:16,444 DEBUG storage: LoopDevice.addChild: kids: 0 ; name: loop2 ; >15:39:16,445 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:16,449 DEBUG storage: DMDevice._setFormat: live-rw ; current: None ; type: None ; >15:39:16,450 INFO storage: added dm live-rw (id 7) to device tree >15:39:16,453 DEBUG storage: DeviceTree.handleUdevDeviceFormat: name: live-rw ; >15:39:16,455 DEBUG storage: DeviceTree.handleUdevDiskLabelFormat: device: live-rw ; label_type: None ; >15:39:16,458 DEBUG storage: Ext4FS.supported: supported: True ; >15:39:16,460 DEBUG storage: getFormat('ext4') returning Ext4FS instance >15:39:16,461 DEBUG storage: device live-rw does not contain a disklabel >15:39:16,463 INFO storage: type detected on 'live-rw' is 'ext4' >15:39:16,609 DEBUG storage: Ext4FS.supported: supported: True ; >15:39:16,611 DEBUG storage: getFormat('ext4') returning Ext4FS instance >15:39:16,615 DEBUG storage: DMDevice._setFormat: live-rw ; current: None ; type: ext4 ; >15:39:16,618 DEBUG storage: looking up parted Device: /dev/mapper/live-rw >15:39:16,624 INFO storage: got device: DMDevice instance (0xb59c7fac) -- > name = live-rw status = True kids = 0 id = 7 > parents = ['existing 0MB loop loop2 (6)'] > uuid = None size = 2048.0 > format = existing ext4 filesystem > major = 0 minor = 0 exists = True protected = True > sysfs path = /devices/virtual/block/dm-0 partedDevice = parted.Device instance -- > model: Linux device-mapper (snapshot) path: /dev/mapper/live-rw type: 12 > sectorSize: 512 physicalSectorSize: 512 > length: 4194304 openCount: 0 readOnly: False > externalMode: False dirty: False bootDirty: False > host: 13107 did: 13107 busy: True > hardwareGeometry: (261, 255, 63) biosGeometry: (261, 255, 63) > PedDevice: <_ped.Device object at 0xb6f00b0c> > target size = 0 path = /dev/mapper/live-rw > format args = [] originalFormat = None target = None dmUuid = None >15:39:16,626 DEBUG storage: Ext4FS.supported: supported: True ; >15:39:16,628 INFO storage: got format: Ext4FS instance (0xb6ef2cac) -- > type = ext4 name = ext4 status = False > device = /dev/mapper/live-rw uuid = 1c95f55c-e231-4409-a46c-5f985cb07a01 exists = True > options = defaults supported = True formattable = True resizable = True > mountpoint = None mountopts = None > label = Anaconda size = 2048.0 targetSize = 2048.0 > >15:39:16,729 DEBUG storage: DiskDevice.teardown: sda ; status: True ; controllable: True ; >15:39:16,803 DEBUG storage: LoopDevice.teardown: loop0 ; status: True ; controllable: False ; >15:39:16,829 DEBUG storage: LoopDevice.teardown: loop1 ; status: False ; controllable: False ; >15:39:16,832 DEBUG storage: DMDevice.teardown: live-rw ; status: True ; controllable: False ; >15:39:16,834 INFO storage: not going to restore from backup of non-existent /etc/mdadm.conf >15:39:16,837 INFO storage: edd: MBR signature on sda is zero. new disk image? >15:39:16,837 INFO storage: edd: collected mbr signatures: {} >15:39:16,838 DEBUG storage: edd: data extracted from 0x80: > type: ATA, ata_device: 0 > channel: 0, mbr_signature: None > pci_dev: 00:01.1, scsi_id: None > scsi_lun: None, sectors: 10485760 >15:39:16,839 WARN storage: edd: directory does not exist: /sys/devices/pci0000:00/0000:00:01.1/host0/target0:0:0/0:0:0:0/block >15:39:16,841 ERR storage: edd: unable to match edd entry 0x80 >15:39:16,842 DEBUG storage: new bootloader stage1 device: None >15:39:16,877 DEBUG storage: Ext4FS.supported: supported: True ; >15:39:16,881 DEBUG storage: Ext4FS.supported: supported: True ; >15:39:16,887 DEBUG storage: new drive order: [] >15:39:16,889 DEBUG storage: checking whether disk sda has an empty extended >15:39:16,891 DEBUG storage: extended is None ; logicals is [] >15:39:18,219 DEBUG storage: getFormat('biosboot') returning BIOSBoot instance >15:39:18,222 DEBUG storage: PartitionDevice._setFormat: req0 ; >15:39:18,224 DEBUG storage: PartitionDevice._setFormat: req0 ; current: None ; type: biosboot ; >15:39:18,225 INFO storage: added partition req0 (id 8) to device tree >15:39:18,225 INFO storage: registered action: [2] Create Device partition req0 (id 8) >15:39:18,226 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:18,226 INFO storage: registered action: [3] Create Format biosboot on partition req0 (id 8) >15:39:18,228 DEBUG storage: DeviceTree.getDeviceByName: name: pv.01 ; >15:39:18,229 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:18,231 DEBUG storage: LVMPhysicalVolume.__init__: mountopts: ; mountpoint: ; fsprofile: ; label: ; >15:39:18,231 DEBUG storage: getFormat('lvmpv') returning LVMPhysicalVolume instance >15:39:18,233 DEBUG storage: PartitionDevice._setFormat: pv.01 ; >15:39:18,235 DEBUG storage: PartitionDevice._setFormat: pv.01 ; current: None ; type: lvmpv ; >15:39:18,235 INFO storage: added partition pv.01 (id 9) to device tree >15:39:18,235 INFO storage: registered action: [4] Create Device partition pv.01 (id 9) >15:39:18,236 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:18,236 INFO storage: registered action: [5] Create Format lvmpv on partition pv.01 (id 9) >15:39:18,237 DEBUG storage: DeviceTree.getDeviceByName: name: pv.01 ; >15:39:18,239 DEBUG storage: DeviceTree.getDeviceByName returned non-existent 1024MB partition pv.01 (9) with non-existent lvmpv >15:39:18,241 DEBUG storage: PartitionDevice.addChild: kids: 0 ; name: pv.01 ; >15:39:18,241 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:18,243 DEBUG storage: LVMVolumeGroupDevice._setFormat: vg_root ; current: None ; type: None ; >15:39:18,243 INFO storage: added lvmvg vg_root (id 10) to device tree >15:39:18,244 INFO storage: registered action: [6] Create Device lvmvg vg_root (id 10) >15:39:18,245 DEBUG storage: DeviceTree.getDeviceByName: name: vg_root ; >15:39:18,246 DEBUG storage: DeviceTree.getDeviceByName returned non-existent 992MB lvmvg vg_root (10) >15:39:18,248 DEBUG storage: DeviceTree.getDeviceByName: name: vg_root-lv_swap ; >15:39:18,249 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:18,251 DEBUG storage: SwapSpace.__init__: mountopts: ; mountpoint: ; fsprofile: ; label: ; >15:39:18,251 DEBUG storage: getFormat('swap') returning SwapSpace instance >15:39:18,253 DEBUG storage: LVMVolumeGroupDevice.addChild: kids: 0 ; name: vg_root ; >15:39:18,255 DEBUG storage: LVMLogicalVolumeDevice._setFormat: vg_root-lv_swap ; current: None ; type: swap ; >15:39:18,255 DEBUG storage: Adding vg_root-lv_swap/1024MB to vg_root >15:39:18,255 INFO storage: added lvmlv vg_root-lv_swap (id 11) to device tree >15:39:18,256 INFO storage: registered action: [7] Create Device lvmlv vg_root-lv_swap (id 11) >15:39:18,256 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:18,257 INFO storage: registered action: [8] Create Format swap on lvmlv vg_root-lv_swap (id 11) >15:39:18,258 DEBUG storage: DeviceTree.getDeviceByName: name: vg_root ; >15:39:18,259 DEBUG storage: DeviceTree.getDeviceByName returned non-existent 992MB lvmvg vg_root (10) >15:39:18,260 DEBUG storage: DeviceTree.getDeviceByName: name: vg_root-lv_root ; >15:39:18,262 DEBUG storage: DeviceTree.getDeviceByName returned None >15:39:18,263 DEBUG storage: Ext4FS.supported: supported: True ; >15:39:18,264 DEBUG storage: getFormat('ext4') returning Ext4FS instance >15:39:18,266 DEBUG storage: LVMVolumeGroupDevice.addChild: kids: 1 ; name: vg_root ; >15:39:18,268 DEBUG storage: LVMLogicalVolumeDevice._setFormat: vg_root-lv_root ; current: None ; type: ext4 ; >15:39:18,268 DEBUG storage: Adding vg_root-lv_root/1024MB to vg_root >15:39:18,268 INFO storage: added lvmlv vg_root-lv_root (id 12) to device tree >15:39:18,269 INFO storage: registered action: [9] Create Device lvmlv vg_root-lv_root (id 12) >15:39:18,269 DEBUG storage: getFormat('None') returning DeviceFormat instance >15:39:18,270 INFO storage: registered action: [10] Create Format ext4 filesystem mounted at / on lvmlv vg_root-lv_root (id 12) >11:39:19,007 DEBUG storage: doAutoPartition(<pyanaconda.Anaconda object at 0xb7589dec>) >11:39:19,007 DEBUG storage: doAutoPart: False >11:39:19,008 DEBUG storage: encryptedAutoPart: False >11:39:19,008 DEBUG storage: autoPartType: 2 >11:39:19,008 DEBUG storage: clearPartType: 1 >11:39:19,009 DEBUG storage: clearPartDisks: [] >11:39:19,010 DEBUG storage: autoPartitionRequests: >PartSpec instance (0xb6f9c6ac) -- > mountpoint = / lv = True singlePV = False btrfs = True > weight = 0 fstype = ext4 encrypted = True > size = 1024 maxSize = 51200 grow = True >PartSpec instance (0xb6f9c72c) -- > mountpoint = /home lv = True singlePV = False btrfs = True > weight = 0 fstype = ext4 encrypted = True > size = 500 maxSize = None grow = True >PartSpec instance (0xb6f9c7ac) -- > mountpoint = /boot lv = False singlePV = False btrfs = False > weight = 2000 fstype = ext4 encrypted = False > size = 500 maxSize = None grow = False >PartSpec instance (0xb582df6c) -- > mountpoint = None lv = False singlePV = False btrfs = False > weight = 5000 fstype = biosboot encrypted = False > size = 1 maxSize = None grow = False >PartSpec instance (0xb582df4c) -- > mountpoint = None lv = True singlePV = False btrfs = False > weight = 0 fstype = swap encrypted = True > size = 1008 maxSize = 2016 grow = True > >11:39:19,011 DEBUG storage: storage.disks: ['sda'] >11:39:19,012 DEBUG storage: storage.partitioned: ['sda'] >11:39:19,013 DEBUG storage: all names: ['/LiveOS/rootfs.img', '/overlay (deleted)', '/run/initramfs/tmp/curl_fetch_url1/squashfs.img', 'live-rw', 'loop0', 'loop1', 'loop2', 'pv.01', 'req0', 'sda', 'vg_root', 'vg_root-lv_root', 'vg_root-lv_swap'] >11:39:19,018 DEBUG storage: DiskDevice.setup: sda ; status: True ; controllable: True ; orig: False ; >11:39:19,021 DEBUG storage: removing all non-preexisting partitions ['pv.01(id 9)', 'req0(id 8)'] from disk(s) ['sda'] >11:39:19,022 DEBUG storage: allocatePartitions: disks=['sda'] ; partitions=['pv.01(id 9)', 'req0(id 8)'] >11:39:19,022 DEBUG storage: removing all non-preexisting partitions ['req0(id 8)', 'pv.01(id 9)'] from disk(s) ['sda'] >11:39:19,023 DEBUG storage: allocating partition: req0 ; id: 8 ; disks: ['sda'] ; >boot: True ; primary: False ; size: 1MB ; grow: False ; max_size: 0 >11:39:19,023 DEBUG storage: checking freespace on sda >11:39:19,024 DEBUG storage: getBestFreeSpaceRegion: disk=/dev/sda part_type=0 req_size=1MB boot=True best=None grow=False >11:39:19,025 DEBUG storage: current free range is 63-10485759 (5119MB) >11:39:19,026 DEBUG storage: updating use_disk to sda, type: 0 >11:39:19,026 DEBUG storage: new free: 63-10485759 / 5119MB >11:39:19,026 DEBUG storage: new free allows for 0 sectors of growth >11:39:19,027 DEBUG storage: found free space for bootable request >11:39:19,027 DEBUG storage: adjusted start sector from 63 to 2048 >11:39:19,029 DEBUG storage: created partition sda1 of 1MB and added it to /dev/sda >11:39:19,030 DEBUG storage: PartitionDevice._setPartedPartition: req0 ; >11:39:19,031 DEBUG storage: device req0 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994f0c> fileSystem: None > number: 1 path: /dev/sda1 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb724f94c> PedPartition: <_ped.Partition object at 0xb727326c> >11:39:19,033 DEBUG storage: PartitionDevice._setDisk: sda1 ; new: sda ; old: None ; >11:39:19,034 DEBUG storage: DiskDevice.addChild: kids: 0 ; name: sda ; >11:39:19,036 DEBUG storage: PartitionDevice._setPartedPartition: sda1 ; >11:39:19,037 DEBUG storage: device sda1 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994f0c> fileSystem: None > number: 1 path: /dev/sda1 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb724f98c> PedPartition: <_ped.Partition object at 0xb72732cc> >11:39:19,037 DEBUG storage: allocating partition: pv.01 ; id: 9 ; disks: ['sda'] ; >boot: False ; primary: False ; size: 1024MB ; grow: True ; max_size: 0 >11:39:19,038 DEBUG storage: checking freespace on sda >11:39:19,039 DEBUG storage: getBestFreeSpaceRegion: disk=/dev/sda part_type=0 req_size=1024MB boot=False best=None grow=True >11:39:19,039 DEBUG storage: current free range is 63-2047 (0MB) >11:39:19,040 DEBUG storage: current free range is 4096-10485759 (5118MB) >11:39:19,040 DEBUG storage: evaluating growth potential for new layout >11:39:19,041 DEBUG storage: calculating growth for disk /dev/sda >11:39:19,042 DEBUG storage: PartitionDevice._setPartedPartition: pv.01 ; >11:39:19,043 DEBUG storage: device pv.01 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994f0c> fileSystem: None > number: 2 path: /dev/sda2 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb724f5ac> PedPartition: <_ped.Partition object at 0xb727332c> >11:39:19,044 DEBUG storage: PartitionDevice._setDisk: sda2 ; new: sda ; old: None ; >11:39:19,046 DEBUG storage: DiskDevice.addChild: kids: 1 ; name: sda ; >11:39:19,047 DEBUG storage: adding request 8 to chunk 10485697 (63-10485759) on /dev/sda >11:39:19,047 DEBUG storage: adding request 9 to chunk 10485697 (63-10485759) on /dev/sda >11:39:19,047 DEBUG storage: Chunk.growRequests: 10485697 on /dev/sda start = 63 end = 10485759 >sectorSize = 512 > >11:39:19,048 DEBUG storage: req: PartitionRequest instance -- >id = 8 name = sda1 growable = False >base = 2048 growth = 0 max_grow = 0 >done = True >11:39:19,048 DEBUG storage: req: PartitionRequest instance -- >id = 9 name = sda2 growable = True >base = 2097152 growth = 0 max_grow = 4292870143 >done = False >11:39:19,049 DEBUG storage: 1 requests and 8386497 (4094MB) left in chunk >11:39:19,049 DEBUG storage: adding 8386497 (4094MB) to 9 (sda2) >11:39:19,049 DEBUG storage: new grow amount for request 9 (sda2) is 8386497 units, or 4094MB >11:39:19,050 DEBUG storage: request 8 (sda1) growth: 0 (0MB) size: 1MB >11:39:19,050 DEBUG storage: request 9 (sda2) growth: 8386497 (4094MB) size: 5118MB >11:39:19,051 DEBUG storage: disk /dev/sda growth: 8386497 (4094MB) >11:39:19,052 DEBUG storage: PartitionDevice._setPartedPartition: sda2 ; >11:39:19,052 DEBUG storage: device sda2 new partedPartition None >11:39:19,054 DEBUG storage: PartitionDevice._setDisk: pv.01 ; new: None ; old: sda ; >11:39:19,055 DEBUG storage: DiskDevice.removeChild: kids: 2 ; name: sda ; >11:39:19,056 DEBUG storage: total growth: 8386497 sectors >11:39:19,056 DEBUG storage: updating use_disk to sda, type: 0 >11:39:19,056 DEBUG storage: new free: 4096-10485759 / 5118MB >11:39:19,057 DEBUG storage: new free allows for 8386497 sectors of growth >11:39:19,058 DEBUG storage: created partition sda2 of 1024MB and added it to /dev/sda >11:39:19,059 DEBUG storage: PartitionDevice._setPartedPartition: pv.01 ; >11:39:19,060 DEBUG storage: device pv.01 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994f0c> fileSystem: None > number: 2 path: /dev/sda2 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb724a90c> PedPartition: <_ped.Partition object at 0xb727338c> >11:39:19,061 DEBUG storage: PartitionDevice._setDisk: sda2 ; new: sda ; old: None ; >11:39:19,063 DEBUG storage: DiskDevice.addChild: kids: 1 ; name: sda ; >11:39:19,065 DEBUG storage: PartitionDevice._setPartedPartition: sda2 ; >11:39:19,065 DEBUG storage: device sda2 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994f0c> fileSystem: None > number: 2 path: /dev/sda2 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb7256b4c> PedPartition: <_ped.Partition object at 0xb727341c> >11:39:19,066 DEBUG storage: growPartitions: disks=['sda'], partitions=['sda2(id 9)', 'sda1(id 8)'] >11:39:19,066 DEBUG storage: growable partitions are ['sda2'] >11:39:19,067 DEBUG storage: growing partitions on sda >11:39:19,067 DEBUG storage: adding request 9 to chunk 10485697 (63-10485759) on /dev/sda >11:39:19,068 DEBUG storage: adding request 8 to chunk 10485697 (63-10485759) on /dev/sda >11:39:19,068 DEBUG storage: disk sda has 1 chunks >11:39:19,068 DEBUG storage: Chunk.growRequests: 10485697 on /dev/sda start = 63 end = 10485759 >sectorSize = 512 > >11:39:19,069 DEBUG storage: req: PartitionRequest instance -- >id = 8 name = sda1 growable = False >base = 2048 growth = 0 max_grow = 0 >done = True >11:39:19,069 DEBUG storage: req: PartitionRequest instance -- >id = 9 name = sda2 growable = True >base = 2097152 growth = 0 max_grow = 4292870143 >done = False >11:39:19,069 DEBUG storage: 1 requests and 8386497 (4094MB) left in chunk >11:39:19,070 DEBUG storage: adding 8386497 (4094MB) to 9 (sda2) >11:39:19,070 DEBUG storage: new grow amount for request 9 (sda2) is 8386497 units, or 4094MB >11:39:19,071 DEBUG storage: partition sda1 (8): 0 >11:39:19,071 DEBUG storage: new geometry for sda1: parted.Geometry instance -- > start: 2048 end: 4095 length: 2048 > device: <parted.device.Device object at 0xb59c78cc> PedGeometry: <_ped.Geometry object at 0xb7256a6c> >11:39:19,072 DEBUG storage: partition sda2 (9): 0 >11:39:19,072 DEBUG storage: new geometry for sda2: parted.Geometry instance -- > start: 4096 end: 10485759 length: 10481664 > device: <parted.device.Device object at 0xb59c78cc> PedGeometry: <_ped.Geometry object at 0xb725678c> >11:39:19,073 DEBUG storage: removing all non-preexisting partitions ['sda1(id 8)', 'sda2(id 9)'] from disk(s) ['sda'] >11:39:19,074 DEBUG storage: PartitionDevice._setPartedPartition: sda1 ; >11:39:19,075 DEBUG storage: device sda1 new partedPartition None >11:39:19,076 DEBUG storage: PartitionDevice._setDisk: req0 ; new: None ; old: sda ; >11:39:19,078 DEBUG storage: DiskDevice.removeChild: kids: 2 ; name: sda ; >11:39:19,079 DEBUG storage: PartitionDevice._setPartedPartition: sda2 ; >11:39:19,079 DEBUG storage: device sda2 new partedPartition None >11:39:19,081 DEBUG storage: PartitionDevice._setDisk: pv.01 ; new: None ; old: sda ; >11:39:19,083 DEBUG storage: DiskDevice.removeChild: kids: 1 ; name: sda ; >11:39:19,083 DEBUG storage: back from removeNewPartitions >11:39:19,083 DEBUG storage: extended: None >11:39:19,084 DEBUG storage: setting req0 new geometry: parted.Geometry instance -- > start: 2048 end: 4095 length: 2048 > device: <parted.device.Device object at 0xb59c78cc> PedGeometry: <_ped.Geometry object at 0xb7256a6c> >11:39:19,085 DEBUG storage: PartitionDevice._setPartedPartition: req0 ; >11:39:19,086 DEBUG storage: device req0 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994f0c> fileSystem: None > number: 1 path: /dev/sda1 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb727540c> PedPartition: <_ped.Partition object at 0xb727344c> >11:39:19,087 DEBUG storage: PartitionDevice._setDisk: sda1 ; new: sda ; old: None ; >11:39:19,089 DEBUG storage: DiskDevice.addChild: kids: 0 ; name: sda ; >11:39:19,091 DEBUG storage: PartitionDevice._setPartedPartition: sda1 ; >11:39:19,091 DEBUG storage: device sda1 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994f0c> fileSystem: None > number: 1 path: /dev/sda1 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb7275b0c> PedPartition: <_ped.Partition object at 0xb727353c> >11:39:19,092 DEBUG storage: setting pv.01 new geometry: parted.Geometry instance -- > start: 4096 end: 10485759 length: 10481664 > device: <parted.device.Device object at 0xb59c78cc> PedGeometry: <_ped.Geometry object at 0xb725678c> >11:39:19,093 DEBUG storage: PartitionDevice._setPartedPartition: pv.01 ; >11:39:19,094 DEBUG storage: device pv.01 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994f0c> fileSystem: None > number: 2 path: /dev/sda2 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb727542c> PedPartition: <_ped.Partition object at 0xb727347c> >11:39:19,095 DEBUG storage: PartitionDevice._setDisk: sda2 ; new: sda ; old: None ; >11:39:19,097 DEBUG storage: DiskDevice.addChild: kids: 1 ; name: sda ; >11:39:19,098 DEBUG storage: PartitionDevice._setPartedPartition: sda2 ; >11:39:19,099 DEBUG storage: device sda2 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994f0c> fileSystem: None > number: 2 path: /dev/sda2 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb727748c> PedPartition: <_ped.Partition object at 0xb727359c> >11:39:19,100 DEBUG storage: new bootloader stage1 device: None >11:39:19,100 DEBUG storage: vg_root size is 5088MB >11:39:19,101 DEBUG storage: vg vg_root has 3040MB free >11:39:19,101 DEBUG storage: vg vg_root: 3040MB free ; lvs: ['lv_swap', 'lv_root'] >11:39:19,102 DEBUG storage: adding request 11 to chunk 159 on /dev/mapper/vg_root >11:39:19,102 DEBUG storage: adding request 12 to chunk 159 on /dev/mapper/vg_root >11:39:19,102 DEBUG storage: Chunk.growRequests: VGChunk instance -- >device = /dev/mapper/vg_root length = 159 size = 5088 >remaining = 1 pool = 95 >11:39:19,103 DEBUG storage: req: LVRequest instance -- >id = 11 name = vg_root-lv_swap growable = False >base = 32 growth = 0 max_grow = 0 >done = True >11:39:19,103 DEBUG storage: req: LVRequest instance -- >id = 12 name = vg_root-lv_root growable = True >base = 32 growth = 0 max_grow = 524256 >done = False >11:39:19,103 DEBUG storage: 1 requests and 95 (3040MB) left in chunk >11:39:19,104 DEBUG storage: adding 95 (3040MB) to 12 (vg_root-lv_root) >11:39:19,104 DEBUG storage: new grow amount for request 12 (vg_root-lv_root) is 95 units, or 3040MB >11:39:19,104 DEBUG storage: trying to set lv vg_root-lv_root size to 4064MB >11:39:19,105 DEBUG storage: vg_root size is 5088MB >11:39:19,105 DEBUG storage: vg vg_root has 3040MB free >11:39:19,109 DEBUG storage: _is_valid_disklabel(sda) returning True >11:39:19,109 DEBUG storage: _is_valid_size(sda) returning True >11:39:19,109 DEBUG storage: _is_valid_location(sda) returning True >11:39:19,110 DEBUG storage: _is_valid_format(sda) returning True >11:39:19,110 DEBUG storage: is_valid_stage1_device(sda) returning True >11:39:19,110 DEBUG storage: _gpt_disk_has_bios_boot(sda) returning True >11:39:19,111 DEBUG storage: is_valid_stage1_device(sda) returning True >11:39:19,111 DEBUG storage: no stage1 device: ['sda'] >11:39:19,111 DEBUG storage: stage1_drive is None >11:39:19,113 DEBUG storage: _is_valid_disklabel(sda) returning True >11:39:19,113 DEBUG storage: _is_valid_size(sda) returning True >11:39:19,114 DEBUG storage: _is_valid_location(sda) returning True >11:39:19,114 DEBUG storage: _is_valid_format(sda) returning True >11:39:19,114 DEBUG storage: is_valid_stage1_device(sda) returning True >11:39:19,115 DEBUG storage: _gpt_disk_has_bios_boot(sda) returning True >11:39:19,115 DEBUG storage: is_valid_stage1_device(sda) returning True >11:39:19,115 DEBUG storage: new bootloader stage1 device: sda >11:39:19,116 DEBUG storage: _is_valid_disklabel(sda) returning True >11:39:19,117 DEBUG storage: _is_valid_size(sda) returning True >11:39:19,117 DEBUG storage: _is_valid_location(sda) returning True >11:39:19,117 DEBUG storage: _is_valid_format(sda) returning True >11:39:19,118 DEBUG storage: is_valid_stage1_device(sda) returning True >11:39:19,118 DEBUG storage: _gpt_disk_has_bios_boot(sda) returning True >11:39:19,118 DEBUG storage: is_valid_stage1_device(sda) returning True >11:39:19,119 DEBUG storage: _is_valid_disklabel(vg_root-lv_root) returning True >11:39:19,120 DEBUG storage: _is_valid_size(vg_root-lv_root) returning True >11:39:19,120 DEBUG storage: _is_valid_location(vg_root-lv_root) returning True >11:39:19,120 DEBUG storage: _is_valid_partition(vg_root-lv_root) returning True >11:39:19,121 DEBUG storage: _is_valid_format(vg_root-lv_root) returning True >11:39:19,121 DEBUG storage: is_valid_stage2_device(vg_root-lv_root) returning True >11:39:19,151 DEBUG storage: LoopDevice.teardown: loop0 ; status: True ; controllable: False ; >11:39:19,175 DEBUG storage: LoopDevice.teardown: loop1 ; status: False ; controllable: False ; >11:39:19,178 DEBUG storage: DMDevice.teardown: live-rw ; status: True ; controllable: False ; >11:39:19,180 DEBUG storage: PartitionDevice.teardown: sda1 ; status: False ; controllable: True ; >11:39:19,182 DEBUG storage: LVMLogicalVolumeDevice.teardown: vg_root-lv_swap ; status: False ; controllable: True ; >11:39:19,183 DEBUG storage: LVMLogicalVolumeDevice.teardown: vg_root-lv_root ; status: False ; controllable: True ; >11:39:19,184 INFO storage: resetting parted disks... >11:39:19,186 DEBUG storage: DiskLabel.resetPartedDisk: device: /dev/sda ; >11:39:19,188 DEBUG storage: PartitionDevice.preCommitFixup: sda1 ; >11:39:19,189 DEBUG storage: PartitionDevice.preCommitFixup: sda2 ; >11:39:19,190 DEBUG storage: action: [0] Destroy Format None on disk sda (id 0) >11:39:19,191 DEBUG storage: action: [1] Create Format msdos disklabel on disk sda (id 0) >11:39:19,191 DEBUG storage: action: [2] Create Device partition sda1 (id 8) >11:39:19,191 DEBUG storage: action: [3] Create Format biosboot on partition sda1 (id 8) >11:39:19,192 DEBUG storage: action: [4] Create Device partition sda2 (id 9) >11:39:19,192 DEBUG storage: action: [5] Create Format lvmpv on partition sda2 (id 9) >11:39:19,192 DEBUG storage: action: [6] Create Device lvmvg vg_root (id 10) >11:39:19,193 DEBUG storage: action: [7] Create Device lvmlv vg_root-lv_swap (id 11) >11:39:19,193 DEBUG storage: action: [8] Create Format swap on lvmlv vg_root-lv_swap (id 11) >11:39:19,193 DEBUG storage: action: [9] Create Device lvmlv vg_root-lv_root (id 12) >11:39:19,194 DEBUG storage: action: [10] Create Format ext4 filesystem mounted at / on lvmlv vg_root-lv_root (id 12) >11:39:19,194 INFO storage: pruning action queue... >11:39:19,195 INFO storage: sorting actions... >11:39:19,197 DEBUG storage: action: [0] Destroy Format None on disk sda (id 0) >11:39:19,197 DEBUG storage: action: [1] Create Format msdos disklabel on disk sda (id 0) >11:39:19,197 DEBUG storage: action: [2] Create Device partition sda1 (id 8) >11:39:19,198 DEBUG storage: action: [4] Create Device partition sda2 (id 9) >11:39:19,198 DEBUG storage: action: [5] Create Format lvmpv on partition sda2 (id 9) >11:39:19,198 DEBUG storage: action: [6] Create Device lvmvg vg_root (id 10) >11:39:19,199 DEBUG storage: action: [9] Create Device lvmlv vg_root-lv_root (id 12) >11:39:19,199 DEBUG storage: action: [10] Create Format ext4 filesystem mounted at / on lvmlv vg_root-lv_root (id 12) >11:39:19,199 DEBUG storage: action: [7] Create Device lvmlv vg_root-lv_swap (id 11) >11:39:19,200 DEBUG storage: action: [8] Create Format swap on lvmlv vg_root-lv_swap (id 11) >11:39:19,200 DEBUG storage: action: [3] Create Format biosboot on partition sda1 (id 8) >11:39:19,200 INFO storage: executing action: [0] Destroy Format None on disk sda (id 0) >11:39:19,202 DEBUG storage: DiskDevice.setup: sda ; status: True ; controllable: True ; orig: True ; >11:39:19,204 DEBUG storage: DeviceFormat.destroy: device: /dev/sda ; status: False ; type: None ; >11:39:19,318 DEBUG storage: DiskDevice.teardown: sda ; status: True ; controllable: True ; >11:39:19,413 INFO storage: executing action: [1] Create Format msdos disklabel on disk sda (id 0) >11:39:19,418 DEBUG storage: DiskDevice.setup: sda ; status: True ; controllable: True ; orig: False ; >11:39:19,420 DEBUG storage: DiskLabel.create: device: /dev/sda ; status: False ; type: disklabel ; >11:39:19,421 DEBUG storage: DiskLabel.create: device: /dev/sda ; status: False ; type: disklabel ; >11:39:19,425 DEBUG storage: DiskLabel.commit: device: /dev/sda ; numparts: 0 ; >11:39:19,569 DEBUG storage: DiskDevice.updateSysfsPath: sda ; status: True ; >11:39:19,572 DEBUG storage: sda sysfsPath set to /devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda >11:39:19,618 INFO storage: executing action: [2] Create Device partition sda1 (id 8) >11:39:19,624 DEBUG storage: PartitionDevice.create: sda1 ; status: False ; >11:39:19,626 DEBUG storage: PartitionDevice.setupParents: kids: 0 ; name: sda1 ; orig: False ; >11:39:19,628 DEBUG storage: DiskDevice.setup: sda ; status: True ; controllable: True ; orig: False ; >11:39:19,630 DEBUG storage: DiskLabel.setup: device: /dev/sda ; status: False ; type: disklabel ; >11:39:19,632 DEBUG storage: DiskLabel.setup: device: /dev/sda ; status: False ; type: disklabel ; >11:39:19,636 DEBUG storage: PartitionDevice._create: sda1 ; status: False ; >11:39:19,640 DEBUG storage: DiskLabel.commit: device: /dev/sda ; numparts: 1 ; >11:39:19,729 DEBUG storage: post-commit partition path is /dev/sda1 >11:39:19,735 DEBUG storage: PartitionDevice._setPartedPartition: sda1 ; >11:39:19,736 DEBUG storage: device sda1 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994eac> fileSystem: None > number: 1 path: /dev/sda1 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb724afcc> PedPartition: <_ped.Partition object at 0xb7273b9c> >11:39:19,739 DEBUG storage: DeviceFormat.destroy: device: /dev/sda1 ; status: False ; type: None ; >11:39:19,769 DEBUG storage: PartitionDevice.setup: sda1 ; status: True ; controllable: True ; orig: False ; >11:39:19,772 DEBUG storage: PartitionDevice.updateSysfsPath: sda1 ; status: True ; >11:39:19,774 DEBUG storage: PartitionDevice.updateSysfsPath: sda1 ; status: True ; >11:39:19,775 DEBUG storage: sda1 sysfsPath set to /devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 >11:39:19,871 INFO storage: executing action: [4] Create Device partition sda2 (id 9) >11:39:19,876 DEBUG storage: PartitionDevice.create: sda2 ; status: False ; >11:39:19,878 DEBUG storage: PartitionDevice.setupParents: kids: 1 ; name: sda2 ; orig: False ; >11:39:19,880 DEBUG storage: DiskDevice.setup: sda ; status: True ; controllable: True ; orig: False ; >11:39:19,882 DEBUG storage: DiskLabel.setup: device: /dev/sda ; status: False ; type: disklabel ; >11:39:19,884 DEBUG storage: DiskLabel.setup: device: /dev/sda ; status: False ; type: disklabel ; >11:39:19,888 DEBUG storage: PartitionDevice._create: sda2 ; status: False ; >11:39:19,892 DEBUG storage: DiskLabel.commit: device: /dev/sda ; numparts: 2 ; >11:39:20,000 DEBUG storage: post-commit partition path is /dev/sda2 >11:39:20,005 DEBUG storage: PartitionDevice._setPartedPartition: sda2 ; >11:39:20,006 DEBUG storage: device sda2 new partedPartition parted.Partition instance -- > disk: <parted.disk.Disk object at 0xb5994eac> fileSystem: None > number: 2 path: /dev/sda2 type: 0 > name: None active: True busy: False > geometry: <parted.geometry.Geometry object at 0xb727e16c> PedPartition: <_ped.Partition object at 0xb727d0ec> >11:39:20,009 DEBUG storage: DeviceFormat.destroy: device: /dev/sda2 ; status: False ; type: None ; >11:39:20,052 DEBUG storage: PartitionDevice.setup: sda2 ; status: True ; controllable: True ; orig: False ; >11:39:20,059 DEBUG storage: PartitionDevice.updateSysfsPath: sda2 ; status: True ; >11:39:20,061 DEBUG storage: PartitionDevice.updateSysfsPath: sda2 ; status: True ; >11:39:20,062 DEBUG storage: sda2 sysfsPath set to /devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2 >11:39:20,162 INFO storage: executing action: [5] Create Format lvmpv on partition sda2 (id 9) >11:39:20,168 DEBUG storage: PartitionDevice.setup: sda2 ; status: True ; controllable: True ; orig: False ; >11:39:20,170 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 1 ; >11:39:20,171 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 2 ; >11:39:20,173 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 3 ; >11:39:20,175 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 4 ; >11:39:20,176 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 5 ; >11:39:20,178 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 8 ; >11:39:20,179 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 9 ; >11:39:20,181 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 10 ; >11:39:20,182 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 11 ; >11:39:20,184 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 12 ; >11:39:20,185 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 13 ; >11:39:20,187 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 14 ; >11:39:20,188 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda2 ; flag: 15 ; >11:39:20,190 DEBUG storage: PartitionDevice.setFlag: path: /dev/sda2 ; flag: 6 ; >11:39:20,193 DEBUG storage: DiskLabel.commitToDisk: device: /dev/sda ; numparts: 2 ; >11:39:20,210 DEBUG storage: LVMPhysicalVolume.create: device: /dev/sda2 ; status: None ; type: lvmpv ; >11:39:20,221 DEBUG storage: LVMPhysicalVolume.create: device: /dev/sda2 ; status: None ; type: lvmpv ; >11:39:20,226 DEBUG storage: LVMPhysicalVolume.destroy: device: /dev/sda2 ; status: None ; type: lvmpv ; >11:39:20,462 DEBUG storage: LVMPhysicalVolume.notifyKernel: device: /dev/sda2 ; type: lvmpv ; >11:39:20,573 DEBUG storage: PartitionDevice.updateSysfsPath: sda2 ; status: True ; >11:39:20,577 DEBUG storage: PartitionDevice.updateSysfsPath: sda2 ; status: True ; >11:39:20,578 DEBUG storage: sda2 sysfsPath set to /devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2 >11:39:20,628 INFO storage: executing action: [6] Create Device lvmvg vg_root (id 10) >11:39:20,634 DEBUG storage: LVMVolumeGroupDevice.create: vg_root ; status: False ; >11:39:20,636 DEBUG storage: LVMVolumeGroupDevice.setupParents: kids: 2 ; name: vg_root ; orig: False ; >11:39:20,638 DEBUG storage: PartitionDevice.setup: sda2 ; status: True ; controllable: True ; orig: False ; >11:39:20,640 DEBUG storage: LVMPhysicalVolume.setup: device: /dev/sda2 ; status: None ; type: lvmpv ; >11:39:20,645 DEBUG storage: LVMVolumeGroupDevice._create: vg_root ; status: False ; >11:39:20,848 DEBUG storage: LVMVolumeGroupDevice.setup: vg_root ; status: True ; controllable: True ; orig: False ; >11:39:20,857 DEBUG storage: LVMVolumeGroupDevice.updateSysfsPath: vg_root ; status: True ; >11:39:20,960 INFO storage: executing action: [9] Create Device lvmlv vg_root-lv_root (id 12) >11:39:20,967 DEBUG storage: LVMLogicalVolumeDevice.create: vg_root-lv_root ; status: False ; >11:39:20,969 DEBUG storage: LVMLogicalVolumeDevice.setupParents: kids: 0 ; name: vg_root-lv_root ; orig: False ; >11:39:20,972 DEBUG storage: LVMVolumeGroupDevice.setup: vg_root ; status: True ; controllable: True ; orig: False ; >11:39:20,979 DEBUG storage: LVMLogicalVolumeDevice._create: vg_root-lv_root ; status: False ; >11:39:21,330 DEBUG storage: LVMLogicalVolumeDevice.setup: vg_root-lv_root ; status: True ; controllable: True ; orig: False ; >11:39:21,338 DEBUG storage: LVMLogicalVolumeDevice.updateSysfsPath: vg_root-lv_root ; status: True ; >11:39:21,346 DEBUG storage: LVMLogicalVolumeDevice.getDMNode: vg_root-lv_root ; status: True ; >11:39:21,497 INFO storage: executing action: [10] Create Format ext4 filesystem mounted at / on lvmlv vg_root-lv_root (id 12) >11:39:21,505 DEBUG storage: LVMLogicalVolumeDevice.setup: vg_root-lv_root ; status: True ; controllable: True ; orig: False ; >11:39:21,509 DEBUG storage: Ext4FS.create: device: /dev/mapper/vg_root-lv_root ; status: False ; type: ext4 ; >11:39:21,512 DEBUG storage: Ext4FS.doFormat: device: /dev/mapper/vg_root-lv_root ; mountpoint: / ; type: ext4 ; >11:39:24,692 DEBUG storage: Ext4FS.notifyKernel: device: /dev/mapper/vg_root-lv_root ; type: ext4 ; >11:39:24,816 DEBUG storage: LVMLogicalVolumeDevice.updateSysfsPath: vg_root-lv_root ; status: True ; >11:39:24,820 DEBUG storage: LVMLogicalVolumeDevice.getDMNode: vg_root-lv_root ; status: True ; >11:39:24,898 INFO storage: executing action: [7] Create Device lvmlv vg_root-lv_swap (id 11) >11:39:24,905 DEBUG storage: LVMLogicalVolumeDevice.create: vg_root-lv_swap ; status: False ; >11:39:24,909 DEBUG storage: LVMLogicalVolumeDevice.setupParents: kids: 0 ; name: vg_root-lv_swap ; orig: False ; >11:39:24,912 DEBUG storage: LVMVolumeGroupDevice.setup: vg_root ; status: True ; controllable: True ; orig: False ; >11:39:24,919 DEBUG storage: LVMLogicalVolumeDevice._create: vg_root-lv_swap ; status: False ; >11:39:25,296 DEBUG storage: LVMLogicalVolumeDevice.setup: vg_root-lv_swap ; status: True ; controllable: True ; orig: False ; >11:39:25,303 DEBUG storage: LVMLogicalVolumeDevice.updateSysfsPath: vg_root-lv_swap ; status: True ; >11:39:25,309 DEBUG storage: LVMLogicalVolumeDevice.getDMNode: vg_root-lv_swap ; status: True ; >11:39:25,491 INFO storage: executing action: [8] Create Format swap on lvmlv vg_root-lv_swap (id 11) >11:39:25,498 DEBUG storage: LVMLogicalVolumeDevice.setup: vg_root-lv_swap ; status: True ; controllable: True ; orig: False ; >11:39:25,502 DEBUG storage: SwapSpace.create: device: /dev/mapper/vg_root-lv_swap ; status: None ; type: swap ; >11:39:25,509 DEBUG storage: SwapSpace.create: device: /dev/mapper/vg_root-lv_swap ; status: None ; type: swap ; >11:39:25,595 DEBUG storage: SwapSpace.notifyKernel: device: /dev/mapper/vg_root-lv_swap ; type: swap ; >11:39:25,713 DEBUG storage: LVMLogicalVolumeDevice.updateSysfsPath: vg_root-lv_swap ; status: True ; >11:39:25,718 DEBUG storage: LVMLogicalVolumeDevice.getDMNode: vg_root-lv_swap ; status: True ; >11:39:25,786 INFO storage: executing action: [3] Create Format biosboot on partition sda1 (id 8) >11:39:25,792 DEBUG storage: PartitionDevice.setup: sda1 ; status: True ; controllable: True ; orig: False ; >11:39:25,795 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 1 ; >11:39:25,798 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 2 ; >11:39:25,800 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 3 ; >11:39:25,802 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 4 ; >11:39:25,805 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 5 ; >11:39:25,808 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 6 ; >11:39:25,810 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 8 ; >11:39:25,812 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 9 ; >11:39:25,815 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 10 ; >11:39:25,817 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 11 ; >11:39:25,820 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 13 ; >11:39:25,822 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 14 ; >11:39:25,825 DEBUG storage: PartitionDevice.unsetFlag: path: /dev/sda1 ; flag: 15 ; >11:39:25,827 DEBUG storage: PartitionDevice.setFlag: path: /dev/sda1 ; flag: 12 ; >11:39:25,831 DEBUG storage: DiskLabel.commitToDisk: device: /dev/sda ; numparts: 2 ; >11:39:26,077 DEBUG storage: BIOSBoot.create: device: /dev/sda1 ; status: False ; type: biosboot ; >11:39:26,164 DEBUG storage: PartitionDevice.updateSysfsPath: sda1 ; status: True ; >11:39:26,169 DEBUG storage: PartitionDevice.updateSysfsPath: sda1 ; status: True ; >11:39:26,172 DEBUG storage: sda1 sysfsPath set to /devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 >11:39:26,248 DEBUG storage: Ext4FS.supported: supported: True ; >11:39:26,253 DEBUG storage: Ext4FS.supported: supported: True ; >11:39:26,260 DEBUG storage: vg_root size is 5088MB >11:39:26,262 DEBUG storage: looking up parted Device: /dev/mapper/vg_root-lv_swap >11:39:26,269 DEBUG storage: looking up parted Device: /dev/mapper/vg_root-lv_root >11:39:26,272 DEBUG storage: vg vg_root has 0MB free >11:39:26,273 DEBUG storage: vg_root size is 5088MB >11:39:26,276 DEBUG storage: vg vg_root has 0MB free >11:39:26,283 DEBUG storage: Ext4FS.supported: supported: True ; >11:39:26,297 DEBUG storage: LVMLogicalVolumeDevice.setup: vg_root-lv_swap ; status: True ; controllable: True ; orig: False ; >11:39:26,304 DEBUG storage: SwapSpace.setup: device: /dev/mapper/vg_root-lv_swap ; status: False ; type: swap ; >11:39:26,307 DEBUG storage: SwapSpace.setup: device: /dev/mapper/vg_root-lv_swap ; status: False ; type: swap ; >11:39:26,403 DEBUG storage: BindFS.supported: supported: False ; >11:39:26,405 DEBUG storage: getFormat('bind') returning BindFS instance >11:39:26,408 DEBUG storage: DirectoryDevice._setFormat: /dev ; current: None ; type: bind ; >11:39:26,411 DEBUG storage: TmpFS.supported: supported: False ; >11:39:26,413 DEBUG storage: getFormat('tmpfs') returning TmpFS instance >11:39:26,416 DEBUG storage: NoDevice._setFormat: tmpfs ; current: None ; type: tmpfs ; >11:39:26,419 DEBUG storage: DevPtsFS.supported: supported: False ; >11:39:26,420 DEBUG storage: getFormat('devpts') returning DevPtsFS instance >11:39:26,422 DEBUG storage: NoDevice._setFormat: devpts ; current: None ; type: devpts ; >11:39:26,425 DEBUG storage: SysFS.supported: supported: False ; >11:39:26,426 DEBUG storage: getFormat('sysfs') returning SysFS instance >11:39:26,433 DEBUG storage: NoDevice._setFormat: sysfs ; current: None ; type: sysfs ; >11:39:26,436 DEBUG storage: ProcFS.supported: supported: False ; >11:39:26,437 DEBUG storage: getFormat('proc') returning ProcFS instance >11:39:26,439 DEBUG storage: NoDevice._setFormat: proc ; current: None ; type: proc ; >11:39:26,442 DEBUG storage: SELinuxFS.supported: supported: False ; >11:39:26,443 DEBUG storage: getFormat('selinuxfs') returning SELinuxFS instance >11:39:26,445 DEBUG storage: NoDevice._setFormat: selinuxfs ; current: None ; type: selinuxfs ; >11:39:26,448 DEBUG storage: USBFS.supported: supported: False ; >11:39:26,450 DEBUG storage: getFormat('usbfs') returning USBFS instance >11:39:26,452 DEBUG storage: NoDevice._setFormat: usbfs ; current: None ; type: usbfs ; >11:39:26,455 DEBUG storage: LVMLogicalVolumeDevice.setup: vg_root-lv_root ; status: True ; controllable: True ; orig: False ; >11:39:26,460 INFO storage: set SELinux context for mountpoint / to system_u:object_r:root_t:s0 >11:39:26,569 INFO storage: set SELinux context for newly mounted filesystem root at / to system_u:object_r:root_t:s0 >11:39:26,578 DEBUG storage: DirectoryDevice.setup: /dev ; status: True ; controllable: True ; orig: False ; >11:39:26,581 INFO storage: set SELinux context for mountpoint /dev to system_u:object_r:device_t:s0 >11:39:26,603 INFO storage: set SELinux context for newly mounted filesystem root at /dev to system_u:object_r:device_t:s0 >11:39:26,611 DEBUG storage: NoDevice.setup: devpts ; status: False ; controllable: True ; orig: False ; >11:39:26,619 INFO storage: set SELinux context for mountpoint /dev/pts to system_u:object_r:devpts_t:s0 >11:39:26,642 INFO storage: set SELinux context for newly mounted filesystem root at /dev/pts to system_u:object_r:devpts_t:s0 >11:39:26,650 DEBUG storage: NoDevice.setup: tmpfs ; status: False ; controllable: True ; orig: False ; >11:39:26,652 INFO storage: set SELinux context for mountpoint /dev/shm to system_u:object_r:tmpfs_t:s0 >11:39:26,676 INFO storage: set SELinux context for newly mounted filesystem root at /dev/shm to system_u:object_r:tmpfs_t:s0 >11:39:26,684 DEBUG storage: NoDevice.setup: proc ; status: False ; controllable: True ; orig: False ; >11:39:26,688 INFO storage: set SELinux context for mountpoint /proc to None >11:39:26,713 INFO storage: set SELinux context for newly mounted filesystem root at /proc to None >11:39:26,774 DEBUG storage: NoDevice.setup: sysfs ; status: False ; controllable: True ; orig: False ; >11:39:26,777 INFO storage: set SELinux context for mountpoint /sys to system_u:object_r:sysfs_t:s0 >11:39:26,801 INFO storage: set SELinux context for newly mounted filesystem root at /sys to system_u:object_r:sysfs_t:s0 >11:39:26,809 DEBUG storage: NoDevice.setup: selinuxfs ; status: False ; controllable: True ; orig: False ; >11:39:26,811 INFO storage: set SELinux context for mountpoint /sys/fs/selinux to system_u:object_r:sysfs_t:s0 >11:39:26,836 INFO storage: set SELinux context for newly mounted filesystem root at /sys/fs/selinux to None >11:41:19,630 INFO storage: not writing out mpath configuration >11:41:19,651 INFO storage: not writing out mpath configuration >11:55:39,047 INFO storage: bootloader stage1 target device is sda >11:55:39,054 INFO storage: bootloader stage2 target device is vg_root-lv_root > > >/tmp/ifcfg.log: >15:39:18,061 DEBUG ifcfg: Network.update() called >15:39:18,139 DEBUG ifcfg: /etc/sysconfig/network-scripts/ifcfg-eth0: ># Generated by dracut initrd >DEVICE=eth0 >ONBOOT=yes >NETBOOT=yes >UUID=06561c93-5dda-4a00-8956-fda8958a799a >BOOTPROTO=dhcp >HWADDR="00:16:3e:55:f8:21" >TYPE=Ethernet >NAME="Boot Disk" >DNS1=10.16.255.2 > >15:39:18,142 DEBUG ifcfg: NetworkDevice eth0: > >15:39:18,142 DEBUG ifcfg: loadIfcfgFile eth0 from /etc/sysconfig/network-scripts/ifcfg-eth0 >15:39:18,142 DEBUG ifcfg: NetworkDevice eth0: >UUID="06561c93-5dda-4a00-8956-fda8958a799a" >NETBOOT="yes" >HWADDR="00:16:3e:55:f8:21" >BOOTPROTO="dhcp" >DEVICE="eth0" >DNS1="10.16.255.2" >TYPE="Ethernet" >ONBOOT="yes" >NAME="Boot Disk" > >15:39:18,153 DEBUG ifcfg: NetworkDevice eth0 set: NM_CONTROLLED=yes >15:39:18,154 DEBUG ifcfg: NetworkDevice eth0 set: BOOTPROTO=dhcp >15:39:18,155 DEBUG ifcfg: NetworkDevice eth0 set: DHCPCLASS=ipa-lab-vms >15:39:18,156 DEBUG ifcfg: NetworkDevice eth0 set: IPV6INIT=yes >15:39:18,156 DEBUG ifcfg: NetworkDevice eth0 set: ONBOOT=yes >15:39:18,156 DEBUG ifcfg: NetworkDevice eth0 set: DNS1=10.16.255.2 >11:41:19,634 DEBUG ifcfg: Network.write() called >11:41:19,636 DEBUG ifcfg: /etc/sysconfig/network-scripts/ifcfg-eth0: ># Generated by dracut initrd >DEVICE=eth0 >ONBOOT=yes >NETBOOT=yes >UUID=06561c93-5dda-4a00-8956-fda8958a799a >BOOTPROTO=dhcp >HWADDR="00:16:3e:55:f8:21" >TYPE=Ethernet >NAME="Boot Disk" >DNS1=10.16.255.2 > >11:41:19,638 DEBUG ifcfg: NetworkDevice eth0: >IPV6INIT="yes" >UUID="06561c93-5dda-4a00-8956-fda8958a799a" >DHCPCLASS="ipa-lab-vms" >NM_CONTROLLED="yes" >NETBOOT="yes" >HWADDR="00:16:3e:55:f8:21" >BOOTPROTO="dhcp" >DEVICE="eth0" >DNS1="10.16.255.2" >TYPE="Ethernet" >ONBOOT="yes" >NAME="Boot Disk" > >11:41:19,639 DEBUG ifcfg: writeIfcfgFile eth0 to /etc/sysconfig/network-scripts/ifcfg-eth0 >11:55:38,271 DEBUG ifcfg: Network.write() called >11:55:38,276 DEBUG ifcfg: /etc/sysconfig/network-scripts/ifcfg-eth0: >IPV6INIT="yes" >UUID="06561c93-5dda-4a00-8956-fda8958a799a" >DHCPCLASS="ipa-lab-vms" >NM_CONTROLLED="yes" >NETBOOT="yes" >HWADDR="00:16:3e:55:f8:21" >BOOTPROTO="dhcp" >DEVICE="eth0" >DNS1="10.16.255.2" >TYPE="Ethernet" >ONBOOT="yes" >NAME="Boot Disk" > >11:55:38,276 DEBUG ifcfg: NetworkDevice eth0: >IPV6INIT="yes" >UUID="06561c93-5dda-4a00-8956-fda8958a799a" >DHCPCLASS="ipa-lab-vms" >NM_CONTROLLED="yes" >NETBOOT="yes" >HWADDR="00:16:3e:55:f8:21" >BOOTPROTO="dhcp" >DEVICE="eth0" >DNS1="10.16.255.2" >TYPE="Ethernet" >ONBOOT="yes" >NAME="Boot Disk" > >11:55:38,276 DEBUG ifcfg: writeIfcfgFile eth0 to /etc/sysconfig/network-scripts/ifcfg-eth0 not needed > > >/tmp/yum.log: >[2012-05-30 11:39:27,140] INFO_2 : Loaded plugins: blacklist, langpacks, whiteout >[2012-05-30 11:39:27,141] DEBUG : Adding en_US to language list >[2012-05-30 11:39:27,145] DEBUG : Config time: 0.203 >[2012-05-30 11:39:27,153] WARN : Repo Fedora 17 - i386 - Test Updates Debug contains -source or -debuginfo, excluding >[2012-05-30 11:39:27,154] WARN : Repo Fedora 17 - Test Updates Source contains -source or -debuginfo, excluding >[2012-05-30 11:39:27,159] WARN : Repo Fedora 17 - i386 - Updates - Debug contains -source or -debuginfo, excluding >[2012-05-30 11:39:27,160] WARN : Repo Fedora 17 - Updates Source contains -source or -debuginfo, excluding >[2012-05-30 11:39:27,164] WARN : Repo Fedora 17 - i386 - Debug contains -source or -debuginfo, excluding >[2012-05-30 11:39:27,165] WARN : Repo Fedora 17 - Source contains -source or -debuginfo, excluding >[2012-05-30 11:39:53,802] DEBUG : repo time: 26.069 >[2012-05-30 11:39:54,662] DEBUG : repo time: 0.856 >[2012-05-30 11:39:55,505] DEBUG : repo time: 0.837 >[2012-05-30 11:39:56,374] DEBUG : repo time: 0.865 >[2012-05-30 11:39:57,219] DEBUG : repo time: 0.839 >[2012-05-30 11:39:57,223] DEBUG : Setting up Package Sacks >[2012-05-30 11:39:57,346] DEBUG : rpmdb time: 0.001 >[2012-05-30 11:39:57,760] DEBUG : pkgsack time: 0.536 >[2012-05-30 11:39:57,763] DEBUG : Setting up Package Sacks >[2012-05-30 11:39:58,240] DEBUG : pkgsack time: 0.477 >[2012-05-30 11:39:58,244] DEBUG : Setting up Package Sacks >[2012-05-30 11:39:59,207] DEBUG : pkgsack time: 0.963 >[2012-05-30 11:39:59,211] DEBUG : Setting up Package Sacks >[2012-05-30 11:39:59,813] DEBUG : pkgsack time: 0.601 >[2012-05-30 11:39:59,817] DEBUG : Setting up Package Sacks >[2012-05-30 11:40:00,356] DEBUG : pkgsack time: 0.539 >[2012-05-30 11:40:01,614] DEBUG : group time: 1.256 >[2012-05-30 11:40:02,264] DEBUG : Obs Init time: 0.450 >[2012-05-30 11:40:03,750] DEBUG : Checking for virtual provide or file-provide for krb5-pkinit-openssl >[2012-05-30 11:40:10,312] DEBUG : Checking for virtual provide or file-provide for systemd-units >[2012-05-30 11:40:11,124] DEBUG : No package named iprutils available to be installed >[2012-05-30 11:40:11,170] DEBUG : No package named s390utils available to be installed >[2012-05-30 11:40:11,172] DEBUG : No package named ppc64-utils available to be installed >[2012-05-30 11:40:11,172] DEBUG : No package named silo available to be installed >[2012-05-30 11:40:11,243] DEBUG : No package named automake15 available to be installed >[2012-05-30 11:40:11,248] DEBUG : No package named automake16 available to be installed >[2012-05-30 11:40:32,485] DEBUG : Building updates object >[2012-05-30 11:40:32,990] DEBUG : up:simple updates time: 0.421 >[2012-05-30 11:40:32,996] DEBUG : up:obs time: 0.006 >[2012-05-30 11:40:32,997] DEBUG : up:condense time: 0.000 >[2012-05-30 11:40:32,997] DEBUG : updates time: 0.511 >[2012-05-30 11:40:33,001] DEBUG : TSINFO: Marking 389-ds-base-libs-1.2.11.1-1.fc17.i686 as install for 389-ds-base-devel-1.2.11.1-1.fc17.i686 >[2012-05-30 11:40:33,002] DEBUG : Quick matched 389-ds-base-libs-1.2.11.1-1.fc17.i686 to require for libslapd.so.0 >[2012-05-30 11:40:33,046] DEBUG : TSINFO: Marking ppp-2.4.5-19.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,048] DEBUG : TSINFO: Marking 1:NetworkManager-glib-0.9.4.0-9.git20120521.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,050] DEBUG : TSINFO: Marking 1:wpa_supplicant-1.0-0.4.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,051] DEBUG : TSINFO: Marking mobile-broadband-provider-info-1.20110218-2.fc17.noarch as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,053] DEBUG : TSINFO: Marking libnl3-3.2.7-1.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,055] DEBUG : TSINFO: Marking glib2-2.32.1-1.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,056] DEBUG : TSINFO: Marking dbus-glib-0.92-3.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,058] DEBUG : TSINFO: Marking 1:dbus-1.4.10-4.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,060] DEBUG : TSINFO: Marking ModemManager-0.5.2.0-1.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,062] DEBUG : TSINFO: Marking udev-182-1.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,065] DEBUG : TSINFO: Marking systemd-sysv-44-12.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,066] DEBUG : TSINFO: Marking libuuid-2.21.1-1.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,070] DEBUG : TSINFO: Marking polkit-0.104-6.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,071] DEBUG : TSINFO: Marking nspr-4.9-2.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,072] DEBUG : Quick matched nspr-4.9-2.fc17.i686 to require for libplc4.so >[2012-05-30 11:40:33,073] DEBUG : TSINFO: Marking nss-util-3.13.4-2.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,075] DEBUG : Quick matched 1:NetworkManager-glib-0.9.4.0-9.git20120521.fc17.i686 to require for libnm-glib.so.4 >[2012-05-30 11:40:33,076] DEBUG : Quick matched libnl3-3.2.7-1.fc17.i686 to require for libnl-genl-3.so.200 >[2012-05-30 11:40:33,076] DEBUG : Quick matched libnl3-3.2.7-1.fc17.i686 to require for libnl-3.so.200 >[2012-05-30 11:40:33,077] DEBUG : TSINFO: Marking libgudev1-182-1.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,078] DEBUG : Quick matched glib2-2.32.1-1.fc17.i686 to require for libgobject-2.0.so.0 >[2012-05-30 11:40:33,078] DEBUG : Quick matched glib2-2.32.1-1.fc17.i686 to require for libgmodule-2.0.so.0 >[2012-05-30 11:40:33,078] DEBUG : Quick matched glib2-2.32.1-1.fc17.i686 to require for libglib-2.0.so.0 >[2012-05-30 11:40:33,079] DEBUG : Quick matched glib2-2.32.1-1.fc17.i686 to require for libgio-2.0.so.0 >[2012-05-30 11:40:33,082] DEBUG : TSINFO: Marking 1:dbus-libs-1.4.10-4.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,083] DEBUG : TSINFO: Marking dnsmasq-2.59-5.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,085] DEBUG : TSINFO: Marking avahi-autoipd-0.6.30-7.fc17.i686 as install for 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >[2012-05-30 11:40:33,090] DEBUG : TSINFO: Marking libacl-2.2.51-5.fc17.i686 as install for acl-2.2.51-5.fc17.i686 >[2012-05-30 11:40:33,092] DEBUG : TSINFO: Marking libattr-2.4.46-5.fc17.i686 as install for acl-2.2.51-5.fc17.i686 >[2012-05-30 11:40:33,093] DEBUG : Quick matched libacl-2.2.51-5.fc17.i686 to require for libacl.so.1 >[2012-05-30 11:40:33,112] DEBUG : TSINFO: Marking audit-libs-2.2.1-1.fc17.i686 as install for audit-2.2.1-1.fc17.i686 >[2012-05-30 11:40:33,114] DEBUG : TSINFO: Marking tcp_wrappers-libs-7.6-69.fc17.i686 as install for audit-2.2.1-1.fc17.i686 >[2012-05-30 11:40:33,115] DEBUG : Quick matched audit-libs-2.2.1-1.fc17.i686 to require for libaudit.so.1 >[2012-05-30 11:40:33,126] DEBUG : TSINFO: Marking python-2.7.3-6.fc17.i686 as install for authconfig-6.2.1-1.fc17.i686 >[2012-05-30 11:40:33,128] DEBUG : TSINFO: Marking libpwquality-1.0.0-2.fc17.i686 as install for authconfig-6.2.1-1.fc17.i686 >[2012-05-30 11:40:33,134] DEBUG : TSINFO: Marking pam-1.1.5-6.fc17.i686 as install for authconfig-6.2.1-1.fc17.i686 >[2012-05-30 11:40:33,136] DEBUG : TSINFO: Marking newt-python-0.52.14-2.fc17.i686 as install for authconfig-6.2.1-1.fc17.i686 >[2012-05-30 11:40:33,176] DEBUG : TSINFO: Marking 4:perl-5.14.2-211.fc17.i686 as install for autoconf-2.68-3.fc17.noarch >[2012-05-30 11:40:33,177] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl >[2012-05-30 11:40:33,178] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl >[2012-05-30 11:40:33,178] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(vars) >[2012-05-30 11:40:33,178] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(strict) >[2012-05-30 11:40:33,178] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(POSIX) >[2012-05-30 11:40:33,179] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(IO::File) >[2012-05-30 11:40:33,179] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(Getopt::Long) >[2012-05-30 11:40:33,180] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(File::stat) >[2012-05-30 11:40:33,184] DEBUG : TSINFO: Marking perl-PathTools-3.33-211.fc17.i686 as install for autoconf-2.68-3.fc17.noarch >[2012-05-30 11:40:33,186] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(File::Copy) >[2012-05-30 11:40:33,187] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(File::Compare) >[2012-05-30 11:40:33,187] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(File::Basename) >[2012-05-30 11:40:33,188] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(Exporter) >[2012-05-30 11:40:33,188] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(Errno) >[2012-05-30 11:40:33,189] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(DynaLoader) >[2012-05-30 11:40:33,190] DEBUG : Quick matched 4:perl-5.14.2-211.fc17.i686 to require for perl(Data::Dumper) >[2012-05-30 11:40:33,193] DEBUG : TSINFO: Marking perl-Carp-1.22-2.fc17.noarch as install for autoconf-2.68-3.fc17.noarch >[2012-05-30 11:40:33,195] DEBUG : TSINFO: Marking info-4.13a-16.fc17.i686 as install for autoconf-2.68-3.fc17.noarch >[2012-05-30 11:40:33,225] DEBUG : TSINFO: Marking sed-4.2.1-8.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,232] DEBUG : TSINFO: Marking kmod-7-1.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,234] DEBUG : TSINFO: Marking zlib-1.2.5-6.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,236] DEBUG : TSINFO: Marking libxml2-2.7.8-7.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,237] DEBUG : Quick matched libxml2-2.7.8-7.fc17.i686 to require for libxml2.so.2 >[2012-05-30 11:40:33,238] DEBUG : TSINFO: Marking libtirpc-0.2.2-2.1.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,239] DEBUG : TSINFO: Marking cyrus-sasl-lib-2.1.23-29.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,241] DEBUG : TSINFO: Marking openldap-2.4.30-2.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,241] DEBUG : Quick matched openldap-2.4.30-2.fc17.i686 to require for liblber-2.4.so.2 >[2012-05-30 11:40:33,245] DEBUG : TSINFO: Marking krb5-libs-1.10-6.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,245] DEBUG : Quick matched krb5-libs-1.10-6.fc17.i686 to require for libkrb5.so.3 >[2012-05-30 11:40:33,246] DEBUG : Quick matched krb5-libs-1.10-6.fc17.i686 to require for libk5crypto.so.3 >[2012-05-30 11:40:33,247] DEBUG : TSINFO: Marking hesiod-3.1.0-21.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,248] DEBUG : TSINFO: Marking libcom_err-1.42-4.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,250] DEBUG : TSINFO: Marking grep-2.12-1.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,251] DEBUG : TSINFO: Marking gawk-4.0.0-4.fc17.i686 as install for 1:autofs-5.0.6-13.fc17.i686 >[2012-05-30 11:40:33,287] DEBUG : TSINFO: Marking ncurses-libs-5.9-4.20120204.fc17.i686 as install for bash-4.2.28-1.fc17.i686 >[2012-05-30 11:40:33,299] DEBUG : TSINFO: Marking 32:bind-libs-9.9.0-4.fc17.i686 as install for 32:bind-utils-9.9.0-4.fc17.i686 >[2012-05-30 11:40:33,300] DEBUG : Quick matched 32:bind-libs-9.9.0-4.fc17.i686 to require for libisccfg.so.90 >[2012-05-30 11:40:33,300] DEBUG : Quick matched 32:bind-libs-9.9.0-4.fc17.i686 to require for libisccc.so.90 >[2012-05-30 11:40:33,300] DEBUG : Quick matched 32:bind-libs-9.9.0-4.fc17.i686 to require for libisc.so.90 >[2012-05-30 11:40:33,301] DEBUG : TSINFO: Marking libidn-1.24-1.fc17.i686 as install for 32:bind-utils-9.9.0-4.fc17.i686 >[2012-05-30 11:40:33,302] DEBUG : Quick matched libidn-1.24-1.fc17.i686 to require for libidn.so.11 >[2012-05-30 11:40:33,306] DEBUG : TSINFO: Marking 1:openssl-1.0.0j-1.fc17.i686 as install for 32:bind-utils-9.9.0-4.fc17.i686 >[2012-05-30 11:40:33,307] DEBUG : TSINFO: Marking libcap-2.22-2.fc17.i686 as install for 32:bind-utils-9.9.0-4.fc17.i686 >[2012-05-30 11:40:33,323] DEBUG : TSINFO: Marking libstdc++-4.7.0-5.fc17.i686 as install for binutils-2.22.52.0.1-10.fc17.i686 >[2012-05-30 11:40:33,324] DEBUG : Quick matched libstdc++-4.7.0-5.fc17.i686 to require for libstdc++.so.6(GLIBCXX_3.4.11) >[2012-05-30 11:40:33,324] DEBUG : Quick matched libstdc++-4.7.0-5.fc17.i686 to require for libstdc++.so.6(GLIBCXX_3.4.10) >[2012-05-30 11:40:33,324] DEBUG : Quick matched libstdc++-4.7.0-5.fc17.i686 to require for libstdc++.so.6(GLIBCXX_3.4) >[2012-05-30 11:40:33,324] DEBUG : Quick matched libstdc++-4.7.0-5.fc17.i686 to require for libstdc++.so.6(CXXABI_1.3) >[2012-05-30 11:40:33,324] DEBUG : Quick matched libstdc++-4.7.0-5.fc17.i686 to require for libstdc++.so.6 >[2012-05-30 11:40:33,328] DEBUG : TSINFO: Marking pciutils-libs-3.1.9-1.fc17.i686 as install for biosdevname-0.3.11-6.fc17.i686 >[2012-05-30 11:40:33,328] DEBUG : Quick matched pciutils-libs-3.1.9-1.fc17.i686 to require for libpci.so.3 >[2012-05-30 11:40:33,338] DEBUG : TSINFO: Marking python-fedora-0.3.28.1-1.fc17.noarch as install for bodhi-client-0.8.5-2.fc17.noarch >[2012-05-30 11:40:33,341] DEBUG : TSINFO: Marking python-simplejson-2.5.2-1.fc17.i686 as install for bodhi-client-0.8.5-2.fc17.noarch >[2012-05-30 11:40:33,342] DEBUG : TSINFO: Marking python-kitchen-1.1.1-1.fc17.noarch as install for bodhi-client-0.8.5-2.fc17.noarch >[2012-05-30 11:40:33,349] DEBUG : TSINFO: Marking python-pycurl-7.19.0-10.fc17.i686 as install for bzr-2.5.0-1.fc17.i686 >[2012-05-30 11:40:33,350] DEBUG : TSINFO: Marking python-paramiko-1.7.7.1-2.fc17.noarch as install for bzr-2.5.0-1.fc17.i686 >[2012-05-30 11:40:33,353] DEBUG : TSINFO: Marking python-libs-2.7.3-6.fc17.i686 as install for bzr-2.5.0-1.fc17.i686 >[2012-05-30 11:40:33,374] DEBUG : TSINFO: Marking xmlrpc-c-client-1.29.0-1701.svn2233.fc17.i686 as install for certmonger-0.56-1.fc17.i686 >[2012-05-30 11:40:33,375] DEBUG : TSINFO: Marking libtevent-0.9.15-1.fc17.i686 as install for certmonger-0.56-1.fc17.i686 >[2012-05-30 11:40:33,376] DEBUG : Quick matched libtevent-0.9.15-1.fc17.i686 to require for libtevent.so.0 >[2012-05-30 11:40:33,377] DEBUG : TSINFO: Marking libtalloc-2.0.7-4.fc17.i686 as install for certmonger-0.56-1.fc17.i686 >[2012-05-30 11:40:33,377] DEBUG : Quick matched libtalloc-2.0.7-4.fc17.i686 to require for libtalloc.so.2 >[2012-05-30 11:40:33,381] DEBUG : TSINFO: Marking popt-1.13-10.fc17.i686 as install for chkconfig-1.3.59-1.fc17.i686 >[2012-05-30 11:40:33,381] DEBUG : Quick matched popt-1.13-10.fc17.i686 to require for libpopt.so.0 >[2012-05-30 11:40:33,396] DEBUG : TSINFO: Marking libselinux-2.1.10-3.fc17.i686 as install for coreutils-8.15-6.fc17.i686 >[2012-05-30 11:40:33,398] DEBUG : TSINFO: Marking 1:gmp-5.0.2-6.fc17.i686 as install for coreutils-8.15-6.fc17.i686 >[2012-05-30 11:40:33,398] DEBUG : Quick matched 1:gmp-5.0.2-6.fc17.i686 to require for gmp >[2012-05-30 11:40:33,417] DEBUG : TSINFO: Marking crontabs-1.11-3.20101115git.fc17.noarch as install for cronie-anacron-1.4.8-11.fc17.i686 >[2012-05-30 11:40:33,423] DEBUG : TSINFO: Marking xemacs-filesystem-21.5.31-4.fc17.noarch as install for cscope-15.7a-8.fc17.i686 >[2012-05-30 11:40:33,424] DEBUG : TSINFO: Marking 1:emacs-filesystem-24.0.95-1.fc17.i686 as install for cscope-15.7a-8.fc17.i686 >[2012-05-30 11:40:33,453] DEBUG : TSINFO: Marking 12:dhcp-libs-4.2.4-0.4.rc1.fc17.i686 as install for 12:dhclient-4.2.4-0.4.rc1.fc17.i686 >[2012-05-30 11:40:33,454] DEBUG : TSINFO: Marking 12:dhcp-common-4.2.4-0.4.rc1.fc17.i686 as install for 12:dhclient-4.2.4-0.4.rc1.fc17.i686 >[2012-05-30 11:40:33,458] DEBUG : TSINFO: Marking 32:bind-libs-lite-9.9.0-4.fc17.i686 as install for 12:dhclient-4.2.4-0.4.rc1.fc17.i686 >[2012-05-30 11:40:33,458] DEBUG : Quick matched 32:bind-libs-lite-9.9.0-4.fc17.i686 to require for libdns-export.so.93 >[2012-05-30 11:40:33,459] DEBUG : TSINFO: Marking libcap-ng-0.6.6-2.fc17.i686 as install for 12:dhclient-4.2.4-0.4.rc1.fc17.i686 >[2012-05-30 11:40:33,473] DEBUG : TSINFO: Marking e2fsprogs-libs-1.42-4.fc17.i686 as install for e2fsprogs-1.42-4.fc17.i686 >[2012-05-30 11:40:33,474] DEBUG : TSINFO: Marking libss-1.42-4.fc17.i686 as install for e2fsprogs-1.42-4.fc17.i686 >[2012-05-30 11:40:33,475] DEBUG : Quick matched e2fsprogs-libs-1.42-4.fc17.i686 to require for libe2p.so.2 >[2012-05-30 11:40:33,477] DEBUG : TSINFO: Marking libblkid-2.21.1-1.fc17.i686 as install for e2fsprogs-1.42-4.fc17.i686 >[2012-05-30 11:40:33,477] DEBUG : Quick matched libblkid-2.21.1-1.fc17.i686 to require for libblkid.so.1(BLKID_2.15) >[2012-05-30 11:40:33,477] DEBUG : Quick matched libblkid-2.21.1-1.fc17.i686 to require for libblkid.so.1(BLKID_1.0) >[2012-05-30 11:40:33,477] DEBUG : Quick matched libblkid-2.21.1-1.fc17.i686 to require for libblkid.so.1 >[2012-05-30 11:40:33,495] DEBUG : TSINFO: Marking elfutils-libs-0.153-2.fc17.i686 as install for elfutils-0.153-2.fc17.i686 >[2012-05-30 11:40:33,498] DEBUG : TSINFO: Marking elfutils-libelf-0.153-2.fc17.i686 as install for elfutils-0.153-2.fc17.i686 >[2012-05-30 11:40:33,499] DEBUG : Quick matched elfutils-libelf-0.153-2.fc17.i686 to require for libelf.so.1(ELFUTILS_1.6) >[2012-05-30 11:40:33,499] DEBUG : Quick matched elfutils-libelf-0.153-2.fc17.i686 to require for libelf.so.1(ELFUTILS_1.5) >[2012-05-30 11:40:33,499] DEBUG : Quick matched elfutils-libelf-0.153-2.fc17.i686 to require for libelf.so.1(ELFUTILS_1.4) >[2012-05-30 11:40:33,499] DEBUG : Quick matched elfutils-libelf-0.153-2.fc17.i686 to require for libelf.so.1(ELFUTILS_1.3) >[2012-05-30 11:40:33,499] DEBUG : Quick matched elfutils-libelf-0.153-2.fc17.i686 to require for libelf.so.1(ELFUTILS_1.2) >[2012-05-30 11:40:33,499] DEBUG : Quick matched elfutils-libelf-0.153-2.fc17.i686 to require for libelf.so.1(ELFUTILS_1.1.1) >[2012-05-30 11:40:33,500] DEBUG : Quick matched elfutils-libelf-0.153-2.fc17.i686 to require for libelf.so.1(ELFUTILS_1.1) >[2012-05-30 11:40:33,500] DEBUG : Quick matched elfutils-libelf-0.153-2.fc17.i686 to require for libelf.so.1(ELFUTILS_1.0) >[2012-05-30 11:40:33,500] DEBUG : Quick matched elfutils-libelf-0.153-2.fc17.i686 to require for libelf.so.1 >[2012-05-30 11:40:33,501] DEBUG : Quick matched elfutils-libs-0.153-2.fc17.i686 to require for libdw.so.1(ELFUTILS_0.148) >[2012-05-30 11:40:33,501] DEBUG : Quick matched elfutils-libs-0.153-2.fc17.i686 to require for libdw.so.1(ELFUTILS_0.138) >[2012-05-30 11:40:33,501] DEBUG : Quick matched elfutils-libs-0.153-2.fc17.i686 to require for libdw.so.1(ELFUTILS_0.127) >[2012-05-30 11:40:33,501] DEBUG : Quick matched elfutils-libs-0.153-2.fc17.i686 to require for libdw.so.1(ELFUTILS_0.126) >[2012-05-30 11:40:33,501] DEBUG : Quick matched elfutils-libs-0.153-2.fc17.i686 to require for libdw.so.1(ELFUTILS_0.122) >[2012-05-30 11:40:33,501] DEBUG : Quick matched elfutils-libs-0.153-2.fc17.i686 to require for libdw.so.1 >[2012-05-30 11:40:33,501] DEBUG : Quick matched elfutils-libs-0.153-2.fc17.i686 to require for libasm.so.1(ELFUTILS_1.0) >[2012-05-30 11:40:33,501] DEBUG : Quick matched elfutils-libs-0.153-2.fc17.i686 to require for libasm.so.1 >[2012-05-30 11:40:33,535] DEBUG : TSINFO: Marking 1:emacs-common-24.0.95-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,538] DEBUG : TSINFO: Marking xorg-x11-fonts-misc-7.5-5.fc17.noarch as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,539] DEBUG : TSINFO: Marking libtiff-3.9.5-3.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,542] DEBUG : TSINFO: Marking librsvg2-2.36.1-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,544] DEBUG : TSINFO: Marking 2:libpng-1.5.10-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,544] DEBUG : Quick matched 2:libpng-1.5.10-1.fc17.i686 to require for libpng15.so.15 >[2012-05-30 11:40:33,546] DEBUG : TSINFO: Marking pango-1.30.0-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,546] DEBUG : Quick matched pango-1.30.0-1.fc17.i686 to require for libpangocairo-1.0.so.0 >[2012-05-30 11:40:33,546] DEBUG : Quick matched pango-1.30.0-1.fc17.i686 to require for libpango-1.0.so.0 >[2012-05-30 11:40:33,548] DEBUG : TSINFO: Marking libotf-0.9.12-3.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,551] DEBUG : TSINFO: Marking m17n-lib-1.6.3-2.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,551] DEBUG : Quick matched m17n-lib-1.6.3-2.fc17.i686 to require for libm17n-core.so.0 >[2012-05-30 11:40:33,554] DEBUG : TSINFO: Marking libjpeg-turbo-1.2.0-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,554] DEBUG : Quick matched libjpeg-turbo-1.2.0-1.fc17.i686 to require for libjpeg.so.62 >[2012-05-30 11:40:33,557] DEBUG : TSINFO: Marking gtk2-2.24.10-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,559] DEBUG : TSINFO: Marking libgomp-4.7.0-5.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,560] DEBUG : TSINFO: Marking gnutls-2.12.17-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,561] DEBUG : Quick matched gnutls-2.12.17-1.fc17.i686 to require for libgnutls.so.26 >[2012-05-30 11:40:33,563] DEBUG : TSINFO: Marking giflib-4.1.6-5.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,565] DEBUG : TSINFO: Marking gdk-pixbuf2-2.26.1-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,568] DEBUG : TSINFO: Marking GConf2-3.2.5-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,569] DEBUG : TSINFO: Marking freetype-2.4.8-3.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,571] DEBUG : TSINFO: Marking fontconfig-2.8.0-6.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,572] DEBUG : TSINFO: Marking cairo-1.10.2-7.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,573] DEBUG : TSINFO: Marking atk-2.4.0-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,575] DEBUG : TSINFO: Marking alsa-lib-1.0.25-3.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,576] DEBUG : Quick matched alsa-lib-1.0.25-3.fc17.i686 to require for libasound.so.2(ALSA_0.9) >[2012-05-30 11:40:33,576] DEBUG : Quick matched alsa-lib-1.0.25-3.fc17.i686 to require for libasound.so.2 >[2012-05-30 11:40:33,577] DEBUG : TSINFO: Marking libXrender-0.9.7-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,579] DEBUG : TSINFO: Marking libXpm-3.5.10-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,580] DEBUG : TSINFO: Marking libXft-2.3.0-2.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,581] DEBUG : TSINFO: Marking libX11-1.4.99.901-2.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,583] DEBUG : TSINFO: Marking libSM-1.2.1-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,587] DEBUG : TSINFO: Marking ImageMagick-6.7.5.6-3.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,587] DEBUG : Quick matched ImageMagick-6.7.5.6-3.fc17.i686 to require for libMagickCore.so.5 >[2012-05-30 11:40:33,588] DEBUG : TSINFO: Marking libICE-1.0.8-1.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,590] DEBUG : TSINFO: Marking desktop-file-utils-0.19-6.fc17.i686 as install for 1:emacs-24.0.95-1.fc17.i686 >[2012-05-30 11:40:33,594] DEBUG : TSINFO: Marking fedora-cert-0.5.9.6-2.fc17.noarch as install for fedora-easy-karma-0-0.16.20110825git36efb338.fc17.noarch >[2012-05-30 11:40:33,605] DEBUG : TSINFO: Marking fedpkg-1.9-1.fc17.noarch as install for fedora-packager-0.5.9.6-2.fc17.noarch >[2012-05-30 11:40:33,606] DEBUG : TSINFO: Marking ykpers-1.6.3-1.fc17.i686 as install for fedora-packager-0.5.9.6-2.fc17.noarch >[2012-05-30 11:40:33,608] DEBUG : TSINFO: Marking rpmlint-1.4-6.fc17.noarch as install for fedora-packager-0.5.9.6-2.fc17.noarch >[2012-05-30 11:40:33,611] DEBUG : TSINFO: Marking file-libs-5.10-5.fc17.i686 as install for file-5.10-5.fc17.i686 >[2012-05-30 11:40:33,612] DEBUG : Quick matched file-libs-5.10-5.fc17.i686 to require for libmagic.so.1 >[2012-05-30 11:40:33,629] DEBUG : TSINFO: Marking cpp-4.7.0-5.fc17.i686 as install for gcc-4.7.0-5.fc17.i686 >[2012-05-30 11:40:33,630] DEBUG : TSINFO: Marking glibc-devel-2.15-37.fc17.i686 as install for gcc-4.7.0-5.fc17.i686 >[2012-05-30 11:40:33,632] DEBUG : TSINFO: Marking cloog-ppl-0.15.11-3.fc17.1.i686 as install for gcc-4.7.0-5.fc17.i686 >[2012-05-30 11:40:33,633] DEBUG : TSINFO: Marking mpfr-3.1.0-2.fc17.i686 as install for gcc-4.7.0-5.fc17.i686 >[2012-05-30 11:40:33,635] DEBUG : TSINFO: Marking libmpc-0.9-2.fc17.2.i686 as install for gcc-4.7.0-5.fc17.i686 >[2012-05-30 11:40:33,641] DEBUG : TSINFO: Marking libstdc++-devel-4.7.0-5.fc17.i686 as install for gcc-c++-4.7.0-5.fc17.i686 >[2012-05-30 11:40:33,650] DEBUG : TSINFO: Marking libquadmath-devel-4.7.0-5.fc17.i686 as install for gcc-gfortran-4.7.0-5.fc17.i686 >[2012-05-30 11:40:33,652] DEBUG : TSINFO: Marking libquadmath-4.7.0-5.fc17.i686 as install for gcc-gfortran-4.7.0-5.fc17.i686 >[2012-05-30 11:40:33,654] DEBUG : TSINFO: Marking libgfortran-4.7.0-5.fc17.i686 as install for gcc-gfortran-4.7.0-5.fc17.i686 >[2012-05-30 11:40:33,654] DEBUG : Quick matched libgfortran-4.7.0-5.fc17.i686 to require for libgfortran.so.3 >[2012-05-30 11:40:33,663] DEBUG : TSINFO: Marking expat-2.1.0-1.fc17.i686 as install for gdb-7.4.50.20120120-42.fc17.i686 >[2012-05-30 11:40:33,676] DEBUG : TSINFO: Marking libunistring-0.9.3-3.fc17.i686 as install for gettext-0.18.1.1-12.fc17.i686 >[2012-05-30 11:40:33,677] DEBUG : TSINFO: Marking gettext-libs-0.18.1.1-12.fc17.i686 as install for gettext-0.18.1.1-12.fc17.i686 >[2012-05-30 11:40:33,678] DEBUG : Quick matched gettext-libs-0.18.1.1-12.fc17.i686 to require for libgettextlib-0.18.1.so >[2012-05-30 11:40:33,679] DEBUG : TSINFO: Marking libcroco-0.6.5-1.fc17.i686 as install for gettext-0.18.1.1-12.fc17.i686 >[2012-05-30 11:40:33,698] DEBUG : TSINFO: Marking perl-Git-1.7.10.2-1.fc17.noarch as install for git-1.7.10.2-1.fc17.i686 >[2012-05-30 11:40:33,700] DEBUG : TSINFO: Marking rsync-3.0.9-2.fc17.i686 as install for git-1.7.10.2-1.fc17.i686 >[2012-05-30 11:40:33,702] DEBUG : TSINFO: Marking 1:perl-Error-0.17016-7.fc17.noarch as install for git-1.7.10.2-1.fc17.i686 >[2012-05-30 11:40:33,705] DEBUG : TSINFO: Marking pcre-8.21-5.fc17.i686 as install for git-1.7.10.2-1.fc17.i686 >[2012-05-30 11:40:33,707] DEBUG : TSINFO: Marking less-444-5.fc17.i686 as install for git-1.7.10.2-1.fc17.i686 >[2012-05-30 11:40:33,713] DEBUG : TSINFO: Marking glibc-common-2.15-37.fc17.i686 as install for glibc-2.15-37.fc17.i686 >[2012-05-30 11:40:33,714] DEBUG : TSINFO: Marking nss-softokn-freebl-3.13.4-2.fc17.i686 as install for glibc-2.15-37.fc17.i686 >[2012-05-30 11:40:33,715] DEBUG : Quick matched nss-softokn-freebl-3.13.4-2.fc17.i686 to require for libfreebl3.so >[2012-05-30 11:40:33,723] DEBUG : TSINFO: Marking 1:libusb-0.1.3-10.fc17.i686 as install for gnupg-1.4.12-1.fc17.i686 >[2012-05-30 11:40:33,724] DEBUG : TSINFO: Marking bzip2-libs-1.0.6-4.fc17.i686 as install for gnupg-1.4.12-1.fc17.i686 >[2012-05-30 11:40:33,734] DEBUG : TSINFO: Marking which-2.20-3.fc17.i686 as install for 1:grub2-2.0-0.25.beta4.fc17.i686 >[2012-05-30 11:40:33,743] DEBUG : TSINFO: Marking fedora-logos-17.0.2-1.fc17.noarch as install for 1:grub2-2.0-0.25.beta4.fc17.i686 >[2012-05-30 11:40:33,745] DEBUG : TSINFO: Marking os-prober-1.53-1.fc17.i686 as install for 1:grub2-2.0-0.25.beta4.fc17.i686 >[2012-05-30 11:40:33,746] DEBUG : TSINFO: Marking xz-libs-5.1.1-2alpha.fc17.i686 as install for 1:grub2-2.0-0.25.beta4.fc17.i686 >[2012-05-30 11:40:33,747] DEBUG : TSINFO: Marking device-mapper-libs-1.02.74-6.fc17.i686 as install for 1:grub2-2.0-0.25.beta4.fc17.i686 >[2012-05-30 11:40:33,748] DEBUG : Quick matched device-mapper-libs-1.02.74-6.fc17.i686 to require for libdevmapper.so.1.02 >[2012-05-30 11:40:33,751] DEBUG : TSINFO: Marking dracut-018-40.git20120522.fc17.noarch as install for 1:grub2-2.0-0.25.beta4.fc17.i686 >[2012-05-30 11:40:33,766] DEBUG : TSINFO: Marking httpd-tools-2.2.22-4.fc17.i686 as install for httpd-2.2.22-4.fc17.i686 >[2012-05-30 11:40:33,769] DEBUG : TSINFO: Marking db4-4.8.30-10.fc17.i686 as install for httpd-2.2.22-4.fc17.i686 >[2012-05-30 11:40:33,771] DEBUG : TSINFO: Marking apr-util-1.4.1-2.fc17.i686 as install for httpd-2.2.22-4.fc17.i686 >[2012-05-30 11:40:33,772] DEBUG : TSINFO: Marking apr-1.4.6-1.fc17.i686 as install for httpd-2.2.22-4.fc17.i686 >[2012-05-30 11:40:33,773] DEBUG : TSINFO: Marking apr-util-ldap-1.4.1-2.fc17.i686 as install for httpd-2.2.22-4.fc17.i686 >[2012-05-30 11:40:33,775] DEBUG : TSINFO: Marking mailcap-2.1.39-1.fc17.noarch as install for httpd-2.2.22-4.fc17.i686 >[2012-05-30 11:40:33,803] DEBUG : TSINFO: Marking sysvinit-tools-2.88-6.dsf.fc17.i686 as install for initscripts-9.37-1.fc17.i686 >[2012-05-30 11:40:33,804] DEBUG : TSINFO: Marking net-tools-1.60-134.20120127git.fc17.i686 as install for initscripts-9.37-1.fc17.i686 >[2012-05-30 11:40:33,806] DEBUG : TSINFO: Marking mingetty-1.08-10.fc17.i686 as install for initscripts-9.37-1.fc17.i686 >[2012-05-30 11:40:33,808] DEBUG : TSINFO: Marking psmisc-22.16-1.fc17.i686 as install for initscripts-9.37-1.fc17.i686 >[2012-05-30 11:40:33,813] DEBUG : TSINFO: Marking fedora-release-17-1.noarch as install for initscripts-9.37-1.fc17.i686 >[2012-05-30 11:40:33,815] DEBUG : TSINFO: Marking 1:findutils-4.5.10-4.fc17.i686 as install for initscripts-9.37-1.fc17.i686 >[2012-05-30 11:40:33,824] DEBUG : TSINFO: Marking perl-XML-Parser-2.41-4.fc17.i686 as install for intltool-0.50.2-1.fc17.noarch >[2012-05-30 11:40:33,826] DEBUG : TSINFO: Marking patch-2.6.1-12.fc17.i686 as install for intltool-0.50.2-1.fc17.noarch >[2012-05-30 11:40:33,829] DEBUG : TSINFO: Marking gettext-devel-0.18.1.1-12.fc17.i686 as install for intltool-0.50.2-1.fc17.noarch >[2012-05-30 11:40:33,838] DEBUG : TSINFO: Marking linux-atm-libs-2.5.1-4.fc17.i686 as install for iproute-3.3.0-2.fc17.i686 >[2012-05-30 11:40:33,854] DEBUG : TSINFO: Marking kbd-misc-1.15.3-5.fc17.noarch as install for kbd-1.15.3-5.fc17.i686 >[2012-05-30 11:40:33,864] DEBUG : TSINFO: Marking linux-firmware-20120206-0.3.git06c8f81.fc17.noarch as install for kernel-PAE-3.3.7-1.fc17.i686 >[2012-05-30 11:40:33,865] DEBUG : TSINFO: Marking grubby-8.11-1.fc17.i686 as install for kernel-PAE-3.3.7-1.fc17.i686 >[2012-05-30 11:40:33,879] DEBUG : TSINFO: Marking rpm-python-4.9.1.3-7.fc17.i686 as install for koji-1.6.0-3.fc17.noarch >[2012-05-30 11:40:33,881] DEBUG : TSINFO: Marking python-urlgrabber-3.9.1-11.fc17.noarch as install for koji-1.6.0-3.fc17.noarch >[2012-05-30 11:40:33,901] DEBUG : TSINFO: Marking libselinux-devel-2.1.10-3.fc17.i686 as install for krb5-devel-1.10-6.fc17.i686 >[2012-05-30 11:40:33,903] DEBUG : TSINFO: Marking keyutils-libs-1.5.5-2.fc17.i686 as install for krb5-devel-1.10-6.fc17.i686 >[2012-05-30 11:40:33,905] DEBUG : TSINFO: Marking libcom_err-devel-1.42-4.fc17.i686 as install for krb5-devel-1.10-6.fc17.i686 >[2012-05-30 11:40:33,906] DEBUG : TSINFO: Marking keyutils-libs-devel-1.5.5-2.fc17.i686 as install for krb5-devel-1.10-6.fc17.i686 >[2012-05-30 11:40:33,933] DEBUG : TSINFO: Marking logrotate-3.8.1-3.fc17.i686 as install for krb5-server-1.10-6.fc17.i686 >[2012-05-30 11:40:33,934] DEBUG : TSINFO: Marking libverto-0.2.4-2.fc17.i686 as install for krb5-server-1.10-6.fc17.i686 >[2012-05-30 11:40:33,951] DEBUG : TSINFO: Marking libverto-tevent-0.2.4-2.fc17.i686 as install for krb5-server-1.10-6.fc17.i686 >[2012-05-30 11:40:33,981] DEBUG : TSINFO: Marking libssh2-1.4.1-2.fc17.i686 as install for libcurl-7.24.0-2.fc17.i686 >[2012-05-30 11:40:33,981] DEBUG : Quick matched libssh2-1.4.1-2.fc17.i686 to require for libssh2.so.1 >[2012-05-30 11:40:33,990] DEBUG : TSINFO: Marking libipa_hbac-1.8.3-11.fc17.i686 as install for libipa_hbac-python-1.8.3-11.fc17.i686 >[2012-05-30 11:40:33,990] DEBUG : Quick matched libipa_hbac-1.8.3-11.fc17.i686 to require for libipa_hbac.so.0 >[2012-05-30 11:40:34,011] DEBUG : TSINFO: Marking lvm2-libs-2.02.95-6.fc17.i686 as install for lvm2-2.02.95-6.fc17.i686 >[2012-05-30 11:40:34,013] DEBUG : TSINFO: Marking libudev-182-1.fc17.i686 as install for lvm2-2.02.95-6.fc17.i686 >[2012-05-30 11:40:34,015] DEBUG : TSINFO: Marking device-mapper-event-libs-1.02.74-6.fc17.i686 as install for lvm2-2.02.95-6.fc17.i686 >[2012-05-30 11:40:34,015] DEBUG : Quick matched device-mapper-event-libs-1.02.74-6.fc17.i686 to require for libdevmapper-event.so.1.02 >[2012-05-30 11:40:34,030] DEBUG : TSINFO: Marking slang-2.2.4-3.fc17.i686 as install for 1:mc-4.8.3-1.fc17.i686 >[2012-05-30 11:40:34,031] DEBUG : Quick matched slang-2.2.4-3.fc17.i686 to require for libslang.so.2 >[2012-05-30 11:40:34,032] DEBUG : TSINFO: Marking gpm-libs-1.20.6-22.fc17.i686 as install for 1:mc-4.8.3-1.fc17.i686 >[2012-05-30 11:40:34,044] DEBUG : TSINFO: Marking libevent-2.0.18-1.fc17.i686 as install for memcached-1.4.10-2.fc17.i686 >[2012-05-30 11:40:34,058] DEBUG : TSINFO: Marking usermode-1.109-1.fc17.i686 as install for mock-1.1.22-2.1.fc17.noarch >[2012-05-30 11:40:34,060] DEBUG : TSINFO: Marking 2:tar-1.26-5.fc17.i686 as install for mock-1.1.22-2.1.fc17.noarch >[2012-05-30 11:40:34,061] DEBUG : TSINFO: Marking python-decoratortools-1.8-3.fc17.noarch as install for mock-1.1.22-2.1.fc17.noarch >[2012-05-30 11:40:34,062] DEBUG : TSINFO: Marking pigz-2.2.4-1.fc17.i686 as install for mock-1.1.22-2.1.fc17.noarch >[2012-05-30 11:40:34,064] DEBUG : TSINFO: Marking createrepo-0.9.9-11.fc17.noarch as install for mock-1.1.22-2.1.fc17.noarch >[2012-05-30 11:40:34,118] DEBUG : TSINFO: Marking rpcbind-0.2.0-16.fc17.i686 as install for 1:nfs-utils-1.2.6-0.fc17.i686 >[2012-05-30 11:40:34,123] DEBUG : TSINFO: Marking libnfsidmap-0.25-1.fc17.i686 as install for 1:nfs-utils-1.2.6-0.fc17.i686 >[2012-05-30 11:40:34,123] DEBUG : Quick matched libnfsidmap-0.25-1.fc17.i686 to require for libnfsidmap >[2012-05-30 11:40:34,125] DEBUG : TSINFO: Marking libmount-2.21.1-1.fc17.i686 as install for 1:nfs-utils-1.2.6-0.fc17.i686 >[2012-05-30 11:40:34,125] DEBUG : Quick matched libmount-2.21.1-1.fc17.i686 to require for libmount.so.1 >[2012-05-30 11:40:34,125] DEBUG : Quick matched libmount-2.21.1-1.fc17.i686 to require for libmount >[2012-05-30 11:40:34,128] DEBUG : TSINFO: Marking libgssglue-0.3-1.fc17.i686 as install for 1:nfs-utils-1.2.6-0.fc17.i686 >[2012-05-30 11:40:34,128] DEBUG : Quick matched libgssglue-0.3-1.fc17.i686 to require for libgssglue.so.1 >[2012-05-30 11:40:34,129] DEBUG : Quick matched libgssglue-0.3-1.fc17.i686 to require for libgssglue >[2012-05-30 11:40:34,130] DEBUG : TSINFO: Marking keyutils-1.5.5-2.fc17.i686 as install for 1:nfs-utils-1.2.6-0.fc17.i686 >[2012-05-30 11:40:34,143] DEBUG : TSINFO: Marking nss-softokn-3.13.4-2.fc17.i686 as install for nss-3.13.4-3.fc17.i686 >[2012-05-30 11:40:34,145] DEBUG : TSINFO: Marking nss-sysinit-3.13.4-3.fc17.i686 as install for nss-3.13.4-3.fc17.i686 >[2012-05-30 11:40:34,152] DEBUG : TSINFO: Marking nss-util-devel-3.13.4-2.fc17.i686 as install for nss-devel-3.13.4-3.fc17.i686 >[2012-05-30 11:40:34,153] DEBUG : Quick matched nss-util-devel-3.13.4-2.fc17.i686 to require for nss-util-devel >[2012-05-30 11:40:34,154] DEBUG : TSINFO: Marking nss-softokn-devel-3.13.4-2.fc17.i686 as install for nss-devel-3.13.4-3.fc17.i686 >[2012-05-30 11:40:34,174] DEBUG : TSINFO: Marking sqlite-3.7.11-2.fc17.i686 as install for nss-tools-3.13.4-3.fc17.i686 >[2012-05-30 11:40:34,182] DEBUG : TSINFO: Marking ntpdate-4.2.6p5-2.fc17.i686 as install for ntp-4.2.6p5-2.fc17.i686 >[2012-05-30 11:40:34,184] DEBUG : TSINFO: Marking libedit-3.0-6.20110802cvs.fc17.i686 as install for ntp-4.2.6p5-2.fc17.i686 >[2012-05-30 11:40:34,191] DEBUG : TSINFO: Marking oddjob-0.31.1-2.fc17.i686 as install for oddjob-mkhomedir-0.31.1-2.fc17.i686 >[2012-05-30 11:40:34,201] DEBUG : TSINFO: Marking cyrus-sasl-devel-2.1.23-29.fc17.i686 as install for openldap-devel-2.4.30-2.fc17.i686 >[2012-05-30 11:40:34,212] DEBUG : TSINFO: Marking openssh-5.9p1-22.fc17.i686 as install for openssh-clients-5.9p1-22.fc17.i686 >[2012-05-30 11:40:34,215] DEBUG : TSINFO: Marking fipscheck-lib-1.3.0-3.fc17.i686 as install for openssh-clients-5.9p1-22.fc17.i686 >[2012-05-30 11:40:34,215] DEBUG : Quick matched fipscheck-lib-1.3.0-3.fc17.i686 to require for libfipscheck.so.1 >[2012-05-30 11:40:34,233] DEBUG : TSINFO: Marking zlib-devel-1.2.5-6.fc17.i686 as install for 1:openssl-devel-1.0.0j-1.fc17.i686 >[2012-05-30 11:40:34,256] DEBUG : TSINFO: Marking libsepol-2.1.5-3.fc17.i686 as install for parted-3.0-9.fc17.i686 >[2012-05-30 11:40:34,266] DEBUG : TSINFO: Marking libuser-0.57.6-1.fc17.i686 as install for passwd-0.78.99-1.fc17.i686 >[2012-05-30 11:40:34,278] DEBUG : TSINFO: Marking pki-selinux-9.0.20-1.fc17.noarch as install for pki-ca-9.0.20-1.fc17.noarch >[2012-05-30 11:40:34,279] DEBUG : TSINFO: Marking pki-common-9.0.20-1.fc17.noarch as install for pki-ca-9.0.20-1.fc17.noarch >[2012-05-30 11:40:34,287] DEBUG : TSINFO: Marking 1:java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6.i686 as install for pki-ca-9.0.20-1.fc17.noarch >[2012-05-30 11:40:34,298] DEBUG : TSINFO: Marking perl-Crypt-SSLeay-0.58-8.fc17.i686 as install for pki-setup-9.0.20-1.fc17.noarch >[2012-05-30 11:40:34,300] DEBUG : TSINFO: Marking 1:perl-XML-LibXML-1.90-1.fc17.i686 as install for pki-setup-9.0.20-1.fc17.noarch >[2012-05-30 11:40:34,303] DEBUG : TSINFO: Marking perl-Socket-2.001-1.fc17.i686 as install for pki-setup-9.0.20-1.fc17.noarch >[2012-05-30 11:40:34,305] DEBUG : TSINFO: Marking perl-File-Slurp-9999.19-3.fc17.noarch as install for pki-setup-9.0.20-1.fc17.noarch >[2012-05-30 11:40:34,319] DEBUG : TSINFO: Marking plymouth-scripts-0.8.4-0.20120319.2.fc17.i686 as install for plymouth-0.8.4-0.20120319.2.fc17.i686 >[2012-05-30 11:40:34,320] DEBUG : TSINFO: Marking plymouth-core-libs-0.8.4-0.20120319.2.fc17.i686 as install for plymouth-0.8.4-0.20120319.2.fc17.i686 >[2012-05-30 11:40:34,320] DEBUG : Quick matched plymouth-core-libs-0.8.4-0.20120319.2.fc17.i686 to require for libply-splash-core.so.2 >[2012-05-30 11:40:34,323] DEBUG : TSINFO: Marking libdrm-2.4.33-3.fc17.i686 as install for plymouth-0.8.4-0.20120319.2.fc17.i686 >[2012-05-30 11:40:34,324] DEBUG : Quick matched libdrm-2.4.33-3.fc17.i686 to require for libdrm_radeon.so.1 >[2012-05-30 11:40:34,324] DEBUG : Quick matched libdrm-2.4.33-3.fc17.i686 to require for libdrm_nouveau.so.1 >[2012-05-30 11:40:34,324] DEBUG : Quick matched libdrm-2.4.33-3.fc17.i686 to require for libdrm_intel.so.1 >[2012-05-30 11:40:34,324] DEBUG : Quick matched libdrm-2.4.33-3.fc17.i686 to require for libdrm.so.2 >[2012-05-30 11:40:34,338] DEBUG : TSINFO: Marking libselinux-utils-2.1.10-3.fc17.i686 as install for policycoreutils-2.1.11-6.fc17.i686 >[2012-05-30 11:40:34,339] DEBUG : TSINFO: Marking libsemanage-2.1.6-3.fc17.i686 as install for policycoreutils-2.1.11-6.fc17.i686 >[2012-05-30 11:40:34,340] DEBUG : Quick matched libsemanage-2.1.6-3.fc17.i686 to require for libsemanage.so.1 >[2012-05-30 11:40:34,341] DEBUG : TSINFO: Marking diffutils-3.2-6.fc17.i686 as install for policycoreutils-2.1.11-6.fc17.i686 >[2012-05-30 11:40:34,355] DEBUG : TSINFO: Marking python-logilab-astng-0.23.1-1.fc17.noarch as install for pylint-0.25.1-1.fc17.noarch >[2012-05-30 11:40:34,385] DEBUG : TSINFO: Marking libxslt-1.1.26-9.fc17.i686 as install for python-lxml-2.3.3-1.fc17.i686 >[2012-05-30 11:40:34,385] DEBUG : Quick matched libxslt-1.1.26-9.fc17.i686 to require for libxslt.so.1(LIBXML2_1.1.26) >[2012-05-30 11:40:34,385] DEBUG : Quick matched libxslt-1.1.26-9.fc17.i686 to require for libxslt.so.1(LIBXML2_1.1.2) >[2012-05-30 11:40:34,386] DEBUG : Quick matched libxslt-1.1.26-9.fc17.i686 to require for libxslt.so.1(LIBXML2_1.0.24) >[2012-05-30 11:40:34,386] DEBUG : Quick matched libxslt-1.1.26-9.fc17.i686 to require for libxslt.so.1(LIBXML2_1.0.22) >[2012-05-30 11:40:34,386] DEBUG : Quick matched libxslt-1.1.26-9.fc17.i686 to require for libxslt.so.1(LIBXML2_1.0.18) >[2012-05-30 11:40:34,386] DEBUG : Quick matched libxslt-1.1.26-9.fc17.i686 to require for libxslt.so.1(LIBXML2_1.0.11) >[2012-05-30 11:40:34,386] DEBUG : Quick matched libxslt-1.1.26-9.fc17.i686 to require for libxslt.so.1 >[2012-05-30 11:40:34,386] DEBUG : Quick matched libxslt-1.1.26-9.fc17.i686 to require for libexslt.so.0 >[2012-05-30 11:40:34,401] DEBUG : TSINFO: Marking python-iniparse-0.4-4.fc17.noarch as install for python-rhsm-0.99.3-1.fc17.noarch >[2012-05-30 11:40:34,402] DEBUG : TSINFO: Marking m2crypto-0.21.1-8.fc17.i686 as install for python-rhsm-0.99.3-1.fc17.noarch >[2012-05-30 11:40:34,430] DEBUG : TSINFO: Marking rpm-libs-4.9.1.3-7.fc17.i686 as install for rpm-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,430] DEBUG : Quick matched rpm-libs-4.9.1.3-7.fc17.i686 to require for librpm.so.2 >[2012-05-30 11:40:34,431] DEBUG : TSINFO: Marking lua-5.1.4-10.fc17.i686 as install for rpm-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,433] DEBUG : TSINFO: Marking libdb-5.2.36-5.fc17.i686 as install for rpm-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,434] DEBUG : TSINFO: Marking libdb-utils-5.2.36-5.fc17.i686 as install for rpm-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,458] DEBUG : TSINFO: Marking xz-5.1.1-2alpha.fc17.i686 as install for rpm-build-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,459] DEBUG : TSINFO: Marking unzip-6.0-5.fc17.i686 as install for rpm-build-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,462] DEBUG : TSINFO: Marking perl-threads-1.86-2.fc17.i686 as install for rpm-build-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,465] DEBUG : TSINFO: Marking rpm-build-libs-4.9.1.3-7.fc17.i686 as install for rpm-build-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,467] DEBUG : TSINFO: Marking gzip-1.4-6.fc17.i686 as install for rpm-build-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,468] DEBUG : TSINFO: Marking bzip2-1.0.6-4.fc17.i686 as install for rpm-build-4.9.1.3-7.fc17.i686 >[2012-05-30 11:40:34,480] DEBUG : TSINFO: Marking fakeroot-1.12.4-4.fc17.i686 as install for rpmdevtools-8.2-2.fc17.noarch >[2012-05-30 11:40:34,484] DEBUG : TSINFO: Marking man-db-2.6.0.2-6.fc17.i686 as install for rpmdevtools-8.2-2.fc17.noarch >[2012-05-30 11:40:34,514] DEBUG : TSINFO: Marking 2:samba4-libs-4.0.0-47alpha18.fc17.i686 as install for 2:samba4-devel-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:40:34,516] DEBUG : TSINFO: Marking libtevent-devel-0.9.15-1.fc17.i686 as install for 2:samba4-devel-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:40:34,518] DEBUG : TSINFO: Marking libtalloc-devel-2.0.7-4.fc17.i686 as install for 2:samba4-devel-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:40:34,519] DEBUG : TSINFO: Marking libldb-devel-1.1.4-2.fc17.i686 as install for 2:samba4-devel-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:40:34,521] DEBUG : TSINFO: Marking 2:samba4-test-4.0.0-47alpha18.fc17.i686 as install for 2:samba4-devel-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:40:34,522] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libsmbconf.so.0 >[2012-05-30 11:40:34,522] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libsmbclient-raw.so.0 >[2012-05-30 11:40:34,522] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libsamdb.so.0 >[2012-05-30 11:40:34,522] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libsamba-util.so.0 >[2012-05-30 11:40:34,522] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libsamba-policy.so.0 >[2012-05-30 11:40:34,523] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libsamba-hostconfig.so.0 >[2012-05-30 11:40:34,523] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libsamba-credentials.so.0 >[2012-05-30 11:40:34,523] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libregistry.so.0 >[2012-05-30 11:40:34,527] DEBUG : TSINFO: Marking 2:samba4-common-4.0.0-47alpha18.fc17.i686 as install for 2:samba4-devel-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:40:34,528] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libndr-standard.so.0 >[2012-05-30 11:40:34,528] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libndr-nbt.so.0 >[2012-05-30 11:40:34,528] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libndr-krb5pac.so.0 >[2012-05-30 11:40:34,529] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libgensec.so.0 >[2012-05-30 11:40:34,529] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libdcerpc.so.0 >[2012-05-30 11:40:34,530] DEBUG : TSINFO: Marking 2:samba4-dc-libs-4.0.0-47alpha18.fc17.i686 as install for 2:samba4-devel-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:40:34,531] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libdcerpc-binding.so.0 >[2012-05-30 11:40:34,532] DEBUG : Quick matched 2:samba4-libs-4.0.0-47alpha18.fc17.i686 to require for libdcerpc-atsvc.so.0 >[2012-05-30 11:40:34,539] DEBUG : TSINFO: Marking checkpolicy-2.1.9-4.fc17.i686 as install for selinux-policy-3.10.0-125.fc17.noarch >[2012-05-30 11:40:34,556] DEBUG : TSINFO: Marking procmail-3.22-29.fc17.i686 as install for sendmail-8.14.5-12.fc17.i686 >[2012-05-30 11:40:34,558] DEBUG : TSINFO: Marking cyrus-sasl-2.1.23-29.fc17.i686 as install for sendmail-8.14.5-12.fc17.i686 >[2012-05-30 11:40:34,603] DEBUG : TSINFO: Marking sssd-client-1.8.3-11.fc17.i686 as install for sssd-1.8.3-11.fc17.i686 >[2012-05-30 11:40:34,605] DEBUG : TSINFO: Marking libldb-1.1.4-2.fc17.i686 as install for sssd-1.8.3-11.fc17.i686 >[2012-05-30 11:40:34,607] DEBUG : TSINFO: Marking libtdb-1.2.9-14.fc17.i686 as install for sssd-1.8.3-11.fc17.i686 >[2012-05-30 11:40:34,607] DEBUG : Quick matched libtdb-1.2.9-14.fc17.i686 to require for libtdb.so.1(TDB_1.2.1) >[2012-05-30 11:40:34,607] DEBUG : Quick matched libtdb-1.2.9-14.fc17.i686 to require for libtdb.so.1 >[2012-05-30 11:40:34,608] DEBUG : TSINFO: Marking libnl-1.1-15.fc17.i686 as install for sssd-1.8.3-11.fc17.i686 >[2012-05-30 11:40:34,609] DEBUG : Quick matched libldb-1.1.4-2.fc17.i686 to require for libldb.so.1 >[2012-05-30 11:40:34,611] DEBUG : TSINFO: Marking libini_config-0.6.2-8.fc17.i686 as install for sssd-1.8.3-11.fc17.i686 >[2012-05-30 11:40:34,612] DEBUG : TSINFO: Marking libdhash-0.4.3-8.fc17.i686 as install for sssd-1.8.3-11.fc17.i686 >[2012-05-30 11:40:34,613] DEBUG : TSINFO: Marking libcollection-0.6.1-8.fc17.i686 as install for sssd-1.8.3-11.fc17.i686 >[2012-05-30 11:40:34,615] DEBUG : TSINFO: Marking c-ares-1.7.5-2.fc17.i686 as install for sssd-1.8.3-11.fc17.i686 >[2012-05-30 11:40:34,638] DEBUG : TSINFO: Marking subversion-libs-1.7.4-6.fc17.i686 as install for subversion-1.7.4-6.fc17.i686 >[2012-05-30 11:40:34,639] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_wc-1.so.0 >[2012-05-30 11:40:34,639] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_subr-1.so.0 >[2012-05-30 11:40:34,639] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_repos-1.so.0 >[2012-05-30 11:40:34,639] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_ra_svn-1.so.0 >[2012-05-30 11:40:34,639] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_ra_neon-1.so.0 >[2012-05-30 11:40:34,639] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_ra_local-1.so.0 >[2012-05-30 11:40:34,639] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_ra-1.so.0 >[2012-05-30 11:40:34,640] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_fs_util-1.so.0 >[2012-05-30 11:40:34,640] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_fs_fs-1.so.0 >[2012-05-30 11:40:34,640] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_fs_base-1.so.0 >[2012-05-30 11:40:34,640] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_fs-1.so.0 >[2012-05-30 11:40:34,640] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_diff-1.so.0 >[2012-05-30 11:40:34,640] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_delta-1.so.0 >[2012-05-30 11:40:34,640] DEBUG : Quick matched subversion-libs-1.7.4-6.fc17.i686 to require for libsvn_client-1.so.0 >[2012-05-30 11:40:34,642] DEBUG : TSINFO: Marking neon-0.29.6-2.fc17.i686 as install for subversion-1.7.4-6.fc17.i686 >[2012-05-30 11:40:34,655] DEBUG : TSINFO: Marking libsss_sudo-1.8.3-11.fc17.i686 as install for sudo-1.8.3p1-7.fc17.i686 >[2012-05-30 11:40:34,656] DEBUG : Quick matched libsss_sudo-1.8.3-11.fc17.i686 to require for libsss_sudo.so.0 >[2012-05-30 11:40:34,661] DEBUG : TSINFO: Marking svrcore-4.0.4-7.fc17.i686 as install for svrcore-devel-4.0.4-7.fc17.i686 >[2012-05-30 11:40:34,662] DEBUG : Quick matched svrcore-4.0.4-7.fc17.i686 to require for libsvrcore.so.0 >[2012-05-30 11:40:34,676] DEBUG : TSINFO: Marking libglade2-2.6.4-8.fc17.i686 as install for sysprof-1.1.8-3.fc17.i686 >[2012-05-30 11:40:34,677] DEBUG : TSINFO: Marking hicolor-icon-theme-0.12-4.fc17.noarch as install for sysprof-1.1.8-3.fc17.i686 >[2012-05-30 11:40:34,707] DEBUG : TSINFO: Marking nss-myhostname-0.3-2.fc17.i686 as install for systemd-44-12.fc17.i686 >[2012-05-30 11:40:34,709] DEBUG : TSINFO: Marking kmod-libs-7-1.fc17.i686 as install for systemd-44-12.fc17.i686 >[2012-05-30 11:40:34,709] DEBUG : Quick matched kmod-libs-7-1.fc17.i686 to require for libkmod.so.2 >[2012-05-30 11:40:34,712] DEBUG : TSINFO: Marking cryptsetup-libs-1.4.2-1.fc17.i686 as install for systemd-44-12.fc17.i686 >[2012-05-30 11:40:34,712] DEBUG : Quick matched cryptsetup-libs-1.4.2-1.fc17.i686 to require for libcryptsetup.so.4 >[2012-05-30 11:40:34,716] DEBUG : TSINFO: Marking systemtap-devel-1.7-7.fc17.i686 as install for systemtap-1.7-7.fc17.i686 >[2012-05-30 11:40:34,718] DEBUG : TSINFO: Marking systemtap-client-1.7-7.fc17.i686 as install for systemtap-1.7-7.fc17.i686 >[2012-05-30 11:40:34,733] DEBUG : TSINFO: Marking tomcat6-lib-6.0.32-20.fc17.noarch as install for tomcat6-6.0.32-20.fc17.noarch >[2012-05-30 11:40:34,734] DEBUG : TSINFO: Marking redhat-lsb-4.0-11.fc17.i686 as install for tomcat6-6.0.32-20.fc17.noarch >[2012-05-30 11:40:34,735] DEBUG : Quick matched redhat-lsb-4.0-11.fc17.i686 to require for redhat-lsb >[2012-05-30 11:40:34,737] DEBUG : TSINFO: Marking apache-commons-pool-1.5.7-2.fc17.noarch as install for tomcat6-6.0.32-20.fc17.noarch >[2012-05-30 11:40:34,741] DEBUG : TSINFO: Marking apache-commons-logging-1.1.1-19.fc17.noarch as install for tomcat6-6.0.32-20.fc17.noarch >[2012-05-30 11:40:34,744] DEBUG : TSINFO: Marking apache-commons-dbcp-1.4-9.fc17.noarch as install for tomcat6-6.0.32-20.fc17.noarch >[2012-05-30 11:40:34,746] DEBUG : TSINFO: Marking apache-commons-daemon-1.0.10-2.fc17.i686 as install for tomcat6-6.0.32-20.fc17.noarch >[2012-05-30 11:40:34,749] DEBUG : TSINFO: Marking apache-commons-collections-3.2.1-12.fc17.noarch as install for tomcat6-6.0.32-20.fc17.noarch >[2012-05-30 11:40:34,769] DEBUG : TSINFO: Marking libutempter-1.1.5-6.fc17.i686 as install for util-linux-2.21.1-1.fc17.i686 >[2012-05-30 11:40:34,769] DEBUG : Quick matched libutempter-1.1.5-6.fc17.i686 to require for libutempter.so.0 >[2012-05-30 11:40:34,785] DEBUG : TSINFO: Marking 2:vim-common-7.3.515-1.fc17.i686 as install for 2:vim-enhanced-7.3.515-1.fc17.i686 >[2012-05-30 11:40:34,788] DEBUG : TSINFO: Marking ruby-libs-1.9.3.194-10.1.fc17.i686 as install for 2:vim-enhanced-7.3.515-1.fc17.i686 >[2012-05-30 11:40:34,790] DEBUG : TSINFO: Marking 4:perl-libs-5.14.2-211.fc17.i686 as install for 2:vim-enhanced-7.3.515-1.fc17.i686 >[2012-05-30 11:40:34,811] DEBUG : TSINFO: Marking xmlrpc-c-client++-1.29.0-1701.svn2233.fc17.i686 as install for xmlrpc-c-devel-1.29.0-1701.svn2233.fc17.i686 >[2012-05-30 11:40:34,812] DEBUG : TSINFO: Marking xmlrpc-c-c++-1.29.0-1701.svn2233.fc17.i686 as install for xmlrpc-c-devel-1.29.0-1701.svn2233.fc17.i686 >[2012-05-30 11:40:34,814] DEBUG : TSINFO: Marking libxml2-devel-2.7.8-7.fc17.i686 as install for xmlrpc-c-devel-1.29.0-1701.svn2233.fc17.i686 >[2012-05-30 11:40:34,820] DEBUG : TSINFO: Marking yum-metadata-parser-1.1.4-6.fc17.i686 as install for yum-3.4.3-23.fc17.noarch >[2012-05-30 11:40:34,821] DEBUG : TSINFO: Marking pygpgme-0.2-2.fc17.i686 as install for yum-3.4.3-23.fc17.noarch >[2012-05-30 11:40:34,870] DEBUG : TSINFO: Marking libwmf-lite-0.2.8.4-32.fc17.i686 as install for ImageMagick-6.7.5.6-3.fc17.i686 >[2012-05-30 11:40:34,872] DEBUG : TSINFO: Marking libtool-ltdl-2.4.2-3.fc17.i686 as install for ImageMagick-6.7.5.6-3.fc17.i686 >[2012-05-30 11:40:34,875] DEBUG : TSINFO: Marking lcms-libs-1.19-5.fc17.i686 as install for ImageMagick-6.7.5.6-3.fc17.i686 >[2012-05-30 11:40:34,876] DEBUG : TSINFO: Marking jasper-libs-1.900.1-19.fc17.i686 as install for ImageMagick-6.7.5.6-3.fc17.i686 >[2012-05-30 11:40:34,878] DEBUG : TSINFO: Marking ghostscript-9.05-1.fc17.i686 as install for ImageMagick-6.7.5.6-3.fc17.i686 >[2012-05-30 11:40:34,879] DEBUG : TSINFO: Marking libXt-1.1.2-2.fc17.i686 as install for ImageMagick-6.7.5.6-3.fc17.i686 >[2012-05-30 11:40:34,881] DEBUG : TSINFO: Marking libXext-1.3.1-1.fc17.i686 as install for ImageMagick-6.7.5.6-3.fc17.i686 >[2012-05-30 11:40:34,882] DEBUG : TSINFO: Marking ilmbase-1.0.2-4.fc17.i686 as install for ImageMagick-6.7.5.6-3.fc17.i686 >[2012-05-30 11:40:34,883] DEBUG : Quick matched ilmbase-1.0.2-4.fc17.i686 to require for libIlmThread.so.6 >[2012-05-30 11:40:34,884] DEBUG : TSINFO: Marking OpenEXR-libs-1.7.0-4.fc17.i686 as install for ImageMagick-6.7.5.6-3.fc17.i686 >[2012-05-30 11:40:34,885] DEBUG : Quick matched ilmbase-1.0.2-4.fc17.i686 to require for libHalf.so.6 >[2012-05-30 11:40:34,914] DEBUG : TSINFO: Marking jpackage-utils-1.7.5-18.fc17.i686 as install for apache-commons-collections-3.2.1-12.fc17.noarch >[2012-05-30 11:40:34,914] DEBUG : Quick matched jpackage-utils-1.7.5-18.fc17.i686 to require for jpackage-utils >[2012-05-30 11:40:34,939] DEBUG : TSINFO: Marking libdaemon-0.14-3.fc17.i686 as install for avahi-autoipd-0.6.30-7.fc17.i686 >[2012-05-30 11:40:34,948] DEBUG : TSINFO: Marking 32:bind-license-9.9.0-4.fc17.noarch as install for 32:bind-libs-9.9.0-4.fc17.i686 >[2012-05-30 11:40:34,969] DEBUG : TSINFO: Marking pixman-0.24.4-2.fc17.i686 as install for cairo-1.10.2-7.fc17.i686 >[2012-05-30 11:40:34,976] DEBUG : TSINFO: Marking ppl-0.11.2-8.fc17.i686 as install for cloog-ppl-0.15.11-3.fc17.1.i686 >[2012-05-30 11:40:34,977] DEBUG : Quick matched ppl-0.11.2-8.fc17.i686 to require for libppl.so.9 >[2012-05-30 11:40:34,990] DEBUG : TSINFO: Marking python-deltarpm-3.6-0.7.20110223git.fc17.i686 as install for createrepo-0.9.9-11.fc17.noarch >[2012-05-30 11:40:34,992] DEBUG : TSINFO: Marking pyliblzma-0.5.3-6.fc17.i686 as install for createrepo-0.9.9-11.fc17.noarch >[2012-05-30 11:40:34,993] DEBUG : TSINFO: Marking libxml2-python-2.7.8-7.fc17.i686 as install for createrepo-0.9.9-11.fc17.noarch >[2012-05-30 11:40:34,995] DEBUG : TSINFO: Marking deltarpm-3.6-0.7.20110223git.fc17.i686 as install for createrepo-0.9.9-11.fc17.noarch >[2012-05-30 11:40:35,003] DEBUG : TSINFO: Marking libgpg-error-1.10-2.fc17.i686 as install for cryptsetup-libs-1.4.2-1.fc17.i686 >[2012-05-30 11:40:35,004] DEBUG : TSINFO: Marking libgcrypt-1.5.0-3.fc17.i686 as install for cryptsetup-libs-1.4.2-1.fc17.i686 >[2012-05-30 11:40:35,005] DEBUG : Quick matched libgcrypt-1.5.0-3.fc17.i686 to require for libgcrypt.so.11 >[2012-05-30 11:40:35,051] DEBUG : TSINFO: Marking device-mapper-1.02.74-6.fc17.i686 as install for device-mapper-libs-1.02.74-6.fc17.i686 >[2012-05-30 11:40:35,072] DEBUG : TSINFO: Marking 1:hardlink-1.0-13.fc17.i686 as install for dracut-018-40.git20120522.fc17.noarch >[2012-05-30 11:40:35,093] DEBUG : TSINFO: Marking liblockfile-1.08-12.fc17.i686 as install for 1:emacs-common-24.0.95-1.fc17.i686 >[2012-05-30 11:40:35,101] DEBUG : TSINFO: Marking fakeroot-libs-1.12.4-4.fc17.i686 as install for fakeroot-1.12.4-4.fc17.i686 >[2012-05-30 11:40:35,110] DEBUG : TSINFO: Marking pyrpkg-1.17-1.fc17.noarch as install for fedpkg-1.9-1.fc17.noarch >[2012-05-30 11:40:35,111] DEBUG : TSINFO: Marking python-offtrac-0.0.3-4.fc17.noarch as install for fedpkg-1.9-1.fc17.noarch >[2012-05-30 11:40:35,123] DEBUG : TSINFO: Marking fipscheck-1.3.0-3.fc17.i686 as install for fipscheck-lib-1.3.0-3.fc17.i686 >[2012-05-30 11:40:35,129] DEBUG : TSINFO: Marking fontpackages-filesystem-1.44-3.fc17.noarch as install for fontconfig-2.8.0-6.fc17.i686 >[2012-05-30 11:40:35,146] DEBUG : TSINFO: Marking shared-mime-info-1.0-1.fc17.i686 as install for gdk-pixbuf2-2.26.1-1.fc17.i686 >[2012-05-30 11:40:35,154] DEBUG : TSINFO: Marking gettext-common-devel-0.18.1.1-12.fc17.noarch as install for gettext-devel-0.18.1.1-12.fc17.i686 >[2012-05-30 11:40:35,172] DEBUG : TSINFO: Marking libffi-3.0.10-2.fc17.i686 as install for glib2-2.32.1-1.fc17.i686 >[2012-05-30 11:40:35,175] DEBUG : TSINFO: Marking gamin-0.1.10-12.fc17.i686 as install for glib2-2.32.1-1.fc17.i686 >[2012-05-30 11:40:35,182] DEBUG : TSINFO: Marking tzdata-2012c-1.fc17.noarch as install for glibc-common-2.15-37.fc17.i686 >[2012-05-30 11:40:35,196] DEBUG : TSINFO: Marking glibc-headers-2.15-37.fc17.i686 as install for glibc-devel-2.15-37.fc17.i686 >[2012-05-30 11:40:35,196] DEBUG : Quick matched glibc-headers-2.15-37.fc17.i686 to require for glibc-headers >[2012-05-30 11:40:35,207] DEBUG : TSINFO: Marking libtasn1-2.12-1.fc17.i686 as install for gnutls-2.12.17-1.fc17.i686 >[2012-05-30 11:40:35,207] DEBUG : Quick matched libtasn1-2.12-1.fc17.i686 to require for libtasn1.so.3 >[2012-05-30 11:40:35,208] DEBUG : TSINFO: Marking p11-kit-0.12-1.fc17.i686 as install for gnutls-2.12.17-1.fc17.i686 >[2012-05-30 11:40:35,235] DEBUG : TSINFO: Marking libXrandr-1.3.1-3.fc17.i686 as install for gtk2-2.24.10-1.fc17.i686 >[2012-05-30 11:40:35,237] DEBUG : TSINFO: Marking 1:cups-libs-1.5.2-12.fc17.i686 as install for gtk2-2.24.10-1.fc17.i686 >[2012-05-30 11:40:35,239] DEBUG : TSINFO: Marking libXinerama-1.1.2-1.fc17.i686 as install for gtk2-2.24.10-1.fc17.i686 >[2012-05-30 11:40:35,240] DEBUG : TSINFO: Marking libXi-1.6.1-1.fc17.i686 as install for gtk2-2.24.10-1.fc17.i686 >[2012-05-30 11:40:35,242] DEBUG : TSINFO: Marking libXfixes-5.0-2.fc17.i686 as install for gtk2-2.24.10-1.fc17.i686 >[2012-05-30 11:40:35,243] DEBUG : TSINFO: Marking libXdamage-1.1.3-3.fc17.i686 as install for gtk2-2.24.10-1.fc17.i686 >[2012-05-30 11:40:35,244] DEBUG : TSINFO: Marking libXcursor-1.1.13-1.fc17.i686 as install for gtk2-2.24.10-1.fc17.i686 >[2012-05-30 11:40:35,246] DEBUG : TSINFO: Marking libXcomposite-0.4.3-3.fc17.i686 as install for gtk2-2.24.10-1.fc17.i686 >[2012-05-30 11:40:35,286] DEBUG : TSINFO: Marking tzdata-java-2012c-1.fc17.noarch as install for 1:java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6.i686 >[2012-05-30 11:40:35,287] DEBUG : TSINFO: Marking rhino-1.7R3-4.fc17.noarch as install for 1:java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6.i686 >[2012-05-30 11:40:35,290] DEBUG : TSINFO: Marking pulseaudio-libs-1.1-9.fc17.i686 as install for 1:java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6.i686 >[2012-05-30 11:40:35,291] DEBUG : Quick matched pulseaudio-libs-1.1-9.fc17.i686 to require for libpulse.so.0 >[2012-05-30 11:40:35,292] DEBUG : TSINFO: Marking lcms2-2.3-2.fc17.i686 as install for 1:java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6.i686 >[2012-05-30 11:40:35,294] DEBUG : TSINFO: Marking libXtst-1.2.0-3.fc17.i686 as install for 1:java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6.i686 >[2012-05-30 11:40:35,296] DEBUG : TSINFO: Marking ca-certificates-2012.81-1.fc17.noarch as install for 1:java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6.i686 >[2012-05-30 11:40:35,322] DEBUG : TSINFO: Marking groff-1.21-8.fc17.i686 as install for less-444-5.fc17.i686 >[2012-05-30 11:40:35,332] DEBUG : TSINFO: Marking libX11-common-1.4.99.901-2.fc17.noarch as install for libX11-1.4.99.901-2.fc17.i686 >[2012-05-30 11:40:35,336] DEBUG : TSINFO: Marking libxcb-1.8.1-1.fc17.i686 as install for libX11-1.4.99.901-2.fc17.i686 >[2012-05-30 11:40:35,381] DEBUG : TSINFO: Marking libpciaccess-0.13.1-1.fc17.i686 as install for libdrm-2.4.33-3.fc17.i686 >[2012-05-30 11:40:35,404] DEBUG : TSINFO: Marking xml-common-0.6.3-36.fc17.noarch as install for libglade2-2.6.4-8.fc17.i686 >[2012-05-30 11:40:35,427] DEBUG : TSINFO: Marking libref_array-0.1.2-8.fc17.i686 as install for libini_config-0.6.2-8.fc17.i686 >[2012-05-30 11:40:35,428] DEBUG : TSINFO: Marking libpath_utils-0.2.1-8.fc17.i686 as install for libini_config-0.6.2-8.fc17.i686 >[2012-05-30 11:40:35,445] DEBUG : TSINFO: Marking libtdb-devel-1.2.9-14.fc17.i686 as install for libldb-devel-1.1.4-2.fc17.i686 >[2012-05-30 11:40:35,446] DEBUG : Quick matched libtdb-devel-1.2.9-14.fc17.i686 to require for pkgconfig(tdb) >[2012-05-30 11:40:35,469] DEBUG : TSINFO: Marking libXmu-1.1.0-3.fc17.i686 as install for libotf-0.9.12-3.fc17.i686 >[2012-05-30 11:40:35,471] DEBUG : TSINFO: Marking libXaw-1.0.9-3.fc17.i686 as install for libotf-0.9.12-3.fc17.i686 >[2012-05-30 11:40:35,480] DEBUG : TSINFO: Marking cracklib-dicts-2.8.18-3.fc17.i686 as install for libpwquality-1.0.0-2.fc17.i686 >[2012-05-30 11:40:35,482] DEBUG : TSINFO: Marking cracklib-2.8.18-3.fc17.i686 as install for libpwquality-1.0.0-2.fc17.i686 >[2012-05-30 11:40:35,503] DEBUG : TSINFO: Marking gtk3-3.4.3-2.fc17.i686 as install for librsvg2-2.36.1-1.fc17.i686 >[2012-05-30 11:40:35,504] DEBUG : Quick matched gtk3-3.4.3-2.fc17.i686 to require for libgdk-3.so.0 >[2012-05-30 11:40:35,505] DEBUG : TSINFO: Marking cairo-gobject-1.10.2-7.fc17.i686 as install for librsvg2-2.36.1-1.fc17.i686 >[2012-05-30 11:40:35,513] DEBUG : TSINFO: Marking libsepol-devel-2.1.5-3.fc17.i686 as install for libselinux-devel-2.1.10-3.fc17.i686 >[2012-05-30 11:40:35,513] DEBUG : Quick matched libsepol-devel-2.1.5-3.fc17.i686 to require for pkgconfig(libsepol) >[2012-05-30 11:40:35,521] DEBUG : TSINFO: Marking ustr-1.0.4-12.fc17.i686 as install for libsemanage-2.1.6-3.fc17.i686 >[2012-05-30 11:40:35,521] DEBUG : Quick matched ustr-1.0.4-12.fc17.i686 to require for libustr-1.0.so.1(USTR_1.0) >[2012-05-30 11:40:35,521] DEBUG : Quick matched ustr-1.0.4-12.fc17.i686 to require for libustr-1.0.so.1 >[2012-05-30 11:40:35,567] DEBUG : TSINFO: Marking libusb1-1.0.9-0.6.rc1.fc17.i686 as install for 1:libusb-0.1.3-10.fc17.i686 >[2012-05-30 11:40:35,607] DEBUG : TSINFO: Marking netxen-firmware-4.0.534-5.fc17.noarch as install for linux-firmware-20120206-0.3.git06c8f81.fc17.noarch >[2012-05-30 11:40:35,625] DEBUG : TSINFO: Marking device-mapper-event-1.02.74-6.fc17.i686 as install for lvm2-libs-2.02.95-6.fc17.i686 >[2012-05-30 11:40:35,631] DEBUG : TSINFO: Marking m17n-db-1.6.3-3.fc17.noarch as install for m17n-lib-1.6.3-2.fc17.i686 >[2012-05-30 11:40:35,640] DEBUG : TSINFO: Marking libpipeline-1.2.0-2.fc17.i686 as install for man-db-2.6.0.2-6.fc17.i686 >[2012-05-30 11:40:35,642] DEBUG : TSINFO: Marking gdbm-1.10-2.fc17.i686 as install for man-db-2.6.0.2-6.fc17.i686 >[2012-05-30 11:40:35,643] DEBUG : TSINFO: Marking groff-base-1.21-8.fc17.i686 as install for man-db-2.6.0.2-6.fc17.i686 >[2012-05-30 11:40:35,654] DEBUG : TSINFO: Marking ncurses-base-5.9-4.20120204.fc17.i686 as install for ncurses-libs-5.9-4.20120204.fc17.i686 >[2012-05-30 11:40:35,664] DEBUG : TSINFO: Marking libproxy-0.4.7-4.fc17.i686 as install for neon-0.29.6-2.fc17.i686 >[2012-05-30 11:40:35,666] DEBUG : TSINFO: Marking pakchois-0.4-5.i686 as install for neon-0.29.6-2.fc17.i686 >[2012-05-30 11:40:35,676] DEBUG : TSINFO: Marking newt-0.52.14-2.fc17.i686 as install for newt-python-0.52.14-2.fc17.i686 >[2012-05-30 11:40:35,676] DEBUG : Quick matched newt-0.52.14-2.fc17.i686 to require for libnewt.so.0.52(NEWT_0.52.6) >[2012-05-30 11:40:35,676] DEBUG : Quick matched newt-0.52.14-2.fc17.i686 to require for libnewt.so.0.52(NEWT_0.52.13) >[2012-05-30 11:40:35,676] DEBUG : Quick matched newt-0.52.14-2.fc17.i686 to require for libnewt.so.0.52(NEWT_0.52) >[2012-05-30 11:40:35,677] DEBUG : Quick matched newt-0.52.14-2.fc17.i686 to require for libnewt.so.0.52 >[2012-05-30 11:40:35,697] DEBUG : TSINFO: Marking nss-softokn-freebl-devel-3.13.4-2.fc17.i686 as install for nss-softokn-devel-3.13.4-2.fc17.i686 >[2012-05-30 11:40:35,781] DEBUG : TSINFO: Marking libthai-0.1.14-5.fc17.i686 as install for pango-1.30.0-1.fc17.i686 >[2012-05-30 11:40:35,782] DEBUG : Quick matched libthai-0.1.14-5.fc17.i686 to require for libthai.so.0(LIBTHAI_0.1) >[2012-05-30 11:40:35,782] DEBUG : Quick matched libthai-0.1.14-5.fc17.i686 to require for libthai.so.0 >[2012-05-30 11:40:35,813] DEBUG : TSINFO: Marking perl-threads-shared-1.40-2.fc17.i686 as install for 4:perl-5.14.2-211.fc17.i686 >[2012-05-30 11:40:35,816] DEBUG : TSINFO: Marking perl-Scalar-List-Utils-1.25-1.fc17.i686 as install for 4:perl-5.14.2-211.fc17.i686 >[2012-05-30 11:40:35,817] DEBUG : TSINFO: Marking 4:perl-macros-5.14.2-211.fc17.i686 as install for 4:perl-5.14.2-211.fc17.i686 >[2012-05-30 11:40:35,821] DEBUG : TSINFO: Marking 1:perl-Pod-Simple-3.16-211.fc17.noarch as install for 4:perl-5.14.2-211.fc17.i686 >[2012-05-30 11:40:35,823] DEBUG : TSINFO: Marking 1:perl-Module-Pluggable-3.90-211.fc17.noarch as install for 4:perl-5.14.2-211.fc17.i686 >[2012-05-30 11:40:35,862] DEBUG : TSINFO: Marking perl-XML-SAX-Base-1.08-2.fc17.noarch as install for 1:perl-XML-LibXML-1.90-1.fc17.i686 >[2012-05-30 11:40:35,864] DEBUG : TSINFO: Marking perl-XML-SAX-0.99-2.fc17.noarch as install for 1:perl-XML-LibXML-1.90-1.fc17.i686 >[2012-05-30 11:40:35,866] DEBUG : TSINFO: Marking perl-XML-NamespaceSupport-1.11-6.fc17.noarch as install for 1:perl-XML-LibXML-1.90-1.fc17.i686 >[2012-05-30 11:40:35,873] DEBUG : TSINFO: Marking perl-URI-1.60-1.fc17.noarch as install for perl-XML-Parser-2.41-4.fc17.i686 >[2012-05-30 11:40:35,874] DEBUG : Quick matched perl-URI-1.60-1.fc17.noarch to require for perl(URI) >[2012-05-30 11:40:35,876] DEBUG : TSINFO: Marking perl-libwww-perl-6.03-2.fc17.noarch as install for perl-XML-Parser-2.41-4.fc17.i686 >[2012-05-30 11:41:13,114] DEBUG : TSINFO: Marking pki-symkey-9.0.20-1.fc17.i686 as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,115] DEBUG : TSINFO: Marking pki-java-tools-9.0.20-1.fc17.noarch as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,117] DEBUG : TSINFO: Marking tomcatjss-6.0.2-2.fc17.noarch as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,120] DEBUG : TSINFO: Marking jss-4.2.6-24.fc17.i686 as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,121] DEBUG : TSINFO: Marking velocity-1.7-3.fc17.noarch as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,126] DEBUG : TSINFO: Marking apache-commons-lang-2.6-6.fc17.noarch as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,132] DEBUG : TSINFO: Marking xml-commons-resolver-1.2-8.fc17.noarch as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,140] DEBUG : TSINFO: Marking xml-commons-apis-1.4.01-6.fc17.noarch as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,149] DEBUG : TSINFO: Marking xerces-j2-2.11.0-7.fc17.noarch as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,156] DEBUG : TSINFO: Marking xalan-j2-2.7.1-8.fc17.noarch as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,173] DEBUG : TSINFO: Marking ldapjdk-4.18-9.fc17.noarch as install for pki-common-9.0.20-1.fc17.noarch >[2012-05-30 11:41:13,201] DEBUG : TSINFO: Marking 14:libpcap-1.2.1-2.fc17.i686 as install for ppp-2.4.5-19.fc17.i686 >[2012-05-30 11:41:13,201] DEBUG : Quick matched 14:libpcap-1.2.1-2.fc17.i686 to require for libpcap.so.1 >[2012-05-30 11:41:13,210] DEBUG : TSINFO: Marking gpgme-1.3.0-5.fc17.i686 as install for pygpgme-0.2-2.fc17.i686 >[2012-05-30 11:41:13,211] DEBUG : Quick matched gpgme-1.3.0-5.fc17.i686 to require for libgpgme.so.11(GPGME_1.0) >[2012-05-30 11:41:13,211] DEBUG : Quick matched gpgme-1.3.0-5.fc17.i686 to require for libgpgme.so.11 >[2012-05-30 11:41:13,217] DEBUG : TSINFO: Marking python-bunch-1.0.1-1.fc17.noarch as install for python-fedora-0.3.28.1-1.fc17.noarch >[2012-05-30 11:41:13,220] DEBUG : TSINFO: Marking python-chardet-2.0.1-4.fc17.noarch as install for python-kitchen-1.1.1-1.fc17.noarch >[2012-05-30 11:41:13,237] DEBUG : TSINFO: Marking python-logilab-common-0.57.1-2.fc17.noarch as install for python-logilab-astng-0.23.1-1.fc17.noarch >[2012-05-30 11:41:13,240] DEBUG : TSINFO: Marking python-crypto-2.5-2.fc17.i686 as install for python-paramiko-1.7.7.1-2.fc17.noarch >[2012-05-30 11:41:13,378] DEBUG : TSINFO: Marking perl-Pod-Perldoc-3.17-2.fc17.noarch as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,379] DEBUG : Quick matched perl-Pod-Perldoc-3.17-2.fc17.noarch to require for perl(Pod::Perldoc::ToPod) >[2012-05-30 11:41:13,379] DEBUG : Quick matched perl-Pod-Perldoc-3.17-2.fc17.noarch to require for perl(Pod::Perldoc::ToNroff) >[2012-05-30 11:41:13,379] DEBUG : Quick matched perl-Pod-Perldoc-3.17-2.fc17.noarch to require for perl(Pod::Perldoc::ToMan) >[2012-05-30 11:41:13,379] DEBUG : Quick matched perl-Pod-Perldoc-3.17-2.fc17.noarch to require for perl(Pod::Perldoc::ToChecker) >[2012-05-30 11:41:13,383] DEBUG : TSINFO: Marking perl-Locale-Codes-3.21-1.fc17.noarch as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,385] DEBUG : TSINFO: Marking perl-Digest-MD5-2.51-211.fc17.i686 as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,386] DEBUG : TSINFO: Marking perl-Class-ISA-0.36-1007.fc17.noarch as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,388] DEBUG : TSINFO: Marking time-1.7-40.fc17.i686 as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,390] DEBUG : TSINFO: Marking pax-3.4-13.fc17.i686 as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,391] DEBUG : TSINFO: Marking bc-1.06.95-6.fc17.i686 as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,393] DEBUG : TSINFO: Marking at-3.1.13-8.fc17.i686 as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,397] DEBUG : TSINFO: Marking mailx-12.5-5.fc17.i686 as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,399] DEBUG : TSINFO: Marking ed-1.5-3.fc17.i686 as install for redhat-lsb-4.0-11.fc17.i686 >[2012-05-30 11:41:13,420] DEBUG : TSINFO: Marking gnupg2-2.0.18-3.fc17.i686 as install for rpm-build-libs-4.9.1.3-7.fc17.i686 >[2012-05-30 11:41:13,450] DEBUG : TSINFO: Marking python-magic-5.10-5.fc17.i686 as install for rpmlint-1.4-6.fc17.noarch >[2012-05-30 11:41:13,453] DEBUG : TSINFO: Marking python-enchant-1.6.5-4.fc17.noarch as install for rpmlint-1.4-6.fc17.noarch >[2012-05-30 11:41:13,469] DEBUG : TSINFO: Marking libyaml-0.1.4-2.fc17.i686 as install for ruby-libs-1.9.3.194-10.1.fc17.i686 >[2012-05-30 11:41:13,534] DEBUG : TSINFO: Marking 2:samba4-client-4.0.0-47alpha18.fc17.i686 as install for 2:samba4-common-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:41:13,534] DEBUG : Quick matched 2:samba4-client-4.0.0-47alpha18.fc17.i686 to require for libtrusts_util.so >[2012-05-30 11:41:13,535] DEBUG : Quick matched 2:samba4-client-4.0.0-47alpha18.fc17.i686 to require for libcli_spoolss.so(SAMBA_4.0.0ALPHA18) >[2012-05-30 11:41:13,535] DEBUG : Quick matched 2:samba4-client-4.0.0-47alpha18.fc17.i686 to require for libcli_spoolss.so >[2012-05-30 11:41:13,536] DEBUG : TSINFO: Marking libbsd-0.3.0-2.fc17.i686 as install for 2:samba4-common-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:41:13,537] DEBUG : Quick matched libbsd-0.3.0-2.fc17.i686 to require for libbsd.so.0 >[2012-05-30 11:41:13,601] DEBUG : TSINFO: Marking pytalloc-2.0.7-4.fc17.i686 as install for 2:samba4-libs-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:41:13,601] DEBUG : Quick matched pytalloc-2.0.7-4.fc17.i686 to require for libpytalloc-util.so.2 >[2012-05-30 11:41:13,670] DEBUG : TSINFO: Marking 2:samba4-4.0.0-47alpha18.fc17.i686 as install for 2:samba4-test-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:41:13,671] DEBUG : Quick matched 2:samba4-4.0.0-47alpha18.fc17.i686 to require for libsmbd_base.so >[2012-05-30 11:41:13,673] DEBUG : TSINFO: Marking 2:samba4-dc-4.0.0-47alpha18.fc17.i686 as install for 2:samba4-test-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:41:13,674] DEBUG : Quick matched 2:samba4-dc-4.0.0-47alpha18.fc17.i686 to require for libdsdb-module.so >[2012-05-30 11:41:13,674] DEBUG : Quick matched 2:samba4-dc-4.0.0-47alpha18.fc17.i686 to require for libdfs_server_ad.so(SAMBA_4.0.0ALPHA18) >[2012-05-30 11:41:13,674] DEBUG : Quick matched 2:samba4-dc-4.0.0-47alpha18.fc17.i686 to require for libdfs_server_ad.so >[2012-05-30 11:41:13,674] DEBUG : Quick matched 2:samba4-dc-4.0.0-47alpha18.fc17.i686 to require for libcmdline-credentials.so(SAMBA_4.0.0ALPHA18) >[2012-05-30 11:41:13,674] DEBUG : Quick matched 2:samba4-dc-4.0.0-47alpha18.fc17.i686 to require for libcmdline-credentials.so >[2012-05-30 11:41:13,729] DEBUG : TSINFO: Marking systemtap-runtime-1.7-7.fc17.i686 as install for systemtap-client-1.7-7.fc17.i686 >[2012-05-30 11:41:13,730] DEBUG : TSINFO: Marking zip-3.0-4.fc17.i686 as install for systemtap-client-1.7-7.fc17.i686 >[2012-05-30 11:41:13,732] DEBUG : TSINFO: Marking avahi-libs-0.6.30-7.fc17.i686 as install for systemtap-client-1.7-7.fc17.i686 >[2012-05-30 11:41:13,732] DEBUG : Quick matched avahi-libs-0.6.30-7.fc17.i686 to require for libavahi-client.so.3 >[2012-05-30 11:41:13,767] DEBUG : TSINFO: Marking tomcat6-servlet-2.5-api-6.0.32-20.fc17.noarch as install for tomcat6-lib-6.0.32-20.fc17.noarch >[2012-05-30 11:41:13,769] DEBUG : TSINFO: Marking tomcat6-jsp-2.1-api-6.0.32-20.fc17.noarch as install for tomcat6-lib-6.0.32-20.fc17.noarch >[2012-05-30 11:41:13,770] DEBUG : TSINFO: Marking tomcat6-el-2.1-api-6.0.32-20.fc17.noarch as install for tomcat6-lib-6.0.32-20.fc17.noarch >[2012-05-30 11:41:13,773] DEBUG : TSINFO: Marking 1:ecj-3.4.2-13.fc17.i686 as install for tomcat6-lib-6.0.32-20.fc17.noarch >[2012-05-30 11:41:13,786] DEBUG : TSINFO: Marking hwdata-0.234-2.fc17.noarch as install for udev-182-1.fc17.i686 >[2012-05-30 11:41:13,800] DEBUG : TSINFO: Marking 2:vim-filesystem-7.3.515-1.fc17.i686 as install for 2:vim-common-7.3.515-1.fc17.i686 >[2012-05-30 11:41:13,833] DEBUG : TSINFO: Marking 1:xorg-x11-font-utils-7.5-7.fc17.i686 as install for xorg-x11-fonts-misc-7.5-5.fc17.noarch >[2012-05-30 11:41:13,834] DEBUG : Quick matched 1:xorg-x11-font-utils-7.5-7.fc17.i686 to require for mkfontdir >[2012-05-30 11:41:13,847] DEBUG : TSINFO: Marking libyubikey-1.7-2.fc17.i686 as install for ykpers-1.6.3-1.fc17.i686 >[2012-05-30 11:41:13,847] DEBUG : Quick matched libyubikey-1.7-2.fc17.i686 to require for libyubikey.so.0(YUBIKEY_1.0) >[2012-05-30 11:41:13,848] DEBUG : Quick matched libyubikey-1.7-2.fc17.i686 to require for libyubikey.so.0 >[2012-05-30 11:41:13,947] DEBUG : TSINFO: Marking urw-fonts-2.4-11.fc17.noarch as install for ghostscript-9.05-1.fc17.i686 >[2012-05-30 11:41:13,948] DEBUG : TSINFO: Marking poppler-data-0.4.5-2.fc17.noarch as install for ghostscript-9.05-1.fc17.i686 >[2012-05-30 11:41:13,950] DEBUG : TSINFO: Marking ghostscript-fonts-5.50-28.fc17.noarch as install for ghostscript-9.05-1.fc17.i686 >[2012-05-30 11:41:13,956] DEBUG : TSINFO: Marking kernel-headers-3.3.7-1.fc17.i686 as install for glibc-headers-2.15-37.fc17.i686 >[2012-05-30 11:41:13,956] DEBUG : Quick matched kernel-headers-3.3.7-1.fc17.i686 to require for kernel-headers >[2012-05-30 11:41:13,968] DEBUG : TSINFO: Marking pinentry-0.8.1-6.fc17.i686 as install for gnupg2-2.0.18-3.fc17.i686 >[2012-05-30 11:41:13,970] DEBUG : TSINFO: Marking pth-2.0.7-15.fc17.i686 as install for gnupg2-2.0.18-3.fc17.i686 >[2012-05-30 11:41:13,971] DEBUG : TSINFO: Marking libassuan-2.0.1-2.fc17.i686 as install for gnupg2-2.0.18-3.fc17.i686 >[2012-05-30 11:41:13,971] DEBUG : Quick matched libassuan-2.0.1-2.fc17.i686 to require for libassuan.so.0 >[2012-05-30 11:41:14,006] DEBUG : TSINFO: Marking colord-0.1.18-2.fc17.i686 as install for gtk3-3.4.3-2.fc17.i686 >[2012-05-30 11:41:14,094] DEBUG : TSINFO: Marking libmodman-2.0.1-4.fc17.i686 as install for libproxy-0.4.7-4.fc17.i686 >[2012-05-30 11:41:14,313] DEBUG : TSINFO: Marking libXau-1.0.6-3.fc17.i686 as install for libxcb-1.8.1-1.fc17.i686 >[2012-05-30 11:41:14,358] DEBUG : TSINFO: Marking perl-Digest-1.17-2.fc17.noarch as install for perl-Digest-MD5-2.51-211.fc17.i686 >[2012-05-30 11:41:14,379] DEBUG : TSINFO: Marking 1:perl-parent-0.225-211.fc17.noarch as install for perl-Pod-Perldoc-3.17-2.fc17.noarch >[2012-05-30 11:41:14,387] DEBUG : TSINFO: Marking 1:perl-Pod-Escapes-1.04-211.fc17.noarch as install for 1:perl-Pod-Simple-3.16-211.fc17.noarch >[2012-05-30 11:41:14,424] DEBUG : TSINFO: Marking perl-WWW-RobotRules-6.01-4.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,426] DEBUG : TSINFO: Marking perl-Net-HTTP-6.02-2.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,427] DEBUG : TSINFO: Marking perl-LWP-MediaTypes-6.01-4.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,429] DEBUG : TSINFO: Marking perl-HTTP-Message-6.03-1.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,429] DEBUG : Quick matched perl-HTTP-Message-6.03-1.fc17.noarch to require for perl(HTTP::Response) >[2012-05-30 11:41:14,429] DEBUG : Quick matched perl-HTTP-Message-6.03-1.fc17.noarch to require for perl(HTTP::Request::Common) >[2012-05-30 11:41:14,430] DEBUG : Quick matched perl-HTTP-Message-6.03-1.fc17.noarch to require for perl(HTTP::Request) >[2012-05-30 11:41:14,431] DEBUG : TSINFO: Marking perl-HTTP-Negotiate-6.00-4.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,432] DEBUG : TSINFO: Marking perl-HTTP-Date-6.00-3.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,434] DEBUG : TSINFO: Marking perl-HTTP-Daemon-6.00-4.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,435] DEBUG : TSINFO: Marking perl-HTTP-Cookies-6.00-4.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,437] DEBUG : TSINFO: Marking perl-File-Listing-6.03-2.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,438] DEBUG : TSINFO: Marking perl-HTML-Parser-3.69-3.fc17.i686 as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,439] DEBUG : Quick matched perl-HTML-Parser-3.69-3.fc17.i686 to require for perl(HTML::Entities) >[2012-05-30 11:41:14,440] DEBUG : TSINFO: Marking perl-Encode-Locale-1.02-5.fc17.noarch as install for perl-libwww-perl-6.03-2.fc17.noarch >[2012-05-30 11:41:14,453] DEBUG : TSINFO: Marking pki-util-9.0.20-1.fc17.noarch as install for pki-java-tools-9.0.20-1.fc17.noarch >[2012-05-30 11:41:14,454] DEBUG : TSINFO: Marking pki-native-tools-9.0.20-1.fc17.i686 as install for pki-java-tools-9.0.20-1.fc17.noarch >[2012-05-30 11:41:14,471] DEBUG : TSINFO: Marking ppl-pwl-0.11.2-8.fc17.i686 as install for ppl-0.11.2-8.fc17.i686 >[2012-05-30 11:41:14,483] DEBUG : TSINFO: Marking libsndfile-1.0.25-2.fc17.i686 as install for pulseaudio-libs-1.1-9.fc17.i686 >[2012-05-30 11:41:14,484] DEBUG : Quick matched libsndfile-1.0.25-2.fc17.i686 to require for libsndfile.so.1 >[2012-05-30 11:41:14,485] DEBUG : TSINFO: Marking json-c-0.9-4.fc17.i686 as install for pulseaudio-libs-1.1-9.fc17.i686 >[2012-05-30 11:41:14,487] DEBUG : TSINFO: Marking libasyncns-0.8-3.fc17.i686 as install for pulseaudio-libs-1.1-9.fc17.i686 >[2012-05-30 11:41:14,496] DEBUG : TSINFO: Marking GitPython-0.3.2-0.2.RC1.fc17.noarch as install for pyrpkg-1.17-1.fc17.noarch >[2012-05-30 11:41:14,511] DEBUG : TSINFO: Marking 1:enchant-1.6.0-4.fc17.i686 as install for python-enchant-1.6.5-4.fc17.noarch >[2012-05-30 11:41:14,516] DEBUG : TSINFO: Marking mx-3.2.3-1.fc17.i686 as install for python-logilab-common-0.57.1-2.fc17.noarch >[2012-05-30 11:41:14,521] DEBUG : TSINFO: Marking jline-1.0-1.fc17.noarch as install for rhino-1.7R3-4.fc17.noarch >[2012-05-30 11:41:14,573] DEBUG : TSINFO: Marking perl-Parse-Yapp-1.05-46.fc17.noarch as install for 2:samba4-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:41:14,574] DEBUG : TSINFO: Marking 2:samba4-winbind-4.0.0-47alpha18.fc17.i686 as install for 2:samba4-4.0.0-47alpha18.fc17.i686 >[2012-05-30 11:41:14,575] DEBUG : Quick matched 2:samba4-winbind-4.0.0-47alpha18.fc17.i686 to require for libidmap.so >[2012-05-30 11:41:14,710] DEBUG : TSINFO: Marking werken-xpath-0.9.4-7.beta.12.4.fc17.noarch as install for velocity-1.7-3.fc17.noarch >[2012-05-30 11:41:14,712] DEBUG : TSINFO: Marking log4j-1.2.16-11.fc17.noarch as install for velocity-1.7-3.fc17.noarch >[2012-05-30 11:41:14,715] DEBUG : TSINFO: Marking junit-4.10-5.fc17.noarch as install for velocity-1.7-3.fc17.noarch >[2012-05-30 11:41:14,716] DEBUG : TSINFO: Marking jdom-1.1.3-1.fc17.noarch as install for velocity-1.7-3.fc17.noarch >[2012-05-30 11:41:14,718] DEBUG : TSINFO: Marking jakarta-oro-2.0.8-10.fc17.noarch as install for velocity-1.7-3.fc17.noarch >[2012-05-30 11:41:14,719] DEBUG : TSINFO: Marking 1:hsqldb-1.8.1.3-7.fc17.noarch as install for velocity-1.7-3.fc17.noarch >[2012-05-30 11:41:14,721] DEBUG : TSINFO: Marking bcel-5.2-10.fc17.noarch as install for velocity-1.7-3.fc17.noarch >[2012-05-30 11:41:14,742] DEBUG : TSINFO: Marking libfontenc-1.1.0-2.fc17.i686 as install for 1:xorg-x11-font-utils-7.5-7.fc17.i686 >[2012-05-30 11:41:14,744] DEBUG : TSINFO: Marking libXfont-1.4.5-1.fc17.i686 as install for 1:xorg-x11-font-utils-7.5-7.fc17.i686 >[2012-05-30 11:41:14,750] DEBUG : TSINFO: Marking python-gitdb-0.5.4-3.fc17.i686 as install for GitPython-0.3.2-0.2.RC1.fc17.noarch >[2012-05-30 11:41:14,754] DEBUG : TSINFO: Marking regexp-1.5-7.fc17.noarch as install for bcel-5.2-10.fc17.noarch >[2012-05-30 11:41:14,766] DEBUG : TSINFO: Marking shared-color-profiles-0.1.5-2.fc17.noarch as install for colord-0.1.18-2.fc17.i686 >[2012-05-30 11:41:14,799] DEBUG : TSINFO: Marking sane-backends-drivers-scanners-1.0.22-10.fc17.i686 as install for colord-0.1.18-2.fc17.i686 >[2012-05-30 11:41:14,801] DEBUG : TSINFO: Marking libgusb-0.1.3-2.fc17.i686 as install for colord-0.1.18-2.fc17.i686 >[2012-05-30 11:41:14,802] DEBUG : TSINFO: Marking color-filesystem-1-9.noarch as install for colord-0.1.18-2.fc17.i686 >[2012-05-30 11:41:14,809] DEBUG : TSINFO: Marking hunspell-1.3.2-4.fc17.i686 as install for 1:enchant-1.6.0-4.fc17.i686 >[2012-05-30 11:41:14,818] DEBUG : TSINFO: Marking tomcat-servlet-3.0-api-7.0.27-2.fc17.noarch as install for 1:hsqldb-1.8.1.3-7.fc17.noarch >[2012-05-30 11:41:14,826] DEBUG : TSINFO: Marking hamcrest-1.1-12.fc17.noarch as install for junit-4.10-5.fc17.noarch >[2012-05-30 11:41:14,851] DEBUG : TSINFO: Marking 1:libvorbis-1.3.3-1.fc17.i686 as install for libsndfile-1.0.25-2.fc17.i686 >[2012-05-30 11:41:14,852] DEBUG : Quick matched 1:libvorbis-1.3.3-1.fc17.i686 to require for libvorbis.so.0 >[2012-05-30 11:41:14,855] DEBUG : TSINFO: Marking 2:libogg-1.3.0-1.fc17.i686 as install for libsndfile-1.0.25-2.fc17.i686 >[2012-05-30 11:41:14,856] DEBUG : TSINFO: Marking gsm-1.0.13-6.fc17.i686 as install for libsndfile-1.0.25-2.fc17.i686 >[2012-05-30 11:41:14,858] DEBUG : TSINFO: Marking flac-1.2.1-9.fc17.i686 as install for libsndfile-1.0.25-2.fc17.i686 >[2012-05-30 11:41:14,879] DEBUG : TSINFO: Marking perl-HTML-Tagset-3.20-10.fc17.noarch as install for perl-HTML-Parser-3.69-3.fc17.i686 >[2012-05-30 11:41:14,879] DEBUG : Quick matched perl-HTML-Tagset-3.20-10.fc17.noarch to require for perl(HTML::Tagset) >[2012-05-30 11:41:14,890] DEBUG : TSINFO: Marking 1:perl-TimeDate-1.20-6.fc17.noarch as install for perl-HTTP-Date-6.00-3.fc17.noarch >[2012-05-30 11:41:14,910] DEBUG : TSINFO: Marking perl-IO-Compress-2.052-1.fc17.noarch as install for perl-HTTP-Message-6.03-1.fc17.noarch >[2012-05-30 11:41:14,910] DEBUG : Quick matched perl-IO-Compress-2.052-1.fc17.noarch to require for perl(IO::Compress::Bzip2) >[2012-05-30 11:41:14,911] DEBUG : Quick matched perl-IO-Compress-2.052-1.fc17.noarch to require for perl(IO::Uncompress::RawInflate) >[2012-05-30 11:41:14,911] DEBUG : Quick matched perl-IO-Compress-2.052-1.fc17.noarch to require for perl(IO::Uncompress::Inflate) >[2012-05-30 11:41:14,911] DEBUG : Quick matched perl-IO-Compress-2.052-1.fc17.noarch to require for perl(IO::Uncompress::Gunzip) >[2012-05-30 11:41:14,911] DEBUG : Quick matched perl-IO-Compress-2.052-1.fc17.noarch to require for perl(IO::Compress::Gzip) >[2012-05-30 11:41:14,911] DEBUG : Quick matched perl-IO-Compress-2.052-1.fc17.noarch to require for perl(IO::Compress::Deflate) >[2012-05-30 11:41:14,915] DEBUG : TSINFO: Marking perl-Compress-Raw-Zlib-2.052-1.fc17.i686 as install for perl-HTTP-Message-6.03-1.fc17.noarch >[2012-05-30 11:41:14,924] DEBUG : TSINFO: Marking perl-IO-Socket-SSL-1.66-1.fc17.noarch as install for perl-Net-HTTP-6.02-2.fc17.noarch >[2012-05-30 11:41:14,948] DEBUG : TSINFO: Marking osutil-2.0.2-2.fc17.i686 as install for pki-util-9.0.20-1.fc17.noarch >[2012-05-30 11:41:15,003] DEBUG : TSINFO: Marking qdox-1.12-4.fc17.noarch as install for hamcrest-1.1-12.fc17.noarch >[2012-05-30 11:41:15,039] DEBUG : TSINFO: Marking perl-Compress-Raw-Bzip2-2.052-1.fc17.i686 as install for perl-IO-Compress-2.052-1.fc17.noarch >[2012-05-30 11:41:15,047] DEBUG : TSINFO: Marking perl-Net-SSLeay-1.48-1.fc17.i686 as install for perl-IO-Socket-SSL-1.66-1.fc17.noarch >[2012-05-30 11:41:15,048] DEBUG : TSINFO: Marking perl-Net-LibIDN-0.12-8.fc17.i686 as install for perl-IO-Socket-SSL-1.66-1.fc17.noarch >[2012-05-30 11:41:15,056] DEBUG : TSINFO: Marking python-async-0.6.1-4.fc17.i686 as install for python-gitdb-0.5.4-3.fc17.i686 >[2012-05-30 11:41:15,057] DEBUG : TSINFO: Marking python-smmap-0.8.1-4.fc17.noarch as install for python-gitdb-0.5.4-3.fc17.i686 >[2012-05-30 11:41:15,068] DEBUG : TSINFO: Marking sane-backends-libs-1.0.22-10.fc17.i686 as install for sane-backends-drivers-scanners-1.0.22-10.fc17.i686 >[2012-05-30 11:41:15,070] DEBUG : TSINFO: Marking sane-backends-1.0.22-10.fc17.i686 as install for sane-backends-drivers-scanners-1.0.22-10.fc17.i686 >[2012-05-30 11:41:15,071] DEBUG : TSINFO: Marking libv4l-0.8.7-1.fc17.i686 as install for sane-backends-drivers-scanners-1.0.22-10.fc17.i686 >[2012-05-30 11:41:15,073] DEBUG : TSINFO: Marking libieee1284-0.2.11-11.fc17.i686 as install for sane-backends-drivers-scanners-1.0.22-10.fc17.i686 >[2012-05-30 11:41:15,117] DEBUG : TSINFO: Marking libgphoto2-2.4.14-1.fc17.i686 as install for sane-backends-1.0.22-10.fc17.i686 >[2012-05-30 11:41:15,118] DEBUG : Quick matched libgphoto2-2.4.14-1.fc17.i686 to require for libgphoto2.so.2 >[2012-05-30 11:41:15,120] DEBUG : TSINFO: Marking libexif-0.6.20-2.fc17.i686 as install for sane-backends-1.0.22-10.fc17.i686 >[2012-05-30 11:41:15,143] DEBUG : TSINFO: Marking lockdev-1.0.4-0.4.20111007git.fc17.i686 as install for libgphoto2-2.4.14-1.fc17.i686 >[2012-05-30 11:41:15,143] DEBUG : Quick matched lockdev-1.0.4-0.4.20111007git.fc17.i686 to require for liblockdev.so.1 >[2012-05-30 11:41:15,145] DEBUG : TSINFO: Marking gd-2.0.35-16.fc17.i686 as install for libgphoto2-2.4.14-1.fc17.i686 >[2012-05-30 11:41:18,840] DEBUG : Depsolve time: 46.370 >[2012-05-30 11:55:37,785] DEBUG : Warning: scriptlet or other non-fatal errors occurred during transaction. >[2012-05-30 11:55:37,900] CRIT : coreutils-8.15-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,901] CRIT : system-config-firewall-base-1.2.29-7.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,901] CRIT : libpwquality-1.0.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,901] CRIT : libcroco-0.6.5-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,901] CRIT : slapi-nis-0.41-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,902] CRIT : info-4.13a-16.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,902] CRIT : python-dns-1.9.4-1.fc16.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,902] CRIT : libxslt-1.1.26-9.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,902] CRIT : libyubikey-1.7-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,903] CRIT : libedit-3.0-6.20110802cvs.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,903] CRIT : openldap-2.4.30-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,903] CRIT : 2:samba4-common-4.0.0-47alpha18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,904] CRIT : plymouth-core-libs-0.8.4-0.20120319.2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,904] CRIT : 1:wpa_supplicant-1.0-0.4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,904] CRIT : glibc-devel-2.15-37.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,904] CRIT : 389-ds-base-devel-1.2.11.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,905] CRIT : libXi-1.6.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,905] CRIT : python-rhsm-0.99.3-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,905] CRIT : lockdev-1.0.4-0.4.20111007git.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,906] CRIT : libutempter-1.1.5-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,906] CRIT : bzip2-libs-1.0.6-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,906] CRIT : libnl-1.1-15.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,907] CRIT : 1:dbus-libs-1.4.10-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,907] CRIT : libXext-1.3.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,907] CRIT : ca-certificates-2012.81-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,907] CRIT : libXaw-1.0.9-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,908] CRIT : expat-2.1.0-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,908] CRIT : pygpgme-0.2-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,908] CRIT : colord-0.1.18-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,909] CRIT : iptables-1.4.12.2-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,909] CRIT : poppler-data-0.4.5-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,909] CRIT : apr-util-1.4.1-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,909] CRIT : xml-commons-apis-1.4.01-6.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,910] CRIT : netxen-firmware-4.0.534-5.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,910] CRIT : pciutils-libs-3.1.9-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,910] CRIT : 1:libusb-0.1.3-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,911] CRIT : 2:samba4-devel-4.0.0-47alpha18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,911] CRIT : python-urlgrabber-3.9.1-11.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,911] CRIT : python-libs-2.7.3-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,911] CRIT : device-mapper-libs-1.02.74-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,912] CRIT : velocity-1.7-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,912] CRIT : openssh-server-5.9p1-22.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,912] CRIT : xemacs-filesystem-21.5.31-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,913] CRIT : elfutils-libelf-0.153-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,913] CRIT : perl-IO-Socket-SSL-1.66-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,913] CRIT : libcap-ng-0.6.6-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,913] CRIT : jakarta-oro-2.0.8-10.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,914] CRIT : neon-0.29.6-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,914] CRIT : krb5-server-1.10-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,914] CRIT : tomcat6-el-2.1-api-6.0.32-20.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,915] CRIT : libini_config-0.6.2-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,915] CRIT : gtk3-3.4.3-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,915] CRIT : kbd-misc-1.15.3-5.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,915] CRIT : fedora-easy-karma-0-0.16.20110825git36efb338.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,916] CRIT : GitPython-0.3.2-0.2.RC1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,916] CRIT : svrcore-4.0.4-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,916] CRIT : m17n-db-1.6.3-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,917] CRIT : libtdb-devel-1.2.9-14.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,917] CRIT : python-nss-0.12-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,917] CRIT : mobile-broadband-provider-info-1.20110218-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,917] CRIT : nss-devel-3.13.4-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,918] CRIT : libXrender-0.9.7-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,918] CRIT : unzip-6.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,918] CRIT : perl-Digest-MD5-2.51-211.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,919] CRIT : systemtap-1.7-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,919] CRIT : python-polib-0.7.0-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,919] CRIT : gettext-devel-0.18.1.1-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,919] CRIT : libipa_hbac-1.8.3-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,920] CRIT : libss-1.42-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,920] CRIT : log4j-1.2.16-11.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,920] CRIT : libgphoto2-2.4.14-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,921] CRIT : rpmdevtools-8.2-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,921] CRIT : jss-4.2.6-24.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,921] CRIT : gawk-4.0.0-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,921] CRIT : libquadmath-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,922] CRIT : 1:perl-TimeDate-1.20-6.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,922] CRIT : openldap-clients-2.4.30-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,922] CRIT : gnupg-1.4.12-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,922] CRIT : pakchois-0.4-5.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,923] CRIT : 1:dbus-1.4.10-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,923] CRIT : grep-2.12-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,923] CRIT : xerces-j2-2.11.0-7.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,924] CRIT : glibc-common-2.15-37.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,924] CRIT : sane-backends-drivers-scanners-1.0.22-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,924] CRIT : e2fsprogs-libs-1.42-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,925] CRIT : wget-1.13.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,925] CRIT : python-logilab-astng-0.23.1-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,925] CRIT : pyOpenSSL-0.12-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,925] CRIT : byacc-1.9.20111219-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,926] CRIT : rootfiles-8.1-8.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,926] CRIT : kernel-PAE-3.3.7-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,926] CRIT : ImageMagick-6.7.5.6-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,927] CRIT : oddjob-mkhomedir-0.31.1-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,927] CRIT : flex-2.5.35-14.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,927] CRIT : libdb-utils-5.2.36-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,927] CRIT : libtevent-devel-0.9.15-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,928] CRIT : cpp-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,928] CRIT : 2:shadow-utils-4.1.4.3-14.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,928] CRIT : linux-firmware-20120206-0.3.git06c8f81.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,928] CRIT : rpcbind-0.2.0-16.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,929] CRIT : alsa-lib-1.0.25-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,929] CRIT : autoconf-2.68-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,929] CRIT : 12:dhcp-libs-4.2.4-0.4.rc1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,930] CRIT : libusb1-1.0.9-0.6.rc1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,930] CRIT : 1:make-3.82-9.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,930] CRIT : 1:openssl-devel-1.0.0j-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,930] CRIT : fedora-cert-0.5.9.6-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,931] CRIT : mercurial-2.2.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,931] CRIT : python-setuptools-0.6.24-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,931] CRIT : glibc-headers-2.15-37.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,932] CRIT : 1:emacs-common-24.0.95-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,932] CRIT : c-ares-1.7.5-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,932] CRIT : perl-Crypt-SSLeay-0.58-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,932] CRIT : libpciaccess-0.13.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,933] CRIT : osutil-2.0.2-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,933] CRIT : tomcat6-lib-6.0.32-20.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,933] CRIT : libsndfile-1.0.25-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,934] CRIT : python-2.7.3-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,934] CRIT : 1:emacs-24.0.95-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,934] CRIT : ed-1.5-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,934] CRIT : libquadmath-devel-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,935] CRIT : systemd-44-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,935] CRIT : 1:perl-Error-0.17016-7.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,935] CRIT : tzdata-java-2012c-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,936] CRIT : m4-1.4.16-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,936] CRIT : xml-common-0.6.3-36.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,936] CRIT : 1:emacs-filesystem-24.0.95-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,936] CRIT : pki-silent-9.0.20-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,937] CRIT : cryptsetup-libs-1.4.2-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,937] CRIT : lua-5.1.4-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,937] CRIT : libtdb-1.2.9-14.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,938] CRIT : readline-6.2-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,938] CRIT : koan-2.2.2-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,938] CRIT : jasper-libs-1.900.1-19.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,938] CRIT : perl-Pod-Perldoc-3.17-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,939] CRIT : filesystem-3-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,939] CRIT : 1:doxygen-1.8.0-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,939] CRIT : krb5-workstation-1.10-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,940] CRIT : apache-commons-lang-2.6-6.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,940] CRIT : python-kerberos-1.1-8.1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,940] CRIT : perl-Parse-Yapp-1.05-46.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,940] CRIT : libgpg-error-1.10-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,941] CRIT : nss-3.13.4-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,941] CRIT : ppp-2.4.5-19.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,941] CRIT : libSM-1.2.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,942] CRIT : pixman-0.24.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,942] CRIT : intltool-0.50.2-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,942] CRIT : librsvg2-2.36.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,942] CRIT : libverto-0.2.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,943] CRIT : 1:libvorbis-1.3.3-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,943] CRIT : hicolor-icon-theme-0.12-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,943] CRIT : bash-4.2.28-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,944] CRIT : libXinerama-1.1.2-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,944] CRIT : tomcat6-servlet-2.5-api-6.0.32-20.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,944] CRIT : usermode-1.109-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,944] CRIT : ncurses-libs-5.9-4.20120204.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,945] CRIT : cracklib-dicts-2.8.18-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,945] CRIT : popt-devel-1.13-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,945] CRIT : perl-HTML-Parser-3.69-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,946] CRIT : attr-2.4.46-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,946] CRIT : perl-libwww-perl-6.03-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,946] CRIT : perl-HTTP-Date-6.00-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,946] CRIT : automake14-1.4p6-22.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,947] CRIT : perl-HTTP-Daemon-6.00-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,947] CRIT : 2:samba4-dc-libs-4.0.0-47alpha18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,947] CRIT : libgssglue-0.3-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,948] CRIT : 1:java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,948] CRIT : python-simplejson-2.5.2-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,948] CRIT : fakeroot-1.12.4-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,948] CRIT : automake-1.11.3-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,949] CRIT : libXt-1.1.2-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,949] CRIT : python-enchant-1.6.5-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,949] CRIT : fontconfig-2.8.0-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,950] CRIT : flac-1.2.1-9.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,950] CRIT : git-1.7.10.2-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,950] CRIT : desktop-file-utils-0.19-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,950] CRIT : ghostscript-fonts-5.50-28.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,951] CRIT : pytalloc-2.0.7-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,951] CRIT : libref_array-0.1.2-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,951] CRIT : rsync-3.0.9-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,952] CRIT : python-lxml-2.3.3-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,952] CRIT : libv4l-0.8.7-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,952] CRIT : crontabs-1.11-3.20101115git.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,952] CRIT : libglade2-2.6.4-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,953] CRIT : perl-XML-SAX-Base-1.08-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,953] CRIT : file-libs-5.10-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,953] CRIT : perl-XML-Parser-2.41-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,954] CRIT : 1:perl-Module-Pluggable-3.90-211.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,954] CRIT : bodhi-client-0.8.5-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,954] CRIT : initscripts-9.37-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,954] CRIT : color-filesystem-1-9.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,955] CRIT : 1:openssl-1.0.0j-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,955] CRIT : apache-commons-daemon-1.0.10-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,955] CRIT : python-memcached-1.47-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,956] CRIT : kmod-libs-7-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,956] CRIT : nss-util-devel-3.13.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,956] CRIT : ykpers-1.6.3-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,956] CRIT : passwd-0.78.99-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,957] CRIT : libbsd-0.3.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,957] CRIT : werken-xpath-0.9.4-7.beta.12.4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,957] CRIT : OpenEXR-libs-1.7.0-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,958] CRIT : procmail-3.22-29.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,958] CRIT : texinfo-4.13a-16.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,958] CRIT : binutils-2.22.52.0.1-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,958] CRIT : python-deltarpm-3.6-0.7.20110223git.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,959] CRIT : jline-1.0-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,959] CRIT : lvm2-2.02.95-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,959] CRIT : nss-softokn-devel-3.13.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,960] CRIT : yum-3.4.3-23.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,960] CRIT : subversion-libs-1.7.4-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,960] CRIT : libtasn1-2.12-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,960] CRIT : os-prober-1.53-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,961] CRIT : GConf2-3.2.5-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,961] CRIT : perl-HTTP-Message-6.03-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,961] CRIT : urw-fonts-2.4-11.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,962] CRIT : pango-1.30.0-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,962] CRIT : diffutils-3.2-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,962] CRIT : libgcrypt-1.5.0-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,962] CRIT : acpid-2.0.16-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,963] CRIT : pki-java-tools-9.0.20-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,963] CRIT : libacl-2.2.51-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,963] CRIT : xmlrpc-c-c++-1.29.0-1701.svn2233.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,964] CRIT : libuuid-2.21.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,964] CRIT : gdk-pixbuf2-2.26.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,964] CRIT : 2:libogg-1.3.0-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,964] CRIT : libcap-2.22-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,965] CRIT : libmpc-0.9-2.fc17.2.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,965] CRIT : bc-1.06.95-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,965] CRIT : cyrus-sasl-devel-2.1.23-29.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,966] CRIT : pulseaudio-libs-1.1-9.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,966] CRIT : diffstat-1.55-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,966] CRIT : 12:dhclient-4.2.4-0.4.rc1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,966] CRIT : pyliblzma-0.5.3-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,967] CRIT : ppl-0.11.2-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,967] CRIT : curl-7.24.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,967] CRIT : shared-mime-info-1.0-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,968] CRIT : libxml2-devel-2.7.8-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,968] CRIT : python-netaddr-0.7.5-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,968] CRIT : libgudev1-182-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,968] CRIT : swig-2.0.5-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,969] CRIT : openldap-devel-2.4.30-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,969] CRIT : certmonger-0.56-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,969] CRIT : newt-python-0.52.14-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,970] CRIT : xmlrpc-c-devel-1.29.0-1701.svn2233.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,970] CRIT : libexif-0.6.20-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,970] CRIT : zlib-1.2.5-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,970] CRIT : gdb-7.4.50.20120120-42.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,971] CRIT : rpm-4.9.1.3-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,971] CRIT : ruby-libs-1.9.3.194-10.1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,971] CRIT : 1:nfs-utils-1.2.6-0.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,971] CRIT : libtool-ltdl-2.4.2-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,972] CRIT : perl-threads-1.86-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,972] CRIT : apache-commons-collections-3.2.1-12.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,972] CRIT : gcc-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,973] CRIT : lcms-libs-1.19-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,973] CRIT : lvm2-libs-2.02.95-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,973] CRIT : mingetty-1.08-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,973] CRIT : perl-Compress-Raw-Bzip2-2.052-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,974] CRIT : sudo-1.8.3p1-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,974] CRIT : sendmail-8.14.5-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,974] CRIT : libotf-0.9.12-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,975] CRIT : systemtap-client-1.7-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,975] CRIT : gtk2-2.24.10-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,975] CRIT : libpipeline-1.2.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,975] CRIT : perl-HTTP-Cookies-6.00-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,976] CRIT : redhat-rpm-config-9.1.0-28.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,976] CRIT : libuuid-devel-2.21.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,976] CRIT : libfontenc-1.1.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,977] CRIT : rpm-python-4.9.1.3-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,977] CRIT : sysprof-1.1.8-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,977] CRIT : fontpackages-filesystem-1.44-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,977] CRIT : 1:valgrind-3.7.0-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,978] CRIT : junit-4.10-5.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,978] CRIT : libselinux-utils-2.1.10-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,978] CRIT : 1:findutils-4.5.10-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,979] CRIT : ldapjdk-4.18-9.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,979] CRIT : xml-commons-resolver-1.2-8.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,979] CRIT : sed-4.2.1-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,979] CRIT : nano-2.3.1-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,980] CRIT : libsepol-devel-2.1.5-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,980] CRIT : libunistring-0.9.3-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,980] CRIT : 2:vim-common-7.3.515-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,981] CRIT : hostname-3.10-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,981] CRIT : device-mapper-event-libs-1.02.74-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,981] CRIT : m17n-lib-1.6.3-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,981] CRIT : libsss_sudo-1.8.3-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,982] CRIT : perl-LWP-MediaTypes-6.01-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,982] CRIT : sssd-1.8.3-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,982] CRIT : gpm-libs-1.20.6-22.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,983] CRIT : perl-threads-shared-1.40-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,983] CRIT : libtirpc-0.2.2-2.1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,983] CRIT : 4:perl-macros-5.14.2-211.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,983] CRIT : avahi-libs-0.6.30-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,984] CRIT : setserial-2.17-28.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,984] CRIT : libtalloc-devel-2.0.7-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,984] CRIT : libXpm-3.5.10-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,985] CRIT : yum-metadata-parser-1.1.4-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,985] CRIT : ppl-pwl-0.11.2-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,985] CRIT : libasyncns-0.8-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,985] CRIT : glibc-2.15-37.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,986] CRIT : elfutils-libs-0.153-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,986] CRIT : libdhash-0.4.3-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,986] CRIT : perl-File-Listing-6.03-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,987] CRIT : libXrandr-1.3.1-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,987] CRIT : fedpkg-1.9-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,987] CRIT : fipscheck-1.3.0-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,987] CRIT : python-offtrac-0.0.3-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,988] CRIT : pki-selinux-9.0.20-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,988] CRIT : checkpolicy-2.1.9-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,988] CRIT : apache-commons-logging-1.1.1-19.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,989] CRIT : tomcat6-jsp-2.1-api-6.0.32-20.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,989] CRIT : pinentry-0.8.1-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,989] CRIT : 2:samba4-libs-4.0.0-47alpha18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,989] CRIT : mx-3.2.3-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,990] CRIT : xalan-j2-2.7.1-8.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,990] CRIT : 2:vim-minimal-7.3.515-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,990] CRIT : libthai-0.1.14-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,991] CRIT : gnupg2-2.0.18-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,991] CRIT : dogtag-pki-ca-theme-9.0.11-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,991] CRIT : libassuan-2.0.1-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,991] CRIT : koji-1.6.0-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,992] CRIT : which-2.20-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,992] CRIT : less-444-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,992] CRIT : rcs-5.8-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,993] CRIT : apr-util-ldap-1.4.1-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,993] CRIT : 1:ecj-3.4.2-13.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,993] CRIT : dbus-glib-0.92-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,993] CRIT : pki-ca-9.0.20-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,994] CRIT : 389-ds-base-libs-1.2.11.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,994] CRIT : 1:mc-4.8.3-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,994] CRIT : cscope-15.7a-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,994] CRIT : pki-util-9.0.20-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,995] CRIT : python-iniparse-0.4-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,995] CRIT : cairo-1.10.2-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,995] CRIT : gettext-libs-0.18.1.1-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,996] CRIT : mod_wsgi-3.3-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,996] CRIT : libsepol-2.1.5-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,996] CRIT : fakeroot-libs-1.12.4-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,997] CRIT : perl-Locale-Codes-3.21-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,997] CRIT : json-c-0.9-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,997] CRIT : sane-backends-1.0.22-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,997] CRIT : sssd-client-1.8.3-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,998] CRIT : krb5-pkinit-1.10-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,998] CRIT : perl-URI-1.60-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:37,998] CRIT : 32:bind-utils-9.9.0-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,999] CRIT : 2:samba4-test-4.0.0-47alpha18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,999] CRIT : libblkid-2.21.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,999] CRIT : jpackage-utils-1.7.5-18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:37,999] CRIT : systemtap-devel-1.7-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,000] CRIT : perl-Digest-1.17-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,000] CRIT : at-3.1.13-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,000] CRIT : libXfont-1.4.5-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,001] CRIT : libXmu-1.1.0-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,001] CRIT : man-db-2.6.0.2-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,001] CRIT : db4-4.8.30-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,001] CRIT : libxml2-2.7.8-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,002] CRIT : hunspell-1.3.2-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,002] CRIT : subversion-1.7.4-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,002] CRIT : mock-1.1.22-2.1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,003] CRIT : fedora-release-17-1.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,003] CRIT : 14:libpcap-1.2.1-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,003] CRIT : libselinux-devel-2.1.10-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,003] CRIT : ustr-1.0.4-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,004] CRIT : udev-182-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,004] CRIT : 1:NetworkManager-0.9.4.0-9.git20120521.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,004] CRIT : selinux-policy-targeted-3.10.0-125.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,005] CRIT : 1:perl-XML-LibXML-1.90-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,005] CRIT : ntp-4.2.6p5-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,005] CRIT : shared-color-profiles-0.1.5-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,005] CRIT : hamcrest-1.1-12.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,006] CRIT : 4:perl-5.14.2-211.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,006] CRIT : 1:hardlink-1.0-13.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,006] CRIT : patch-2.6.1-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,007] CRIT : perl-Compress-Raw-Zlib-2.052-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,007] CRIT : perl-Net-HTTP-6.02-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,007] CRIT : 2:vim-filesystem-7.3.515-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,007] CRIT : regexp-1.5-7.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,008] CRIT : tomcatjss-6.0.2-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,008] CRIT : kmod-7-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,008] CRIT : 2:vim-enhanced-7.3.515-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,009] CRIT : libXfixes-5.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,009] CRIT : nss-softokn-freebl-devel-3.13.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,009] CRIT : python-smmap-0.8.1-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,009] CRIT : e2fsprogs-1.42-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,010] CRIT : pcre-8.21-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,010] CRIT : sysvinit-tools-2.88-6.dsf.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,010] CRIT : patchutils-0.3.2-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,011] CRIT : python-crypto-2.5-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,011] CRIT : libipa_hbac-python-1.8.3-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,011] CRIT : libtalloc-2.0.7-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,011] CRIT : pth-2.0.7-15.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,012] CRIT : indent-2.2.11-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,012] CRIT : python-bunch-1.0.1-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,012] CRIT : nss-util-3.13.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,013] CRIT : tzdata-2012c-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,013] CRIT : apache-commons-dbcp-1.4-9.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,013] CRIT : time-1.7-40.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,013] CRIT : 1:gmp-5.0.2-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,014] CRIT : libyaml-0.1.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,014] CRIT : p11-kit-0.12-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,014] CRIT : hwdata-0.234-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,014] CRIT : cracklib-2.8.18-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,015] CRIT : iproute-3.3.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,015] CRIT : ntpdate-4.2.6p5-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,015] CRIT : gettext-common-devel-0.18.1.1-12.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,016] CRIT : tomcat6-6.0.32-20.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,016] CRIT : device-mapper-1.02.74-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,016] CRIT : ctags-5.8-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,016] CRIT : python-devel-2.7.3-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,017] CRIT : perl-HTTP-Negotiate-6.00-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,017] CRIT : mpfr-3.1.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,017] CRIT : cyrus-sasl-lib-2.1.23-29.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,018] CRIT : 1:enchant-1.6.0-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,018] CRIT : yum-utils-1.1.31-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,018] CRIT : m2crypto-0.21.1-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,018] CRIT : 2:samba4-4.0.0-47alpha18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,019] CRIT : 1:perl-Pod-Simple-3.16-211.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,019] CRIT : 1:NetworkManager-glib-0.9.4.0-9.git20120521.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,019] CRIT : libnfsidmap-0.25-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,020] CRIT : pigz-2.2.4-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,020] CRIT : gettext-0.18.1.1-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,020] CRIT : portreserve-0.0.5-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,020] CRIT : gamin-0.1.10-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,021] CRIT : libXcomposite-0.4.3-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,021] CRIT : logrotate-3.8.1-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,021] CRIT : tomcat-servlet-3.0-api-7.0.27-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,022] CRIT : libldb-devel-1.1.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,022] CRIT : kernel-PAE-devel-3.3.7-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,022] CRIT : file-5.10-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,022] CRIT : redhat-lsb-4.0-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,023] CRIT : libstdc++-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,023] CRIT : python-kitchen-1.1.1-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,023] CRIT : 1:xorg-x11-font-utils-7.5-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,024] CRIT : oprofile-0.9.7-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,024] CRIT : psmisc-22.16-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,024] CRIT : libcom_err-1.42-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,024] CRIT : bison-2.5-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,025] CRIT : kernel-headers-3.3.7-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,025] CRIT : cyrus-sasl-gssapi-2.1.23-29.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,025] CRIT : perl-File-Slurp-9999.19-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,026] CRIT : ilmbase-1.0.2-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,026] CRIT : gd-2.0.35-16.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,026] CRIT : procps-3.2.8-26.20110302git.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,026] CRIT : 2:tar-1.26-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,027] CRIT : ncurses-base-5.9-4.20120204.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,027] CRIT : mod_nss-1.0.8-16.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,027] CRIT : libevent-2.0.18-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,028] CRIT : createrepo-0.9.9-11.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,028] CRIT : atk-2.4.0-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,028] CRIT : nss-sysinit-3.13.4-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,028] CRIT : libXdamage-1.1.3-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,029] CRIT : 1:perl-parent-0.225-211.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,029] CRIT : 4:perl-libs-5.14.2-211.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,029] CRIT : systemtap-runtime-1.7-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,030] CRIT : bzr-2.5.0-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,030] CRIT : cronie-1.4.8-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,030] CRIT : libXau-1.0.6-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,030] CRIT : libdrm-2.4.33-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,031] CRIT : cyrus-sasl-2.1.23-29.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,031] CRIT : fedora-logos-17.0.2-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,031] CRIT : pylint-0.25.1-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,031] CRIT : pki-common-9.0.20-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,032] CRIT : dogtag-pki-common-theme-9.0.11-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,032] CRIT : qdox-1.12-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,032] CRIT : perl-Net-SSLeay-1.48-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,033] CRIT : fedora-packager-0.5.9.6-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,033] CRIT : sane-backends-libs-1.0.22-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,033] CRIT : libldb-1.1.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,034] CRIT : python-chardet-2.0.1-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,034] CRIT : plymouth-scripts-0.8.4-0.20120319.2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,034] CRIT : kbd-1.15.3-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,034] CRIT : tcp_wrappers-libs-7.6-69.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,035] CRIT : libattr-2.4.46-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,035] CRIT : perl-XML-NamespaceSupport-1.11-6.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,035] CRIT : 12:dhcp-common-4.2.4-0.4.rc1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,035] CRIT : oddjob-0.31.1-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,036] CRIT : gcc-gfortran-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,036] CRIT : apache-commons-pool-1.5.7-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,036] CRIT : xorg-x11-fonts-misc-7.5-5.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,037] CRIT : popt-1.13-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,037] CRIT : perl-Carp-1.22-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,037] CRIT : jdom-1.1.3-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,037] CRIT : gnutls-2.12.17-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,038] CRIT : nspr-4.9-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,038] CRIT : openssh-5.9p1-22.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,038] CRIT : perl-XML-SAX-0.99-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,039] CRIT : newt-0.52.14-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,039] CRIT : setup-2.8.48-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,039] CRIT : automake17-1.7.9-15.fc17.1.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,039] CRIT : libICE-1.0.8-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,040] CRIT : krb5-libs-1.10-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,040] CRIT : xmlrpc-c-client-1.29.0-1701.svn2233.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,040] CRIT : mailcap-2.1.39-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,041] CRIT : gpgme-1.3.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,041] CRIT : libcollection-0.6.1-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,041] CRIT : libcurl-7.24.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,041] CRIT : libgusb-0.1.3-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,042] CRIT : fipscheck-lib-1.3.0-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,042] CRIT : 32:bind-libs-lite-9.9.0-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,042] CRIT : libXft-2.3.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,043] CRIT : libgomp-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,043] CRIT : zip-3.0-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,043] CRIT : libffi-3.0.10-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,043] CRIT : rpm-build-libs-4.9.1.3-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,044] CRIT : openssh-clients-5.9p1-22.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,044] CRIT : libdaemon-0.14-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,044] CRIT : python-paramiko-1.7.7.1-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,044] CRIT : grubby-8.11-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,045] CRIT : libX11-common-1.4.99.901-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,045] CRIT : pam-1.1.5-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,045] CRIT : polkit-0.104-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,046] CRIT : pki-native-tools-9.0.20-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,046] CRIT : giflib-4.1.6-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,046] CRIT : mailx-12.5-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,046] CRIT : zlib-devel-1.2.5-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,047] CRIT : pam_krb5-2.3.13-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,047] CRIT : 2:samba4-client-4.0.0-47alpha18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,047] CRIT : libtiff-3.9.5-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,048] CRIT : gdbm-1.10-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,048] CRIT : rhino-1.7R3-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,048] CRIT : groff-base-1.21-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,048] CRIT : ModemManager-0.5.2.0-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,049] CRIT : basesystem-10.0-6.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,049] CRIT : perl-Encode-Locale-1.02-5.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,049] CRIT : libidn-1.24-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,050] CRIT : authconfig-6.2.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,050] CRIT : libnl3-3.2.7-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,050] CRIT : iputils-20101006-14.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,050] CRIT : strace-4.7-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,051] CRIT : gsm-1.0.13-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,051] CRIT : libtool-2.4.2-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,051] CRIT : cairo-gobject-1.10.2-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,052] CRIT : 2:libpng-1.5.10-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,052] CRIT : 1:grub2-2.0-0.25.beta4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,052] CRIT : keyutils-libs-1.5.5-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,052] CRIT : audit-libs-2.2.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,053] CRIT : selinux-policy-3.10.0-125.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,053] CRIT : libgfortran-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,053] CRIT : python-pyasn1-0.1.2-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,053] CRIT : libX11-1.4.99.901-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,054] CRIT : nss-softokn-3.13.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,054] CRIT : slang-2.2.4-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,054] CRIT : rpm-libs-4.9.1.3-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,055] CRIT : 2:samba4-dc-4.0.0-47alpha18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,055] CRIT : libgcc-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,055] CRIT : perl-WWW-RobotRules-6.01-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,055] CRIT : 32:bind-license-9.9.0-4.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,056] CRIT : sqlite-3.7.11-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,056] CRIT : memcached-1.4.10-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,056] CRIT : perl-Net-LibIDN-0.12-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,057] CRIT : libmount-2.21.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,057] CRIT : cvs-1.11.23-25.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,057] CRIT : hesiod-3.1.0-21.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,057] CRIT : net-tools-1.60-134.20120127git.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,058] CRIT : bcel-5.2-10.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,058] CRIT : 1:pkgconfig-0.25-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,058] CRIT : libXcursor-1.1.13-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,059] CRIT : xmlrpc-c-client++-1.29.0-1701.svn2233.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,059] CRIT : python-krbV-1.0.90-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,059] CRIT : libjpeg-turbo-1.2.0-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,059] CRIT : libtevent-0.9.15-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,060] CRIT : ghostscript-9.05-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,060] CRIT : hunspell-en-0.20110318-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,060] CRIT : nss-softokn-freebl-3.13.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,061] CRIT : libproxy-0.4.7-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,061] CRIT : cpio-2.11-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,061] CRIT : perl-Socket-2.001-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,061] CRIT : elfutils-0.153-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,062] CRIT : parted-3.0-9.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,062] CRIT : libsemanage-2.1.6-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,062] CRIT : httpd-2.2.22-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,062] CRIT : 1:cups-libs-1.5.2-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,063] CRIT : python-fedora-0.3.28.1-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,063] CRIT : xz-5.1.1-2alpha.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,063] CRIT : pax-3.4-13.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,064] CRIT : glib2-2.32.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,064] CRIT : nss-myhostname-0.3-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,064] CRIT : nspr-devel-4.9-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,065] CRIT : libstdc++-devel-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,065] CRIT : pyrpkg-1.17-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,065] CRIT : libwmf-lite-0.2.8.4-32.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,065] CRIT : xz-libs-5.1.1-2alpha.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,066] CRIT : nss-tools-3.13.4-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,066] CRIT : pki-setup-9.0.20-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,066] CRIT : libXtst-1.2.0-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,066] CRIT : ltrace-0.6.0-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,067] CRIT : perl-IO-Compress-2.052-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,067] CRIT : lcms2-2.3-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,067] CRIT : 32:bind-libs-9.9.0-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,068] CRIT : httpd-tools-2.2.22-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,068] CRIT : deltarpm-3.6-0.7.20110223git.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,068] CRIT : python-logilab-common-0.57.1-2.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,068] CRIT : libieee1284-0.2.11-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,069] CRIT : libxml2-python-2.7.8-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,069] CRIT : biosdevname-0.3.11-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,069] CRIT : bzip2-1.0.6-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,070] CRIT : linux-atm-libs-2.5.1-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,070] CRIT : rpm-build-4.9.1.3-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,070] CRIT : libuser-0.57.6-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,070] CRIT : rsyslog-5.8.10-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,071] CRIT : 1:hsqldb-1.8.1.3-7.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,071] CRIT : perl-PathTools-3.33-211.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,071] CRIT : perl-HTML-Tagset-3.20-10.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,072] CRIT : 2:samba4-winbind-4.0.0-47alpha18.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,072] CRIT : groff-1.21-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,072] CRIT : liblockfile-1.08-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,072] CRIT : gcc-c++-4.7.0-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,073] CRIT : chkconfig-1.3.59-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,073] CRIT : python-async-0.6.1-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,073] CRIT : libcom_err-devel-1.42-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,073] CRIT : xmlrpc-c-1.29.0-1701.svn2233.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,074] CRIT : libssh2-1.4.1-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,074] CRIT : krb5-devel-1.10-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,074] CRIT : dracut-018-40.git20120522.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,075] CRIT : 1:autofs-5.0.6-13.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,075] CRIT : apr-1.4.6-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,075] CRIT : keyutils-1.5.5-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,075] CRIT : libudev-182-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,076] CRIT : 1:perl-Pod-Escapes-1.04-211.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,076] CRIT : cloog-ppl-0.15.11-3.fc17.1.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,076] CRIT : cronie-anacron-1.4.8-11.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,077] CRIT : audit-2.2.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,077] CRIT : libxcb-1.8.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,077] CRIT : libverto-tevent-0.2.4-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,077] CRIT : perl-Scalar-List-Utils-1.25-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,078] CRIT : acl-2.2.51-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,078] CRIT : rpmlint-1.4-6.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,078] CRIT : systemd-sysv-44-12.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,079] CRIT : svrcore-devel-4.0.4-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,079] CRIT : python-ldap-2.4.6-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,079] CRIT : ncurses-5.9-4.20120204.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,079] CRIT : perl-Class-ISA-0.36-1007.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,080] CRIT : plymouth-0.8.4-0.20120319.2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,080] CRIT : libdb-5.2.36-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,080] CRIT : dnsmasq-2.59-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,080] CRIT : mod_auth_kerb-5.4-13.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,081] CRIT : python-magic-5.10-5.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,081] CRIT : python-gitdb-0.5.4-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,081] CRIT : python-pycurl-7.19.0-10.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,082] CRIT : policycoreutils-2.1.11-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,082] CRIT : device-mapper-event-1.02.74-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,082] CRIT : perl-Git-1.7.10.2-1.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,082] CRIT : libpath_utils-0.2.1-8.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,083] CRIT : avahi-autoipd-0.6.30-7.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,083] CRIT : libcurl-devel-7.24.0-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,083] CRIT : libmodman-2.0.1-4.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,084] CRIT : python-decoratortools-1.8-3.fc17.noarch was supposed to be installed but is not! >[2012-05-30 11:55:38,084] CRIT : keyutils-libs-devel-1.5.5-2.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,084] CRIT : freetype-2.4.8-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,084] CRIT : libselinux-2.1.10-3.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,085] CRIT : util-linux-2.21.1-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,085] CRIT : gzip-1.4-6.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,085] CRIT : pki-symkey-9.0.20-1.fc17.i686 was supposed to be installed but is not! >[2012-05-30 11:55:38,149] DEBUG : VerifyTransaction time: 0.250 > > >/mnt/sysimage/root/install.log: >11:42:55 Installing filesystem-3-2.fc17.i686 >warning: filesystem-3-2.fc17.i686: Header V3 RSA/SHA256 Signature, key ID 1aca3465: NOKEY >11:42:56 Installing setup-2.8.48-1.fc17.noarch >11:42:57 Installing filesystem-3-2.fc17.i686 >11:42:58 Installing ca-certificates-2012.81-1.fc17.noarch >11:42:59 Installing emacs-filesystem-24.0.95-1.fc17.i686 >11:42:59 Installing bind-license-9.9.0-4.fc17.noarch >11:42:59 Installing mailcap-2.1.39-1.fc17.noarch >11:42:59 Installing dogtag-pki-common-theme-9.0.11-1.fc17.noarch >11:42:59 Installing xemacs-filesystem-21.5.31-4.fc17.noarch >11:43:00 Installing dogtag-pki-ca-theme-9.0.11-1.fc17.noarch >11:43:00 Installing basesystem-10.0-6.fc17.noarch >11:43:01 Installing libX11-common-1.4.99.901-2.fc17.noarch >11:43:02 Installing ncurses-base-5.9-4.20120204.fc17.i686 >11:43:02 Installing kernel-headers-3.3.7-1.fc17.i686 >11:43:04 Installing gettext-common-devel-0.18.1.1-12.fc17.noarch >11:43:05 Installing tzdata-2012c-1.fc17.noarch >11:43:08 Installing vim-filesystem-7.3.515-1.fc17.i686 >11:43:08 Installing fedora-release-17-1.noarch >11:43:08 Installing fakeroot-libs-1.12.4-4.fc17.i686 >11:43:08 Installing fontpackages-filesystem-1.44-3.fc17.noarch >11:43:08 Installing tzdata-java-2012c-1.fc17.noarch >11:43:09 Installing mobile-broadband-provider-info-1.20110218-2.fc17.noarch >11:43:09 Installing m17n-db-1.6.3-3.fc17.noarch >11:43:10 Installing kbd-misc-1.15.3-5.fc17.noarch >11:43:11 Installing poppler-data-0.4.5-2.fc17.noarch >11:43:13 Installing rootfiles-8.1-8.fc17.noarch >11:43:14 Installing libgcc-4.7.0-5.fc17.i686 >11:43:14 Installing nss-softokn-freebl-3.13.4-2.fc17.i686 >11:43:14 Installing glibc-common-2.15-37.fc17.i686 >11:43:30 Installing glibc-2.15-37.fc17.i686 >11:43:51 Installing ncurses-libs-5.9-4.20120204.fc17.i686 >11:43:52 Installing bash-4.2.28-1.fc17.i686 >11:43:54 Installing libsepol-2.1.5-3.fc17.i686 >11:43:54 Installing libselinux-2.1.10-3.fc17.i686 >11:43:54 Installing libattr-2.4.46-5.fc17.i686 >11:43:55 Installing libcap-2.22-2.fc17.i686 >11:43:55 Installing glibc-headers-2.15-37.fc17.i686 >11:43:56 Installing ecj-3.4.2-13.fc17.i686 >11:43:57 Installing tomcat-servlet-3.0-api-7.0.27-2.fc17.noarch >/var/tmp/rpm-tmp.oBvdn7: line 1: /usr/sbin/update-alternatives: No such file or directory >warning: %post(tomcat-servlet-3.0-api-0:7.0.27-2.fc17.noarch) scriptlet failed, exit status 127 >11:43:58 Installing nss-softokn-freebl-devel-3.13.4-2.fc17.i686 >11:43:58 Installing zlib-1.2.5-6.fc17.i686 >11:43:58 Installing info-4.13a-16.fc17.i686 >11:43:58 Installing libcom_err-1.42-4.fc17.i686 >11:43:58 Installing libstdc++-4.7.0-5.fc17.i686 >11:43:59 Installing nspr-4.9-2.fc17.i686 >11:43:59 Installing libxml2-2.7.8-7.fc17.i686 >11:44:00 Installing popt-1.13-10.fc17.i686 >11:44:01 Installing chkconfig-1.3.59-1.fc17.i686 >11:44:01 Installing nss-util-3.13.4-2.fc17.i686 >11:44:01 Installing freetype-2.4.8-3.fc17.i686 >11:44:02 Installing sed-4.2.1-8.fc17.i686 >11:44:02 Installing bzip2-libs-1.0.6-4.fc17.i686 >11:44:03 Installing dbus-libs-1.4.10-4.fc17.i686 >11:44:03 Installing libacl-2.2.51-5.fc17.i686 >11:44:03 Installing libtalloc-2.0.7-4.fc17.i686 >11:44:03 Installing expat-2.1.0-1.fc17.i686 >11:44:03 Installing fontconfig-2.8.0-6.fc17.i686 >/var/tmp/rpm-tmp.aRUv8k: line 5: mkdir: command not found >/var/tmp/rpm-tmp.aRUv8k: line 11: grep: command not found >11:44:04 Installing libuuid-2.21.1-1.fc17.i686 >11:44:04 Installing audit-libs-2.2.1-1.fc17.i686 >11:44:04 Installing libjpeg-turbo-1.2.0-1.fc17.i686 >11:44:04 Installing libtevent-0.9.15-1.fc17.i686 >11:44:04 Installing xz-libs-5.1.1-2alpha.fc17.i686 >11:44:05 Installing readline-6.2-4.fc17.i686 >11:44:05 Installing elfutils-libelf-0.153-2.fc17.i686 >11:44:05 Installing libtdb-1.2.9-14.fc17.i686 >11:44:05 Installing keyutils-libs-1.5.5-2.fc17.i686 >11:44:06 Installing krb5-libs-1.10-6.fc17.i686 >11:44:07 Installing gmp-5.0.2-6.fc17.i686 >11:44:07 Installing gawk-4.0.0-4.fc17.i686 >11:44:08 Installing libpng-1.5.10-1.fc17.i686 >11:44:09 Installing db4-4.8.30-10.fc17.i686 >11:44:09 Installing sqlite-3.7.11-2.fc17.i686 >11:44:10 Installing libtiff-3.9.5-3.fc17.i686 >11:44:10 Installing libdb-5.2.36-5.fc17.i686 >11:44:11 Installing cyrus-sasl-lib-2.1.23-29.fc17.i686 >11:44:11 Installing libldb-1.1.4-2.fc17.i686 >11:44:11 Installing pcre-8.21-5.fc17.i686 >11:44:12 Installing grep-2.12-1.fc17.i686 >11:44:12 Installing libgpg-error-1.10-2.fc17.i686 >11:44:13 Installing libbsd-0.3.0-2.fc17.i686 >11:44:13 Installing tcp_wrappers-libs-7.6-69.fc17.i686 >11:44:13 Installing libICE-1.0.8-1.fc17.i686 >11:44:13 Installing libSM-1.2.1-1.fc17.i686 >11:44:13 Installing findutils-4.5.10-4.fc17.i686 >11:44:14 Installing cpio-2.11-6.fc17.i686 >11:44:14 Installing file-libs-5.10-5.fc17.i686 >11:44:15 Installing file-5.10-5.fc17.i686 >11:44:15 Installing libgcrypt-1.5.0-3.fc17.i686 >11:44:15 Installing mpfr-3.1.0-2.fc17.i686 >11:44:16 Installing lua-5.1.4-10.fc17.i686 >11:44:16 Installing apr-1.4.6-1.fc17.i686 >11:44:16 Installing apr-util-1.4.1-2.fc17.i686 >11:44:16 Installing xmlrpc-c-1.29.0-1701.svn2233.fc17.i686 >11:44:17 Installing m4-1.4.16-3.fc17.i686 >11:44:17 Installing diffutils-3.2-6.fc17.i686 >11:44:17 Installing libunistring-0.9.3-3.fc17.i686 >11:44:18 Installing libmpc-0.9-2.fc17.2.i686 >11:44:18 Installing libgomp-4.7.0-5.fc17.i686 >11:44:18 Installing libidn-1.24-1.fc17.i686 >11:44:18 Installing procps-3.2.8-26.20110302git.fc17.i686 >11:44:19 Installing libusb1-1.0.9-0.6.rc1.fc17.i686 >11:44:19 Installing libusb-0.1.3-10.fc17.i686 >11:44:19 Installing gdbm-1.10-2.fc17.i686 >11:44:19 Installing tomcat6-servlet-2.5-api-6.0.32-20.fc17.noarch >11:44:19 Installing perl-Pod-Escapes-1.04-211.fc17.noarch >11:44:19 Installing perl-threads-1.86-2.fc17.i686 >11:44:20 Installing perl-macros-5.14.2-211.fc17.i686 >11:44:20 Installing perl-libs-5.14.2-211.fc17.i686 >11:44:20 Installing perl-threads-shared-1.40-2.fc17.i686 >11:44:20 Installing perl-Carp-1.22-2.fc17.noarch >11:44:21 Installing perl-Socket-2.001-1.fc17.i686 >11:44:21 Installing perl-Module-Pluggable-3.90-211.fc17.noarch >11:44:21 Installing perl-PathTools-3.33-211.fc17.i686 >11:44:21 Installing perl-Pod-Simple-3.16-211.fc17.noarch >11:44:21 Installing perl-Scalar-List-Utils-1.25-1.fc17.i686 >11:44:21 Installing perl-5.14.2-211.fc17.i686 >11:44:35 Installing perl-URI-1.60-1.fc17.noarch >11:44:35 Installing autoconf-2.68-3.fc17.noarch >11:44:37 Installing perl-LWP-MediaTypes-6.01-4.fc17.noarch >11:44:38 Installing perl-Compress-Raw-Zlib-2.052-1.fc17.i686 >11:44:38 Installing elfutils-libs-0.153-2.fc17.i686 >11:44:39 Installing kmod-libs-7-1.fc17.i686 >11:44:39 Installing kmod-7-1.fc17.i686 >11:44:39 Installing xz-5.1.1-2alpha.fc17.i686 >11:44:39 Installing libv4l-0.8.7-1.fc17.i686 >11:44:39 Installing avahi-libs-0.6.30-7.fc17.i686 >11:44:40 Installing libss-1.42-4.fc17.i686 >11:44:40 Installing libquadmath-4.7.0-5.fc17.i686 >11:44:40 Installing which-2.20-3.fc17.i686 >11:44:40 Installing patch-2.6.1-12.fc17.i686 >11:44:40 Installing psmisc-22.16-1.fc17.i686 >11:44:41 Installing libogg-1.3.0-1.fc17.i686 >11:44:41 Installing libexif-0.6.20-2.fc17.i686 >11:44:41 Installing libffi-3.0.10-2.fc17.i686 >11:44:42 Installing gamin-0.1.10-12.fc17.i686 >11:44:42 Installing pkgconfig-0.25-4.fc17.i686 >11:44:42 Installing glib2-2.32.1-1.fc17.i686 >11:44:44 Installing shared-mime-info-1.0-1.fc17.i686 >11:44:45 Installing nspr-devel-4.9-2.fc17.i686 >11:44:46 Installing libtalloc-devel-2.0.7-4.fc17.i686 >11:44:46 Installing atk-2.4.0-1.fc17.i686 >11:44:46 Installing dbus-glib-0.92-3.fc17.i686 >11:44:47 Installing libcroco-0.6.5-1.fc17.i686 >11:44:47 Installing slang-2.2.4-3.fc17.i686 >11:44:48 Installing libieee1284-0.2.11-11.fc17.i686 >11:44:48 Installing libtevent-devel-0.9.15-1.fc17.i686 >11:44:48 Installing nss-util-devel-3.13.4-2.fc17.i686 >11:44:48 Installing zlib-devel-1.2.5-6.fc17.i686 >11:44:48 Installing hwdata-0.234-2.fc17.noarch >11:44:49 Installing automake-1.11.3-1.fc17.noarch >11:44:50 Installing perl-Error-0.17016-7.fc17.noarch >11:44:50 Installing perl-XML-SAX-Base-1.08-2.fc17.noarch >11:44:51 Installing perl-XML-NamespaceSupport-1.11-6.fc17.noarch >11:44:51 Installing perl-Encode-Locale-1.02-5.fc17.noarch >11:44:51 Installing perl-XML-LibXML-1.90-1.fc17.i686 >11:44:51 Installing perl-XML-SAX-0.99-2.fc17.noarch >11:44:52 Installing gettext-libs-0.18.1.1-12.fc17.i686 >11:44:52 Installing desktop-file-utils-0.19-6.fc17.i686 >11:44:52 Installing libipa_hbac-1.8.3-11.fc17.i686 >11:44:53 Installing xmlrpc-c-c++-1.29.0-1701.svn2233.fc17.i686 >11:44:53 Installing libassuan-2.0.1-2.fc17.i686 >11:44:53 Installing nss-softokn-3.13.4-2.fc17.i686 >11:44:53 Installing libgssglue-0.3-1.fc17.i686 >11:44:54 Installing libtirpc-0.2.2-2.1.fc17.i686 >11:44:54 Installing jasper-libs-1.900.1-19.fc17.i686 >11:44:54 Installing vim-minimal-7.3.515-1.fc17.i686 >11:44:55 Installing tar-1.26-5.fc17.i686 >11:44:56 Installing unzip-6.0-5.fc17.i686 >11:44:56 Installing bzip2-1.0.6-4.fc17.i686 >11:44:56 Installing groff-base-1.21-8.fc17.i686 >11:44:59 Installing hunspell-1.3.2-4.fc17.i686 >11:44:59 Installing ilmbase-1.0.2-4.fc17.i686 >11:45:00 Installing make-3.82-9.fc17.i686 >11:45:00 Installing libfontenc-1.1.0-2.fc17.i686 >11:45:00 Installing libselinux-utils-2.1.10-3.fc17.i686 >11:45:01 Installing libedit-3.0-6.20110802cvs.fc17.i686 >11:45:01 Installing libcap-ng-0.6.6-2.fc17.i686 >11:45:01 Installing pixman-0.24.4-2.fc17.i686 >11:45:01 Installing libverto-0.2.4-2.fc17.i686 >11:45:02 Installing libtool-ltdl-2.4.2-3.fc17.i686 >11:45:02 Installing hostname-3.10-1.fc17.i686 >11:45:02 Installing gpm-libs-1.20.6-22.fc17.i686 >11:45:02 Installing sysvinit-tools-2.88-6.dsf.fc17.i686 >11:45:02 Installing pth-2.0.7-15.fc17.i686 >11:45:02 Installing libcollection-0.6.1-8.fc17.i686 >11:45:03 Installing libnl3-3.2.7-1.fc17.i686 >11:45:03 Installing hesiod-3.1.0-21.fc17.i686 >11:45:03 Installing lcms2-2.3-2.fc17.i686 >11:45:03 Installing nss-softokn-devel-3.13.4-2.fc17.i686 >11:45:04 Installing libtdb-devel-1.2.9-14.fc17.i686 >11:45:04 Installing libldb-devel-1.1.4-2.fc17.i686 >11:45:04 Installing libsepol-devel-2.1.5-3.fc17.i686 >11:45:04 Installing libselinux-devel-2.1.10-3.fc17.i686 >11:45:05 Installing libcom_err-devel-1.42-4.fc17.i686 >11:45:05 Installing perl-WWW-RobotRules-6.01-4.fc17.noarch >11:45:05 Installing perl-TimeDate-1.20-6.fc17.noarch >11:45:05 Installing perl-HTTP-Date-6.00-3.fc17.noarch >11:45:05 Installing perl-File-Listing-6.03-2.fc17.noarch >11:45:05 Installing perl-Parse-Yapp-1.05-46.fc17.noarch >11:45:05 Installing perl-Locale-Codes-3.21-1.fc17.noarch >11:45:06 Installing perl-Digest-1.17-2.fc17.noarch >11:45:06 Installing kernel-PAE-devel-3.3.7-1.fc17.i686 >11:45:30 Installing perl-File-Slurp-9999.19-3.fc17.noarch >11:45:31 Installing perl-parent-0.225-211.fc17.noarch >11:45:31 Installing perl-Pod-Perldoc-3.17-2.fc17.noarch >11:45:31 Installing perl-HTML-Tagset-3.20-10.fc17.noarch >11:45:32 Installing perl-Class-ISA-0.36-1007.fc17.noarch >11:45:32 Installing tomcat6-jsp-2.1-api-6.0.32-20.fc17.noarch >11:45:32 Installing keyutils-libs-devel-1.5.5-2.fc17.i686 >11:45:32 Installing urw-fonts-2.4-11.fc17.noarch >11:45:37 Installing tomcat6-el-2.1-api-6.0.32-20.fc17.noarch >11:45:37 Installing xml-common-0.6.3-36.fc17.noarch >11:45:37 Installing libstdc++-devel-4.7.0-5.fc17.i686 >11:45:40 Installing glibc-devel-2.15-37.fc17.i686 >11:45:41 Installing perl-Digest-MD5-2.51-211.fc17.i686 >11:45:41 Installing krb5-devel-1.10-6.fc17.i686 >11:45:42 Installing libverto-tevent-0.2.4-2.fc17.i686 >11:45:42 Installing libXfont-1.4.5-1.fc17.i686 >11:45:43 Installing xorg-x11-font-utils-7.5-7.fc17.i686 >11:45:43 Installing ghostscript-fonts-5.50-28.fc17.noarch >11:45:44 Installing xorg-x11-fonts-misc-7.5-5.fc17.noarch >11:45:51 Installing OpenEXR-libs-1.7.0-4.fc17.i686 >11:45:51 Installing enchant-1.6.0-4.fc17.i686 >11:45:51 Installing libpciaccess-0.13.1-1.fc17.i686 >11:45:52 Installing newt-0.52.14-2.fc17.i686 >11:45:52 Installing libvorbis-1.3.3-1.fc17.i686 >11:45:53 Installing flac-1.2.1-9.fc17.i686 >11:45:54 Installing libgfortran-4.7.0-5.fc17.i686 >11:45:55 Installing elfutils-0.153-2.fc17.i686 >11:45:55 Installing perl-Compress-Raw-Bzip2-2.052-1.fc17.i686 >11:45:55 Installing perl-IO-Compress-2.052-1.fc17.noarch >11:45:56 Installing perl-HTML-Parser-3.69-3.fc17.i686 >11:45:56 Installing perl-HTTP-Message-6.03-1.fc17.noarch >11:45:56 Installing perl-HTTP-Daemon-6.00-4.fc17.noarch >11:45:56 Installing perl-HTTP-Cookies-6.00-4.fc17.noarch >11:45:56 Installing perl-HTTP-Negotiate-6.00-4.fc17.noarch >11:45:56 Installing perl-Net-LibIDN-0.12-8.fc17.i686 >11:45:57 Installing cpp-4.7.0-5.fc17.i686 >11:46:00 Installing libxslt-1.1.26-9.fc17.i686 >11:46:01 Installing cyrus-sasl-gssapi-2.1.23-29.fc17.i686 >11:46:01 Installing libdb-utils-5.2.36-5.fc17.i686 >11:46:01 Installing keyutils-1.5.5-2.fc17.i686 >11:46:02 Installing bc-1.06.95-6.fc17.i686 >11:46:02 Installing rsync-3.0.9-2.fc17.i686 >11:46:02 Installing nss-myhostname-0.3-2.fc17.i686 >11:46:02 Installing pinentry-0.8.1-6.fc17.i686 >11:46:03 Installing m17n-lib-1.6.3-2.fc17.i686 >11:46:03 Installing ppl-pwl-0.11.2-8.fc17.i686 >11:46:03 Installing ppl-0.11.2-8.fc17.i686 >11:46:05 Installing cloog-ppl-0.15.11-3.fc17.1.i686 >11:46:05 Installing libmodman-2.0.1-4.fc17.i686 >11:46:05 Installing libproxy-0.4.7-4.fc17.i686 >11:46:05 Installing e2fsprogs-libs-1.42-4.fc17.i686 >11:46:06 Installing ed-1.5-3.fc17.i686 >11:46:06 Installing time-1.7-40.fc17.i686 >11:46:06 Installing pigz-2.2.4-1.fc17.i686 >11:46:06 Installing checkpolicy-2.1.9-4.fc17.i686 >11:46:06 Installing procmail-3.22-29.fc17.i686 >11:46:07 Installing libpipeline-1.2.0-2.fc17.i686 >11:46:07 Installing vim-common-7.3.515-1.fc17.i686 >11:46:16 Installing ncurses-5.9-4.20120204.fc17.i686 >11:46:18 Installing gzip-1.4-6.fc17.i686 >11:46:19 Installing cracklib-2.8.18-3.fc17.i686 >11:46:19 Installing cracklib-dicts-2.8.18-3.fc17.i686 >11:46:22 Installing libpwquality-1.0.0-2.fc17.i686 >11:46:23 Installing coreutils-8.15-6.fc17.i686 >11:46:29 Installing pam-1.1.5-6.fc17.i686 >11:46:31 Installing hicolor-icon-theme-0.12-4.fc17.noarch >11:46:32 Installing fedora-logos-17.0.2-1.fc17.noarch >11:46:37 Installing openssl-1.0.0j-1.fc17.i686 >11:46:39 Installing python-libs-2.7.3-6.fc17.i686 >11:46:57 Installing python-2.7.3-6.fc17.i686 >11:46:57 Installing jpackage-utils-1.7.5-18.fc17.i686 >11:46:58 Installing libblkid-2.21.1-1.fc17.i686 >11:46:58 Installing binutils-2.22.52.0.1-10.fc17.i686 >11:47:05 Installing python-simplejson-2.5.2-1.fc17.i686 >11:47:06 Installing gcc-4.7.0-5.fc17.i686 >11:47:28 Installing logrotate-3.8.1-3.fc17.i686 >11:47:29 Installing pyOpenSSL-0.12-2.fc17.i686 >11:47:30 Installing gettext-0.18.1.1-12.fc17.i686 >11:47:32 Installing python-iniparse-0.4-4.fc17.noarch >11:47:32 Installing libmount-2.21.1-1.fc17.i686 >11:47:32 Installing yum-metadata-parser-1.1.4-6.fc17.i686 >11:47:32 Installing libevent-2.0.18-1.fc17.i686 >11:47:33 Installing alsa-lib-1.0.25-3.fc17.i686 >11:47:34 Installing libquadmath-devel-4.7.0-5.fc17.i686 >11:47:34 Installing jakarta-oro-2.0.8-10.fc17.noarch >11:47:35 Installing jline-1.0-1.fc17.noarch >11:47:35 Installing rhino-1.7R3-4.fc17.noarch >11:47:39 Installing python-enchant-1.6.5-4.fc17.noarch >11:47:39 Installing libxml2-devel-2.7.8-7.fc17.i686 >11:47:42 Installing python-offtrac-0.0.3-4.fc17.noarch >11:47:42 Installing python-smmap-0.8.1-4.fc17.noarch >11:47:42 Installing python-crypto-2.5-2.fc17.i686 >11:47:44 Installing python-paramiko-1.7.7.1-2.fc17.noarch >11:47:45 Installing python-bunch-1.0.1-1.fc17.noarch >11:47:45 Installing m2crypto-0.21.1-8.fc17.i686 >11:47:46 Installing python-chardet-2.0.1-4.fc17.noarch >11:47:47 Installing python-kitchen-1.1.1-1.fc17.noarch >11:47:48 Installing python-async-0.6.1-4.fc17.i686 >11:47:48 Installing python-gitdb-0.5.4-3.fc17.i686 >11:47:48 Installing python-magic-5.10-5.fc17.i686 >11:47:48 Installing python-decoratortools-1.8-3.fc17.noarch >11:47:49 Installing gcc-c++-4.7.0-5.fc17.i686 >11:47:54 Installing grubby-8.11-1.fc17.i686 >11:47:54 Installing pytalloc-2.0.7-4.fc17.i686 >11:47:54 Installing pyliblzma-0.5.3-6.fc17.i686 >11:47:54 Installing newt-python-0.52.14-2.fc17.i686 >11:47:54 Installing authconfig-6.2.1-1.fc17.i686 >11:47:55 Installing mx-3.2.3-1.fc17.i686 >11:47:59 Installing python-logilab-common-0.57.1-2.fc17.noarch >11:48:00 Installing python-logilab-astng-0.23.1-1.fc17.noarch >11:48:00 Installing python-krbV-1.0.90-4.fc17.i686 >11:48:00 Installing libxml2-python-2.7.8-7.fc17.i686 >11:48:01 Installing gdb-7.4.50.20120120-42.fc17.i686 >11:48:03 Installing perl-Crypt-SSLeay-0.58-8.fc17.i686 >11:48:04 Installing fipscheck-lib-1.3.0-3.fc17.i686 >11:48:04 Installing fipscheck-1.3.0-3.fc17.i686 >11:48:04 Installing perl-Net-SSLeay-1.48-1.fc17.i686 >11:48:05 Installing perl-IO-Socket-SSL-1.66-1.fc17.noarch >11:48:05 Installing perl-Net-HTTP-6.02-2.fc17.noarch >11:48:05 Installing perl-libwww-perl-6.03-2.fc17.noarch >11:48:06 Installing perl-XML-Parser-2.41-4.fc17.i686 >11:48:06 Installing bind-libs-lite-9.9.0-4.fc17.i686 >11:48:07 Installing bind-libs-9.9.0-4.fc17.i686 >11:48:08 Installing httpd-tools-2.2.22-4.fc17.i686 >11:48:08 Installing libssh2-1.4.1-2.fc17.i686 >11:48:08 Installing sssd-client-1.8.3-11.fc17.i686 >11:48:09 Installing nss-3.13.4-3.fc17.i686 >11:48:10 Installing nss-sysinit-3.13.4-3.fc17.i686 >11:48:11 Installing nss-devel-3.13.4-3.fc17.i686 >11:48:11 Installing openldap-2.4.30-2.fc17.i686 >11:48:12 Installing samba4-libs-4.0.0-47alpha18.fc17.i686 >11:48:20 Installing samba4-common-4.0.0-47alpha18.fc17.i686 >11:48:22 Installing samba4-dc-libs-4.0.0-47alpha18.fc17.i686 >11:48:23 Installing samba4-dc-4.0.0-47alpha18.fc17.i686 >11:48:26 Installing samba4-client-4.0.0-47alpha18.fc17.i686 >11:48:28 Installing libcurl-7.24.0-2.fc17.i686 >11:48:29 Installing dhcp-libs-4.2.4-0.4.rc1.fc17.i686 >11:48:31 Installing python-pycurl-7.19.0-10.fc17.i686 >11:48:34 Installing curl-7.24.0-2.fc17.i686 >11:48:34 Installing fedora-cert-0.5.9.6-2.fc17.noarch >11:48:34 Installing python-fedora-0.3.28.1-1.fc17.noarch >11:48:35 Installing rpm-4.9.1.3-7.fc17.i686 >11:48:36 Installing rpm-libs-4.9.1.3-7.fc17.i686 >11:48:37 Installing redhat-rpm-config-9.1.0-28.fc17.noarch >11:48:37 Installing xmlrpc-c-client-1.29.0-1701.svn2233.fc17.i686 >11:48:37 Installing color-filesystem-1-9.noarch >11:48:37 Installing python-urlgrabber-3.9.1-11.fc17.noarch >11:48:38 Installing deltarpm-3.6-0.7.20110223git.fc17.i686 >11:48:38 Installing openldap-clients-2.4.30-2.fc17.i686 >11:48:39 Installing gnupg2-2.0.18-3.fc17.i686 >11:48:41 Installing rpm-build-libs-4.9.1.3-7.fc17.i686 >11:48:42 Installing rpm-python-4.9.1.3-7.fc17.i686 >11:48:42 Installing koji-1.6.0-3.fc17.noarch >11:48:43 Installing rpm-build-4.9.1.3-7.fc17.i686 >11:48:44 Installing rpmlint-1.4-6.fc17.noarch >11:48:45 Installing libuser-0.57.6-1.fc17.i686 >11:48:46 Installing passwd-0.78.99-1.fc17.i686 >11:48:46 Installing svrcore-4.0.4-7.fc17.i686 >11:48:46 Installing nss-tools-3.13.4-3.fc17.i686 >11:48:47 Installing svrcore-devel-4.0.4-7.fc17.i686 >11:48:47 Installing shared-color-profiles-0.1.5-2.fc17.noarch >11:48:48 Installing dhcp-common-4.2.4-0.4.rc1.fc17.i686 >11:48:48 Installing libcurl-devel-7.24.0-2.fc17.i686 >11:48:49 Installing pki-native-tools-9.0.20-1.fc17.i686 >11:48:49 Installing 389-ds-base-libs-1.2.11.1-1.fc17.i686 >11:48:50 Installing gpgme-1.3.0-5.fc17.i686 >11:48:50 Installing pygpgme-0.2-2.fc17.i686 >11:48:50 Installing yum-3.4.3-23.fc17.noarch >11:48:52 Installing bodhi-client-0.8.5-2.fc17.noarch >11:48:53 Installing yum-utils-1.1.31-4.fc17.noarch >11:48:53 Installing python-deltarpm-3.6-0.7.20110223git.fc17.i686 >11:48:53 Installing createrepo-0.9.9-11.fc17.noarch >11:48:53 Installing xmlrpc-c-client++-1.29.0-1701.svn2233.fc17.i686 >11:48:54 Installing apr-util-ldap-1.4.1-2.fc17.i686 >11:48:54 Installing libnfsidmap-0.25-1.fc17.i686 >11:48:54 Installing mailx-12.5-5.fc17.i686 >11:48:55 Installing groff-1.21-8.fc17.i686 >11:48:58 Installing less-444-5.fc17.i686 >11:48:59 Installing man-db-2.6.0.2-6.fc17.i686 >11:49:30 Installing libyubikey-1.7-2.fc17.i686 >11:49:31 Installing ykpers-1.6.3-1.fc17.i686 >11:49:31 Installing plymouth-core-libs-0.8.4-0.20120319.2.fc17.i686 >11:49:32 Installing libnl-1.1-15.fc17.i686 >11:49:33 Installing pciutils-libs-3.1.9-1.fc17.i686 >11:49:33 Installing pakchois-0.4-5.i686 >11:49:33 Installing c-ares-1.7.5-2.fc17.i686 >11:49:34 Installing libref_array-0.1.2-8.fc17.i686 >11:49:34 Installing libtasn1-2.12-1.fc17.i686 >11:49:35 Installing lcms-libs-1.19-5.fc17.i686 >11:49:35 Installing mingetty-1.08-10.fc17.i686 >11:49:36 Installing libsss_sudo-1.8.3-11.fc17.i686 >11:49:37 Installing libasyncns-0.8-3.fc17.i686 >11:49:37 Installing libdhash-0.4.3-8.fc17.i686 >11:49:37 Installing libthai-0.1.14-5.fc17.i686 >11:49:38 Installing json-c-0.9-4.fc17.i686 >11:49:38 Installing libpcap-1.2.1-2.fc17.i686 >11:49:38 Installing ustr-1.0.4-12.fc17.i686 >11:49:39 Installing libsemanage-2.1.6-3.fc17.i686 >11:49:39 Installing shadow-utils-4.1.4.3-14.fc17.i686 >11:49:41 Installing libutempter-1.1.5-6.fc17.i686 >11:49:42 Installing hardlink-1.0-13.fc17.i686 >11:49:42 Installing libyaml-0.1.4-2.fc17.i686 >11:49:42 Installing ruby-libs-1.9.3.194-10.1.fc17.i686 >11:49:46 Installing p11-kit-0.12-1.fc17.i686 >11:49:46 Installing gnutls-2.12.17-1.fc17.i686 >11:49:47 Installing cups-libs-1.5.2-12.fc17.i686 >11:49:48 Installing neon-0.29.6-2.fc17.i686 >11:49:48 Installing subversion-libs-1.7.4-6.fc17.i686 >11:49:49 Installing libXau-1.0.6-3.fc17.i686 >11:49:49 Installing libxcb-1.8.1-1.fc17.i686 >11:49:50 Installing libX11-1.4.99.901-2.fc17.i686 >11:49:50 Installing libXext-1.3.1-1.fc17.i686 >11:49:51 Installing libXrender-0.9.7-1.fc17.i686 >11:49:51 Installing cairo-1.10.2-7.fc17.i686 >11:49:51 Installing gdk-pixbuf2-2.26.1-1.fc17.i686 >11:49:52 Installing libXt-1.1.2-2.fc17.i686 >11:49:53 Installing libXi-1.6.1-1.fc17.i686 >11:49:53 Installing libXfixes-5.0-2.fc17.i686 >11:49:53 Installing libXpm-3.5.10-1.fc17.i686 >11:49:53 Installing libXdamage-1.1.3-3.fc17.i686 >11:49:53 Installing libXcursor-1.1.13-1.fc17.i686 >11:49:54 Installing libXtst-1.2.0-3.fc17.i686 >11:49:54 Installing libXmu-1.1.0-3.fc17.i686 >11:49:54 Installing cairo-gobject-1.10.2-7.fc17.i686 >11:49:54 Installing libXrandr-1.3.1-3.fc17.i686 >11:49:54 Installing libXft-2.3.0-2.fc17.i686 >11:49:54 Installing pango-1.30.0-1.fc17.i686 >11:49:55 Installing libXinerama-1.1.2-1.fc17.i686 >11:49:55 Installing libXcomposite-0.4.3-3.fc17.i686 >11:49:55 Installing gtk2-2.24.10-1.fc17.i686 >11:49:59 Installing giflib-4.1.6-5.fc17.i686 >11:49:59 Installing libglade2-2.6.4-8.fc17.i686 >11:49:59 Installing libXaw-1.0.9-3.fc17.i686 >11:50:00 Installing libotf-0.9.12-3.fc17.i686 >11:50:00 Installing gd-2.0.35-16.fc17.i686 >11:50:00 Installing ghostscript-9.05-1.fc17.i686 >11:50:05 Installing zip-3.0-4.fc17.i686 >11:50:05 Installing libdaemon-0.14-3.fc17.i686 >11:50:06 Installing avahi-autoipd-0.6.30-7.fc17.i686 >11:50:07 Installing gsm-1.0.13-6.fc17.i686 >11:50:07 Installing libsndfile-1.0.25-2.fc17.i686 >11:50:08 Installing pulseaudio-libs-1.1-9.fc17.i686 >11:50:08 Installing java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6.i686 >11:50:43 Installing xml-commons-apis-1.4.01-6.fc17.noarch >11:50:43 Installing apache-commons-collections-3.2.1-12.fc17.noarch >11:50:44 Installing apache-commons-logging-1.1.1-19.fc17.noarch >11:50:45 Installing apache-commons-pool-1.5.7-2.fc17.noarch >11:50:45 Installing apache-commons-dbcp-1.4-9.fc17.noarch >11:50:45 Installing xml-commons-resolver-1.2-8.fc17.noarch >11:50:46 Installing xalan-j2-2.7.1-8.fc17.noarch >11:50:48 Installing xerces-j2-2.11.0-7.fc17.noarch >11:50:49 Installing jdom-1.1.3-1.fc17.noarch >11:50:49 Installing apache-commons-lang-2.6-6.fc17.noarch >11:50:50 Installing werken-xpath-0.9.4-7.beta.12.4.fc17.noarch >11:50:51 Installing tomcat6-lib-6.0.32-20.fc17.noarch >11:50:54 Installing log4j-1.2.16-11.fc17.noarch >11:50:55 Installing apache-commons-daemon-1.0.10-2.fc17.i686 >11:50:55 Installing regexp-1.5-7.fc17.noarch >11:50:55 Installing bcel-5.2-10.fc17.noarch >11:50:57 Installing qdox-1.12-4.fc17.noarch >11:50:57 Installing jss-4.2.6-24.fc17.i686 >11:50:58 Installing ldapjdk-4.18-9.fc17.noarch >11:50:59 Installing hamcrest-1.1-12.fc17.noarch >11:50:59 Installing junit-4.10-5.fc17.noarch >11:50:59 Installing pki-symkey-9.0.20-1.fc17.i686 >11:51:00 Installing osutil-2.0.2-2.fc17.i686 >11:51:00 Installing pki-util-9.0.20-1.fc17.noarch >11:51:00 Installing pki-java-tools-9.0.20-1.fc17.noarch >11:51:01 Installing pax-3.4-13.fc17.i686 >11:51:01 Installing libwmf-lite-0.2.8.4-32.fc17.i686 >11:51:01 Installing linux-atm-libs-2.5.1-4.fc17.i686 >11:51:01 Installing device-mapper-1.02.74-6.fc17.i686 >11:51:02 Installing iproute-3.3.0-2.fc17.i686 >11:51:02 Installing device-mapper-libs-1.02.74-6.fc17.i686 >11:51:03 Installing cryptsetup-libs-1.4.2-1.fc17.i686 >11:51:03 Installing util-linux-2.21.1-1.fc17.i686 >11:51:05 Installing libudev-182-1.fc17.i686 >11:51:05 Installing udev-182-1.fc17.i686 >11:51:07 Installing initscripts-9.37-1.fc17.i686 >11:51:09 Installing systemd-sysv-44-12.fc17.i686 >11:51:10 Installing systemd-44-12.fc17.i686 >/var/tmp/rpm-tmp.D8aj9m: line 12: 8785 Segmentation fault /usr/sbin/authconfig --update --nostart > /dev/null 2>&1 >/var/tmp/rpm-tmp.D8aj9m: line 12: 8787 Segmentation fault /usr/sbin/authconfig --updateall --nostart > /dev/null 2>&1 >11:51:13 Installing dbus-1.4.10-4.fc17.i686 >11:51:14 Installing iptables-1.4.12.2-5.fc17.i686 >11:51:15 Installing iputils-20101006-14.fc17.i686 >11:51:15 Installing net-tools-1.60-134.20120127git.fc17.i686 >11:51:16 Installing libgudev1-182-1.fc17.i686 >11:51:16 Installing dracut-018-40.git20120522.fc17.noarch >11:51:18 Installing policycoreutils-2.1.11-6.fc17.i686 >11:51:19 Installing polkit-0.104-6.fc17.i686 >11:51:19 Installing device-mapper-event-libs-1.02.74-6.fc17.i686 >11:51:20 Installing samba4-winbind-4.0.0-47alpha18.fc17.i686 >11:51:20 Installing samba4-4.0.0-47alpha18.fc17.i686 >11:51:22 Installing httpd-2.2.22-4.fc17.i686 >11:51:24 Installing cyrus-sasl-2.1.23-29.fc17.i686 >11:51:25 Installing openssh-5.9p1-22.fc17.i686 >11:51:27 Installing samba4-test-4.0.0-47alpha18.fc17.i686 >11:51:29 Installing selinux-policy-3.10.0-125.fc17.noarch >11:51:29 Installing selinux-policy-targeted-3.10.0-125.fc17.noarch >11:51:34 Installing pki-selinux-9.0.20-1.fc17.noarch >11:52:38 Installing pki-setup-9.0.20-1.fc17.noarch >11:52:38 Installing dhclient-4.2.4-0.4.rc1.fc17.i686 >11:52:39 Installing hsqldb-1.8.1.3-7.fc17.noarch >11:52:40 Installing velocity-1.7-3.fc17.noarch >11:52:41 Installing netxen-firmware-4.0.534-5.fc17.noarch >11:52:42 Installing openssh-clients-5.9p1-22.fc17.i686 >11:52:42 Installing linux-firmware-20120206-0.3.git06c8f81.fc17.noarch >11:52:52 Installing kernel-PAE-3.3.7-1.fc17.i686 >11:53:15 Installing perl-Git-1.7.10.2-1.fc17.noarch >11:53:16 Installing git-1.7.10.2-1.fc17.i686 >11:53:23 Installing GitPython-0.3.2-0.2.RC1.fc17.noarch >11:53:24 Installing gettext-devel-0.18.1.1-12.fc17.i686 >11:53:27 Installing systemtap-devel-1.7-7.fc17.i686 >11:53:29 Installing systemtap-runtime-1.7-7.fc17.i686 >11:53:31 Installing systemtap-client-1.7-7.fc17.i686 >11:53:36 Installing cyrus-sasl-devel-2.1.23-29.fc17.i686 >11:53:37 Installing openldap-devel-2.4.30-2.fc17.i686 >11:53:38 Installing sendmail-8.14.5-12.fc17.i686 >11:53:41 Installing device-mapper-event-1.02.74-6.fc17.i686 >11:53:41 Installing lvm2-libs-2.02.95-6.fc17.i686 >11:53:42 Installing GConf2-3.2.5-1.fc17.i686 >11:53:43 Installing NetworkManager-glib-0.9.4.0-9.git20120521.fc17.i686 >11:53:44 Installing libgusb-0.1.3-2.fc17.i686 >11:53:44 Installing ModemManager-0.5.2.0-1.fc17.i686 >11:53:45 Installing wpa_supplicant-1.0-0.4.fc17.i686 >11:53:46 Installing lockdev-1.0.4-0.4.20111007git.fc17.i686 >11:53:46 Installing libgphoto2-2.4.14-1.fc17.i686 >11:53:47 Installing sane-backends-libs-1.0.22-10.fc17.i686 >11:53:48 Installing sane-backends-drivers-scanners-1.0.22-10.fc17.i686 >11:53:50 Installing sane-backends-1.0.22-10.fc17.i686 >11:53:51 Installing colord-0.1.18-2.fc17.i686 >11:53:52 Installing gtk3-3.4.3-2.fc17.i686 >11:53:57 Installing librsvg2-2.36.1-1.fc17.i686 >11:53:58 Installing ImageMagick-6.7.5.6-3.fc17.i686 >11:54:01 Installing rpcbind-0.2.0-16.fc17.i686 >11:54:06 Installing ppp-2.4.5-19.fc17.i686 >11:54:07 Installing at-3.1.13-8.fc17.i686 >11:54:07 Installing ntpdate-4.2.6p5-2.fc17.i686 >11:54:08 Installing portreserve-0.0.5-4.fc17.i686 >11:54:08 Installing rsyslog-5.8.10-1.fc17.i686 >11:54:09 Installing crontabs-1.11-3.20101115git.fc17.noarch >11:54:09 Installing cronie-anacron-1.4.8-11.fc17.i686 >11:54:10 Installing cronie-1.4.8-11.fc17.i686 >error: rpmdb: BDB0058 page 626: illegal page type or format >error: rpmdb: BDB0061 PANIC: Invalid argument >error: rpmdb: BDB3016 Packages: pgin failed for page 626 >error: db5 error(-30973) from dbcursor->c_get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from dbcursor->c_close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->put: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) allocating new package instance >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: cronie-1.4.8-11.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:10 Installing redhat-lsb-4.0-11.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "redhat-lsb" records from Name index >error: redhat-lsb-4.0-11.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:10 Installing tomcat6-6.0.32-20.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "tomcat6" records from Name index >error: tomcat6-0:6.0.32-20.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:10 Installing tomcatjss-6.0.2-2.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "tomcatjss" records from Name index >error: tomcatjss-6.0.2-2.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:10 Installing pki-common-9.0.20-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "pki-common" records from Name index >error: pki-common-9.0.20-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:12 Installing dnsmasq-2.59-5.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "dnsmasq" records from Name index >error: dnsmasq-2.59-5.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:12 Installing oddjob-0.31.1-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "oddjob" records from Name index >error: oddjob-0.31.1-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:12 Installing os-prober-1.53-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "os-prober" records from Name index >error: os-prober-1.53-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:13 Installing libdrm-2.4.33-3.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "libdrm" records from Name index >error: libdrm-2.4.33-3.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:13 Installing plymouth-scripts-0.8.4-0.20120319.2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "plymouth-scripts" records from Name index >error: plymouth-scripts-0.8.4-0.20120319.2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:13 Installing plymouth-0.8.4-0.20120319.2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "plymouth" records from Name index >error: plymouth-0.8.4-0.20120319.2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:13 Installing usermode-1.109-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "usermode" records from Name index >error: usermode-1.109-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:14 Installing mock-1.1.22-2.1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "mock" records from Name index >error: mock-1.1.22-2.1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:14 Installing pyrpkg-1.17-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "pyrpkg" records from Name index >error: pyrpkg-1.17-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:14 Installing fedpkg-1.9-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "fedpkg" records from Name index >error: fedpkg-1.9-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:14 Installing fakeroot-1.12.4-4.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "fakeroot" records from Name index >error: fakeroot-1.12.4-4.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:14 Installing rpmdevtools-8.2-2.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "rpmdevtools" records from Name index >error: rpmdevtools-8.2-2.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:15 Installing liblockfile-1.08-12.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "liblockfile" records from Name index >error: liblockfile-1.08-12.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:15 Installing emacs-common-24.0.95-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "emacs-common" records from Name index >error: emacs-common-1:24.0.95-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:27 Installing libpath_utils-0.2.1-8.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "libpath_utils" records from Name index >error: libpath_utils-0.2.1-8.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:28 Installing fedora-packager-0.5.9.6-2.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "fedora-packager" records from Name index >error: fedora-packager-0.5.9.6-2.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:28 Installing pki-silent-9.0.20-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "pki-silent" records from Name index >error: pki-silent-9.0.20-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:28 Installing pki-ca-9.0.20-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "pki-ca" records from Name index >error: pki-ca-9.0.20-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:28 Installing 389-ds-base-devel-1.2.11.1-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "389-ds-base-devel" records from Name index >error: 389-ds-base-devel-1.2.11.1-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:28 Installing systemtap-1.7-7.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "systemtap" records from Name index >error: systemtap-1.7-7.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:29 Installing intltool-0.50.2-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "intltool" records from Name index >error: intltool-0.50.2-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:29 Installing samba4-devel-4.0.0-47alpha18.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "samba4-devel" records from Name index >error: samba4-devel-2:4.0.0-47alpha18.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:29 Installing system-config-firewall-base-1.2.29-7.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "system-config-firewall-base" records from Name index >error: system-config-firewall-base-1.2.29-7.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:29 Installing xmlrpc-c-devel-1.29.0-1701.svn2233.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "xmlrpc-c-devel" records from Name index >error: xmlrpc-c-devel-1.29.0-1701.svn2233.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:30 Installing fedora-easy-karma-0-0.16.20110825git36efb338.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "fedora-easy-karma" records from Name index >error: fedora-easy-karma-0-0.16.20110825git36efb338.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:30 Installing python-ldap-2.4.6-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-ldap" records from Name index >error: python-ldap-0:2.4.6-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:30 Installing python-nss-0.12-3.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-nss" records from Name index >error: python-nss-0.12-3.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:30 Installing pylint-0.25.1-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "pylint" records from Name index >error: pylint-0.25.1-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:30 Installing python-rhsm-0.99.3-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-rhsm" records from Name index >error: python-rhsm-0.99.3-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:31 Installing libtool-2.4.2-3.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "libtool" records from Name index >error: libtool-2.4.2-3.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:31 Installing koan-2.2.2-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "koan" records from Name index >error: koan-2.2.2-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:31 Installing python-dns-1.9.4-1.fc16.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-dns" records from Name index >error: python-dns-1.9.4-1.fc16.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:32 Installing python-polib-0.7.0-3.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-polib" records from Name index >error: python-polib-0.7.0-3.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:32 Installing python-setuptools-0.6.24-2.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-setuptools" records from Name index >error: python-setuptools-0.6.24-2.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:32 Installing python-memcached-1.47-3.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-memcached" records from Name index >error: python-memcached-1.47-3.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:32 Installing python-netaddr-0.7.5-4.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-netaddr" records from Name index >error: python-netaddr-0.7.5-4.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:33 Installing python-devel-2.7.3-6.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-devel" records from Name index >error: python-devel-2.7.3-6.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:33 Installing python-pyasn1-0.1.2-1.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-pyasn1" records from Name index >error: python-pyasn1-0.1.2-1.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:34 Installing openssl-devel-1.0.0j-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "openssl-devel" records from Name index >error: openssl-devel-1:1.0.0j-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:34 Installing hunspell-en-0.20110318-2.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "hunspell-en" records from Name index >error: hunspell-en-0.20110318-2.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:35 Installing libuuid-devel-2.21.1-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "libuuid-devel" records from Name index >error: libuuid-devel-2.21.1-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:35 Installing automake17-1.7.9-15.fc17.1.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "automake17" records from Name index >error: automake17-1.7.9-15.fc17.1.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:35 Installing automake14-1.4p6-22.fc17.noarch >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "automake14" records from Name index >error: automake14-1.4p6-22.fc17.noarch: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:35 Installing popt-devel-1.13-10.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "popt-devel" records from Name index >error: popt-devel-1.13-10.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:36 Installing libini_config-0.6.2-8.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "libini_config" records from Name index >error: libini_config-0.6.2-8.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:36 Installing sssd-1.8.3-11.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "sssd" records from Name index >error: sssd-1.8.3-11.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:37 Installing emacs-24.0.95-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "emacs" records from Name index >error: emacs-1:24.0.95-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:39 Installing grub2-2.0-0.25.beta4.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "grub2" records from Name index >error: grub2-1:2.0-0.25.beta4.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:42 Installing oddjob-mkhomedir-0.31.1-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "oddjob-mkhomedir" records from Name index >error: oddjob-mkhomedir-0.31.1-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:43 Installing NetworkManager-0.9.4.0-9.git20120521.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "NetworkManager" records from Name index >error: NetworkManager-1:0.9.4.0-9.git20120521.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:44 Installing krb5-server-1.10-6.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "krb5-server" records from Name index >error: krb5-server-1.10-6.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:45 Installing ntp-4.2.6p5-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "ntp" records from Name index >error: ntp-4.2.6p5-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:45 Installing nfs-utils-1.2.6-0.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "nfs-utils" records from Name index >error: nfs-utils-1:1.2.6-0.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:45 Installing lvm2-2.02.95-6.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "lvm2" records from Name index >error: lvm2-2.02.95-6.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:46 Installing sysprof-1.1.8-3.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "sysprof" records from Name index >error: sysprof-1.1.8-3.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:46 Installing autofs-5.0.6-13.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "autofs" records from Name index >error: autofs-1:5.0.6-13.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:47 Installing openssh-server-5.9p1-22.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "openssh-server" records from Name index >error: openssh-server-5.9p1-22.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:47 Installing mod_nss-1.0.8-16.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "mod_nss" records from Name index >error: mod_nss-1.0.8-16.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:47 Installing mod_auth_kerb-5.4-13.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "mod_auth_kerb" records from Name index >error: mod_auth_kerb-5.4-13.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:47 Installing certmonger-0.56-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "certmonger" records from Name index >error: certmonger-0.56-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:48 Installing acpid-2.0.16-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "acpid" records from Name index >error: acpid-2.0.16-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:48 Installing cvs-1.11.23-25.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "cvs" records from Name index >error: cvs-1.11.23-25.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:48 Installing audit-2.2.1-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "audit" records from Name index >error: audit-2.2.1-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:49 Installing subversion-1.7.4-6.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "subversion" records from Name index >error: subversion-1.7.4-6.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:49 Installing kbd-1.15.3-5.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "kbd" records from Name index >error: kbd-1.15.3-5.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:50 Installing memcached-1.4.10-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "memcached" records from Name index >error: memcached-0:1.4.10-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:50 Installing biosdevname-0.3.11-6.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "biosdevname" records from Name index >error: biosdevname-0.3.11-6.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:50 Installing parted-3.0-9.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "parted" records from Name index >error: parted-3.0-9.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:51 Installing vim-enhanced-7.3.515-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "vim-enhanced" records from Name index >error: vim-enhanced-2:7.3.515-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:51 Installing oprofile-0.9.7-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "oprofile" records from Name index >error: oprofile-0.9.7-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:52 Installing sudo-1.8.3p1-7.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "sudo" records from Name index >error: sudo-1.8.3p1-7.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:53 Installing bzr-2.5.0-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "bzr" records from Name index >error: bzr-2.5.0-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:57 Installing gnupg-1.4.12-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "gnupg" records from Name index >error: gnupg-1.4.12-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:57 Installing slapi-nis-0.41-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "slapi-nis" records from Name index >error: slapi-nis-0.41-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:58 Installing bind-utils-9.9.0-4.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "bind-utils" records from Name index >error: bind-utils-32:9.9.0-4.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:54:58 Installing gcc-gfortran-4.7.0-5.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "gcc-gfortran" records from Name index >error: gcc-gfortran-4.7.0-5.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:01 Installing e2fsprogs-1.42-4.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "e2fsprogs" records from Name index >error: e2fsprogs-1.42-4.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:02 Installing mercurial-2.2.1-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "mercurial" records from Name index >error: mercurial-2.2.1-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:03 Installing python-kerberos-1.1-8.1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-kerberos" records from Name index >error: python-kerberos-1.1-8.1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:04 Installing python-lxml-2.3.3-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "python-lxml" records from Name index >error: python-lxml-2.3.3-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:04 Installing libipa_hbac-python-1.8.3-11.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "libipa_hbac-python" records from Name index >error: libipa_hbac-python-1.8.3-11.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:04 Installing mod_wsgi-3.3-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "mod_wsgi" records from Name index >error: mod_wsgi-3.3-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:05 Installing wget-1.13.4-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "wget" records from Name index >error: wget-1.13.4-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:05 Installing krb5-pkinit-1.10-6.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "krb5-pkinit" records from Name index >error: krb5-pkinit-1.10-6.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:05 Installing krb5-workstation-1.10-6.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "krb5-workstation" records from Name index >error: krb5-workstation-1.10-6.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:06 Installing pam_krb5-2.3.13-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "pam_krb5" records from Name index >error: pam_krb5-2.3.13-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:06 Installing mc-4.8.3-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "mc" records from Name index >error: mc-1:4.8.3-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:08 Installing valgrind-3.7.0-4.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "valgrind" records from Name index >error: valgrind-1:3.7.0-4.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:31 Installing patchutils-0.3.2-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "patchutils" records from Name index >error: patchutils-0.3.2-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:31 Installing rcs-5.8-2.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "rcs" records from Name index >error: rcs-5.8-2.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:31 Installing flex-2.5.35-14.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "flex" records from Name index >error: flex-2.5.35-14.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:31 Installing bison-2.5-3.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "bison" records from Name index >error: bison-2.5-3.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:32 Installing swig-2.0.5-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "swig" records from Name index >error: swig-2.0.5-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:33 Installing ltrace-0.6.0-11.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "ltrace" records from Name index >error: ltrace-0.6.0-11.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:33 Installing acl-2.2.51-5.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "acl" records from Name index >error: acl-2.2.51-5.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:33 Installing doxygen-1.8.0-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "doxygen" records from Name index >error: doxygen-1:1.8.0-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:35 Installing texinfo-4.13a-16.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "texinfo" records from Name index >error: texinfo-4.13a-16.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:35 Installing nano-2.3.1-3.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "nano" records from Name index >error: nano-2.3.1-3.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:36 Installing indent-2.2.11-6.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "indent" records from Name index >error: indent-2.2.11-6.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:36 Installing attr-2.4.46-5.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "attr" records from Name index >error: attr-2.4.46-5.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:36 Installing cscope-15.7a-8.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "cscope" records from Name index >error: cscope-15.7a-8.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:36 Installing strace-4.7-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "strace" records from Name index >error: strace-4.7-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:37 Installing byacc-1.9.20111219-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "byacc" records from Name index >error: byacc-1.9.20111219-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:37 Installing diffstat-1.55-1.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "diffstat" records from Name index >error: diffstat-1.55-1.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:37 Installing setserial-2.17-28.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "setserial" records from Name index >error: setserial-2.17-28.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >11:55:37 Installing ctags-5.8-4.fc17.i686 >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: error(-30973) getting "ctags" records from Name index >error: ctags-5.8-4.fc17.i686: install failed >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->sync: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->cursor: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->get: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from db->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >error: rpmdb: BDB1581 File handles still open at environment close >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/__db.001 >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/__db.002 >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/__db.003 >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Packages >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Name >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Basenames >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Group >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Requirename >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Providename >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Conflictname >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Obsoletename >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Triggername >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Dirnames >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Installtid >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Sigmd5 >error: rpmdb: BDB1582 Open file handle: /mnt/sysimage/var/lib/rpm/Sha1header >error: rpmdb: BDB0060 PANIC: fatal region error detected; run recovery >error: db5 error(-30973) from dbenv->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >*** FINISHED INSTALLING PACKAGES *** > >/proc/cmdline: >method=http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/ ksdevice=link lang= text ks=http://10.16.78.1/cblr/svc/op/ks/profile/Fedora-17-i386-freeipa dhcpclass=ipa-lab-vms kssendmac > > >/tmp/syslog: >15:39:07,794 INFO kernel:imklog 5.8.10, log source = /proc/kmsg started. >15:39:07,794 INFO rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="664" x-info="http://www.rsyslog.com"] start >15:39:07,837 INFO kernel:[ 0.000000] Initializing cgroup subsys cpuset >15:39:07,837 INFO kernel:[ 0.000000] Initializing cgroup subsys cpu >15:39:07,837 NOTICE kernel:[ 0.000000] Linux version 3.3.4-5.fc17.i686 (mockbuild@x86-18.phx2.fedoraproject.org) (gcc version 4.7.0 20120504 (Red Hat 4.7.0-4) (GCC) ) #1 SMP Mon May 7 17:45:26 UTC 2012 >15:39:07,837 INFO kernel:[ 0.000000] Disabled fast string operations >15:39:07,837 INFO kernel:[ 0.000000] BIOS-provided physical RAM map: >15:39:07,837 INFO kernel:[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) >15:39:07,837 INFO kernel:[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) >15:39:07,837 INFO kernel:[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) >15:39:07,837 INFO kernel:[ 0.000000] BIOS-e820: 0000000000100000 - 000000003fffd000 (usable) >15:39:07,837 INFO kernel:[ 0.000000] BIOS-e820: 000000003fffd000 - 0000000040000000 (reserved) >15:39:07,837 INFO kernel:[ 0.000000] BIOS-e820: 00000000fffbc000 - 0000000100000000 (reserved) >15:39:07,837 INFO kernel:[ 0.000000] Using x86 segment limits to approximate NX protection >15:39:07,837 INFO kernel:[ 0.000000] DMI 2.4 present. >15:39:07,837 DEBUG kernel:[ 0.000000] DMI: Red Hat KVM, BIOS 0.5.1 01/01/2007 >15:39:07,837 DEBUG kernel:[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) >15:39:07,837 DEBUG kernel:[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable) >15:39:07,837 INFO kernel:[ 0.000000] last_pfn = 0x3fffd max_arch_pfn = 0x100000 >15:39:07,837 DEBUG kernel:[ 0.000000] MTRR default type: write-back >15:39:07,837 DEBUG kernel:[ 0.000000] MTRR fixed ranges enabled: >15:39:07,837 DEBUG kernel:[ 0.000000] 00000-9FFFF write-back >15:39:07,837 DEBUG kernel:[ 0.000000] A0000-BFFFF uncachable >15:39:07,837 DEBUG kernel:[ 0.000000] C0000-FFFFF write-protect >15:39:07,837 DEBUG kernel:[ 0.000000] MTRR variable ranges enabled: >15:39:07,837 DEBUG kernel:[ 0.000000] 0 base 00E0000000 mask 3FE0000000 uncachable >15:39:07,837 DEBUG kernel:[ 0.000000] 1 disabled >15:39:07,837 DEBUG kernel:[ 0.000000] 2 disabled >15:39:07,837 DEBUG kernel:[ 0.000000] 3 disabled >15:39:07,837 DEBUG kernel:[ 0.000000] 4 disabled >15:39:07,837 DEBUG kernel:[ 0.000000] 5 disabled >15:39:07,837 DEBUG kernel:[ 0.000000] 6 disabled >15:39:07,837 DEBUG kernel:[ 0.000000] 7 disabled >15:39:07,837 INFO kernel:[ 0.000000] PAT not supported by CPU. >15:39:07,837 INFO kernel:[ 0.000000] found SMP MP-table at [c00fda70] fda70 >15:39:07,837 DEBUG kernel:[ 0.000000] initial memory mapped : 0 - 01000000 >15:39:07,837 DEBUG kernel:[ 0.000000] Base memory trampoline at [c009b000] 9b000 size 16384 >15:39:07,837 INFO kernel:[ 0.000000] init_memory_mapping: 0000000000000000-00000000373fe000 >15:39:07,837 DEBUG kernel:[ 0.000000] 0000000000 - 0000400000 page 4k >15:39:07,837 DEBUG kernel:[ 0.000000] 0000400000 - 0037000000 page 2M >15:39:07,837 DEBUG kernel:[ 0.000000] 0037000000 - 00373fe000 page 4k >15:39:07,837 DEBUG kernel:[ 0.000000] kernel direct mapping tables up to 373fe000 @ ffa000-1000000 >15:39:07,837 INFO kernel:[ 0.000000] RAMDISK: 3e917000 - 3fff0000 >15:39:07,837 INFO kernel:[ 0.000000] Allocated new RAMDISK: 35d25000 - 373fdd8c >15:39:07,837 INFO kernel:[ 0.000000] Move RAMDISK from 000000003e917000 - 000000003ffefd8b to 35d25000 - 373fdd8b >15:39:07,837 WARNING kernel:[ 0.000000] ACPI: RSDP 000fda20 00014 (v00 BOCHS ) >15:39:07,837 WARNING kernel:[ 0.000000] ACPI: RSDT 3fffd6f0 00030 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) >15:39:07,837 WARNING kernel:[ 0.000000] ACPI: FACP 3ffffe40 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) >15:39:07,837 WARNING kernel:[ 0.000000] ACPI: DSDT 3fffd8b0 02544 (v01 BXPC BXDSDT 00000001 INTL 20090123) >15:39:07,837 WARNING kernel:[ 0.000000] ACPI: FACS 3ffffe00 00040 >15:39:07,837 WARNING kernel:[ 0.000000] ACPI: SSDT 3fffd810 0009E (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) >15:39:07,837 WARNING kernel:[ 0.000000] ACPI: APIC 3fffd720 00078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) >15:39:07,837 DEBUG kernel:[ 0.000000] ACPI: Local APIC address 0xfee00000 >15:39:07,837 NOTICE kernel:[ 0.000000] 139MB HIGHMEM available. >15:39:07,837 NOTICE kernel:[ 0.000000] 883MB LOWMEM available. >15:39:07,837 INFO kernel:[ 0.000000] mapped low ram: 0 - 373fe000 >15:39:07,837 INFO kernel:[ 0.000000] low ram: 0 - 373fe000 >15:39:07,837 INFO kernel:[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 >15:39:07,837 INFO kernel:[ 0.000000] kvm-clock: cpu 0, msr 0:c4b0c1, boot clock >15:39:07,837 WARNING kernel:[ 0.000000] Zone PFN ranges: >15:39:07,837 WARNING kernel:[ 0.000000] DMA 0x00000010 -> 0x00001000 >15:39:07,837 WARNING kernel:[ 0.000000] Normal 0x00001000 -> 0x000373fe >15:39:07,837 WARNING kernel:[ 0.000000] HighMem 0x000373fe -> 0x0003fffd >15:39:07,837 WARNING kernel:[ 0.000000] Movable zone start PFN for each node >15:39:07,837 WARNING kernel:[ 0.000000] Early memory PFN ranges >15:39:07,837 WARNING kernel:[ 0.000000] 0: 0x00000010 -> 0x0000009f >15:39:07,837 WARNING kernel:[ 0.000000] 0: 0x00000100 -> 0x0003fffd >15:39:07,837 DEBUG kernel:[ 0.000000] On node 0 totalpages: 262028 >15:39:07,837 DEBUG kernel:[ 0.000000] free_area_init_node: node 0, pgdat c0b9bf00, node_mem_map f5524200 >15:39:07,837 DEBUG kernel:[ 0.000000] DMA zone: 32 pages used for memmap >15:39:07,837 DEBUG kernel:[ 0.000000] DMA zone: 0 pages reserved >15:39:07,837 DEBUG kernel:[ 0.000000] DMA zone: 3951 pages, LIFO batch:0 >15:39:07,837 DEBUG kernel:[ 0.000000] Normal zone: 1736 pages used for memmap >15:39:07,837 DEBUG kernel:[ 0.000000] Normal zone: 220470 pages, LIFO batch:31 >15:39:07,837 DEBUG kernel:[ 0.000000] HighMem zone: 280 pages used for memmap >15:39:07,837 DEBUG kernel:[ 0.000000] HighMem zone: 35559 pages, LIFO batch:7 >15:39:07,837 INFO kernel:[ 0.000000] Using APIC driver default >15:39:07,837 INFO kernel:[ 0.000000] ACPI: PM-Timer IO Port: 0xb008 >15:39:07,837 DEBUG kernel:[ 0.000000] ACPI: Local APIC address 0xfee00000 >15:39:07,837 INFO kernel:[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) >15:39:07,837 INFO kernel:[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) >15:39:07,837 INFO kernel:[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) >15:39:07,837 INFO kernel:[ 0.000000] IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23 >15:39:07,837 INFO kernel:[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) >15:39:07,837 INFO kernel:[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) >15:39:07,837 INFO kernel:[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) >15:39:07,837 INFO kernel:[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) >15:39:07,837 INFO kernel:[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) >15:39:07,837 DEBUG kernel:[ 0.000000] ACPI: IRQ0 used by override. >15:39:07,837 DEBUG kernel:[ 0.000000] ACPI: IRQ2 used by override. >15:39:07,837 DEBUG kernel:[ 0.000000] ACPI: IRQ5 used by override. >15:39:07,837 DEBUG kernel:[ 0.000000] ACPI: IRQ9 used by override. >15:39:07,837 DEBUG kernel:[ 0.000000] ACPI: IRQ10 used by override. >15:39:07,837 DEBUG kernel:[ 0.000000] ACPI: IRQ11 used by override. >15:39:07,837 INFO kernel:[ 0.000000] Using ACPI (MADT) for SMP configuration information >15:39:07,837 INFO kernel:[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs >15:39:07,837 DEBUG kernel:[ 0.000000] nr_irqs_gsi: 40 >15:39:07,837 INFO kernel:[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000 >15:39:07,837 INFO kernel:[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000 >15:39:07,837 INFO kernel:[ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000 >15:39:07,837 INFO kernel:[ 0.000000] Allocating PCI resources starting at 40000000 (gap: 40000000:bffbc000) >15:39:07,837 INFO kernel:[ 0.000000] Booting paravirtualized kernel on KVM >15:39:07,837 INFO kernel:[ 0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1 >15:39:07,837 INFO kernel:[ 0.000000] PERCPU: Embedded 13 pages/cpu @f5000000 s31040 r0 d22208 u4194304 >15:39:07,837 DEBUG kernel:[ 0.000000] pcpu-alloc: s31040 r0 d22208 u4194304 alloc=1*4194304 >15:39:07,837 DEBUG kernel:[ 0.000000] pcpu-alloc: [0] 0 >15:39:07,837 INFO kernel:[ 0.000000] kvm-clock: cpu 0, msr 0:350070c1, primary cpu clock >15:39:07,837 WARNING kernel:[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 259980 >15:39:07,837 NOTICE kernel:[ 0.000000] Kernel command line: method=http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/ ksdevice=link lang= text ks=http://10.16.78.1/cblr/svc/op/ks/profile/Fedora-17-i386-freeipa dhcpclass=ipa-lab-vms kssendmac >15:39:07,837 INFO kernel:[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) >15:39:07,837 INFO kernel:[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) >15:39:07,837 INFO kernel:[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) >15:39:07,837 INFO kernel:[ 0.000000] Initializing CPU#0 >15:39:07,837 INFO kernel:[ 0.000000] allocated 2097000 bytes of page_cgroup >15:39:07,837 INFO kernel:[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups >15:39:07,837 INFO kernel:[ 0.000000] Initializing HighMem for node 0 (000373fe:0003fffd) >15:39:07,837 INFO kernel:[ 0.000000] Memory: 1004052k/1048564k available (5311k kernel code, 44060k reserved, 2568k data, 616k init, 143356k highmem) >15:39:07,837 INFO kernel:[ 0.000000] virtual kernel memory layout: >15:39:07,837 INFO kernel:[ 0.000000] fixmap : 0xffa96000 - 0xfffff000 (5540 kB) >15:39:07,837 INFO kernel:[ 0.000000] pkmap : 0xff400000 - 0xff800000 (4096 kB) >15:39:07,837 INFO kernel:[ 0.000000] vmalloc : 0xf7bfe000 - 0xff3fe000 ( 120 MB) >15:39:07,837 INFO kernel:[ 0.000000] lowmem : 0xc0000000 - 0xf73fe000 ( 883 MB) >15:39:07,837 INFO kernel:[ 0.000000] .init : 0xc0bb2000 - 0xc0c4c000 ( 616 kB) >15:39:07,837 INFO kernel:[ 0.000000] .data : 0xc092ff15 - 0xc0bb1f40 (2568 kB) >15:39:07,837 INFO kernel:[ 0.000000] .text : 0xc0400000 - 0xc092ff15 (5311 kB) >15:39:07,837 INFO kernel:[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok. >15:39:07,837 INFO kernel:[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 >15:39:07,837 INFO kernel:[ 0.000000] Hierarchical RCU implementation. >15:39:07,837 INFO kernel:[ 0.000000] NR_IRQS:2304 nr_irqs:256 16 >15:39:07,837 DEBUG kernel:[ 0.000000] CPU 0 irqstacks, hard=f4c08000 soft=f4c0a000 >15:39:07,837 INFO kernel:[ 0.000000] Console: colour VGA+ 80x25 >15:39:07,837 INFO kernel:[ 0.000000] console [tty0] enabled >15:39:07,837 WARNING kernel:[ 0.000000] Detected 2500.066 MHz processor. >15:39:07,837 INFO kernel:[ 0.001999] Calibrating delay loop (skipped) preset value.. 5000.13 BogoMIPS (lpj=2500066) >15:39:07,837 INFO kernel:[ 0.003009] pid_max: default: 32768 minimum: 301 >15:39:07,837 INFO kernel:[ 0.004054] Security Framework initialized >15:39:07,837 INFO kernel:[ 0.005035] SELinux: Initializing. >15:39:07,837 DEBUG kernel:[ 0.006020] SELinux: Starting in permissive mode >15:39:07,837 INFO kernel:[ 0.006144] Mount-cache hash table entries: 512 >15:39:07,837 INFO kernel:[ 0.007304] Initializing cgroup subsys cpuacct >15:39:07,837 INFO kernel:[ 0.008009] Initializing cgroup subsys memory >15:39:07,837 INFO kernel:[ 0.009010] Initializing cgroup subsys devices >15:39:07,837 INFO kernel:[ 0.009843] Initializing cgroup subsys freezer >15:39:07,837 INFO kernel:[ 0.010011] Initializing cgroup subsys net_cls >15:39:07,837 INFO kernel:[ 0.011012] Initializing cgroup subsys blkio >15:39:07,837 INFO kernel:[ 0.012015] Initializing cgroup subsys perf_event >15:39:07,837 INFO kernel:[ 0.013108] Disabled fast string operations >15:39:07,837 INFO kernel:[ 0.014021] mce: CPU supports 10 MCE banks >15:39:07,837 INFO kernel:[ 0.015670] SMP alternatives: switching to UP code >15:39:07,837 INFO kernel:[ 0.162118] Freeing SMP alternatives: 24k freed >15:39:07,837 INFO kernel:[ 0.162999] ACPI: Core revision 20120111 >15:39:07,837 INFO kernel:[ 0.165150] ftrace: allocating 21882 entries in 43 pages >15:39:07,837 INFO kernel:[ 0.174150] Enabling APIC mode: Flat. Using 1 I/O APICs >15:39:07,837 INFO kernel:[ 0.176981] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 >15:39:07,837 INFO kernel:[ 0.176984] CPU0: Intel QEMU Virtual CPU version (cpu64-rhel6) stepping 03 >15:39:07,837 INFO kernel:[ 0.179981] Performance Events: Broken PMU hardware detected, using software events only. >15:39:07,837 WARNING kernel:[ 0.182332] NMI watchdog disabled (cpu0): hardware events not enabled >15:39:07,837 INFO kernel:[ 0.183011] Brought up 1 CPUs >15:39:07,837 INFO kernel:[ 0.183984] Total of 1 processors activated (5000.13 BogoMIPS). >15:39:07,837 INFO kernel:[ 0.185670] devtmpfs: initialized >15:39:07,837 INFO kernel:[ 0.187770] atomic64 test passed for i586+ platform with CX8 and with SSE >15:39:07,837 INFO kernel:[ 0.188053] RTC time: 15:37:03, date: 05/30/12 >15:39:07,837 INFO kernel:[ 0.189050] NET: Registered protocol family 16 >15:39:07,837 INFO kernel:[ 0.190248] ACPI: bus type pci registered >15:39:07,837 INFO kernel:[ 0.191987] PCI: PCI BIOS revision 2.10 entry at 0xffe77, last bus=0 >15:39:07,837 INFO kernel:[ 0.192982] PCI: Using configuration type 1 for base access >15:39:07,837 INFO kernel:[ 0.194990] bio: create slab <bio-0> at 0 >15:39:07,837 INFO kernel:[ 0.195961] ACPI: Added _OSI(Module Device) >15:39:07,837 INFO kernel:[ 0.195982] ACPI: Added _OSI(Processor Device) >15:39:07,837 INFO kernel:[ 0.196981] ACPI: Added _OSI(3.0 _SCP Extensions) >15:39:07,837 INFO kernel:[ 0.197982] ACPI: Added _OSI(Processor Aggregator Device) >15:39:07,837 DEBUG kernel:[ 0.199491] ACPI: EC: Look up EC in DSDT >15:39:07,837 INFO kernel:[ 0.201571] ACPI: Interpreter enabled >15:39:07,837 INFO kernel:[ 0.201997] ACPI: (supports S0 S5) >15:39:07,837 INFO kernel:[ 0.202982] ACPI: Using IOAPIC for interrupt routing >15:39:07,838 INFO kernel:[ 0.207985] ACPI: No dock devices found. >15:39:07,838 INFO kernel:[ 0.208789] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug >15:39:07,838 INFO kernel:[ 0.210003] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) >15:39:07,838 DEBUG kernel:[ 0.210997] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored) >15:39:07,838 DEBUG kernel:[ 0.210999] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored) >15:39:07,838 DEBUG kernel:[ 0.211002] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored) >15:39:07,838 DEBUG kernel:[ 0.211004] pci_root PNP0A03:00: host bridge window [mem 0xe0000000-0xfebfffff] (ignored) >15:39:07,838 DEBUG kernel:[ 0.211010] PCI: root bus 00: using default resources >15:39:07,838 INFO kernel:[ 0.211048] PCI host bridge to bus 0000:00 >15:39:07,838 INFO kernel:[ 0.211980] pci_bus 0000:00: root bus resource [io 0x0000-0xffff] >15:39:07,838 INFO kernel:[ 0.212979] pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff] >15:39:07,838 DEBUG kernel:[ 0.214013] pci 0000:00:00.0: [8086:1237] type 0 class 0x000600 >15:39:07,838 DEBUG kernel:[ 0.214299] pci 0000:00:01.0: [8086:7000] type 0 class 0x000601 >15:39:07,838 DEBUG kernel:[ 0.214715] pci 0000:00:01.1: [8086:7010] type 0 class 0x000101 >15:39:07,838 DEBUG kernel:[ 0.215026] pci 0000:00:01.1: reg 20: [io 0xc000-0xc00f] >15:39:07,838 DEBUG kernel:[ 0.215208] pci 0000:00:01.2: [8086:7020] type 0 class 0x000c03 >15:39:07,838 DEBUG kernel:[ 0.215460] pci 0000:00:01.2: reg 20: [io 0xc020-0xc03f] >15:39:07,838 DEBUG kernel:[ 0.215639] pci 0000:00:01.3: [8086:7113] type 0 class 0x000680 >15:39:07,838 INFO kernel:[ 0.216006] pci 0000:00:01.3: quirk: [io 0xb000-0xb03f] claimed by PIIX4 ACPI >15:39:07,838 INFO kernel:[ 0.216987] pci 0000:00:01.3: quirk: [io 0xb100-0xb10f] claimed by PIIX4 SMB >15:39:07,838 DEBUG kernel:[ 0.218110] pci 0000:00:02.0: [1013:00b8] type 0 class 0x000300 >15:39:07,838 DEBUG kernel:[ 0.221061] pci 0000:00:02.0: reg 10: [mem 0xf0000000-0xf1ffffff pref] >15:39:07,838 DEBUG kernel:[ 0.224046] pci 0000:00:02.0: reg 14: [mem 0xf2000000-0xf2000fff] >15:39:07,838 DEBUG kernel:[ 0.236048] pci 0000:00:02.0: reg 30: [mem 0xf2010000-0xf201ffff pref] >15:39:07,838 DEBUG kernel:[ 0.236300] pci 0000:00:03.0: [10ec:8139] type 0 class 0x000200 >15:39:07,838 DEBUG kernel:[ 0.237027] pci 0000:00:03.0: reg 10: [io 0xc100-0xc1ff] >15:39:07,838 DEBUG kernel:[ 0.237105] pci 0000:00:03.0: reg 14: [mem 0xf2020000-0xf20200ff] >15:39:07,838 DEBUG kernel:[ 0.237486] pci 0000:00:03.0: reg 30: [mem 0xf2030000-0xf203ffff pref] >15:39:07,838 DEBUG kernel:[ 0.237577] pci 0000:00:04.0: [1af4:1002] type 0 class 0x000500 >15:39:07,838 DEBUG kernel:[ 0.237649] pci 0000:00:04.0: reg 10: [io 0xc200-0xc21f] >15:39:07,838 DEBUG kernel:[ 0.238207] pci_bus 0000:00: on NUMA node 0 >15:39:07,838 DEBUG kernel:[ 0.238267] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] >15:39:07,838 INFO kernel:[ 0.239055] pci0000:00: Unable to request _OSC control (_OSC support mask: 0x1e) >15:39:07,838 INFO kernel:[ 0.244795] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11) >15:39:07,838 INFO kernel:[ 0.246052] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11) >15:39:07,838 INFO kernel:[ 0.247052] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11) >15:39:07,838 INFO kernel:[ 0.248679] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11) >15:39:07,838 INFO kernel:[ 0.250022] ACPI: PCI Interrupt Link [LNKS] (IRQs 9) *0 >15:39:07,838 INFO kernel:[ 0.251243] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none >15:39:07,838 INFO kernel:[ 0.252973] vgaarb: loaded >15:39:07,838 INFO kernel:[ 0.253708] vgaarb: bridge control possible 0000:00:02.0 >15:39:07,838 NOTICE kernel:[ 0.254268] SCSI subsystem initialized >15:39:07,838 DEBUG kernel:[ 0.255111] libata version 3.00 loaded. >15:39:07,838 INFO kernel:[ 0.255229] usbcore: registered new interface driver usbfs >15:39:07,838 INFO kernel:[ 0.256004] usbcore: registered new interface driver hub >15:39:07,838 INFO kernel:[ 0.257017] usbcore: registered new device driver usb >15:39:07,838 INFO kernel:[ 0.258095] PCI: Using ACPI for IRQ routing >15:39:07,838 DEBUG kernel:[ 0.258982] PCI: pci_cache_line_size set to 64 bytes >15:39:07,838 DEBUG kernel:[ 0.259142] reserve RAM buffer: 000000000009fc00 - 000000000009ffff >15:39:07,838 DEBUG kernel:[ 0.259148] reserve RAM buffer: 000000003fffd000 - 000000003fffffff >15:39:07,838 INFO kernel:[ 0.259975] NetLabel: Initializing >15:39:07,838 INFO kernel:[ 0.260754] NetLabel: domain hash size = 128 >15:39:07,838 INFO kernel:[ 0.260971] NetLabel: protocols = UNLABELED CIPSOv4 >15:39:07,838 INFO kernel:[ 0.261999] NetLabel: unlabeled traffic allowed by default >15:39:07,838 INFO kernel:[ 0.262996] Switching to clocksource kvm-clock >15:39:07,838 INFO kernel:[ 0.275605] pnp: PnP ACPI init >15:39:07,838 INFO kernel:[ 0.276410] ACPI: bus type pnp registered >15:39:07,838 DEBUG kernel:[ 0.277248] pnp 00:00: [bus 00-ff] >15:39:07,838 DEBUG kernel:[ 0.277251] pnp 00:00: [io 0x0cf8-0x0cff] >15:39:07,838 DEBUG kernel:[ 0.277253] pnp 00:00: [io 0x0000-0x0cf7 window] >15:39:07,838 DEBUG kernel:[ 0.277255] pnp 00:00: [io 0x0d00-0xffff window] >15:39:07,838 DEBUG kernel:[ 0.277257] pnp 00:00: [mem 0x000a0000-0x000bffff window] >15:39:07,838 DEBUG kernel:[ 0.277259] pnp 00:00: [mem 0xe0000000-0xfebfffff window] >15:39:07,838 DEBUG kernel:[ 0.277314] pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active) >15:39:07,838 DEBUG kernel:[ 0.277373] pnp 00:01: [io 0x0070-0x0071] >15:39:07,838 DEBUG kernel:[ 0.277415] pnp 00:01: [irq 8] >15:39:07,838 DEBUG kernel:[ 0.277417] pnp 00:01: [io 0x0072-0x0077] >15:39:07,838 DEBUG kernel:[ 0.277452] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active) >15:39:07,838 DEBUG kernel:[ 0.277487] pnp 00:02: [io 0x0060] >15:39:07,838 DEBUG kernel:[ 0.277489] pnp 00:02: [io 0x0064] >15:39:07,838 DEBUG kernel:[ 0.277511] pnp 00:02: [irq 1] >15:39:07,838 DEBUG kernel:[ 0.277536] pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active) >15:39:07,838 DEBUG kernel:[ 0.277578] pnp 00:03: [irq 12] >15:39:07,838 DEBUG kernel:[ 0.277613] pnp 00:03: Plug and Play ACPI device, IDs PNP0f13 (active) >15:39:07,838 DEBUG kernel:[ 0.277636] pnp 00:04: [io 0x03f2-0x03f5] >15:39:07,838 DEBUG kernel:[ 0.277638] pnp 00:04: [io 0x03f7] >15:39:07,838 DEBUG kernel:[ 0.277660] pnp 00:04: [irq 6] >15:39:07,838 DEBUG kernel:[ 0.277662] pnp 00:04: [dma 2] >15:39:07,838 DEBUG kernel:[ 0.277687] pnp 00:04: Plug and Play ACPI device, IDs PNP0700 (active) >15:39:07,838 DEBUG kernel:[ 0.277765] pnp 00:05: [io 0x03f8-0x03ff] >15:39:07,838 DEBUG kernel:[ 0.277788] pnp 00:05: [irq 4] >15:39:07,838 DEBUG kernel:[ 0.277813] pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active) >15:39:07,838 DEBUG kernel:[ 0.277892] pnp 00:06: [mem 0xfed00000-0xfed003ff] >15:39:07,838 DEBUG kernel:[ 0.277932] pnp 00:06: Plug and Play ACPI device, IDs PNP0103 (active) >15:39:07,838 INFO kernel:[ 0.278086] pnp: PnP ACPI: found 7 devices >15:39:07,838 INFO kernel:[ 0.278887] ACPI: ACPI bus type pnp unregistered >15:39:07,838 DEBUG kernel:[ 0.316436] PCI: max bus depth: 0 pci_try_num: 1 >15:39:07,838 DEBUG kernel:[ 0.316450] pci_bus 0000:00: resource 4 [io 0x0000-0xffff] >15:39:07,838 DEBUG kernel:[ 0.316452] pci_bus 0000:00: resource 5 [mem 0x00000000-0xffffffff] >15:39:07,838 INFO kernel:[ 0.316493] NET: Registered protocol family 2 >15:39:07,838 INFO kernel:[ 0.317407] IP route cache hash table entries: 32768 (order: 5, 131072 bytes) >15:39:07,838 INFO kernel:[ 0.318940] TCP established hash table entries: 131072 (order: 8, 1048576 bytes) >15:39:07,838 INFO kernel:[ 0.322028] TCP bind hash table entries: 65536 (order: 7, 524288 bytes) >15:39:07,838 INFO kernel:[ 0.323732] TCP: Hash tables configured (established 131072 bind 65536) >15:39:07,838 INFO kernel:[ 0.324658] TCP reno registered >15:39:07,838 INFO kernel:[ 0.325439] UDP hash table entries: 512 (order: 2, 16384 bytes) >15:39:07,838 INFO kernel:[ 0.326356] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) >15:39:07,838 INFO kernel:[ 0.327376] NET: Registered protocol family 1 >15:39:07,838 INFO kernel:[ 0.328222] pci 0000:00:00.0: Limiting direct PCI/PCI transfers >15:39:07,838 INFO kernel:[ 0.329119] pci 0000:00:01.0: PIIX3: Enabling Passive Release >15:39:07,838 INFO kernel:[ 0.330003] pci 0000:00:01.0: Activating ISA DMA hang workarounds >15:39:07,838 WARNING kernel:[ 0.331066] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 >15:39:07,838 DEBUG kernel:[ 0.332064] pci 0000:00:02.0: Boot video device >15:39:07,838 DEBUG kernel:[ 0.332089] PCI: CLS 0 bytes, default 64 >15:39:07,838 INFO kernel:[ 0.332155] Unpacking initramfs... >15:39:07,838 INFO kernel:[ 3.963116] Freeing initrd memory: 23396k freed >15:39:07,838 INFO kernel:[ 3.973954] apm: BIOS not found. >15:39:07,838 INFO kernel:[ 3.974977] Intel AES-NI instructions are not detected. >15:39:07,838 INFO kernel:[ 3.976129] audit: initializing netlink socket (disabled) >15:39:07,838 NOTICE kernel:[ 3.977002] type=2000 audit(1338392227.975:1): initialized >15:39:07,838 WARNING kernel:[ 3.995345] highmem bounce pool size: 64 pages >15:39:07,838 INFO kernel:[ 3.996197] HugeTLB registered 4 MB page size, pre-allocated 0 pages >15:39:07,838 NOTICE kernel:[ 3.998692] VFS: Disk quotas dquot_6.5.2 >15:39:07,838 WARNING kernel:[ 3.999555] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) >15:39:07,838 INFO kernel:[ 4.000928] msgmni has been set to 1726 >15:39:07,838 DEBUG kernel:[ 4.001801] SELinux: Registering netfilter hooks >15:39:07,838 INFO kernel:[ 4.002753] alg: No test for stdrng (krng) >15:39:07,838 INFO kernel:[ 4.003583] NET: Registered protocol family 38 >15:39:07,838 INFO kernel:[ 4.004458] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) >15:39:07,838 INFO kernel:[ 4.005997] io scheduler noop registered >15:39:07,838 INFO kernel:[ 4.006811] io scheduler deadline registered >15:39:07,838 INFO kernel:[ 4.007641] io scheduler cfq registered (default) >15:39:07,838 INFO kernel:[ 4.008635] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >15:39:07,838 INFO kernel:[ 4.009539] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 >15:39:07,838 INFO kernel:[ 4.010458] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 >15:39:07,838 INFO kernel:[ 4.011458] acpiphp: Slot [1] registered >15:39:07,838 INFO kernel:[ 4.012281] acpiphp: Slot [2] registered >15:39:07,838 INFO kernel:[ 4.013113] acpiphp: Slot [3] registered >15:39:07,838 INFO kernel:[ 4.013925] acpiphp: Slot [4] registered >15:39:07,838 INFO kernel:[ 4.014756] acpiphp: Slot [5] registered >15:39:07,838 INFO kernel:[ 4.015584] acpiphp: Slot [6] registered >15:39:07,838 INFO kernel:[ 4.016414] acpiphp: Slot [7] registered >15:39:07,838 INFO kernel:[ 4.017232] acpiphp: Slot [8] registered >15:39:07,838 INFO kernel:[ 4.018061] acpiphp: Slot [9] registered >15:39:07,838 INFO kernel:[ 4.018869] acpiphp: Slot [10] registered >15:39:07,838 INFO kernel:[ 4.019699] acpiphp: Slot [11] registered >15:39:07,838 INFO kernel:[ 4.020530] acpiphp: Slot [12] registered >15:39:07,838 INFO kernel:[ 4.021359] acpiphp: Slot [13] registered >15:39:07,838 INFO kernel:[ 4.022186] acpiphp: Slot [14] registered >15:39:07,838 INFO kernel:[ 4.022991] acpiphp: Slot [15] registered >15:39:07,838 INFO kernel:[ 4.023830] acpiphp: Slot [16] registered >15:39:07,838 INFO kernel:[ 4.024666] acpiphp: Slot [17] registered >15:39:07,838 INFO kernel:[ 4.025497] acpiphp: Slot [18] registered >15:39:07,838 INFO kernel:[ 4.026321] acpiphp: Slot [19] registered >15:39:07,838 INFO kernel:[ 4.027142] acpiphp: Slot [20] registered >15:39:07,838 INFO kernel:[ 4.028000] acpiphp: Slot [21] registered >15:39:07,838 INFO kernel:[ 4.028829] acpiphp: Slot [22] registered >15:39:07,838 INFO kernel:[ 4.029664] acpiphp: Slot [23] registered >15:39:07,838 INFO kernel:[ 4.030497] acpiphp: Slot [24] registered >15:39:07,838 INFO kernel:[ 4.031320] acpiphp: Slot [25] registered >15:39:07,838 INFO kernel:[ 4.032143] acpiphp: Slot [26] registered >15:39:07,838 INFO kernel:[ 4.032955] acpiphp: Slot [27] registered >15:39:07,838 INFO kernel:[ 4.033786] acpiphp: Slot [28] registered >15:39:07,838 INFO kernel:[ 4.034612] acpiphp: Slot [29] registered >15:39:07,838 INFO kernel:[ 4.035444] acpiphp: Slot [30] registered >15:39:07,838 INFO kernel:[ 4.036275] acpiphp: Slot [31] registered >15:39:07,838 INFO kernel:[ 4.038099] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 >15:39:07,838 INFO kernel:[ 4.039620] ACPI: Power Button [PWRF] >15:39:07,838 INFO kernel:[ 4.041783] GHES: HEST is not enabled! >15:39:07,838 DEBUG kernel:[ 4.042661] virtio-pci 0000:00:04.0: setting latency timer to 64 >15:39:07,838 INFO kernel:[ 4.042787] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled >15:39:07,838 INFO kernel:[ 4.065697] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A >15:39:07,838 INFO kernel:[ 4.088844] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A >15:39:07,838 WARNING kernel:[ 4.090092] hpet_acpi_add: no address or irqs in _CRS >15:39:07,838 INFO kernel:[ 4.090959] Non-volatile memory driver v1.3 >15:39:07,838 INFO kernel:[ 4.091791] Linux agpgart interface v0.103 >15:39:07,838 INFO kernel:[ 4.093405] loop: module loaded >15:39:07,838 DEBUG kernel:[ 4.094275] ata_piix 0000:00:01.1: version 2.13 >15:39:07,838 DEBUG kernel:[ 4.094376] ata_piix 0000:00:01.1: setting latency timer to 64 >15:39:07,838 INFO kernel:[ 4.094758] scsi0 : ata_piix >15:39:07,838 INFO kernel:[ 4.095601] scsi1 : ata_piix >15:39:07,838 INFO kernel:[ 4.096406] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 >15:39:07,838 INFO kernel:[ 4.097334] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15 >15:39:07,838 INFO kernel:[ 4.098335] Fixed MDIO Bus: probed >15:39:07,838 INFO kernel:[ 4.099176] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver >15:39:07,838 INFO kernel:[ 4.100115] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver >15:39:07,838 INFO kernel:[ 4.101026] uhci_hcd: USB Universal Host Controller Interface driver >15:39:07,838 DEBUG kernel:[ 4.101977] uhci_hcd 0000:00:01.2: setting latency timer to 64 >15:39:07,838 INFO kernel:[ 4.101990] uhci_hcd 0000:00:01.2: UHCI Host Controller >15:39:07,838 INFO kernel:[ 4.102900] uhci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1 >15:39:07,838 INFO kernel:[ 4.104546] uhci_hcd 0000:00:01.2: irq 11, io base 0x0000c020 >15:39:07,838 INFO kernel:[ 4.105519] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 >15:39:07,838 INFO kernel:[ 4.106475] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >15:39:07,838 INFO kernel:[ 4.107985] usb usb1: Product: UHCI Host Controller >15:39:07,838 INFO kernel:[ 4.108862] usb usb1: Manufacturer: Linux 3.3.4-5.fc17.i686 uhci_hcd >15:39:07,838 INFO kernel:[ 4.109777] usb usb1: SerialNumber: 0000:00:01.2 >15:39:07,838 INFO kernel:[ 4.110777] hub 1-0:1.0: USB hub found >15:39:07,838 INFO kernel:[ 4.111591] hub 1-0:1.0: 2 ports detected >15:39:07,838 INFO kernel:[ 4.112555] usbcore: registered new interface driver usbserial >15:39:07,838 INFO kernel:[ 4.113520] USB Serial support registered for generic >15:39:07,838 INFO kernel:[ 4.114416] usbcore: registered new interface driver usbserial_generic >15:39:07,838 INFO kernel:[ 4.115356] usbserial: USB Serial Driver core >15:39:07,838 INFO kernel:[ 4.116663] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 >15:39:07,838 INFO kernel:[ 4.118981] serio: i8042 KBD port at 0x60,0x64 irq 1 >15:39:07,838 INFO kernel:[ 4.119843] serio: i8042 AUX port at 0x60,0x64 irq 12 >15:39:07,838 INFO kernel:[ 4.120822] mousedev: PS/2 mouse device common for all mice >15:39:07,838 INFO kernel:[ 4.122107] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 >15:39:07,838 DEBUG kernel:[ 4.125930] psmouse serio1: hgpk: ID: 10 00 64 >15:39:07,838 INFO kernel:[ 4.126770] rtc_cmos 00:01: RTC can wake from S4 >15:39:07,838 INFO kernel:[ 4.127825] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0 >15:39:07,838 INFO kernel:[ 4.128837] rtc0: alarms up to one day, 114 bytes nvram >15:39:07,838 INFO kernel:[ 4.129804] device-mapper: uevent: version 1.0.3 >15:39:07,838 INFO kernel:[ 4.130715] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com >15:39:07,838 INFO kernel:[ 4.132374] cpuidle: using governor ladder >15:39:07,838 INFO kernel:[ 4.133190] cpuidle: using governor menu >15:39:07,838 INFO kernel:[ 4.134096] EFI Variables Facility v0.08 2004-May-17 >15:39:07,838 INFO kernel:[ 4.135067] usbcore: registered new interface driver usbhid >15:39:07,838 INFO kernel:[ 4.135964] usbhid: USB HID core driver >15:39:07,838 INFO kernel:[ 4.136867] ip_tables: (C) 2000-2006 Netfilter Core Team >15:39:07,838 INFO kernel:[ 4.137811] TCP cubic registered >15:39:07,838 INFO kernel:[ 4.138597] Initializing XFRM netlink socket >15:39:07,838 INFO kernel:[ 4.139560] NET: Registered protocol family 10 >15:39:07,838 INFO kernel:[ 4.140613] Mobile IPv6 >15:39:07,838 INFO kernel:[ 4.141375] NET: Registered protocol family 17 >15:39:07,838 NOTICE kernel:[ 4.142206] Registering the dns_resolver key type >15:39:07,838 INFO kernel:[ 4.143088] Using IPI No-Shortcut mode >15:39:07,838 DEBUG kernel:[ 4.143949] PM: Hibernation image not present or could not be loaded. >15:39:07,838 INFO kernel:[ 4.143980] registered taskstats version 1 >15:39:07,838 INFO kernel:[ 4.145071] Magic number: 12:420:640 >15:39:07,838 INFO kernel:[ 4.145966] rtc_cmos 00:01: setting system clock to 2012-05-30 15:37:07 UTC (1338392227) >15:39:07,838 INFO kernel:[ 4.147602] Initializing network drop monitor service >15:39:07,838 DEBUG kernel:[ 4.267718] ata1.01: NODEV after polling detection >15:39:07,838 INFO kernel:[ 4.267965] ata1.00: ATA-7: QEMU HARDDISK, 0.12.1, max UDMA/100 >15:39:07,838 INFO kernel:[ 4.268882] ata1.00: 10485760 sectors, multi 16: LBA48 >15:39:07,838 INFO kernel:[ 4.270152] ata1.00: configured for MWDMA2 >15:39:07,838 NOTICE kernel:[ 4.271173] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 0.12 PQ: 0 ANSI: 5 >15:39:07,839 NOTICE kernel:[ 4.273090] sd 0:0:0:0: Attached scsi generic sg0 type 0 >15:39:07,906 ERR : Failed to open /etc/fstab: No such file or directory >15:39:07,906 NOTICE systemd: systemd-remount-api-vfs.service: main process exited, code=exited, status=1 >15:39:07,906 NOTICE systemd: Unit systemd-remount-api-vfs.service entered failed state. >15:39:07,906 INFO : Root directory is writable, skipping check. >15:39:07,906 INFO lvm: No volume groups found >15:39:07,906 WARNING (plymouth): Failed at step EXEC spawning /bin/plymouth: No such file or directory >15:39:07,906 INFO systemd-tmpfile: Successfully loaded SELinux database in 54ms 190us, size on heap is 408K. >15:39:07,906 ERR udevd: ctx=0x215b8720 path=/lib/modules/3.3.4-5.fc17.i686/kernel/sound/core/snd-pcm.ko error=No such file or directory >15:39:07,906 WARNING (lymouthd): Failed at step EXEC spawning /sbin/plymouthd: No such file or directory >15:39:07,906 NOTICE systemd: plymouth-start.service: control process exited, code=exited status=203 >15:39:07,906 NOTICE systemd: Unit plymouth-start.service entered failed state. >15:39:07,917 NOTICE kernel:[ 4.274139] sd 0:0:0:0: [sda] 10485760 512-byte logical blocks: (5.36 GB/5.00 GiB) >15:39:07,918 NOTICE kernel:[ 4.275729] sd 0:0:0:0: [sda] Write Protect is off >15:39:07,918 DEBUG kernel:[ 4.276576] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 >15:39:07,918 NOTICE kernel:[ 4.276597] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA >15:39:07,918 INFO kernel:[ 4.280299] sda: unknown partition table >15:39:07,918 NOTICE kernel:[ 4.281279] sd 0:0:0:0: [sda] Attached SCSI disk >15:39:07,918 INFO kernel:[ 4.282232] Freeing unused kernel memory: 616k freed >15:39:07,918 INFO kernel:[ 4.286872] Write protecting the kernel text: 5312k >15:39:07,918 INFO kernel:[ 4.292948] Write protecting the kernel read-only data: 2092k >15:39:07,918 INFO kernel:[ 4.557319] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input2 >15:39:07,918 INFO kernel:[ 4.977400] Refined TSC clocksource calibration: 2500.089 MHz. >15:39:07,918 INFO kernel:[ 5.173258] squashfs: version 4.0 (2009/01/31) Phillip Lougher >15:39:07,918 INFO kernel:[ 5.183769] Loading iSCSI transport class v2.0-870. >15:39:07,918 NOTICE kernel:[ 5.187375] iscsi: registered transport (tcp) >15:39:07,918 INFO kernel:[ 5.197128] alua: device handler registered >15:39:07,918 INFO kernel:[ 5.206837] emc: device handler registered >15:39:07,918 INFO kernel:[ 5.216195] hp_sw: device handler registered >15:39:07,918 INFO kernel:[ 5.225665] rdac: device handler registered >15:39:07,918 INFO kernel:[ 5.248397] FDC 0 is a S82078B >15:39:07,918 INFO kernel:[ 5.258001] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found >15:39:07,918 INFO kernel:[ 5.267926] No iBFT detected. >15:39:07,918 INFO kernel:[ 5.277357] md: raid0 personality registered for level 0 >15:39:07,918 INFO kernel:[ 5.289518] md: raid1 personality registered for level 1 >15:39:07,918 INFO kernel:[ 5.299192] async_tx: api initialized (async) >15:39:07,918 INFO kernel:[ 5.300774] xor: automatically using best checksumming function: pIII_sse >15:39:07,918 INFO kernel:[ 5.306019] pIII_sse : 7956.000 MB/sec >15:39:07,918 INFO kernel:[ 5.306818] xor: using function: pIII_sse (7956.000 MB/sec) >15:39:07,918 WARNING kernel:[ 5.326061] raid6: int32x1 902 MB/s >15:39:07,918 WARNING kernel:[ 5.343025] raid6: int32x2 746 MB/s >15:39:07,918 WARNING kernel:[ 5.360097] raid6: int32x4 660 MB/s >15:39:07,918 WARNING kernel:[ 5.377061] raid6: int32x8 769 MB/s >15:39:07,918 WARNING kernel:[ 5.394026] raid6: mmxx1 3101 MB/s >15:39:07,918 WARNING kernel:[ 5.411034] raid6: mmxx2 3472 MB/s >15:39:07,918 WARNING kernel:[ 5.428045] raid6: sse1x1 1628 MB/s >15:39:07,918 WARNING kernel:[ 5.445028] raid6: sse1x2 1972 MB/s >15:39:07,918 WARNING kernel:[ 5.462028] raid6: sse2x1 2621 MB/s >15:39:07,918 WARNING kernel:[ 5.479036] raid6: sse2x2 3410 MB/s >15:39:07,918 WARNING kernel:[ 5.479824] raid6: using algorithm sse2x2 (3410 MB/s) >15:39:07,918 INFO kernel:[ 5.490887] md: raid6 personality registered for level 6 >15:39:07,918 INFO kernel:[ 5.491781] md: raid5 personality registered for level 5 >15:39:07,918 INFO kernel:[ 5.492647] md: raid4 personality registered for level 4 >15:39:07,918 INFO kernel:[ 5.521773] md: raid10 personality registered for level 10 >15:39:07,918 INFO kernel:[ 5.531402] md: linear personality registered for level -1 >15:39:07,918 INFO kernel:[ 5.571913] device-mapper: multipath: version 1.3.0 loaded >15:39:07,918 INFO kernel:[ 5.581606] device-mapper: multipath round-robin: version 1.0.0 loaded >15:39:07,918 INFO kernel:[ 6.100128] RPC: Registered named UNIX socket transport module. >15:39:07,918 INFO kernel:[ 6.101055] RPC: Registered udp transport module. >15:39:07,918 INFO kernel:[ 6.101878] RPC: Registered tcp transport module. >15:39:07,918 INFO kernel:[ 6.102727] RPC: Registered tcp NFSv4.1 backchannel transport module. >15:39:07,918 INFO kernel:[ 6.452734] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) >15:39:07,918 WARNING kernel:[ 6.454064] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 >15:39:07,918 INFO kernel:[ 6.494997] 8139cp 0000:00:03.0: eth0: RTL-8139C+ at 0xf7bfe000, 00:16:3e:55:f8:21, IRQ 10 >15:39:07,918 DEBUG kernel:[ 6.496652] 8139cp 0000:00:03.0: setting latency timer to 64 >15:39:07,918 INFO kernel:[ 6.544916] 8139too: 8139too Fast Ethernet driver 0.9.28 >15:39:07,918 INFO kernel:[ 6.824150] 8139cp 0000:00:03.0: eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 >15:39:07,918 INFO kernel:[ 118.897705] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) >15:39:07,918 DEBUG kernel:[ 120.096604] SELinux: 2048 avtab hash slots, 99000 rules. >15:39:07,918 DEBUG kernel:[ 120.119746] SELinux: 2048 avtab hash slots, 99000 rules. >15:39:07,918 DEBUG kernel:[ 120.193883] SELinux: 9 users, 15 roles, 4112 types, 222 bools, 1 sens, 1024 cats >15:39:07,918 DEBUG kernel:[ 120.193888] SELinux: 83 classes, 99000 rules >15:39:07,918 INFO kernel:[ 120.200640] SELinux: Permission ptrace_child in class process not defined in policy. >15:39:07,918 INFO kernel:[ 120.202376] SELinux: the above unknown classes and permissions will be allowed >15:39:07,918 DEBUG kernel:[ 120.203894] SELinux: Completing initialization. >15:39:07,918 DEBUG kernel:[ 120.203896] SELinux: Setting up existing superblocks. >15:39:07,918 DEBUG kernel:[ 120.203910] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.203916] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.203920] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.203925] SELinux: initialized (dev proc, type proc), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.203944] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >15:39:07,918 DEBUG kernel:[ 120.203957] SELinux: initialized (dev devtmpfs, type devtmpfs), uses transition SIDs >15:39:07,918 DEBUG kernel:[ 120.204349] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs >15:39:07,918 DEBUG kernel:[ 120.204354] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.206353] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs >15:39:07,918 DEBUG kernel:[ 120.206357] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.206361] SELinux: initialized (dev devpts, type devpts), uses transition SIDs >15:39:07,918 DEBUG kernel:[ 120.206376] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs >15:39:07,918 DEBUG kernel:[ 120.206385] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs >15:39:07,918 DEBUG kernel:[ 120.206390] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.206413] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.207088] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >15:39:07,918 DEBUG kernel:[ 120.207093] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >15:39:07,918 DEBUG kernel:[ 120.210434] SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.210471] SELinux: initialized (dev loop0, type squashfs), uses xattr >15:39:07,918 DEBUG kernel:[ 120.210500] SELinux: initialized (dev dm-0, type ext4), uses xattr >15:39:07,918 NOTICE kernel:[ 120.212630] type=1403 audit(1338392343.566:2): policy loaded auid=4294967295 ses=4294967295 >15:39:07,918 DEBUG kernel:[ 120.285899] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >15:39:07,918 DEBUG kernel:[ 120.286338] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.390142] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.390484] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.390849] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.391140] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.391409] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.391674] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.391961] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.392251] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 120.715529] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 121.029229] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >15:39:07,918 DEBUG kernel:[ 121.291988] SELinux: initialized (dev configfs, type configfs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 121.298611] SELinux: initialized (dev securityfs, type securityfs), uses genfs_contexts >15:39:07,918 DEBUG kernel:[ 121.360525] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs >15:39:07,918 INFO kernel:[ 121.459393] EXT4-fs (dm-0): re-mounted. Opts: user_xattr,barrier=1,data=ordered >15:39:07,918 NOTICE kernel:[ 122.830088] type=1400 audit(1338392346.184:3): avc: denied { create } for pid=615 comm="systemd-tmpfile" name="tmp" scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir >15:39:07,918 NOTICE kernel:[ 122.833614] type=1400 audit(1338392346.187:4): avc: denied { setattr } for pid=615 comm="systemd-tmpfile" name="tmp" dev="dm-0" ino=115723 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir >15:39:07,918 NOTICE kernel:[ 122.833738] type=1400 audit(1338392346.187:5): avc: denied { relabelfrom } for pid=615 comm="systemd-tmpfile" name="tmp" dev="dm-0" ino=115723 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir >15:39:07,918 INFO kernel:[ 122.945483] piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb100, revision 0 >15:39:07,918 NOTICE kernel:[ 124.290225] type=1400 audit(1338392347.644:6): avc: denied { execute } for pid=666 comm="bash" name="hostname" dev="dm-0" ino=99901 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:hostname_exec_t:s0 tclass=file >15:39:07,918 NOTICE kernel:[ 124.290236] type=1400 audit(1338392347.644:7): avc: denied { read open } for pid=666 comm="bash" name="hostname" dev="dm-0" ino=99901 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:hostname_exec_t:s0 tclass=file >15:39:07,918 NOTICE kernel:[ 124.290279] type=1400 audit(1338392347.644:8): avc: denied { execute_no_trans } for pid=666 comm="bash" path="/usr/bin/hostname" dev="dm-0" ino=99901 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:hostname_exec_t:s0 tclass=file >15:39:07,918 NOTICE kernel:[ 124.312604] type=1400 audit(1338392347.666:9): avc: denied { read } for pid=662 comm="bash" name=".profile" dev="dm-0" ino=65751 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:admin_home_t:s0 tclass=file >15:39:07,918 NOTICE kernel:[ 124.312615] type=1400 audit(1338392347.666:10): avc: denied { open } for pid=662 comm="bash" name=".profile" dev="dm-0" ino=65751 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:admin_home_t:s0 tclass=file >15:39:07,918 NOTICE kernel:[ 124.318160] type=1400 audit(1338392347.672:11): avc: denied { read } for pid=662 comm="bash" name="linux" dev="dm-0" ino=187 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:usr_t:s0 tclass=file >15:39:07,950 INFO dbus-daemon: dbus[671]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) >15:39:07,950 NOTICE dbus: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) >15:39:08,002 INFO polkitd: started daemon version 0.104 using authority implementation `local' version `0.104' >15:39:08,004 INFO dbus-daemon: dbus[671]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' >15:39:08,005 NOTICE dbus: [system] Successfully activated service 'org.freedesktop.PolicyKit1' >15:39:08,041 WARNING NetworkManager: ifcfg-rh: Could not get hostname: failed to read /etc/sysconfig/network >15:39:08,043 NOTICE NetworkManager: ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1 >15:39:08,044 INFO NetworkManager: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. >15:39:08,045 INFO NetworkManager: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. >15:39:08,049 NOTICE NetworkManager: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... >15:39:08,050 NOTICE NetworkManager: ifcfg-rh: read connection 'Boot Disk' >15:39:08,051 NOTICE NetworkManager: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... >15:39:08,052 INFO NetworkManager: <info> trying to start the modem manager... >15:39:08,060 INFO dbus-daemon: dbus[671]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) >15:39:08,061 NOTICE dbus: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) >15:39:08,062 INFO NetworkManager: <info> monitoring kernel firmware directory '/lib/firmware'. >15:39:08,109 INFO NetworkManager: <info> WiFi enabled by radio killswitch; enabled by state file >15:39:08,110 INFO NetworkManager: <info> WWAN enabled by radio killswitch; enabled by state file >15:39:08,120 INFO NetworkManager: <info> WiMAX enabled by radio killswitch; enabled by state file >15:39:08,139 INFO NetworkManager: <info> Networking is enabled by state file >15:39:08,161 WARNING NetworkManager: <warn> failed to allocate link cache: (-10) Operation not supported >15:39:08,189 INFO NetworkManager: <info> (eth0): carrier is ON >15:39:08,208 INFO NetworkManager: <info> (eth0): new Ethernet device (driver: '8139cp' ifindex: 2) >15:39:08,211 INFO NetworkManager: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 >15:39:08,228 INFO NetworkManager: <info> (eth0): now managed >15:39:08,240 INFO NetworkManager: <info> (eth0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] >15:39:08,245 INFO NetworkManager: <info> (eth0): preparing device. >15:39:08,253 INFO NetworkManager: <info> Activation (eth0) starting connection 'Boot Disk' >15:39:08,267 INFO NetworkManager: <info> (eth0): device state change: unavailable -> ip-config (reason 'none') [20 70 0] >15:39:08,286 WARNING NetworkManager: (nm-device.c:2343):nm_device_activate_schedule_stage3_ip_config_start: runtime check failed: (state >= NM_DEVICE_STATE_PREPARE && state <= NM_DEVICE_STATE_NEED_AUTH) >15:39:08,333 INFO NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. >15:39:08,357 WARNING NetworkManager: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files >15:39:08,415 INFO NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... >15:39:08,450 INFO NetworkManager: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds) >15:39:08,469 INFO modem-manager: <info> ModemManager (version 0.5.2.0-1.fc17) starting... >15:39:08,491 INFO NetworkManager: <info> dhclient started with pid 685 >15:39:08,541 INFO NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. >15:39:08,546 NOTICE dbus: [system] Successfully activated service 'org.freedesktop.ModemManager' >15:39:08,555 INFO NetworkManager: <info> modem-manager is now available >15:39:08,575 INFO modem-manager: <info> Loaded plugin Samsung >15:39:08,588 INFO modem-manager: <info> Loaded plugin Wavecom >15:39:08,597 INFO modem-manager: <info> Loaded plugin Option >15:39:08,628 INFO modem-manager: <info> Loaded plugin Option High-Speed >15:39:08,643 INFO modem-manager: <info> Loaded plugin Nokia >15:39:08,680 INFO modem-manager: <info> Loaded plugin Generic >15:39:08,690 INFO modem-manager: <info> Loaded plugin Gobi >15:39:08,691 INFO modem-manager: <info> Loaded plugin AnyData >15:39:08,708 INFO modem-manager: <info> Loaded plugin Linktop >15:39:08,709 INFO modem-manager: <info> Loaded plugin ZTE >15:39:08,711 INFO modem-manager: <info> Loaded plugin MotoC >15:39:08,715 INFO modem-manager: <info> Loaded plugin Novatel >15:39:08,726 INFO modem-manager: <info> Loaded plugin X22X >15:39:08,733 INFO modem-manager: <info> Loaded plugin Ericsson MBM >15:39:08,741 INFO modem-manager: <info> Loaded plugin Huawei >15:39:08,742 INFO modem-manager: <info> Loaded plugin Sierra >15:39:08,755 INFO modem-manager: <info> Loaded plugin Longcheer >15:39:08,759 INFO modem-manager: <info> Loaded plugin SimTech >15:39:08,767 INFO dhclient: Internet Systems Consortium DHCP Client 4.2.4rc1 >15:39:08,769 INFO dhclient: Copyright 2004-2012 Internet Systems Consortium. >15:39:08,781 INFO dhclient: All rights reserved. >15:39:08,782 INFO dhclient: For info, please visit https://www.isc.org/software/dhcp/ >15:39:08,785 INFO dhclient: >15:39:08,788 INFO dbus-daemon: modem-manager[683]: <info> ModemManager (version 0.5.2.0-1.fc17) starting... >15:39:08,790 INFO dbus-daemon: dbus[671]: [system] Successfully activated service 'org.freedesktop.ModemManager' >15:39:08,801 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Samsung >15:39:08,804 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Wavecom >15:39:08,811 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Option >15:39:08,813 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Option High-Speed >15:39:08,819 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Nokia >15:39:08,820 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Generic >15:39:08,824 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Gobi >15:39:08,827 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin AnyData >15:39:08,828 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Linktop >15:39:08,837 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin ZTE >15:39:08,841 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin MotoC >15:39:08,845 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Novatel >15:39:08,846 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin X22X >15:39:08,847 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Ericsson MBM >15:39:08,854 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Huawei >15:39:08,858 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Sierra >15:39:08,859 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin Longcheer >15:39:08,860 INFO dbus-daemon: modem-manager[683]: <info> Loaded plugin SimTech >15:39:08,865 INFO NetworkManager: <info> (eth0): DHCPv4 state changed nbi -> preinit >15:39:08,866 INFO dhclient: Listening on LPF/eth0/00:16:3e:55:f8:21 >15:39:08,868 INFO dhclient: Sending on LPF/eth0/00:16:3e:55:f8:21 >15:39:08,888 INFO dhclient: Sending on Socket/fallback >15:39:08,890 INFO dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x5e752ba1) >15:39:08,897 INFO dhclient: DHCPACK from 10.16.78.150 (xid=0x5e752ba1) >15:39:08,898 INFO NetworkManager: <info> (eth0): DHCPv4 state changed preinit -> reboot >15:39:08,900 INFO NetworkManager: <info> address 10.16.79.206 >15:39:08,905 INFO NetworkManager: <info> prefix 22 (255.255.252.0) >15:39:08,910 INFO NetworkManager: <info> gateway 10.16.79.254 >15:39:08,915 INFO NetworkManager: <info> nameserver '10.16.78.150' >15:39:08,919 INFO NetworkManager: <info> domain name 'idm.lab.bos.redhat.com' >15:39:08,922 INFO dhclient: bound to 10.16.79.206 -- renewal in 47101 seconds. >15:39:08,925 INFO NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... >15:39:08,934 INFO NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started... >15:39:08,941 INFO NetworkManager: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0] >15:39:08,942 INFO NetworkManager: <info> Policy set 'Boot Disk' (eth0) as default for IPv4 routing and DNS. >15:39:08,949 INFO NetworkManager: <info> Activation (eth0) successful, device activated. >15:39:08,951 NOTICE dbus: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) >15:39:08,958 INFO NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. >15:39:08,959 INFO NetworkManager: <info> Setting system hostname to 'unused' (from address lookup) >15:39:08,966 INFO dbus-daemon: dbus[671]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) >15:39:08,974 INFO dbus-daemon: dbus[671]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' >15:39:08,979 NOTICE dbus: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' >15:39:09,129 INFO dbus-daemon: /etc/NetworkManager/dispatcher.d/04-iscsi: line 13: /sbin/ip: No such file or directory >15:39:13,676 WARNING kernel:[ 130.321710] audit_printk_skb: 6 callbacks suppressed >15:39:13,676 NOTICE kernel:[ 130.321713] type=1400 audit(1338392353.675:14): avc: denied { append } for pid=720 comm="auditd" path="/tmp/anaconda.log" dev="dm-0" ino=25745 scontext=system_u:system_r:auditd_t:s0 tcontext=system_u:object_r:initrc_tmp_t:s0 tclass=file >15:39:13,676 NOTICE kernel:[ 130.321917] type=1400 audit(1338392353.675:15): avc: denied { read write } for pid=720 comm="auditd" path="/dev/mapper/control" dev="devtmpfs" ino=6967 scontext=system_u:system_r:auditd_t:s0 tcontext=system_u:object_r:lvm_control_t:s0 tclass=chr_file >15:39:13,695 WARNING kernel:[ 130.340637] auditd (721): /proc/721/oom_adj is deprecated, please use /proc/721/oom_score_adj instead. >15:39:20,391 WARNING kernel:[ 137.132813] lvm: sending ioctl 1261 to a partition! >15:39:20,391 WARNING kernel:[ 137.132817] lvm: sending ioctl 1261 to a partition! >15:39:21,268 WARNING kernel:[ 138.009442] lvm: sending ioctl 1261 to a partition! >15:39:21,268 WARNING kernel:[ 138.009445] lvm: sending ioctl 1261 to a partition! >15:39:21,268 WARNING kernel:[ 138.009448] lvm: sending ioctl 1261 to a partition! >15:39:25,232 WARNING kernel:[ 141.973514] lvm: sending ioctl 1261 to a partition! >15:39:25,232 WARNING kernel:[ 141.973517] lvm: sending ioctl 1261 to a partition! >15:39:25,232 WARNING kernel:[ 141.973520] lvm: sending ioctl 1261 to a partition! >15:39:26,392 INFO kernel:[ 143.132417] Adding 1048572k swap on /dev/mapper/vg_root-lv_swap. Priority:-1 extents:1 across:1048572k >15:39:26,565 INFO kernel:[ 143.306575] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) >15:39:26,565 DEBUG kernel:[ 143.306594] SELinux: initialized (dev dm-1, type ext4), uses xattr >15:39:26,671 DEBUG kernel:[ 143.412930] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >15:51:13,500 INFO kernel:[ 850.241925] authconfig[8785]: segfault at bf99dbbb ip 0075bf54 sp bf99dba7 error 4 in libpython2.7.so.1.0[671000+15e000] >15:51:13,579 INFO kernel:[ 850.320704] authconfig[8787]: segfault at bfea280b ip 002b9f54 sp bfea27f7 error 4 in libpython2.7.so.1.0[1cf000+15e000] >15:51:33,800 DEBUG kernel:[ 870.541914] SELinux: 2048 avtab hash slots, 99143 rules. >15:51:33,823 DEBUG kernel:[ 870.564385] SELinux: 2048 avtab hash slots, 99143 rules. >15:51:33,890 DEBUG kernel:[ 870.631896] SELinux: 9 users, 15 roles, 4126 types, 222 bools, 1 sens, 1024 cats >15:51:33,890 DEBUG kernel:[ 870.631902] SELinux: 83 classes, 99143 rules >15:51:33,901 INFO kernel:[ 870.638642] SELinux: Permission ptrace_child in class process not defined in policy. >15:51:33,905 INFO kernel:[ 870.638790] SELinux: the above unknown classes and permissions will be allowed >15:52:33,364 DEBUG kernel:[ 930.105844] SELinux: 2048 avtab hash slots, 101077 rules. >15:52:33,388 DEBUG kernel:[ 930.129500] SELinux: 2048 avtab hash slots, 101077 rules. >15:52:33,462 DEBUG kernel:[ 930.203896] SELinux: 9 users, 15 roles, 4224 types, 222 bools, 1 sens, 1024 cats >15:52:33,462 DEBUG kernel:[ 930.203902] SELinux: 83 classes, 101077 rules >15:52:33,472 INFO kernel:[ 930.209918] SELinux: Permission ptrace_child in class process not defined in policy. >15:52:33,476 INFO kernel:[ 930.210085] SELinux: the above unknown classes and permissions will be allowed >15:52:38,106 INFO kernel:[ 934.847436] mktemp[9415]: segfault at f982900e ip 00c971d0 sp bfa5c08c error 6 in libc-2.15.so[b8f000+1a8000] >15:53:40,972 INFO kernel:[ 997.713157] makemap[9507] general protection ip:6198b0 sp:bfdb70ac error:0 in libcrypt-2.15.so[619000+8000] >15:53:41,063 INFO kernel:[ 997.804121] makemap[9508] general protection ip:8028b0 sp:bff0afdc error:0 in libcrypt-2.15.so[802000+8000] >15:53:41,121 INFO kernel:[ 997.862104] makemap[9509] general protection ip:4d88b0 sp:bfacbfec error:0 in libcrypt-2.15.so[4d8000+8000] >15:53:41,177 INFO kernel:[ 997.918716] makemap[9510] general protection ip:3628b0 sp:bfcd3dcc error:0 in libcrypt-2.15.so[362000+8000] >15:53:41,223 INFO kernel:[ 997.964629] newaliases[9513]: segfault at 57ae61d3 ip 00c6a2e2 sp bf8b6f5b error 4 in libc-2.15.so[b60000+1a8000] >15:55:38,914 INFO kernel:[ 1115.655076] authconfig[9605]: segfault at bfbe166b ip 00329f54 sp bfbe1657 error 4 in libpython2.7.so.1.0[23f000+15e000] > > >/run/install/ks.cfg: >#platform=x86, AMD64, or Intel EM64T ># System authorization information >auth --useshadow --enablemd5 ># System bootloader configuration >bootloader --location=mbr ># Partition clearing information >clearpart --all --initlabel ># Use text mode install >text ># Firewall configuration >firewall --enabled --port=22:tcp ># Run the Setup Agent on first boot >firstboot --disable ># System keyboard >keyboard us ># System language >lang en_US ># Use network installation >url --url=http://gromit.redhat.com/pub/fedora/linux/releases/17/Fedora/i386/os/ ># If any cobbler repo definitions were referenced in the kickstart profile, include them here. >repo --name=Fedora-17-SRPM --baseurl=http://download.bos.redhat.com/pub/fedora/linux/releases/17/Fedora/source/SRPMS/ >repo --name=Fedora-17-i386-Everything --baseurl=http://download.bos.redhat.com/pub/fedora/linux/releases/17/Everything/i386/os/ >repo --name=Fedora-17-i386-updates --baseurl=http://download.bos.redhat.com/pub/fedora/linux/updates/17/i386/ >repo --name=Fedora-17-i386-debuginfo --baseurl=http://download.bos.redhat.com/pub/fedora/linux/releases/17/Everything/i386/debug/ > ># Network information >network --bootproto=dhcp --device=eth0 --nameserver=10.16.255.2 --onboot=on --dhcpclass=ipa-lab-vms > ># Reboot after installation >reboot > >#Root password >rootpw cobbler ># SELinux configuration ># Error: no snippet data for selinux > ># Do not configure the X Window System unless we are installing the desktop ># profile >skipx > ># System timezone >timezone America/New_York --utc ># Install OS instead of upgrade >install ># Clear the Master Boot Record >zerombr ># Custom partitioning >part biosboot --fstype=biosboot --size=1 >part pv.01 --size=1024 --grow >volgroup vg_root pv.01 >logvol swap --vgname=vg_root --fstype swap --name=lv_swap --size=1024 >logvol / --vgname=vg_root --size=1024 --grow --name=lv_root > > >%pre >set -x -v >exec 1>/tmp/ks-pre.log 2>&1 > ># Once root's homedir is there, copy over the log. >while : ; do > sleep 10 > if [ -d /mnt/sysimage/root ]; then > cp /tmp/ks-pre.log /mnt/sysimage/root/ > logger "Copied %pre section log to system" > break > fi >done & > > >wget "http://10.16.78.1/cblr/svc/op/trig/mode/pre/profile/Fedora-17-i386-freeipa" -O /dev/null > >echo "send vendor-class-identifier \"ipa-lab-vms\";" >> /etc/dhclient-eth0.conf ># BZ #468436 >rm -f /etc/dhcp/dhclient-eth0.conf >echo "send vendor-class-identifier \"ipa-lab-vms\";" >> /etc/dhcp/dhclient-eth0.conf > ># Enable installation monitoring > >%end > >%packages --nobase >@core >yum-utils >sudo >audit >openssh-server >openssh-clients >iptables >mc >vim-enhanced >acpid ># These are needed for NFS home dirs >nfs-utils >portreserve >autofs ># Needed in %post >wget ># Needed for --replace-self for systems >koan ># Remove unnecessary desktop crap >-alsa-lib >-cairo >-fedora-release-notes >-gtk2 >-ghostscript >-ghostscript-fonts >-redhat-lsb >-qt3 > >@Development Tools >-oprofile-gui >-frysk >-ccache >vim-enhanced >emacs >nano >@Fedora Packager >openldap-clients >nss >nss-tools >krb5-server >krb5-pkinit-openssl >cyrus-sasl-gssapi >ntp >httpd >mod_wsgi >mod_auth_kerb >mod_nss >python-ldap >python-krbV >acl >python-pyasn1 >memcached >python-memcached >systemd-units >selinux-policy >selinux-policy >selinux-policy >selinux-policy >slapi-nis >pki-ca >pki-silent >pki-setup >dogtag-pki-common-theme >dogtag-pki-ca-theme >tomcat6 >subscription-manager >python-dns >python-ldap >cyrus-sasl-gssapi >ntp >krb5-workstation >authconfig >pam_krb5 >wget >libcurl >xmlrpc-c >libcurl >xmlrpc-c >libcurl >xmlrpc-c >sssd >certmonger >nss-tools >bind-utils >oddjob-mkhomedir >python-krbV >python-dns >python-krbV >python-ldap >python-kerberos >gnupg >iproute >pyOpenSSL >python-nss >python-lxml >python-netaddr >python-netaddr >libipa_hbac-python >-subscription-manager > >389-ds-base-devel >svrcore-devel >policycoreutils >systemd-units >samba4-devel >nspr-devel >nss-devel >openssl-devel >openldap-devel >krb5-devel >krb5-workstation >libuuid-devel >libcurl-devel >xmlrpc-c-devel >libcurl-devel >xmlrpc-c-devel >libcurl-devel >xmlrpc-c-devel >popt-devel >autoconf >automake >m4 >libtool >gettext >python-devel >python-ldap >python-setuptools >python-krbV >python-nss >python-netaddr >python-netaddr >python-kerberos >python-rhsm >pyOpenSSL >pylint >python-polib >libipa_hbac-python >python-memcached >sssd >python-lxml >python-pyasn1 >python-dns >-subscription-manager > > > > > >%end > >%post >set -x -v >exec 1>/root/ks-post.log 2>&1 > ># Start yum configuration >wget "http://10.16.78.1/cblr/svc/op/yum/profile/Fedora-17-i386-freeipa" --output-document=/etc/yum.repos.d/cobbler-config.repo > ># Add disabled repositories > ># Downloads a disabled updates-testing repository for a fedora release > ># Backup stock yum repositories and use only ours >pushd /etc/yum.repos.d >tar cvfz stock-repos.tar.gz fedora*.repo >rm -f fedora*.repo >popd > ># End yum configuration ># Post install services config >/sbin/chkconfig network on ># make virsh shutdown work >/sbin/chkconfig acpid on ># These are needed for autofs-mounted home directories >/sbin/chkconfig rpcbind on >/sbin/chkconfig netfs on >/sbin/chkconfig autofs on > ># Post install kernel config ># Start post install kernel options update >/sbin/grubby --update-kernel=`/sbin/grubby --default-kernel` --args="dhcpclass=ipa-lab-vms " ># End post install kernel options update > > > ># Post install network config ># Start post_install_network_config generated code ># End post_install_network_config generated code > ># Configure DHCP class >perl -i -pe 's!DHCP_CLASS=.*!DHCP_CLASS=ipa-lab-vms!i' /etc/sysconfig/network-scripts/ifcfg-* > >echo "send vendor-class-identifier \"ipa-lab-vms\";" >> /etc/dhclient-eth0.conf ># Download configuration files ># Start download cobbler managed config files (if applicable) ># End download cobbler managed config files (if applicable) > ># Start koan environment setup >echo "export COBBLER_SERVER=10.16.78.1" > /etc/profile.d/cobbler.sh >echo "setenv COBBLER_SERVER 10.16.78.1" > /etc/profile.d/cobbler.csh ># End koan environment setup > ># Begin cobbler registration ># cobbler registration is disabled in /etc/cobbler/settings ># End cobbler registrationn > ># Add UNIX nonprivileged users and SSH keys from the cobbler server > >useradd -K CREATE_HOME=no jhrozek -u 500 > >useradd -K CREATE_HOME=no pzuna -u 501 > >useradd -K CREATE_HOME=no jderose -u 502 > >useradd -K CREATE_HOME=no rcrit -u 503 > >useradd -K CREATE_HOME=no sgallagh -u 504 > >useradd -K CREATE_HOME=no simo -u 506 > >useradd -K CREATE_HOME=no ssorce -u 508 > >useradd -K CREATE_HOME=no edewata -u 509 > >useradd -K CREATE_HOME=no mnagy -u 510 > >useradd -K CREATE_HOME=no ayoung -u 511 > >useradd -K CREATE_HOME=no jenny -u 512 > >useradd -K CREATE_HOME=no jdennis -u 513 > >useradd -K CREATE_HOME=no nalin -u 514 > >useradd -K CREATE_HOME=no kwright -u 515 > >useradd -K CREATE_HOME=no mharmsen -u 516 > >useradd -K CREATE_HOME=no asn -u 517 > >useradd -K CREATE_HOME=no dpal -u 518 > >useradd -K CREATE_HOME=no sbose -u 519 > >useradd -K CREATE_HOME=no davido -u 520 > >useradd -K CREATE_HOME=no shanks -u 521 > >useradd -K CREATE_HOME=no mgregg -u 522 > >useradd -K CREATE_HOME=no jzeleny -u 523 > >useradd -K CREATE_HOME=no alee -u 524 > >useradd -K CREATE_HOME=no mkosek -u 525 > >useradd -K CREATE_HOME=no jcholast -u 526 > >useradd -K CREATE_HOME=no ohamada -u 527 > >useradd -K CREATE_HOME=no pvoborni -u 528 > >useradd -K CREATE_HOME=no pbrezina -u 529 > >useradd -K CREATE_HOME=no ab -u 530 > >useradd -K CREATE_HOME=no jkuncar -u 531 > >useradd -K CREATE_HOME=no pviktori -u 532 > >useradd -K CREATE_HOME=no pspacek -u 533 > >useradd -K CREATE_HOME=no npmccallum -u 534 > > ># Install public keys for root user >cd /root >mkdir --mode=700 .ssh >cat >> .ssh/authorized_keys << PUBLIC_KEY >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAwHUUF3HPH+DkU6j8k7Q1wHGRJY9NeLqSav3h95mTSCQYPSC7I9RTJ4OORgqCbEzrP/DYrrn4TtQ9dhRJar3ZY+F36SH5yFIXORblAIbFU+/anahBuFS9vHi1MqFPckGmwJ4QCpjQhdYxo1ro0e1RuGSaQNp/w9N6S/fDz4Cj4I99xDzSeQeGHxYv0e60plQ8dUajmnaGmYRJHF9a6Ban7IWySActCja7eQP2zIRXEZMpuhl1E0U4y+gHTFIgD3zQai3QrXm8RUrQURIJ0u6BlGS910OPbHqLpLTFWG08L8sNUcYzC+DY6yoCSO0n/Df3pVRS4C95Krf3FqppMTjdfQ== jakub@hendrix >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA2b8JV0ZqJ8CwwBTqIDDgoo8S1ma9WYiVW5cg/pezYSrpj/h7sXERJa6LLIk/LYQKH3eRD2rW9mMWaIM8JDSvlcWe4dSubwo8SbAUgvVnit4CVRLfR8REbgWfhp4kGcrlOUaaMwrIpFC3XnFMdRNlA6Z/DuSIDNAmR5DFSlYbYcrV6BcqZ8LtJW3QeIyv9KrugbGoxMmnX4dBees317cIZ0HK+YlMBQ1WiuQOfdUYRR7/RJoZP+0g7EnDF2dZZP/jy+nBFkncTL4PB9ukGlCsybW2GHGWSB0vyOjpSmqxObszQ86f1lvr7qzsl+a9MAF3+9XQQqn0L40YEdbj0VDpEQ== pzuna@dhcp-lab-161.englab.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAgEA3F3ysc3r+pwdBcrc+P7SW2lZ8d0bx/LA3a7gqnISPFMBO+UlMq/N9QQkkjZazIK4OX0l9Bi/1pIyJGB+OXKLjJDOhRb8IjIeuBuZtjUEi/yT7j+Ge9HGUUU8/wMfjkLTL29CZQq4j5Jk3iBEc9a0ZqcEMlv+yDwgBcwqQBy/Iig9xKWFOjXSCO22kRLZuaUPwC0khwwx8SfrtHUtQFJzFeXLZoVk0DRpDS71REpy5WqJAbqM3k3yfzYSU5GJlRbnIL3qSc0lESLVbV3zLfYKbtnpd5qfnBVA/kKuHvDRXwWqLknW92Jtmda+zTyJzMv55jrkYfT+Kv9UvKvCHOHFQZv4u/fa2fr8noGfHkquRpAe6GR8lPD4PtvEVOQyFGxS8tD7x6tv3VS8ZQ0dtL3jgT1OaA5wuIDTBg7N61YSkU8BjcgtvdsrDWIXCgtLbLxWXztlRJNR6flyOR3vy3qMbnoPjrd0WgW6KTRB6TzPPEefRmXQBphkd7STHt6qzdn+OJkqNjIHWTbzKv3EWmzGVlW8+Q6ae7F/S7eS1FeSdY4Er44Y9tjbCXTe0STQPbGXyIxwIdgMFu2e1hXjAvhFdGgQfC6OLxuGYW/KRBhNB6EaQYbSJWqIDfRDQYdxMBmI8AcGqpRy/N3oyQ331KyPjLav0qFCDBg/zqMTwBCk3Lc= Jason Gerard DeRose <jderose@jasonderose.org> >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAkVt0yeC+66kmMTyIZ1/oXp6toeiVtgrQ+uXgMR8DV83tD4nJzK9Dsej1I3fTqloG++ptNpmA3CIL8v2rnBkCembFCPT8dl7hB1mENkjw1oXNjVukomqQ/bwP/qAxMwfsLrWQnOpNUUAUYo/qQogVd/9wAPG5obsOufIGK+HN6OQpQdVVGh+UTAEF2QG4BsZj40JyM2vmcFYt4sNViOQoSinXhrKPDApxv842WomAAt5z3/7EjfKOLI2Rkahj8Jc9jeSmYqAJWPRevpjemwzAP0ylqPtrBr+CNp5fPBrhZ9zNj/TFj9vtOHzpHuvYWGJoxHCfcM0475JgmOe/rt+5oQ== rcrit@darlene >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAuITswCzmN81Va0AuG1tNCPzDYdK+q0HWh/D8RqvlS/YNNuscHWwYoAR4/L6Au0cEkhlHSO9Zrzq1I7S8swa8muBt0PpVQJTss6hFllf0Zm+Waxt4xh7qOWNzw34OFm5ngeg2RPu48MEqEg1Ucq8kpsf4SnfXlgj9OIN+7VTzLrMnyEaGZ/Wx52K4k6Hf2kPSGaKfIBmPcAy40F8kMaEZ4Z9mS1cH9HyN0gM9BSLoBHN2ggsaG7EuoZ0LRD8gw779iN0p0lHgG/fXpvI1cetIExiWFo+xpnHSiiQCMOOSB+0j7lABIrobZSvb3W2Fdn1K6gYnrzpCJXCsoJjOs1TgbQ== sgallagh@sgallagh.bos.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA0xh1VtuBlf2iAz94fg4o4FBUKT0Fawk+ducPRcWLFrmkjgvEaJ5W3472kxw1tm4iHhjYZmZcrBXxAWpo4zOBrpyHmL7J50Kaj3nOZGEwNzhAR6hW8JTrH1u+nflnaRNJbUZRstjma6nbYWarRW8JvHAVnLoMAEkZlaGDyK7qGwK0jF4p7hKuHntZWmd/mVpeao/TipXdh+lqezzoFROy1dOkl1o2fSHiPqGQapf7esGVYL6oeU9o1WjH1c98325Y72f9+sJ+hY+FB5N98cDVBMqi/IuVZynIqtSoNFbSFi06PF6l23NcvxijbltaNw+5Q1bQFNieUwY61KbBg5v4pw== ssorce@willson >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA0xh1VtuBlf2iAz94fg4o4FBUKT0Fawk+ducPRcWLFrmkjgvEaJ5W3472kxw1tm4iHhjYZmZcrBXxAWpo4zOBrpyHmL7J50Kaj3nOZGEwNzhAR6hW8JTrH1u+nflnaRNJbUZRstjma6nbYWarRW8JvHAVnLoMAEkZlaGDyK7qGwK0jF4p7hKuHntZWmd/mVpeao/TipXdh+lqezzoFROy1dOkl1o2fSHiPqGQapf7esGVYL6oeU9o1WjH1c98325Y72f9+sJ+hY+FB5N98cDVBMqi/IuVZynIqtSoNFbSFi06PF6l23NcvxijbltaNw+5Q1bQFNieUwY61KbBg5v4pw== ssorce@willson >ssh-dss AAAAB3NzaC1kc3MAAACBAIzWjjSzEUZYTlpze5h7dZ6F9F5OE4ECKVxwxXRyPbslFNMHYkYeLjsl1LzHuj5jJl0XmmS80qMKL73lXd8yj6VC/2OOlS/szDyVVYhLTMK0yeCWWgKMEtVH/haZQy+vY3DvHcZajt2hXnThaHxMl8YVysD0edUj6xdvBlJuwNGXAAAAFQDd50UreNlNit/4BmTumxM55sb7ywAAAIARMWp9JpONejwo1LJuF9jHPyVrptYT4kxb1wmXKSLG96m5c2s2Cum5oJkShyXek650nu1UhVTZLGX2dOyGawUeHDRKRe3wRXrQZlLUIaeURAHHeqIGxTmWHibPpaw57rUrb1A4xqown+hU6XDu8itkha/aV+hQXt2FdFG7jljjHAAAAIAj8jKTX7fSWJ8uUZfAeuBApNDTumvfteNYs0gR+xfwiskd7RyoVLHc0zsBIgBmwj8btwTzpIQkJMygkwDIfb+Rsoir4Oct7eu6RfBGZwWK0bQdjwnfybMVZhj72KrMfYS6oOQ2iNlSDkgBZmprbSKhDy7hPoGKMj2Hf6h6gqZ2gA== Endi Sukma >Dewata@server >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAt8HDNEWgZb5v4uYfauCQPoz+hL1JHzhWnvypEQzcW365emK4vHha9LoBMZdr6uS0xwEL/Uwbodt6za6voM/xF58yfJ5hgf81QThsQL4XL3zI+Lt2+E783d3eN8zMzAvH3k3aRGivdhQHVLeXP5CgDHx55m12T01TaCJl20T6Bj5gV5dSaEqDHoHlS0TzlOn0q6MpMwdvEjine6xUN5YzR1IR0TUGXhqN/nNcoErycSRUQzGibM1ihmpqnlSJmee41SeLZQIxAiR+HbNthcgG+fVxqA7bRx7odTCIsjLmlG16gX/rDWrfUZ8SbTaNVjNc+BX2JyJlob8oclwvuqYsRQ== mnagy@wolverine.englab.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAqKAqbqRDUFPbcu+eQikVWPBNi9GvgCCO1QnjlC7hNbYOuldQar9Kbgb8A+DTqCIilf2x4RVfJkht3vcyxpP+Tkid2xetxo/EPKusPHa8DbzlCaouizi9KYSpN7Zk2NEqOdQvswIpbogktCbsQB1F/MYY8rKrRG9pfW+bbeuQTsrYFog91QdOJXNzbIG82jkUkFBCxv8tM6F6+OwI83VXz8X+oG4MaQhusaFizN8ruWsc7SVnpuLziSk1dZwqNLQ+tPo2CWuj5rNrn/TyDnwY+bqNCkEKCx0v7ZcAL+Z49ITpyTz+DO1NNaUFquVZONuqF2MZr5ZTMdOy1DRtgCx7sQ== ayoung@ayoung.boston.devel.redhat.com >ssh-dss AAAAB3NzaC1kc3MAAACBAP4ndG2co1O7TQfhoavvFs0zi64mOsCv2oetoTzKhVZoB9US631kac9gCsbDTV8jDehIpbNxte6jcvBUpqqc9qgkbsrt9LVjp9upDzrhSCVYKJjqfQ9rHludfM2aa0cq7FNDlEvK0YTkUFd3uDfhwShpSOK+C8rZ9OEdHkvkw6vZAAAAFQDGCPR7dcTdO1yc4qKbiRiuX4JjKwAAAIEAvI8pwaam8mWG4mbsrSfAqv7s3X4dufK9OEqYpl2HwWzbTKe5JA3wj9q5NegHPpPpu3IICDB9lHJGPp4HLB+FzV7WleDmCzMG6EROoFUhXf2QrbsXf2mlhISZqQHr/ZRdSBjbvBuC9/WG1DapIcCC8Zn7Rs4vQ5v95o8E5FMuX0MAAACAWgh0ghNcG8foxJCeN6y33hbUI3Q63kkIlnb16gsW82NSHGJotBCIPN242fvPAebY++6mSFmbi78KHha+meWBDVkzIeD5cXmJss+KWHJK9WSDrwJtL+HJ3DvOhN0SohYs+eo5V90lPmj+vWwHvg36UpmGeqReZCDZk/R2s6Ak/6Y= jgalipea@jgalipea.csb > >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA9vMMbNPyapdcw7WJCcb7rVSBo74Yvp5cDADnGd7ie7JGxMnRvoquBQKy3D9tnGPVEnUP1jIaDr6V+C2Yh5FJHitXmBKBvChYJITungZc6GVYEJf7bXHQ1DJBoB/U6Cx9TdOLTUOn7hRh2AIrAUof5yPjLiIG4u68IU75Y7pe2RCZkVqM+z5R4p2uKeeh+/tFV0a0F+4Mhuk0Bj4o+X6PcY7Pu3qwxnvgTPRmE4KqwLrbl+kRv0t3UOSTuWKfddx+zUM7qoFVowpjFpDByYnBiuWp1OntZKG9LabtM2WT4RyHS5hf+GOgCR34VmZb3p+yOaEm5ROdZfbXQ6jrhUfC1Q== jdennis@localhost.localdomain >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA0d3jaN3FaVG1COQQ9dYGKu9y1jFyrO0F5xsyaEdxTpKDrv8jekhJQBPcJBz2zACSF6VbBD1NNq3um0WpHhuQhpjlnn9u7R0UcZlym+nOWpe8SL4/ZeTRFbYeTLBY/Mm9exignhH0ptLeEVyv2uh7Myvf3GPfvG95cVKW0/KhVp4ZXuINR3smwaL2kkzsmGdsPzr0mYnRhTITf4WxVIqC+5GX71PphIAAZGR0kbdPNqbNKffSHrYo8iLXUSwXKkwX9XWKqaDbSREgna2SXzcocFHnqp8c1qMimmn4GyOGuhWfcaW70QBjMDPBr3cpFTQ2f58syZ6SSmzklStftVTSkw== >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAwOiprdotnOdq4QcBU+I5KXpoLg7dNj0CM4YrLFCXQd9SeMoTma3rlEHE/qZL9hnMbWztjdBc3rMJewLDKR5Ob2jq/68w1NOVvtePcgsNJUncvlxy0uWaexzjSDRBQ1zjDVTINpJ4IKroFOSSpbqmqrDrmZ5sBslfLwHYle6Q6f4660jU/O1m3nw7OihMsE4J2f10OapEgVnqBR03rrWXgSwQev+5gIIRXao4ESpPnztUZ1kXtToJBSsh7Mp4R8msJSwQ/8xitlY5a4QTnGooNVhSXpVZMYslYqlXG9lcCN3APr8BlcVDCW1x9Zny3M7q6QcL2sMJme33QPiFTriLAQ== kwright@kwright.csb >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAz9gM0FLRpWwAWiZWa0IUTJxJcKPVE+mlsVT0MVBGBZ+YQsHdL83AVnbvcOfwKPr3iMFgPw7C9PIlv4CeLFV8Jp88wmM19LzLDVzrBlFY6299JCX3dXyWGywMCXMKR+Fv/oh8+oSl/PPkDU4VeOog38rPLJyYvIamlF/FIcPgoEt7A9JP3cfp+PYCvp+YUIJm/XbEzJ4W0ynJPjSECVsQlDBNbFfvJGHVYCm5vVbIEf71LyOmU2f/lYJid2VLWp76a91ezDLncbnU2WMLXfhtrOs9ZykyLUgdATp4IqqMjZmteI047F9RGqvZU6dINiYGfzISS0CmC1vCSJ6lIlG4rw== mharmsen@pkilinux.sjc.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA5kI3l6jYj64QcJ8NLt089bEExuN0IiV6mv4l/bM/04Hw5SB6U73V3MReo+yIV+hGJ20LYBwSVZJIdwOKaZvUycJ3Y/C0dn2k8FzjV48poXtDknqakYFtfCZtNSVTyIiFsLgv6BK4Jx56+KnjQAxT+iPFYhAsFpMEuhQKy50XhSyppuhLvn7T0XqPyE0WdiCpJTu9vKsdH2LWX3hmWKWNtxn7B6YV55ZbHj7kW2UQxIjcVN7QNS1NqR3x6F4Tkw3SKJjiPI37cpUCPYx1xyFaorENT764rOOOONUukSXXO1U1HSYJM/G5dnNVzLsEXUrV4jSKkGfeie3AAaYjk7n1dw== gladiac@magrathea >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAyUPe7+Zw0m1/QKLvI3NaADaPinDbe9bB9y6oxyA9qIZuscyFj0Rfrn8QsAZWqviRZEqnZQZrK0MtIL5xGq0wNst2Z9nv/Ur1vh+tVo/rLPFS6vXI5GpVWXlIzibmVSJGIFFbOd6D8CXmTQl83xENZ+K5FMBqoI709EagD35Czi+sD8YVWvPKlJJFRbNW/rko4Fgz+E7JIU6T6xCO53LV0jt7Wep5QvImDrqZfXVzwdG8Fo5vEeI7pW/V+6htIyKVn+zfCKC2yQ9VWBcP9RVnwL8MAGiDZk7mvGKeT40ygOkvfI+BEt6XQK2Gwmch/FG83+1pvMi41pg2+tkbawzmhw== dpal@dpal.csb >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAww530n5CZNKsdK9IOlMj34f/SEXZXKm+wG2uJV51ueLZoEUrh1Ov7wAeNB93Y61iXO4Lh8fKbm13plX8ScoxL2R2jStqtGMWbvhAw9fLj1W0D7qJxezJN23wKzUVuLfZC5Al80vzVf+kKA51iaLyYrVE52HKlLQJ36wqWNvPjz2ynRGGA4zbLPQhza6/rx/+mmxKmrA5frhhvEFTWr6XUGBMj1EzKUmbd1LGT1hKLBNfIpgL1shAAgIQ5AHei2vqlc3n//zSSGOxrKmDfsBjVuDRqWeduxPVInZOFOQNwQOxUnGIV10iSIgS822NU0Y9Ya11OLjdyX28i3gjE1U/yQ== sbose@nb.localdomain >ssh-dss AAAAB3NzaC1kc3MAAACBAJsT5Yx22ZHHTJXmJi7h/seL0cvjFBgogjpHuxLXUAK+Y6qXZx5VJrATlGMVHVVv3+qrGwaMERH1/GcSQFHg65Du22dQ4MX40zs6udkflr7/cUCD8gE4n9G0cHIqYtms3nLcxqyUWkmD8G9I6gZdXZRGiAFzfsYeB4VYs2SGpZwpAAAAFQD7OY00k3u2qRcU4+b3gLtxna7OgQAAAIAtR+VfXjYoVwhSb01AdpfZiSOUhhlP8YrBSKkywtvIxeW5B/6hyeFFyrVxGOErP6rr2WFtryXU5eppXhkdKgSh8odW4UGUDDfZWnm32S9rB8AtZrcjYGmmKuMoJVDA980wjxHye10CqEueEWPcZVWgufLqOONJpXGsMCNj5HbjbAAAAIAbusSJq4eEHcu1QUTSkXIy5XofqQG2rvp9PVOGDKYMYB6x+lYhXIvK/dztfL5ii/HsQ8LcvDeCZkJ+Tx3s2J3aPMk39THtVF8i5qO47wP9D7BuiT9Y7mB8pYtXYuzl66QORbkz/PbDLsz/mOnXjJlnjSJhyXJ+Pb2h7QsH/kmEGg== daobrien@daobrien.csb >ssh-dss AAAAB3NzaC1kc3MAAACBAKgiXekCmdmi80t0Aph9psuwDEgsdvNJt8LrFuM/VPMs8B9AWWsTc5dYRMrXt91zwaIgjpHziFxw2ydjwnNyrpBhyiZRizWZ4Na9bZ+ii5lrdw+Pf/t0NmRxcMYzuGY0J/prB2MUFUtS5EOadbP4CHntoBf+3S+p8FD1RH7o7H+zAAAAFQDRj1EfRHAJu+Af9i+JkcphenhGPwAAAIEApkJtMEX5/lAlPx4sIWqDwGHk1dSVD4PPuQ/enMz+KJXRde/iEAsRFZ1Hhz/z0yx5s5bklS+iffqHOHNaXBuntOhY2aKY3NxN26LuLioCiwy8NbA+YTrHJBp+tyY8k/Ur2OIkecOhAG4RjmKNFneXnGNqlyqa8IaZBnALuj6xtGgAAACAUZaIc/h47/836tYRNTO8gSOrhmYbfNZmxBN3lTEhB1Dzck2E2HxN4++T5Zgrt5fJo40lCYMVgFsxxEWecVqXzQMwHWI+w8at56Kxx7piGYWHlwKE8eJERLRlpa6Zp3XlZwUxEJPupe5bZAO9A/PtnQgkNLhupBfasqKREskqoYI= gsr@gsrlappy.pnq.redhat.com >ssh-dss AAAAB3NzaC1kc3MAAACBAPjZ0IIRF8+z6eiid3Qc/0rzpSfyBGTeEsKb+r4zI3faG5cVWaPALh7naV4Khn1moyxg/pBoufttrXUvddRht6aVzzUj4sJOtQH407AfXAYz9CgiIIU2gMHF/u96rxCeUhr/mJR7r7vxI8MJ4AQDAgMykqhtWD+k6FLKNc70zGVzAAAAFQDPDII70kOruWTxNNOtP384oDK6pwAAAIArJGpqWYVq64B41d1+EAmQDHIcIonSAcY9qyG7DgZjZj9syNvx+Jlkkij2z68WGcPD6skBz/cedwDAceAVXv8ADUI24ozWErSMojj2vvNpHE11MY1xBQlK5fs9W8QBv3WkV4c15VOEtva2Wu1y2HHMsx270vMejVemCB9nD7inuwAAAIBvrHh178lrLQahL4AdU1ZKD60jjLe+F08u5DOzRCUopqF5ortdy/k4OJkR6ZAzDGRR970mB3KdtazuUQ57IPYW3bW+V5QDURGlsTetneuCxy2+qNSZCQkZS2btMOoJgSNa2PS2BmGWJUf2KWJAsv8HAl1DXMfcRTF1F0uM6/WDcA== root@apoc.dsdev.sjc.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQC/bdEAe2aqYjmo8JX0Di7+coNlXX6iT41FIYQ6TMqPHJVe4xlz8gsURDjY6apOaQaWb8LCciGMNWRsnUbx5nvBAUPeM+GFJx92H6VbigGJeiG2ty3YAW/ZxSAagSRsGWsGvP2imGZzE4tpF6yJhcmuJap36MBlB/n1+nTOy29xHywpJgpjZeV7/01MZ96JHyu1kzqQREa75Fu3IkHIu+zqHOqUTl3qD+dYb5LkTpc4nvHDSmWIIEDUyvNz2/dlegQMFL/abtWWMRxzv9sc/OCgVl1A/o2u2uG1gcTSxS0CudbH8NTrMYB6kbsTzezgaIMVFowUO6uWrgdE3qnLEYxA4/Yq6fu32d+Z6TLJzbcYzXETuOtTzoZK3Ql23udzVy9A5K1LQrB1VQHCubLSCT40ZM7BuRSUSkTwbXDw8f4dIo9IRibG99bgdubR9T0UrUSBL9pu/YrgIZ7kX3Ijejmd9tFle38Yv6/VjOsxgbrrdc6y4dJZonD1fTx1Tz0r/h9aBnpVs9VodLqG2G9h/tS2OzPtQLclta2wGy6fY8t2q1JQr86HcjqNptBlz3Q4Qk+anKFpuVtecajWhFb0rJdpfynJPDjqmhijuYzAKbLzX9x7dup5G1DQzPaivtX0H0MEDKHSnwo3P7nZ48I3bGu37QIK4IS3sCXgQRkvXmGnSQ== jz@janzeleny.cz >ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEApxOtFC2hIOR0y3fFD/iPyf7ZPW4zlSXYszhntdXjH2MwkCzvYp+BoO1DUbN7KQhQWxll6neFxbaf8JBWWzM2XSmV4Q+il+SeJrBlog4wYGx+6YsAywB0a3bFYYMU3aKnTw2yF0BV8dyCAbp7lS1B1dontF677CVdswpo7sQmaPhZyZSliD3wE+1gCC8HxByT3hLhFwg37OqbV26bvTDEob9vKFCZsiKqqp+0mJ7lwjzbNo/uGpDQ4zLFAuRugwAk+rXwBuAwrGgro61uNRGuOj/1uiZX8BfdaEe4Nv18I+DQ2umFKe4mJDeZW2aeI9P3x24xwSZOTyn+PXwcCs3oBQ== alee@aleeredhat.laptop >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDEdoVZRw1xYzMN224uGTIl/chDoolLC3fGHOPIUP5PNeefdy+ldBHAln0U9eM3BcYJs8A8z+f/0WKunXal5MfCXIj6agG4W0bUXELCZ3Cd0bRqY8kH9fSEwOvbKtEy8zIoBrqg+6ZciCEbWAsJyl7EDhL8pl4gwZr+mIMR0Z+omwXI9idb5OZU/NQDz0ae8klbmNUky1YJDlWcw7IMq3EKtxMfcgu9AXBs+l0b6c+XR1cZgEgP1ASykHAMquf2D+4qqRkN4IlQ8FDMo32gyFOfjKBaRvMZ9wQZC3j0OItQtlYYzr8veeHaegE59gnQ1balJMijWS51zT3jrGmzVO7j8XwFqZK5qsoqchQd4YAny+rh5ZzyjPZIJlLYOUDmz6RPtqFxxzqoacP0j9oj0sTG+u3qHygrpfwKm/7TVveco64iA534O9H1N1bi5ZcPbzzeo8W0biM/ejIXEBsrizn9C72mC9Y/j0GTbWEJ33tVp+YGRXH8EEkPNadFp+8IMpexgXrnwqWsX+vl+x1J1ZlrBJ6Y9pHuEFeaKoohFU0TkWUzbKcds5htci/vqGa9ZdyvAeFIWMZpIc8TTiyGCBaEunWq/JkeO423mCXQfZG/SiourHjhn+syMm0kKgrxlPqhhl8dZfyGG4hyDAUXM3p6+bRfPafUJIQ7gfM9orzmeQ== mkosek@dhcp-25-52.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDf/esIhu05ms/k32sEpu3/OuNmD9jhD/AsXaVdrMyYdWTMi66hBuRFHv6N1s02PwcfJ2/bdryNOzkBg9l4uOHCPmj1G7SZ3apW6A33g3+odTkk8uV+mwv1GiWWpk4Cl+FWkRpDKvlHtBlQpSuefehpUadDky4Ak4odi+v7fWVANDoSEO3exxFDtX18T6p0phDeuYK41C8jLXgGpe6bfTL0kVn0RrvredZcR3KtYFQ5BZhray/VJ/pUpeuX4UqaC2NljJjfRTjps57EMiMVS+eVGFHvTe4ikMz7ZC0T728/QODZbPLrccnuCYEHomGtSiV8rVDMj6FOzIZFEuVmi8Qf jcholast@urfe.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDFEfo7Efl3/i4HHjdkR+AavYuMlhrpd0pZE7OjGQgnvC/abe4Xzd8CFDsWH5M/b51Llbyv7xaRiFVrRfJ6QEikwfIkCUadKQVxHpOt/LgR1pALeIT/X9oZy8gXvsrKErsv+3eD2eqVCs2Dti3LKct1W+64Rk5rnyOeaq1h6kMNUKDoFCMZZt0yjg6JIyCqTkFqfUKXwWFAAXzxDjj9+mcEefrOVZIRef208Ce7FMcSkmT/YtPkBJL2TEVGcuRdxJzJkn/jwhnJ8/f9p+ODmfcCJWgMGciuM5L8FeZmZeqv1VoZ7DlOdbjAT3FbyZ96//1MwK6hydxyCyNWeHaKlwG/ jcholast@pylon.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDjkifeW/vlS0EswvSMMGIMJ6nr72hhId6DN1LOQuhbPIQsbtO/xWOReuIuY5WlkDCdT2abkn8Rla05MXcKe8uE3soTq6yGJz9JqSfpw1aGvSqoAP8kFqZSPLS0lhqaIgUI2zhUKgevuypKNptsm3MBFO+dAX3i6RB6JdHY7KgE1nq23CK2evslnITmB+OJQlpYhcVfNLZ10d/EZ0nm0PpX3bNVYk5hJTKSpFheKIYJhae/UxBvkIs2adYrFy7F1CE79V+gLyKr5tqYY5ilHIUPb4gORzGb1QidZL4TyiMCVkbUDykjPG/dGduvfKv1T+uOkvQyVOjrbUpwzw4CgyQN ohamada@dhcp-25-196.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC0qSU0p8Sfx4DGljiiq6BxKy3sVjVh9OzDKijrW728oQ9bQW/aknWUKO1TsgNceD1ZC/rSMdPoLVhNiLSqrFnB3F4U9JnBaSPjIF/S+xe/WV0yNBCgquqce4sZqo5nywxeF1DX+oSk3sdRH99jgGNIGG4sf9uQf1tvjLLbKpNYlmDE2+cn8OEjjEAFjgUJh4U/juqvaDmSAevZ3qGI55Yn2PCd5eTh6RVCi7O38NeCvl/ej4lORv+LlsPVsWJJ7x2Xo/KOYcGZs3UVdIgxzLYCNPP+Ege3YOGKZcVeupRaqDwJWdYkTHSCCVvda2rIuHWNHOFHumSm/nf44LW5/F5v pvoborni@dhcp-25-197.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC2I7D8k9pKO89FwLf4LS1yyVk4PsY0DzVesRnxS8Kk91p2MPkHD4SYHffT+AP22hZrDbxj7F8afRYACLoJL9Ilsp6//z6dU7FjNMucNFi1XnrXX8CDriJq6hKTjktX/39luqx0XImocDfKnh56gWj7sGlR0N1ayLIX8iKflDij5igSAm6NJ+jsO6DO6wTsCCAXolUfsf0kpU1FejnnnxD0xkuWN24c6HfT1ITTG9Fb1wf/d2Oc4lMg9fKRXcO+3fjX449IzgOxt8hcEXCSiGDNY1bjC3KQD8oFCBP1kn/t2f065zyhxP8lHztYbt5GHX3qZWYxObP805dLK9GXogxp pavka@dhcp-0-248.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDG/JJzB9XNKTqRVDwGT8vi2FMQ/y2gTJKRdZ8GJKVGPOjQg7gWcy3kCKZsve0uA5Qu8JfnBQcE5v54XTk02C9ryDu+BGb8qYz1dI5a8bPltsM/UeNfxylxl73xKWUgtUbvTNDUIUi+/l/VYO3ElI9dyCNq8tpKXJ42W97/eTyW4gb49eSKchQ/xbFNKXfohk42jlUJ63w0UWBKXFWbpP2NFzQlx2SAVkoD4urq3anaV8icGV/BI6JNfgP5ddczeQuCkRrq9xA9xv+tKWTrQi5f1pg44fgQAAYOOGHEt0rKe0Ithwb0y8oHTt4UGrS39ac4M3PSWImahtStGeBDhLr3 abokovoy@redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDGt9ABj7zQET6Xqlb8UHQzgJ/tb1OqSQnj86UIop0/DdYlgdjyXM3CdcFYBPfY0hkPz0rumoXDn4xL5hNH3yIPtOMd8ZcGFK8c0eKGyDpFQMfkFILxDchBb4cr3E3qABxOfD4Kgq4j/Io1MpYHghYCELNOJWHpAZTTJQCPLK1Sijg08AB4CnRMWMIM/T8fAkjeefPiG9y9Z6yJQdmkou1Qb2wlL5qPMf7G0FO4yX8ds1lM0QmyXBWUVQYF0oAu3XxxaF2k0EEWmfVcS2b4v3HYnYffHMN+c5mMz80oS26HuzZR5ARbefUM18jabU2N79m6y4jrHDeBii1r66Z2nPvX jkuncar@dhcp-30-189.brq.redhat.comssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDEeOXQ3cYBT/5S+EbzNDVRnuGvrNw3KIaepu4NpBDztBG0zi6ZRs5APlkE2jY9o6CB9enwblPT602w/0NHdp6j/QrhPqf9vFzfeBwLtKHoiAHtOobMmHJTlzFlbLr0sLKCfHVEpIocejqfPJXtlQ8d2DZc5McG8tumsAt4ttaxXX0PG4TuGSm/E5EBKBUNnWOCveuzevQpTT85HYjJz86jzgotHn87c8DVywJ7rPTJXgSulcfTueDaLEgC6Kd5FL21KYV0SC+Y2WtpBkNeJzLPfAT+nXRAElTzMlhkTTT7xLOWnluwDDctNDWY9y6zdz2PNwF5Cc/MaQ4IGcJ2KiUp pviktori@dhcp-31-13.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDB0zJDbFsqrNaeW2FZYVA6+sbL9HXv4UcCXQiGOPnhRrZWzdlUU6iUwcRyrVrn6ebmzOhFxnN6MlKICvPod6iIAMQDzQSSvaRF5e7vez8uu1yX4Ps3aA2DWmPrIhoii57JEoJs1y07UvMdPws8LtFe9l8dHxvqNtfTafjwEDjEUlsEwQc/1BM8+oKhcyzbDIMqevAmp6a7VpzxzbOETkX2Zguy8cZaYrip5njHDOqDTp9oGwgF+4GzIkIZzWTGnD+gvnGVuQFZcaWbNgoJ1Nn2FTkioVDt06Z+OlnhI2aJeSm5LP9aGo6FmsMeeUeYAjrKnyKeAbad/VxtaYKYHj71 pspacek@dhcp-31-12.brq.redhat.com >ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDCWK1LN1G5zgqpsJ49oKfEiUM1lVIIbE6qlPHcIdr1YoFmqhsQWfOSmku91XWjUGmgHw1/C5Kzo3MF3tSIdm8XVMW7u/vgvJjrIVPZVTKsgqPC4MS8hsMTDhuELIsR1Wk+ksdUUTl+OLiwQzKVZxqjZfcyuoOxFEbfSlerdNtv89HTEPUbKD9ehgMM/2quaJviuV7vysZWE2f/puBp8h8Z6ZzLTheuxrOg5JePJTmwl6hnMKmk7vXGDPHeuQzHom/NmpfM+rq4741ZD3j8tUNngsgKyBJXdTbamxu4+b+V31AO/+3jCevPnlsXdzx+MwTo6qWxKczDS8y8hmI4i49Z nmccallu@localhost.localdomain > >PUBLIC_KEY >chmod 600 .ssh/authorized_keys > > >cat >> /etc/sudoers << SUDOERS_END >User_Alias LABUSERS = jhrozek, pzuna, jderose, rcrit, sgallagh, simo, ssorce, edewata, mnagy, ayoung, jenny, jdennis, nalin, kwright, mharmsen, asn, dpal, sbose, davido, shanks, mgregg, jzeleny, alee, mkosek, jcholast, ohamada, pvoborni, pbrezina, ab, jkuncar, pviktori, pspacek, npmccallum >LABUSERS ALL = NOPASSWD: ALL >SUDOERS_END > > ># Various authenticaion config changes ># Fix SELinux context on the newly created authorized_keys file >restorecon /root/.ssh/authorized_keys ># Disable root logging in with password >echo "PermitRootLogin without-password" >> /etc/ssh/sshd_config > ># Set default runlevel > ># Add all our users to the sudoers file ># Enable NFS home directories from cobbler server on this machine >setsebool -P use_nfs_home_dirs 1 >cat >> /etc/auto.master <<EOF ># NFS exported home directories >/home /etc/auto.home >EOF >cat >> /etc/auto.home <<EOF >* -rw,intr gordo.idm.lab.bos.redhat.com:/home/& >EOF >service autofs start >chkconfig autofs on > ># Enable post-install boot notification > ># Show system information in /etc/issue and /etc/motd >cat >> /etc/rc.local <<EOF >echo "=== Cobbler installed machine ===" > /etc/issue >echo "" >> /etc/issue >cat /etc/redhat-release >> /etc/issue >echo "Kernel \r on an \m" >> /etc/issue >echo "" >> /etc/issue >echo "Cobbler distro: Fedora-17-i386" >> /etc/issue >echo "Installed from: 10.16.78.1" >> /etc/issue >echo "" >> /etc/issue >EOF > >wget http://10.16.78.1/cobbler/localmirror/issue.sh -O /root/rc.local >cat /root/rc.local >> /etc/rc.local > ># Unset networking info >cp /etc/sysconfig/network /etc/sysconfig/network.bak >grep -v ^HOSTNAME /etc/sysconfig/network.bak > /etc/sysconfig/network >rm -f /etc/sysconfig/network > ># Start final steps ># Run per-system scripts > > > >wget "http://10.16.78.1/cblr/svc/op/ks/profile/Fedora-17-i386-freeipa" -O /root/cobbler.ks >wget "http://10.16.78.1/cblr/svc/op/trig/mode/post/profile/Fedora-17-i386-freeipa" -O /dev/null ># End final steps >%end
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 826634
: 587772