Unknown parameters in dmesg

[HristoGrigorov]

If I see these kind of records in 'dmesg' :

[Tue Dec 15 01:52:15 2020] [fw4_0];Global param: operation failed: Unknown parameter (param name fwconn_tracker_enable_app_opaque)
[Tue Dec 15 01:52:15 2020] [fw4_0];Global param: operation failed: Unknown parameter (param name fwconn_tracker_frequency_writes_to_disk)
[Tue Dec 15 01:52:15 2020] [fw4_0];Global param: operation failed: Unknown parameter (param name fwconn_tracker_pool_size)
[Tue Dec 15 01:52:15 2020] [fw4_0];Global param: operation failed: Unknown parameter (param name fwconn_tracker_suppression_max_events)
[Tue Dec 15 01:52:15 2020] [fw4_0];Global param: operation failed: Unknown parameter (param name fwconn_tracker_suppression_max_seconds)
[Tue Dec 15 01:52:15 2020] [fw4_0];Global param: operation failed: Unknown parameter (param name fwconn_tracker_suspended)
[Tue Dec 15 01:52:16 2020] [fw4_0];Global param: operation failed: Unknown parameter (param name fwconn_tracker_monitor)

what have I done wrong this time ? 😀

[PhoneBoy]

Are those in fwkern.conf by chance?

[HristoGrigorov]

Yeah, first thing I checked. Nothing like that here.

[PhoneBoy]

This looks like a bug in cpdiag according to a couple of TAC cases.
I believe a fix will get pushed via an auto-update soon.
Might be worth opening a TAC case.

[HristoGrigorov]

Thanx, I may open SR if I have the time for it.

[PhoneBoy]

I dug into the TAC cases a little more and only one mentions cpdiag...so may not entirely be entirely related.

[HristoGrigorov]

It happens every day at 01:52. Must be a scheduled job.