Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash after pool socket close with Windows executable #27

Open
use-dashes-instead opened this issue Sep 28, 2019 · 0 comments
Open

Crash after pool socket close with Windows executable #27

use-dashes-instead opened this issue Sep 28, 2019 · 0 comments

Comments

@use-dashes-instead
Copy link

I have been getting this error seemingly at random. I got it in 2.1 as well as in 2.2. Using the Windows executable with xmrig-amd.

!!! Pool (gulf.moneroocean.stream:10016) <-> miner link was broken due to closed miner socket
[2019-09-28 17:11:56] no active pools, stop mining
!!! Pool (gulf.moneroocean.stream:10016) socket error
!!! Pool (us.moneroocean.stream:10016) socket error
!!! Pool (ca.moneroocean.stream:10016) socket error
net.js:1048
throw new RangeError('"port" option should be >= 0 and < 65536: ' + port);
^

RangeError: "port" option should be >= 0 and < 65536: 100161
at lookupAndConnect (net.js:1048:13)
at Socket.connect (net.js:1021:5)
at Object.connect (net.js:113:35)
at connect_pool (C:\snapshot\meta-miner\mm.js:400:91)
at pool_err (C:\snapshot\meta-miner\mm.js:550:5)
at Socket. (C:\snapshot\meta-miner\mm.js:452:5)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant