Bug 827408
Summary: | netconsole doesn't work after configured in TUI | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | yuanquan chen <yuachen> |
Component: | ovirt-node | Assignee: | Mike Burns <mburns> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.3 | CC: | acathrow, bsarathy, chetan, cshao, fdeutsch, gouyang, jboggs, leiwang, mburns, ovirt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-node-2.5.0-3.el6 | Doc Type: | Bug Fix |
Doc Text: |
The netconsole service was not enabled by default, therefore console log messages were not automatically forwarded from the hypervisor to a configured remote host. Netconsole is now enabled by default, and all messages above the threshold specified in /proc/sys/kernel/printk are forwarded.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-28 16:35:36 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: | |
Embargoed: |
Description
yuanquan chen
2012-06-01 11:43:30 UTC
netconsoles purpose is to send all _console log messages_ via UDP to a remote host. And that seems to be working. /proc/sys/kernel/printk defines the threshold what messages go to the console (and therefor netconsole too). The examples you gave above (echo abc > /dev/kmsg) are just not above the threshold and therefor not displayed on the console and send to the remote server, but logged to dmesg (which has a lower threshold). syslog is the way to go to receive everything that goes to dmesg (AFAIK) This patch fixes a side problem: Netconsole is not enabled by default. http://gerrit.ovirt.org/5027 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0556.html |