0.14.0.dev3 Segmentation fault when reconnecting to pool after connection was lost / disconnected. #848

jmsjr · 2018-03-05T11:04:44Z

Ethminer Version:

ethminer version 0.14.0.dev3+git.83693003
Build: linux/release/gnu

OS:

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"

Been running 0.14.0.dev3 for 18 hours. I actually have 2 instances / processes of ethminer running on the rig:

One for a single CUDA/Nvidia GPU 8GB
Another for 2x OpenCL/AMD GPUs 4GB

The ethminer process for the OpenCL GPUs segfaulted after the connection to the pool was lost and ethminer tries to reconnect.
The ethminer process for the CUDA GPU is still running as I speak.

Observations from the console output below ( note that I replaced my wallet address / userpass argument below with xxxxxxxx ):

A message saying "No new work received in 180 seconds."
An error message saying "Exception thrown in Worker thread: write: protocol is shutdown". So I presume at this point that the TCP connection is lost / disconnected / etc.
An message saying disconnected from the pool: "Disconnected from asia1.ethermine.org"
Then a message saying "Retrying in X seconds"
Then a core dump message / segfault when it was about to reconnect.

Note that I am also using TLS on port 5555

  m  16:38:30|ethminer|  Speed  45.99 Mh/s    gpu/0 21.95 57C 60%   gpu/1 24.05 57C 60%   [A789+0:R0+0:F0] Time: 18:40
  ℹ  16:38:32|stratum |  No new work received in 180  seconds.
  m  16:38:35|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 57C 60%   gpu/1 24.05 57C 60%   [A789+0:R0+0:F0] Time: 18:40
  ✘  16:38:37|main    |  Exception thrown in Worker thread: write: protocol is shutdown
  m  16:38:40|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 57C 60%   gpu/1 24.05 57C 60%   [A789+0:R0+0:F0] Time: 18:40
  m  16:38:45|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 57C 60%   gpu/1 24.05 57C 60%   [A789+0:R0+0:F0] Time: 18:40
  m  16:38:50|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 58C 60%   gpu/1 24.05 58C 60%   [A789+0:R0+0:F0] Time: 18:40
  m  16:38:55|ethminer|  Speed  46.00 Mh/s    gpu/0 21.95 57C 60%   gpu/1 24.05 57C 60%   [A789+0:R0+0:F0] Time: 18:40
  m  16:39:00|ethminer|  Speed  45.92 Mh/s    gpu/0 21.95 58C 60%   gpu/1 23.97 58C 60%   [A789+0:R0+0:F0] Time: 18:40
  m  16:39:05|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 58C 60%   gpu/1 24.05 58C 60%   [A789+0:R0+0:F0] Time: 18:40
  m  16:39:10|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 58C 60%   gpu/1 24.05 58C 60%   [A789+0:R0+0:F0] Time: 18:41
  m  16:39:15|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 58C 60%   gpu/1 24.05 58C 60%   [A789+0:R0+0:F0] Time: 18:41
  ℹ  16:39:18|stratum |  Disconnected from asia1.ethermine.org
  ✘  16:39:18|stratum |  Retrying in 3 ...
  ✘  16:39:19|stratum |  Retrying in 2 ...
  m  16:39:20|ethminer|  not-connected
  ✘  16:39:20|stratum |  Retrying in 1 ...
./start_ethermine.org-opencl.sh: line 17:  8092 Segmentation fault      (core dumped) bin/ethminer --farm-recheck 2000 -G --stratum asia1.ethermine.org:5555 --
stratum-failover us2.ethermine.org:5555 --userpass 0xecxxxxxxxx.rig01-opencl --stratum-protocol 0 --report-hashrate --verbosity 9
 -HWMON 0 --stratum-ssl 0

FWIW, I actually am using ethminer because of a similar behaviour I have with Claymore:

Claymore DevFee couldn't connect to stratum, restarts miner, complains not enough GPU memory DAG

... so I am giving ethminer a try. Hopefully it is not the same issue as with Claymore ( e.g. seems to be that GPU memory was not being cleared before restarting the miner process )

The text was updated successfully, but these errors were encountered:

DeadManWalkingTO · 2018-03-05T13:30:32Z

CUDA Hardware Test Launch Command:

ethminer -RH -X -S asia1.ethermine.org:4444 -FS us1.ethermine.org:4444 -O 0x7013275311fc37ccc1e40193D75086293eCb43A4.hardwaretest

Try with latest Ethminer version to ensure that's not hardware problem and feedback please.
Thank you!

jmsjr · 2018-03-05T14:04:14Z

CUDA Hardware Test Launch Command:

Nothing to do with CUDA .. The ethminer process running on CUDA / Nvidia GPUs were still running when I opened this issue.

It's the ethminer process running on OpenCL / AMD GPUs that segfaulted when trying to reconnect after the connection to the pool was lost / disconnected.

Try with latest Ethminer version to ensure that's not hardware problem and feedback please.
Thank you!

OK, I am confused, because I AM using the latest ethminer version ... 0.14.0.dev3 .. .from the releases page ( https://github.com/ethereum-mining/ethminer/releases ), which shows 0.14.0.dev3 ... or are you referring for me to do a git clone and build from master ?

smurfy · 2018-03-05T16:06:25Z

it is possible its the same issue @jean-m-cyr seen at my pr #828 and we are in the process of cleaning this up.

jean-m-cyr · 2018-03-05T17:41:10Z

@smurfy Possibly unrelated, but I've noticed that sometimes under Linux a console ctl-c will result in similar segfault with crash dump. Only happens when using SSL.

smurfy · 2018-03-05T17:46:04Z

possible. i hope to fix these problems with #828 , well initially that PR was meant for something else to be fixed and i noticed some other stuff also not working so i fixed them as-well :)

Do you get your segfaults with or without #828 . If without it could be the m_socket.close() thingy.

jean-m-cyr · 2018-03-05T17:54:08Z

I've moved the io_service.stop() to after the m_socket.close() locally so I don't get the failover crashes runing regular tcp anymore. It doesn't help for SSL crashes. Not exactly the same as #828

smurfy · 2018-03-05T18:01:55Z

Well @jmsjr gets:

✘ 16:38:37|main | Exception thrown in Worker thread: write: protocol is shutdown

Which you also get. Not sure where the exception is thrown. (probably in PoolClient either while trying to write or read).

And then catched somewhere. So maybe after catching it late something gets destroyed, in an ugly state which causes the reconnect to segfault :)

So i try to actually reproduce the problem. In my dev environment and then debug it by adding a shitload of debug output :)

jean-m-cyr · 2018-03-05T18:07:02Z

@smurfy When I was playing with this trying to figure out the SSL case, I recall finding out that the disconnect method was being called recursively. Maybe not recursively, but at least twice somehow!!!
Never got past understanding why.

Yes. the protocol is shutdown message applies only to SSL, and typically precedes the crash by a second or two. I don't think catching the write on closed socket exception is going to fix it. The crash doesn't occur immediately after the exception.

jmsjr · 2018-03-05T21:07:51Z

FYI .. Happened again just a few minutes ago... and again to the same ethminer process running on OpenCL / AMD GPUs. Note that I do not have them overclocked at all, just stock settings.

The ethminer process on CUDA still running... Don't know if the ethminer process ever got disconnected / lost TCP connection though... so maybe just a coincidence it is always the ethminer process running on OpenCL that is always disconnected.

  ℹ  07:54:47|stratum |  No new work received in 180  seconds.
  ✘  07:54:49|main    |  Exception thrown in Worker thread: write: protocol is shutdown
  m  07:54:51|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:15
  m  07:54:56|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.06 54C 60%   [A223+0:R0+0:F0] Time: 06:15
  m  07:55:01|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 55C 60%   gpu/1 24.06 55C 60%   [A223+0:R0+0:F0] Time: 06:15
  m  07:55:06|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.06 54C 60%   [A223+0:R0+0:F0] Time: 06:15
  m  07:55:11|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 55C 60%   gpu/1 24.05 55C 60%   [A223+0:R0+0:F0] Time: 06:15
  m  07:55:16|ethminer|  Speed  46.01 Mh/s    gpu/0 21.96 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:15
  m  07:55:21|ethminer|  Speed  46.01 Mh/s    gpu/0 21.96 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:16
.......snip.....
 ℹ  07:56:53|cl-1    |  Nonce 0xe8114f8546790854 submitted to asia1.ethermine.org
  m  07:56:56|ethminer|  Speed  45.94 Mh/s    gpu/0 21.96 54C 60%   gpu/1 23.98 54C 60%   [A223+0:R0+0:F0] Time: 06:17
  m  07:57:01|ethminer|  Speed  46.01 Mh/s    gpu/0 21.96 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:17
  m  07:57:06|ethminer|  Speed  46.01 Mh/s    gpu/0 22.03 54C 60%   gpu/1 23.98 54C 60%   [A223+0:R0+0:F0] Time: 06:17
  m  07:57:11|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 55C 60%   gpu/1 24.06 55C 60%   [A223+0:R0+0:F0] Time: 06:17
  m  07:57:16|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:17
  m  07:57:21|ethminer|  Speed  46.09 Mh/s    gpu/0 21.96 54C 60%   gpu/1 24.13 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:57:26|ethminer|  Speed  46.01 Mh/s    gpu/0 21.96 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:57:31|ethminer|  Speed  46.01 Mh/s    gpu/0 21.96 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:57:36|ethminer|  Speed  46.16 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.13 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:57:41|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:57:46|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 55C 60%   gpu/1 24.05 55C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:57:51|ethminer|  Speed  46.01 Mh/s    gpu/0 21.96 54C 60%   gpu/1 24.06 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:57:56|ethminer|  Speed  46.00 Mh/s    gpu/0 21.95 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:58:01|ethminer|  Speed  46.00 Mh/s    gpu/0 21.95 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:58:06|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:58:11|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:58:16|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:18
  m  07:58:21|ethminer|  Speed  46.01 Mh/s    gpu/0 21.95 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:58:26|ethminer|  Speed  46.01 Mh/s    gpu/0 21.95 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:58:31|ethminer|  Speed  46.01 Mh/s    gpu/0 21.95 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:58:36|ethminer|  Speed  46.16 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.13 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:58:41|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:58:46|ethminer|  Speed  46.08 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:58:51|ethminer|  Speed  46.00 Mh/s    gpu/0 21.95 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:19
 m  07:58:56|ethminer|  Speed  46.00 Mh/s    gpu/0 21.95 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:59:01|ethminer|  Speed  46.00 Mh/s    gpu/0 21.95 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:59:06|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.06 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:59:11|ethminer|  Speed  46.10 Mh/s    gpu/0 22.04 54C 60%   gpu/1 24.06 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:59:16|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:19
  m  07:59:21|ethminer|  Speed  46.09 Mh/s    gpu/0 22.03 54C 60%   gpu/1 24.06 54C 60%   [A223+0:R0+0:F0] Time: 06:20
  m  07:59:26|ethminer|  Speed  46.01 Mh/s    gpu/0 21.96 54C 60%   gpu/1 24.05 54C 60%   [A223+0:R0+0:F0] Time: 06:20
  ℹ  07:59:26|stratum |  Disconnected from asia1.ethermine.org
  ✘  07:59:26|stratum |  Retrying in 3 ...
  ✘  07:59:27|stratum |  Retrying in 2 ...
  ✘  07:59:28|stratum |  Retrying in 1 ...
  ✘  07:59:29|stratum |  Handle response failed: protocol is shutdown
./start_ethermine.org-opencl.sh: line 18: 13140 Segmentation fault      (core dumped) bin/ethminer --farm-recheck 2000 -G --stratum asia1.ethermine.org:5555 --stratum-failover us2.ethermine.org:5555 --userpass 0xexxxxxxxxxxxxx.rig01-opencl --stratum-protocol 0 --report-hashrate --verbosity 9 -HWMON 0 --stratum-ssl 0 --cl-parallel-hash 8

jmsjr · 2018-03-05T21:18:51Z

May I suggest that .. perhaps, while debugging, in an attempt to reproduce the issue ... put a rule in iptables to drop packets from the pool .. to get the "No new work from xxxx message" ... and then drop the iptables rule after the message "Disconnected from xxxx" and when just about to reconnect ??

jmsjr · 2018-03-05T21:35:30Z

FYI .. I also managed to somehow trigger it ( although randomly I suppose ) just by hitting Ctrl-C on the running ethminer process ( this time on the process running on CUDA GPUs ):

cu  08:32:50|cuda-0  |  Switch time 10 ms.
  m  08:32:54|ethminer|  Speed  28.33 Mh/s    gpu/0 28.33 63C 80%   [A0+0:R0+0:F0] Time: 00:05
  ℹ  08:32:56|stratum |  Received new job #6a44ca6c… from asia1.ethermine.org
 cu  08:32:56|cuda-0  |  Switch time 11 ms.
  m  08:32:59|ethminer|  Speed  28.24 Mh/s    gpu/0 28.24 63C 80%   [A0+0:R0+0:F0] Time: 00:05
^C  ✘  08:33:00|main    |  Exception thrown in Worker thread: write: protocol is shutdown
  ✘  08:33:01|stratum |  Read response failed: End of file
./start_ethermine.org-cuda.sh: line 18: 13736 Segmentation fault      (core dumped) bin/ethminer --farm-recheck 2000 -U --stratum asia1.ethermine.org:5555 --st
ratum-failover us2.ethermine.org:5555 --userpass 0xecxxxxxxxxxx.rig01-cuda --stratum-protocol 0 --report-hashrate --verbosity 9 -HW
MON 0 --stratum-ssl 0 --cuda-parallel-hash 6

jean-m-cyr · 2018-03-06T18:32:43Z

I believe this is fixed with PR #828. Please re-test and close.

jmsjr · 2018-03-07T22:16:13Z

Was the fix / latest master for TLS / SSL connections only ? Just an FYI .. I have not tried the latest from master ( still using release/0.14.0dev3 ), I just had this happen on a non-TLS / non-SSL connection as well:

  m  08:35:53|ethminer|  Speed  46.00 Mh/s    gpu/0 21.95 54C 60%   gpu/1 24.05 54C 60%   [A3118+0:R0+0:F0] Time: 37:18
  ℹ  08:35:53|stratum |  No new work received in 180  seconds.
  ℹ  08:35:53|stratum |  Disconnected from eth-pool.ucrypto.net
  ✘  08:35:53|stratum |  Retrying in 3 ...
  ✘  08:35:54|stratum |  Retrying in 2 ...
  ✘  08:35:55|stratum |  Retrying in 1 ...
  ✘  08:35:56|stratum |  Read response failed: Operation canceled
  m  08:35:58|ethminer|  not-connected

..snip..

  m  08:38:03|ethminer|  not-connected
  ✘  08:38:06|stratum |  Could not connect to stratum server eth-pool.ucrypto.net:8008, Connection timed out
  ℹ  08:38:06|stratum |  Disconnected from eth-pool.ucrypto.net
  ✘  08:38:06|stratum |  Retrying in 3 ...
  ✘  08:38:07|stratum |  Retrying in 2 ...
  m  08:38:08|ethminer|  not-connected
  ✘  08:38:08|stratum |  Retrying in 1 ...
  ✘  08:38:09|stratum |  Handle response failed: Broken pipe
  ✘  08:38:09|stratum |  Handle response failed: Operation canceled
  ✘  08:38:09|stratum |  Handle response failed: Operation canceled
...snip...
 m  08:40:18|ethminer|  not-connected
  ℹ  08:40:19|cl-0    |  Nonce 0xe81e7783964186aa submitted to eth-pool.ucrypto.net
  ✘  08:40:20|stratum |  Could not connect to stratum server eth-pool.ucrypto.net:8008, Connection timed out
  ℹ  08:40:20|stratum |  Disconnected from eth-pool.ucrypto.net
  ✘  08:40:20|stratum |  Retrying in 3 ...
  ✘  08:40:21|stratum |  Retrying in 2 ...
  ✘  08:40:22|stratum |  Retrying in 1 ...
  ✘  08:40:23|stratum |  Handle response failed: Broken pipe
  ✘  08:40:23|stratum |  Handle response failed: Operation canceled
  m  08:40:23|ethminer|  not-connected
  ℹ  08:40:23|stratum |  Connected to eth-pool.ucrypto.net
  ✘  08:40:23|stratum |  **Rejected  in 4073 ms.
  ✘  08:40:23|stratum |  Read response failed: Connection reset by peer
  ℹ  08:40:23|stratum |  Disconnected from eth-pool.ucrypto.net
  ✘  08:40:23|stratum |  Retrying in 3 ...
  ℹ  08:40:24|cl-0    |  Nonce 0xe81e77839c36240d submitted to eth-pool.ucrypto.net
