node-add-local test fails: Platform stuck in STARTING state with SSL peer authentication errors #3042
Description
Problem
The node-add-local test is failing because the platform remains stuck in STARTING state and never transitions to ACTIVE. The node experiences continuous SSL peer authentication failures.
We used to think it was failed due to some github runner resource issue.
Test Details
Test: node-add-local
Failure Mode: Platform stuck waiting to become ACTIVE
Root Cause: SSL peer authentication failures preventing node synchronization
Error Logs
The swirlds.log shows repeated SSL authentication errors:
2025-12-06 21:12:19.550 76 WARN SOCKET_EXCEPTIONS <<peer_sync_server #1>> InboundConnectionHandler: Inbound connection from /10.10.0.61 to 2 had IOException: Caused by exception: SSLPeerUnverifiedException Message: peer not authenticated
(Due to rate limiting, this condition has been triggered 3509 times without being reported.)
2025-12-06 21:13:19.564 77 WARN SOCKET_EXCEPTIONS <<peer_sync_server #1>> InboundConnectionHandler: Inbound connection from /10.10.0.61 to 2 had IOException: Caused by exception: SSLPeerUnverifiedException Message: peer not authenticated
(Due to rate limiting, this condition has been triggered 3658 times without being reported.)
2025-12-06 21:14:19.579 78 WARN SOCKET_EXCEPTIONS <<peer_sync_server #1>> InboundConnectionHandler: Inbound connection from /10.10.0.61 to 2 had IOException: Caused by exception: SSLPeerUnverifiedException Message: peer not authenticated
(Due to rate limiting, this condition has been triggered 3644 times without being reported.)
2025-12-06 21:15:19.583 79 WARN SOCKET_EXCEPTIONS <<peer_sync_server #1>> InboundConnectionHandler: Inbound connection from /10.10.0.61 to 2 had IOException: Caused by exception: SSLPeerUnverifiedException Message: peer not authenticated
(Due to rate limiting, this condition has been triggered 3653 times without being reported.)
2025-12-06 21:16:19.345 80 ERROR EXCEPTION <platformForkJoinThread-7> DefaultSignedStateSentinel: Old signed state detected. The most likely causes are either that the node has gotten stuck or that there has been a memory leak.
null
2025-12-06 21:16:19.591 81 WARN SOCKET_EXCEPTIONS <<peer_sync_server #1>> InboundConnectionHandler: Inbound connection from /10.10.0.61 to 2 had IOException: Caused by exception: SSLPeerUnverifiedException Message: peer not authenticated
(Due to rate limiting, this condition has been triggered 3681 times without being reported.)
Many times rerun the test, the test would pass