|
From: Tung Q. N. <tun...@de...> - 2024-07-08 10:02:58
|
>*Jun 29 14:45:36 in-debbld-33 kernel: [1724399.196945] Unable to remove publication from failed node Jun 29 14:45:36 in-debbld-33
>kernel:
>[1724399.196945] (type=20185106, lower=1, node=0xd1045013, port=2177385505, key=2177385506) Jun 29 14:45:36 in-debbld-33
>kernel:
>[1724399.196948] Unable to remove publication from failed node Jun 29
>14:45:36 in-debbld-33 kernel: [1724399.196948] (type=20185106, lower=1, node=0xd1045013, port=2177385505, key=2177385506)
>Jun 29 14:45:36
>in-debbld-33 kernel: [1724399.196954] Unable to remove publication from failed node Jun 29 14:45:36 in-debbld-33 kernel:
>[1724399.196954] (type=20185106, lower=1, node=0xd1045013, port=2177385505, key=2177385506)*
>
>###############################################################################################################
>######
>
>
>
>Any idea why this would be happening ?
Memory error could cause this. I observed the same thing in my system:
"
2024-05-27T07:27:22.747+02:00 kernel:[425219.492047] {...}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
...
2024-05-27T07:27:22.747+02:00 kernel:[425219.517622] {...}[Hardware Error]: section_type: memory error
...
2024-05-27T07:27:22.973+02:00 kernel:[425221.704107] tipc: Unable to remove publication from failed node
2024-05-27T07:27:22.973+02:00 kernel:[425221.704107] (type=143322, lower=9, node=0x1001009, port=1295954722, key=1295954723)
2024-05-27T07:27:22.973+02:00 kernel:[425221.717912] tipc: Unable to remove publication from failed node
2024-05-27T07:27:22.973+02:00 kernel:[425221.717912] (type=143322, lower=9, node=0x1001009, port=1295954722, key=1295954723)
"
|