./start_ucrypto.net-opencl.sh: line 16: 15424 Segmentation fault      (core dumped) bin/ethminer --farm-recheck 2000 -G --stratum eth-pool.ucrypto.net:8008 --userpass 0xeXXXXXXXXXX --stratum-protocol 1 --report-hashrate --verbosity 9 -HWMON 0 --cl-parallel-hash 8

satori-q3a · 2018-03-10T14:59:42Z

The windows version seems ok. My internet router lost connection and reconnected, ethminer 1.4.0 dev 3 was able to reestablish the nanopool connection.

jmsjr · 2018-03-13T12:33:48Z

I don't think this is fixed. I just built ethminer from master ( git commit hash de05cc3 )

bin/ethminer --version
ethminer version 0.14.0.dev3+git.de05cc3
Build: linux/release/gnu

I got this after about 1 hour running TLS on asia1.ethermine.org

 ℹ  23:28:15|cuda-1  |  Nonce 0xf02f5c9cf53d0272 submitted to asia1.ethermine.org
  m  23:28:16|ethminer|  Speed  56.88 Mh/s    gpu/0 28.44 50C 45% 90W  gpu/1 28.44 56C 75% 100W  [A58+2:R0+0:F0] Time: 01:13
  ✘  23:28:17|stratum |  No no response received in 2 seconds.
  ℹ  23:28:18|stratum |  Disconnected from asia1.ethermine.org
  ℹ  23:28:18|stratum |  Shutting down miners...
  ℹ  23:28:19|stratum |  Retrying in 3 ...
  ℹ  23:28:20|stratum |  Retrying in 2 ...
  m  23:28:21|ethminer|  not-connected 
  ℹ  23:28:21|stratum |  Retrying in 1 ...
./start_ethermine.org-cuda.sh: line 20:  5243 Segmentation fault      (core dumped) bin/ethminer --farm-recheck 2000 -U --stratum asia1.ethermine.org:5555 --stratum-failover us2.ethermine.org:5555 --userpass 0xexxxxxxxx --stratum-protocol 0 --report-hashrate --verbosity 9 -HW
MON 1 --stratum-ssl 0 --cuda-parallel-hash 6 --cuda-streams 4 --cuda-grid-size 4096

So it seems like ethminer decided to disconnect because it did not receive a response to the submission of a share after 2 seconds ...I thought I recall that previously, some of the accepted response from the pool was longer than 2 seconds.

P.S. As I type this, I got another one segfault due to that 2 seconds without response from pool on submission of a share.

Switching back to 0.14.0.dev3 release proper and without using TLS for now.

jmsjr · 2018-03-13T12:49:09Z

Also, I get segfault as well when simply hitting Ctrl-C:

  m  23:47:37|ethminer|  Speed  27.26 Mh/s    gpu/0 27.26 49C 48%   [A34+1:R0+0:F0] Time: 01:32
  m  23:47:42|ethminer|  Speed  27.18 Mh/s    gpu/0 27.18 49C 48%   [A34+1:R0+0:F0] Time: 01:32
  m  23:47:47|ethminer|  Speed  26.94 Mh/s    gpu/0 26.94 49C 48%   [A34+1:R0+0:F0] Time: 01:32
^C  ℹ  23:47:49|ethminer|  Shutting down...
  ✘  23:47:49|stratum |  Read response failed: End of file
./start_ethermine.org-opencl.sh: line 18:  5261 Segmentation fault      (core dumped) bin/ethminer --farm-recheck 2000 -G --stratum asia1.ethermine.org:5555 --stratum-failover us2.ethermine.org:5555 --userpass 0xxxxxx --stratum-protocol 0 --report-hashrate --verbosity 9 -HWMON 1 --stratum-ssl 0 --cl-parallel-hash 8

jmsjr · 2018-03-13T13:32:01Z

