Editing Remote console setup
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 209: | Line 209: | ||
sysctl -w kernel.printk="7 4 1 7" | sysctl -w kernel.printk="7 4 1 7" | ||
− | After testing you can | + | After testing you can repair previous setting the same way. |
− | Load | + | Load netconsole module (see above) and on console server do netcat command. On OpenVZ side provocate any console message, f.e. connect any USB hardware or try command: |
− | + | <pre> | |
+ | modprobe tun | ||
+ | </pre> | ||
+ | |||
+ | If you see any console message on OpenVZ side, you should see message on console server too. If not, something is wrong. When debugging a problem, do not use tcpdump on OpenVZ side — it is not able to show netconsole packets. Instead, use tcpdump on console server. Quite common the source of problems with netconsole are firewalls. | ||
− | |||
== See also == | == See also == |