[Bug] Running aptos fullnode (with consensus observer) panicking #18383
Description
Hello - ive been running a fullnode (with consensus observer enabled) on my machine (with the proper specs) for the last few weeks using the instructions from https://aptos.dev/network/nodes/full-node and everything was working fine up until today when i noticed the REST API tcp connection was flapping - im looking at my docker logs and see this error:
2025-12-23T05:04:50.894979160Z details = """
2025-12-23T05:04:50.894995229Z panicked at consensus/src/pipeline/buffer_item.rs:150:21:
2025-12-23T05:04:50.895001800Z assertion left == right failed
2025-12-23T05:04:50.895009929Z left: BlockInfo { epoch: 14079, round: 31478, id: HashValue(8b9a559cac89d046bb7dfd276644a127cf024faee448f7f55e0fa2ec93f8ff67), executed_state_id: HashValue(e3a0cd13c671ddff26c19fd28decef6ea863c08ce2f3c36ea241be466b83d5f3), version: 3963857781, timestamp_usecs: 1766466289568411, next_epoch_state: None }
2025-12-23T05:04:50.895016729Z right: BlockInfo { epoch: 14079, round: 31478, id: HashValue(8b9a559cac89d046bb7dfd276644a127cf024faee448f7f55e0fa2ec93f8ff67), executed_state_id: HashValue(53082b1c179084dba4254197d5503da8cf168be282875e5166acdb7c6753ac3b), version: 3963857781, timestamp_usecs: 1766466289568411, next_epoch_state: None }"""
I nuked my db and resynced again - however ran into the same issue once again once it caught up
my fullnode.yaml in case it helps:
base:
role: "full_node"
data_dir: "/opt/aptos/data"
waypoint:
from_file: "/opt/aptos/etc/waypoint.txt"
execution:
genesis_file_location: "/opt/aptos/etc/genesis.blob"
storage:
rocksdb_configs:
enable_storage_sharding: true
full_node_networks:
- network_id: "public"
discovery_method: "onchain"
listen_address: "/ip4/0.0.0.0/tcp/6182"
api:
enabled: true
address: "0.0.0.0:8080"
consensus:
enable_pre_commit: false
consensus_observer:
observer_enabled: true
publisher_enabled: true