Always get "error: network activity timed out" with k1pool.com for ZIL

[rob4226]

Hello,

For some reason I can never consistently connect to K1Pool for ZIL. It always says connection error: network activity timed out, then it connects and mines to the backup pool (shardpool in this example).

I thought it was just an intermittent issue with K1Pool but I've tried it many times over the past 3 weeks and with rigel version 1.11.0, 1.12.0, and 1.12.1 on Windows 10. I tried different combos of algo, and even single mining ZIL but get same error. Both the US and EU urls get the same connection timeout error (us.zil.k1pool.com:1111 and eu.zil.k1pool.com:1111).

I tried the same URL in other miners and they are able to mine and stay connected to K1pool.

I tried a stratum pinger to us.zil.k1pool.com:1111 and it seems the problem is, while most pings are 30ms, some pings are ridiculously long, like 1 second. I'm assuming that's why rigel considers it a timeout error. I have gotten the same results every time I've tried over the past 3 weeks.

k1pool for ZIL Zilliqa Coin
US:
PING stratum us.zil.k1pool.com (51.79.72.218) port 1111
us.zil.k1pool.com (51.79.72.218): seq=0, time=20.0376ms
us.zil.k1pool.com (51.79.72.218): seq=1, time=592.1837ms
us.zil.k1pool.com (51.79.72.218): seq=2, time=969.9581ms
us.zil.k1pool.com (51.79.72.218): seq=3, time=29.3055ms
us.zil.k1pool.com (51.79.72.218): seq=4, time=34.6609ms

--- us.zil.k1pool.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 6.7720655s
min/avg/max = 20.0376ms, 329.22916ms, 969.9581ms

Do you have any recommendations on how to fix this?

Thanks!

[2023-12-28 18:53:57] [us.zil.k1pool.com:1111] connection error: network activity timed out
[2023-12-28 18:53:57] [us.zil.k1pool.com:1111] connecting...
[2023-12-28 18:53:57] [us2-zil.shardpool.io:3333] connecting...
[2023-12-28 18:53:57] [us.zil.k1pool.com:1111] connected
[2023-12-28 18:53:57] [us2-zil.shardpool.io:3333] connected

[rigelminer]

Hi, could you please post your full rigel config? You can redact your wallet addresses of course.

[rob4226]

Hi, could you please post your full rigel config? You can redact your wallet addresses of course.

Sure, here is my config that I run on Windows 10:

:: triple-erg-iron-zil.bat
:: erg + iron + zil

rigel.exe -a autolykos2+ironfish+zil --log-file M:/rigel-miner-triple-erg-iron-zil.log --zil-countdown ^
    -o [1]stratum+tcp://us-erg.2miners.com:8888           -u [1]ergoaddresxxxxxxxxxxxxxxxxxxxxxxxxx.worker1  ^
    -o [1]stratum+tcp://us2.ergo.herominers.com:1180 ^
    -o [1]stratum+tcp://ergo-us-east1.nanopool.org:10600 ^
    -o [2]stratum+tcp://us2.ironfish.herominers.com:1145  -u [2]ironfishaddressxxxxxxxxxxxxxxxxxxxx.worker1 ^
    -o [2]stratum+tcp://iron.kryptex.network:7777 ^
    -o [3]zmp+tcp://us.zil.k1pool.com:1111                 -u [3]K1pooladdressxxxxxxxxxxxxxxxxxxxxx.worker1 ^
    -o [3]zmp+tcp://us2-zil.shardpool.io:3333              -u [3]ziladdressxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ^
    -w worker1 --api-bind 127.0.0.1:5000 --temp-limit tc[65-80] --fan-control t:[60;_][50;25-90] ^
    --lock-cclock [1]1500,1500 --mclock [1]1100,1100 --pl [1]110,110 ^
    --cclock [2]195,195 --mclock [2]200,200 --pl [2]105,100 ^
    --lock-cclock [3]1500,1500 --mclock [3]1100,1100 --pl [3]110,110

Also, just want to add that I tried a similar config on a different Linux HiveOS rig that also exhibited the same K1pool + ZIL network timeout issue. Thanks!

[rigelminer]

Thanks for the config. I've done some investigation and the issue seems to occur only for ZIL pools when there's a failover. I think I have fixed it, but I would be grateful if you could confirm that. Please try this 1.12.1-zil-failovers build when you have time: link

[rob4226]

@rigelminer Thank you for responding!

So I tried 1.12.1-zil-failovers for the past 4 hours and each time it tried to connect to the ZIL K1pool it outputted pretty much the same log as the previous version (pasted below). The only difference is this time it does not failover to the backup pool for ZIL. The miner reports 0 shares, and I checked the pools and no shares were reported.

[2023-12-30 20:53:09] +========================================+
[2023-12-30 20:53:09] 
[2023-12-30 20:53:12] [us.zil.k1pool.com:1111] connection error: network activity timed out
[2023-12-30 20:53:12] [us.zil.k1pool.com:1111] connecting...
[2023-12-30 20:53:12] [us2-zil.shardpool.io:3333] connecting...
[2023-12-30 20:53:12] [us2-zil.shardpool.io:3333] connected
[2023-12-30 20:53:12] [us.zil.k1pool.com:1111] connected
[2023-12-30 20:53:29] 
[2023-12-30 20:53:29] +============== Rigel v1.12.1-zil-failovers - [Windows] ===============+

I also ran it with no ZIL failover pools, just the one F1pool pool for 1.5 hours and I got the same results, no shares get sent with a timeout error.

Log with only one pool for ZIL, no failover pools:

[2023-12-30 22:03:59] +========================================+
[2023-12-30 22:03:59] 
[2023-12-30 22:04:00] [us.zil.k1pool.com:1111] connection error: network activity timed out
[2023-12-30 22:04:00] [us.zil.k1pool.com:1111] connecting...
[2023-12-30 22:04:00] [us.zil.k1pool.com:1111] connected
[2023-12-30 22:04:19] 
[2023-12-30 22:04:19] +=============== Rigel v1.12.1-zil-failovers - [Windows] ===============+

[rigelminer]

Oh, sorry. I must've fixed another issue then. Still happy about it because zil failover logic was flawed - the miner would connect to both the primary and the failover pool at the same time. As for the network activity timed out error, my guess is something's blocking connections to k1pool. Could you run the 1.12.1-zil-failovers version with --log-network --log-file zil.log and post your log file? Running your config on my machine I can see regular back-and-forth communication with K1Pool that qualifies for "network activity" so I never get that timeout issue. k1pool.log

[rob4226]

These log lines are found each time a connection is made to k1pool, it is always preceded with the timeout error:

[2024-01-02 04:01:41] [us.zil.k1pool.com:1111] connection error: network activity timed out
[2024-01-02 04:01:41] [us.zil.k1pool.com:1111] connecting...
[2024-01-02 04:01:41] [us2-zil.shardpool.io:3333] connecting...
[2024-01-02 04:01:41] [us2-zil.shardpool.io:3333] connected
[2024-01-02 04:01:41] [us.zil.k1pool.com:1111] connected
[2024-01-02 04:01:41] [us2-zil.shardpool.io:3333] => {"id":0,"method":"login","params":[{"userAgent":"Rigel/1.12.1-zil-failovers","login":"*****.***"}]}
[2024-01-02 04:01:41] [us.zil.k1pool.com:1111] => {"id":0,"method":"login","params":[{"userAgent":"Rigel/1.12.1-zil-failovers","login":"*****.***"}]}

Usually, I would assume it is something with my connection or setup, but I tried another miner (gminer) and for some reason I don't get any timeouts and all shares make it to k1pool.

This time with rigel, I did see a few shares get through to k1pool, but not consistently.

Maybe k1pool takes longer to respond than other pools, so the connection timeout setting is too short for it?

I don't want you to waste time if I'm the only person seeing it, but I guess just keep an eye out in case anyone else also reports the same thing. Thanks!

[rigelminer]

When I asked about the log file I was more interested in seeing what's happening before the timeout error. The miner is supposed to be sending hashrate reporting messages every 30 seconds and the pool sends out new jobs at regular intervals too (see my log). Is it happening in your case? I guess not, otherwise the timeout error wouldn't have occurred, but the log file would confirm that.

[rigelminer]

Closing due to inactivity