| Summary: | journal: End of file while reading data: Input/outputerror | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Huaisheng <yehs1> | ||||||
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fangge Jin <fjin> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 7.3 | CC: | berrange, dyuan, fchen16, fjin, jkachuck, jsuchane, rbalakri, systemd-maint-list, xuzhang, yehs1 | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-12-02 13:35:00 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1369100 | ||||||||
| Attachments: |
|
||||||||
Hello Lenovo, Please attach a sosreport directly after seeing this issue. Please also confirm if you have been able to recreate this issue on another physical system. Thank You Joe Kachuck Created attachment 1221439 [details]
sosreport
Current we only found this issue happened with Haswell Denlow platform, here is cpuinfo, if any others needs to be uploaded for this case, please let me know it. Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Xeon(R) CPU E3-1270 v3 @ 3.50GHz Stepping: 3 CPU MHz: 3759.082 BogoMIPS: 6983.78 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-7 Hello, It appears this may be a known error: End of file while reading data: nc: using stream socket: Input/output error If you specified 'ssh' transport, the daemon is probably not running on the server. If you start ssh service on your server. Does this error go away? Thank You Joe Kachuck (In reply to Joseph Kachuck from comment #4) > Hello, > It appears this may be a known error: > End of file while reading data: nc: using stream socket: Input/output error > > If you specified 'ssh' transport, the daemon is probably not running on the > server. > If you start ssh service on your server. Does this error go away? > > Thank You > Joe Kachuck Hi Joe, Thanks for your quick response. I am not sure what the meaning of "start ssh service on your server". In general we often use ssh client to connect the test server, do you mean I should open a terminal on the test server locally and have a look the error message is gone or not? Hello, I believe this is a libvert issue. Please confirm if the host and guest are running sshd service. This may remove this issue. If not engineering will need to respond. Thank You Joe Kachuck These message are not on their own an example of any serious problem. In fact you'd pretty much expect to see these messages in many normal circumstances. So if anything, libvirt probably just wants to figure out a way of downgrading them to a lower severity level log message, though that it rather difficult due to the way libvirt feeds its errors in to the logging system. Anyway to anyone seeing these, you can safely ignore them, unless you have other known functional problems with libvirt occurring at the same time. Actually we haven't turned on any virtualization stuff on purpose. But it is okay for us since this defect isn't caused by Lenovo's product design. If we could find any problems about libvirt in the future, we will report that to your side. For this issue, you could close it right now. And really thanks for your quick response. The reproduce steps are:
0. Install libvirt-2.0.0-10.el7.x86_64
1. Start a guest
# virsh start avocado-vt-vm1
2. Check /var/log/messages
...
Nov 18 13:57:26 localhost systemd: Starting Virtual Machine qemu-2-avocado-vt-vm1.
Nov 18 13:57:26 localhost kvm: 1 guest now active
Nov 18 13:57:26 localhost journal: End of file while reading data: Input/output error
...
3. The log messages come from virtlogd apparently:
# systemctl status virtlogd
● virtlogd.service - Virtual machine log manager
Loaded: loaded (/usr/lib/systemd/system/virtlogd.service; indirect; vendor preset: disabled)
Active: active (running) since Fri 2016-11-18 14:03:10 CST; 14s ago
Docs: man:virtlogd(8)
http://libvirt.org
Main PID: 14334 (virtlogd)
CGroup: /system.slice/virtlogd.service
└─14334 /usr/sbin/virtlogd
Nov 18 14:03:10 localhost.localdomain systemd[1]: Started Virtual machine log manager.
Nov 18 14:03:10 localhost.localdomain systemd[1]: Starting Virtual machine log manager...
Nov 18 14:03:19 localhost.localdomain virtlogd[14334]: libvirt version: 2.0.0, package: 10.el7 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2016...hat.com)
Nov 18 14:03:19 localhost.localdomain virtlogd[14334]: hostname: localhost.localdomain
Nov 18 14:03:19 localhost.localdomain virtlogd[14334]: End of file while reading data: Input/output error
Hint: Some lines were ellipsized, use -l to show in full.
Closing per comment 8. |
Created attachment 1221130 [details] /var/log/messages Description of problem: Some error messages could be found at /var/log/messages Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Fully install RHEL 7.3 2. Check /var/log/messages 3. Actual results: [root@localhost ~]# cat /var/log/messages | grep -i error Nov 14 00:10:58 localhost journal: End of file while reading data: Input/outputerror Nov 14 00:31:34 localhost journal: internal error: End of file from monitor Nov 14 00:31:34 localhost journal: End of file while reading data: Input/outputerror Expected results: No these error info. Additional info: