possible error with priority node connection
So I try to connect my node A to the xmrchain node B as a priority node. 

```
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.461	[P2P6]	INFO	net.p2p	src/p2p/net_node.inl:2675	[176.9.0.187:18080 3738d72d-86df-4722-8017-0e5badb645b2 OUT] NEW CONNECTION
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.461	[P2P6]	INFO	net.p2p.traffic	contrib/epee/include/net/levin_protocol_handler_async.h:57	[176.9.0.187:18080 OUT] 274 bytes sent for category command-1001 initiated by us
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.567	[P2P8]	INFO	net	contrib/epee/include/storages/levin_abstract_invoke2.h:74	Failed to invoke command 1001 return code -3
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.567	[P2P8]	WARNING	net.p2p	src/p2p/net_node.inl:1160	[176.9.0.187:18080 OUT] COMMAND_HANDSHAKE invoke failed. (-3, LEVIN_ERROR_CONNECTION_DESTROYED)
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	WARNING	net.p2p	src/p2p/net_node.inl:1219	[176.9.0.187:18080 OUT] COMMAND_HANDSHAKE Failed
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	net.p2p	src/p2p/net_node.inl:1412	[176.9.0.187:18080 OUT] [priority]Failed to HANDSHAKE with peer 176.9.0.187:18080
bitmonero.log-2023-11-12-16-40-40:2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:133	Exception: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_weak_ptr> >
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:134	Unwound call stack:
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [1]  0x107) [0x562d78f40ed7]:__cxa_throw+0x107) [0x562d78f40ed7]
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [2] /bin/monerod(+0xbeffc) [0x562d78b1fffc] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [3] /bin/monerod(+0x3507d7) [0x562d78db17d7] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [4] /bin/monerod(+0x363f84) [0x562d78dc4f84] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [5] /bin/monerod(+0x37358b) [0x562d78dd458b] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [6] /bin/monerod(+0x3736c9) [0x562d78dd46c9] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [7] /bin/monerod(+0x3d6a1f) [0x562d78e37a1f] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [8] /bin/monerod(+0x34ed63) [0x562d78dafd63] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [9] /bin/monerod(+0x3816f9) [0x562d78de26f9] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [10] /bin/monerod(+0x3506a5) [0x562d78db16a5] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [11] /bin/monerod(+0xc0986) [0x562d78b21986] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [12] /bin/monerod(+0x36fb01) [0x562d78dd0b01] 
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [13]  0x11bcd) [0x7f2efe96dbcd]:_64-linux-gnu/libboost_thread.so.1.65.1(+0x11bcd) [0x7f2efe96dbcd]
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [14]  0x76db) [0x7f2efd8dd6db]:_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f2efd8dd6db]
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	    [15]  0x3f) [0x7f2efd60661f]:_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f2efd60661f]
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	INFO	stacktrace	src/common/stack_trace.cpp:172	
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.568	[P2P6]	ERROR	net	contrib/epee/include/net/levin_protocol_handler_async.h:340	[176.9.0.187:18080 OUT] [levin_protocol] -->> start_outer_call failed
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.569	[P2P8]	INFO	net.cn	src/cryptonote_protocol/cryptonote_protocol_handler.inl:2953	[176.9.0.187:18080 OUT] [0] state: closed in state before_handshake
bitmonero.log-2023-11-12-16-40-40-2023-11-12 15:52:05.570	[P2P8]	INFO	net.p2p	src/p2p/net_node.inl:2694	[176.9.0.187:18080 3738d72d-86df-4722-8017-0e5badb645b2 OUT] CLOSE CONNECTION
--
```

It turns out I also have the xmrchain node B set to connect to A as a priority node, because node A has xmrchain as an INC connection

```
user@user-ProLiant-DL325-Gen10:~/.bitmonero$ monerod --rpc-bind-port 12345 print_cn | grep 176.9.0.187
INC 176.9.0.187:50792        IPv4 
```

probably nothing, but i don't understand why its throwing the stacktrace thing. I thought that was for when things are borkt. 

though if you run two nodes, it would make sense to have them set to make each other a priority to connect to. But I guess you only need to tell one of them to make it a priority? 