Error in pooling: Did not find signage point or EOS

Chia Pools
1

chia blockchain 1.2.2

farmer chia.farmer.farmer         : ERROR    Error in pooling: (3, 'Did not find signage point or EOS d45c57c963b3d5f3a681a0f5afb8ba754647908f7204de1f919982ac5e6f31fd, None')
farmer chia.farmer.farmer         : ERROR    Error in pooling: (3, 'Did not find signage point or EOS f455500c6dd8bb2f5cfd4d794c239a84a410224570782c0649654f3f7b913756, None')
farmer chia.farmer.farmer         : ERROR    Error in pooling: (3, 'Did not find signage point or EOS f455500c6dd8bb2f5cfd4d794c239a84a410224570782c0649654f3f7b913756, None')
farmer chia.farmer.farmer         : ERROR    Error in pooling: (3, 'Did not find signage point or EOS de692ed42e121230cf1ac440d015f9365e5931bfbc9dd25b243b4282dd871d3b, None')
farmer chia.farmer.farmer         : ERROR    Error in pooling: (3, 'Did not find signage point or EOS

pool log

pool root :   INFO     post_partial response {'error_code': 3, 'error_message': 'Did not find signage point or EOS d0fd4a6d8eec8992b9698de0a5f38dc19d32ad55a0bd77d4b8e999321c9912dd, None'}, time: 10.02328372001648 launcher_id: 0x707a5fe5545cd47f220c7a80c6f72eb4f9cf3545c32d248990043b8980292d13
pool root :   INFO     post_partial response {'error_code': 3, 'error_message': 'Did not find signage point or EOS d3959996add2d8fbcaa093160deef8d28aa729ef1b20923e4fad822751223b82, None'}, time: 10.018839359283447 launcher_id: 0x707a5fe5545cd47f220c7a80c6f72eb4f9cf3545c32d248990043b8980292d13
pool root :   INFO     post_partial response {'error_code': 3, 'error_message': 'Did not find signage point or EOS d3959996add2d8fbcaa093160deef8d28aa729ef1b20923e4fad822751223b82, None'}, time: 10.03123927116394 launcher_id: 0x707a5fe5545cd47f220c7a80c6f72eb4f9cf3545c32d248990043b8980292d13
2

Are you asking for help on this? Or just pointing it out. This is a known issue with the protocol and is still an open issue. Pools are working on fixes but it is an issue with the reference code. Here is the issue if you didn’t know:

1 Like
3

yes i need help. What can I do

4

There is nothing you can do. It is an issue that the Chia team and the pools are working on. You can let your pool know that you are having the errors. Just so they know. But I’m sure they already know.

1 Like
5

Its not a known issue because its not a pool/chia issue.

It means the pool you’re using is running a node that is lagging behind.
Probably means they are using a cheap VPS with not enough CPU/RAM/DISK :slight_smile:

We dont have that problem if you’re willing to try: https://openchia.io

1 Like
6

That’s not accurate. What you are saying could be true, but not always. He would get the same message if he was the one that was slow. Not the pool. Trying to say the pool is at fault is wrong and makes you look bad as a pool operator.

7

I know 100% of what I am talking about.
The logs he pasted are responses of a pool. Only way he could get that response is the signage point was not found in the pool node blockchain.

8

Checked our support logs and we’ve never had this error reported (and we’ve dealt with A LOT of requests). So I’m guessing its either a very rare one or indeed its a pool problem. Not enough evidence to conclude so and I’m sure there’s ways to cause it on either end. Reverted signage point errors on the other hand are relatively common and are due to the chia node being unable to handle high load on the network causing block propagation delays, and forked sidechains as result which leads into forked (reverted) signage points.

9

My bad. I had been responding to another post and when I saw your response, I thought it was that thread. Didn’t realize I was in the signage point thread.

But, now that I know where I am, this EOS issue is an open issue in the protocol (issue link posted above) and as far as I know, affects all pools. If you don’t have this issue at all, that is pretty interesting.

1 Like
10

Yes, you are right. really, the lowest VDS.

11

And what these mistakes mean after two years, I repeat it several times a day. I have Gigahorse fences if that is not related?

2023-04-10T19:07:34.597 farmer chia.farmer.farmer         : ERROR    Error in pooling: (3, 'Did not find signage point or EOS f1e09366ee8296c20cb8c843a07225e4553ff5ec381d77d0d109596cc681c78a, None')
2023-04-10T19:22:30.744 full_node asyncio                 : ERROR    Exception in callback _ProactorBasePipeTransport._call_connection_lost(None)
handle: <Handle _ProactorBasePipeTransport._call_connection_lost(None)>
Traceback (most recent call last):
  File "C:\CHIA-G~1\.\asyncio\events.py", line 80, in _run
  File "C:\CHIA-G~1\.\asyncio\proactor_events.py", line 165, in _call_connection_lost
ConnectionResetError: [WinError 10054] Stávající připojení bylo vynuceně ukončeno vzdáleným hostitelem
2023-04-10T19:24:04.815 full_node full_node_server        : WARNING  Cannot write to closing transport 88.235.10.197
2023-04-10T19:30:22.383 full_node full_node_server        : WARNING  Cannot write to closing transport 109.247.21.63
2023-04-10T19:59:54.965 full_node full_node_server        : WARNING  Cannot write to closing transport 46.223.252.171

Translation: Stávající připojení bylo vynuceně ukončeno vzdáleným hostitelem - An existing connection has been forcibly terminated by the remote host