Page MenuHomeVyOS Platform

Drop support for "system console netconsole"
Closed, ResolvedPublicFEATURE REQUEST

Description

https://www.kernel.org/doc/Documentation/networking/netconsole.txt

This module logs kernel printk messages over UDP allowing debugging of problem where disk logging fails and serial consoles are impractical.

It can be used either built-in or as a module. As a built-in, netconsole initializes immediately after NIC cards and will bring up the specified interface as soon as possible. While this doesn't allow capture of early kernel panics, it does capture most of the boot process.

This feature is due for porting to XML/Python in conjunction with the serial console interfaces. As this is only a one-way communication we can not use it to recover the system. For sending log messages to a remote host we usually use syslog.

I'd like to drop this in 1.3

Vyatta docs say:

Details

Difficulty level
Easy (less than an hour)
Version
1.3
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Config syntax change (migratable)

Related Objects

StatusSubtypeAssignedTask
ResolvedFEATURE REQUESTc-po
ResolvedFEATURE REQUESTc-po

Event Timeline

c-po changed the task status from Open to In progress.Jun 7 2020, 7:35 PM
c-po claimed this task.
c-po triaged this task as High priority.
c-po changed Version from - to 1.3.
c-po changed Is it a breaking change? from Unspecified (possibly destroys the router) to Config syntax change (migratable).
c-po renamed this task from Drop support for netconsole to Drop support for "system console netconsole".Jun 7 2020, 7:38 PM
c-po updated the task description. (Show Details)

@c-po I have not tried this previously, but if it works well, I would like to keep it for kernel debugging on bare-metal devices.

A Serial/IPMI interface would be much more suited for kernel debugging.

@zsdc the current implementation only works once the system has been fully booted up and the config nodes have been process. So there is no "early" kernel debugging. It is started with priority 400 (after all network stuff) - thus I question its existence for Kernel debugging.

It would only make sense if the entire system is changed to supply the config stuff to the Kernel commandline and then send it to a dedicated MAC address target as network will be initialized late.

I think we can safely remove it indeed.

I've never seen anyone discuss this feature or ask about it, makes me think very few people use it and most will learn it existed only from release notes saying it was removed.

c-po changed Difficulty level from Unknown (require assessment) to Easy (less than an hour).