After switching back to 0.14.0dev3 release proper and WITHOUT using TLS, the console output shows the response from the pool for submitting a share received after more than 2 seconds ( 2.9 seconds ) without forcing ethminer to reconnect:

 ℹ  00:35:55|cuda-0  |  Nonce 0xc50898a1de3502c9 submitted to asia1.ethermine.org
  m  00:35:57|ethminer|  Speed  56.97 Mh/s    gpu/0 28.47 50C 45% 90W  gpu/1 28.50 55C 75% 102W  [A36+0:R0+0:F0] Time: 00:50
  ℹ  00:35:58|stratum |  Received new job #37a30f4f… from asia1.ethermine.org
  ℹ  00:35:58|stratum |  **Accepted  in 2938 ms.

I presume the reconnect if no response from the pool when submitting a share is a recent change after 0.14.0dev3 release proper.
Also, isn't 2 seconds a bit aggresive ?

Can we re-open this issue ?

jean-m-cyr closed this as completed Mar 10, 2018

jmsjr mentioned this issue Mar 14, 2018

Part 2 - 0.14.0.dev4 Segmentation fault when reconnecting to pool after connection was lost / disconnected #890

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

0.14.0.dev3 Segmentation fault when reconnecting to pool after connection was lost / disconnected. #848

0.14.0.dev3 Segmentation fault when reconnecting to pool after connection was lost / disconnected. #848

jmsjr commented Mar 5, 2018

DeadManWalkingTO commented Mar 5, 2018 •

edited

Loading

jmsjr commented Mar 5, 2018 •

edited

Loading

smurfy commented Mar 5, 2018

jean-m-cyr commented Mar 5, 2018

smurfy commented Mar 5, 2018

jean-m-cyr commented Mar 5, 2018 •

edited

Loading

smurfy commented Mar 5, 2018 •

edited

Loading

jean-m-cyr commented Mar 5, 2018 •

edited

Loading

jmsjr commented Mar 5, 2018 •

edited

Loading

jmsjr commented Mar 5, 2018 •

edited

Loading

jmsjr commented Mar 5, 2018

jean-m-cyr commented Mar 6, 2018 •

edited

Loading

jmsjr commented Mar 7, 2018

satori-q3a commented Mar 10, 2018

jmsjr commented Mar 13, 2018 •

edited

Loading

jmsjr commented Mar 13, 2018

jmsjr commented Mar 13, 2018 •

edited

Loading

0.14.0.dev3 Segmentation fault when reconnecting to pool after connection was lost / disconnected. #848

0.14.0.dev3 Segmentation fault when reconnecting to pool after connection was lost / disconnected. #848

Comments

jmsjr commented Mar 5, 2018

DeadManWalkingTO commented Mar 5, 2018 • edited Loading

jmsjr commented Mar 5, 2018 • edited Loading

smurfy commented Mar 5, 2018

jean-m-cyr commented Mar 5, 2018

smurfy commented Mar 5, 2018

jean-m-cyr commented Mar 5, 2018 • edited Loading

smurfy commented Mar 5, 2018 • edited Loading

jean-m-cyr commented Mar 5, 2018 • edited Loading

jmsjr commented Mar 5, 2018 • edited Loading

jmsjr commented Mar 5, 2018 • edited Loading

jmsjr commented Mar 5, 2018

jean-m-cyr commented Mar 6, 2018 • edited Loading

jmsjr commented Mar 7, 2018

satori-q3a commented Mar 10, 2018

jmsjr commented Mar 13, 2018 • edited Loading

jmsjr commented Mar 13, 2018

jmsjr commented Mar 13, 2018 • edited Loading

DeadManWalkingTO commented Mar 5, 2018 •

edited

Loading

jmsjr commented Mar 5, 2018 •

edited

Loading

jean-m-cyr commented Mar 5, 2018 •

edited

Loading

smurfy commented Mar 5, 2018 •

edited

Loading

jean-m-cyr commented Mar 5, 2018 •

edited

Loading

jmsjr commented Mar 5, 2018 •

edited

Loading

jmsjr commented Mar 5, 2018 •

edited

Loading

jean-m-cyr commented Mar 6, 2018 •

edited

Loading

jmsjr commented Mar 13, 2018 •

edited

Loading

jmsjr commented Mar 13, 2018 •

edited

Loading