Attachment 873812 Details for Bug 1075041 – libvirtd.log

libvirtd.log

libvirtd.log (text/x-log), 20.36 KB, created by shilpa on 2014-03-13 06:47:21 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: shilpa

Created: 2014-03-13 06:47:21 UTC

Size: 20.36 KB

patch

obsolete

>2014-02-04 17:23:37.513+0000: 22641: info : libvirt version: 0.10.2, package: 29.el6_5.3 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-01-21-16:23:12, x86-022.build.eng.bos.redhat.com)
>2014-02-04 17:23:37.513+0000: 22641: error : qemuDomainSnapshotPrepare:11390 : unsupported configuration: reuse is not supported with this QEMU binary
>2014-02-04 17:23:37.655+0000: 22644: error : qemuDomainSnapshotPrepare:11390 : unsupported configuration: reuse is not supported with this QEMU binary
>2014-02-10 07:06:39.325+0000: 8455: info : libvirt version: 0.10.2, package: 29.el6_5.3 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-01-21-16:23:12, x86-022.build.eng.bos.redhat.com)
>2014-02-10 07:06:39.325+0000: 8455: error : virSecurityDACRestoreSecurityFileLabel:344 : cannot resolve symlink /var/lib/nova/mnt/4e01e5b7288b310654b33912ecc4773d/volume-ec2ac86d-8b26-4ada-ab22-d9a888f0e695: Transport endpoint is not connected
>2014-02-10 07:07:34.552+0000: 8452: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-10 07:07:36.558+0000: 8452: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-10 08:31:09.350+0000: 31054: info : libvirt version: 0.10.2, package: 29.el6_5.3 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-01-21-16:23:12, x86-022.build.eng.bos.redhat.com)
>2014-02-10 08:31:09.350+0000: 31054: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-10 08:59:50.433+0000: 30299: info : libvirt version: 0.10.2, package: 29.el6_5.3 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-01-21-16:23:12, x86-022.build.eng.bos.redhat.com)
>2014-02-10 08:59:50.433+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-10 09:14:25.408+0000: 30299: error : qemuMonitorIO:614 : internal error End of file from monitor
>2014-02-10 09:41:06.291+0000: 30302: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --destination 192.168.122.0/24 --out-interface virbr0 --match state --state ESTABLISHED,RELATED --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-02-10 09:41:06.294+0000: 30302: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --source 192.168.122.0/24 --in-interface virbr0 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-02-10 09:41:06.296+0000: 30302: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --in-interface virbr0 --out-interface virbr0 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-02-10 09:41:06.298+0000: 30302: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --out-interface virbr0 --jump REJECT) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-02-10 09:41:06.300+0000: 30302: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete FORWARD --in-interface virbr0 --jump REJECT) unexpected exit status 1: iptables: No chain/target/match by that name.
>
>2014-02-10 09:41:06.302+0000: 30302: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 53 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-02-10 09:41:06.304+0000: 30302: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 53 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-02-10 09:41:06.309+0000: 30302: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 67 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-02-10 09:41:06.311+0000: 30302: error : virCommandWait:2319 : internal error Child process (/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT) unexpected exit status 1: iptables: Bad rule (does a matching rule exist in that chain?).
>
>2014-02-10 10:04:27.406+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-10 10:14:38.536+0000: 30299: error : qemuMonitorIO:614 : internal error End of file from monitor
>2014-02-10 10:49:49.117+0000: 30299: error : qemuMonitorIO:614 : internal error End of file from monitor
>2014-02-10 10:55:07.730+0000: 30299: error : qemuMonitorIO:614 : internal error End of file from monitor
>2014-02-11 07:24:15.172+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-11 07:24:15.173+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-12 06:57:40.772+0000: 30299: error : qemuMonitorIO:614 : internal error End of file from monitor
>2014-02-12 10:27:30.886+0000: 30303: error : qemuProcessReadLogOutput:1526 : internal error Process exited while reading console log output: char device redirected to /dev/pts/0
>qemu-kvm: -drive file=/var/lib/nova/mnt/b5e61da7fdba3f3bd0bafd1215216639/volume-7821d8df-bd77-45c0-b35f-e29573ec0b80,if=none,id=drive-virtio-disk0,format=raw,serial=7821d8df-bd77-45c0-b35f-e29573ec0b80,cache=none: could not open disk image /var/lib/nova/mnt/b5e61da7fdba3f3bd0bafd1215216639/volume-7821d8df-bd77-45c0-b35f-e29573ec0b80: Permission denied
>
>2014-02-12 10:47:17.970+0000: 30300: error : qemuMonitorOpenUnix:293 : failed to connect to monitor socket: No such process
>2014-02-12 10:47:17.970+0000: 30300: error : qemuProcessWaitForMonitor:1806 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/0
>qemu-kvm: -drive file=/var/lib/nova/mnt/b5e61da7fdba3f3bd0bafd1215216639/volume-7821d8df-bd77-45c0-b35f-e29573ec0b80,if=none,id=drive-virtio-disk0,format=raw,serial=7821d8df-bd77-45c0-b35f-e29573ec0b80,cache=none: could not open disk image /var/lib/nova/mnt/b5e61da7fdba3f3bd0bafd1215216639/volume-7821d8df-bd77-45c0-b35f-e29573ec0b80: Permission denied
>
>2014-02-13 05:39:21.916+0000: 30299: error : qemuMonitorIO:614 : internal error End of file from monitor
>2014-02-13 07:14:23.316+0000: 30302: error : virSecurityDACRestoreSecurityFileLabel:344 : cannot resolve symlink /var/lib/nova/mnt/b5e61da7fdba3f3bd0bafd1215216639/volume-6299fd6a-ff07-47c7-9e3d-c03def66a327: No such file or directory
>2014-02-13 07:14:24.211+0000: 30304: error : virFileOpenAs:1093 : failed to open file '/var/lib/nova/mnt/b5e61da7fdba3f3bd0bafd1215216639/volume-6299fd6a-ff07-47c7-9e3d-c03def66a327': No such file or directory
>2014-02-13 07:14:24.211+0000: 30304: error : virStorageFileGetMetadataRecurse:939 : cannot open file '/var/lib/nova/mnt/b5e61da7fdba3f3bd0bafd1215216639/volume-6299fd6a-ff07-47c7-9e3d-c03def66a327': No such file or directory
>2014-02-13 07:17:30.050+0000: 30304: error : virFileOpenAs:1093 : failed to open file '/var/lib/nova/mnt/b5e61da7fdba3f3bd0bafd1215216639/volume-6299fd6a-ff07-47c7-9e3d-c03def66a327': No such file or directory
>2014-02-13 07:17:30.050+0000: 30304: error : virStorageFileGetMetadataRecurse:939 : cannot open file '/var/lib/nova/mnt/b5e61da7fdba3f3bd0bafd1215216639/volume-6299fd6a-ff07-47c7-9e3d-c03def66a327': No such file or directory
>2014-02-13 08:26:02.217+0000: 30299: error : qemuMonitorIO:614 : internal error End of file from monitor
>2014-02-13 08:26:26.401+0000: 30299: error : qemuMonitorIO:614 : internal error End of file from monitor
>2014-02-13 08:27:18.581+0000: 30299: error : qemuMonitorIO:614 : internal error End of file from monitor
>2014-02-18 07:27:03.784+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-18 07:27:03.785+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-20 16:01:22.776+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-20 16:01:22.777+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-20 16:02:14.145+0000: 30303: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-02-20 16:03:30.740+0000: 30301: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-02-20 16:04:34.755+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-20 16:06:01.585+0000: 30301: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk3' could not be initialized
>2014-02-20 16:13:16.039+0000: 30301: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-02-20 16:17:53.584+0000: 30304: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-02-20 16:24:38.633+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-20 16:24:54.113+0000: 30300: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-02-20 16:28:55.241+0000: 30299: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-02-20 16:29:07.211+0000: 30304: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-02-20 16:29:25.169+0000: 30304: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-02-20 17:22:29.252+0000: 30300: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-02-20 17:34:09.902+0000: 12533: info : libvirt version: 0.10.2, package: 29.el6_5.3 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-01-21-16:23:12, x86-022.build.eng.bos.redhat.com)
>2014-02-20 17:34:09.902+0000: 12533: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-02-20 17:44:17.215+0000: 12532: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-02-25 10:34:26.678+0000: 12530: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 06:39:26.625+0000: 12530: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 06:39:29.038+0000: 12530: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 07:19:34.776+0000: 30426: info : libvirt version: 0.10.2, package: 29.el6_5.4 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-02-12-06:16:25, x86-026.build.eng.bos.redhat.com)
>2014-03-03 07:19:34.776+0000: 30426: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 07:22:12.375+0000: 30426: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 09:33:38.754+0000: 30426: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 09:36:00.128+0000: 30429: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-03 09:37:47.087+0000: 30426: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 09:38:18.770+0000: 30429: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-03 09:38:46.621+0000: 22381: info : libvirt version: 0.10.2, package: 29.el6_5.4 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-02-12-06:16:25, x86-026.build.eng.bos.redhat.com)
>2014-03-03 09:38:46.621+0000: 22381: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-03 09:42:11.029+0000: 22383: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-03 09:47:25.244+0000: 22381: warning : virSecuritySELinuxRestoreSecurityFileLabel:939 : cannot lookup default selinux label for /mnt/gluster/instance/833dac4d-713f-4cd6-a00a-32b0ea68f64d/console.log
>2014-03-03 09:51:09.931+0000: 22380: warning : virSecuritySELinuxRestoreSecurityFileLabel:939 : cannot lookup default selinux label for /mnt/gluster/instance/2507422c-abc6-47ef-93cd-870be374fc4e/console.log
>2014-03-03 09:51:16.323+0000: 22380: warning : virSecuritySELinuxRestoreSecurityFileLabel:939 : cannot lookup default selinux label for /mnt/gluster/instance/d9314d85-45be-459d-be72-b59a9e2440bf/console.log
>2014-03-03 09:51:56.098+0000: 22382: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-03 09:52:43.395+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 09:52:43.396+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 09:53:24.459+0000: 22380: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-03 10:08:21.170+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 10:08:41.754+0000: 22379: warning : virSecuritySELinuxRestoreSecurityFileLabel:939 : cannot lookup default selinux label for /mnt/gluster/instance/34b158fa-d7bf-4513-951b-3a86141cd6ed/console.log
>2014-03-03 10:08:44.135+0000: 22379: warning : virSecuritySELinuxRestoreSecurityFileLabel:939 : cannot lookup default selinux label for /mnt/gluster/instance/174a3f07-8646-4df1-b0ee-971ec544b35b/console.log
>2014-03-03 10:09:24.920+0000: 22379: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-03 10:13:47.078+0000: 22381: warning : virSecuritySELinuxRestoreSecurityFileLabel:939 : cannot lookup default selinux label for /mnt/gluster/instance/a0435235-2516-464f-b8de-2a3b0fa24fce/console.log
>2014-03-03 10:14:36.338+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 10:14:36.339+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-03 10:16:04.902+0000: 22383: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-03 10:16:38.769+0000: 22381: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-03 10:16:42.333+0000: 22379: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-03-04 06:31:12.843+0000: 22381: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-04 06:33:24.861+0000: 22383: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-04 06:41:15.640+0000: 22379: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-04 06:56:31.585+0000: 22381: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-04 10:47:43.025+0000: 22382: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk3' could not be initialized
>2014-03-04 11:52:26.681+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-04 11:52:34.899+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-04 12:03:45.162+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-04 12:07:45.349+0000: 22383: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-06 07:14:17.704+0000: 22378: error : qemuMonitorIORead:514 : Unable to read from monitor: Connection reset by peer
>2014-03-10 09:57:24.876+0000: 22382: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-03-10 09:58:46.094+0000: 22379: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk3' could not be initialized
>2014-03-10 10:00:13.339+0000: 22383: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk3' could not be initialized
>2014-03-10 10:03:59.560+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-10 10:03:59.561+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-10 11:18:52.672+0000: 22378: error : virNetSocketReadWire:1194 : End of file while reading data: Input/output error
>2014-03-10 11:52:21.238+0000: 22379: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-03-11 10:06:45.818+0000: 22381: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-03-11 10:09:10.098+0000: 22380: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized
>2014-03-11 10:09:29.809+0000: 22383: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk2' could not be initialized
>2014-03-11 10:10:02.443+0000: 22382: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk3' could not be initialized
>2014-03-11 10:10:29.891+0000: 22380: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk3' could not be initialized
>2014-03-11 10:10:43.266+0000: 22383: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk4' could not be initialized
>2014-03-11 10:11:02.080+0000: 22382: error : qemuMonitorJSONCheckError:357 : internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk4' could not be initialized

Actions: View

Attachments on bug 1075041: 873812 | 873814 | 874280