search

JuicyPasta / Claymore-No-Fee-Proxy

Removes Claymore's 1-2% mining fee
138 stars 67 forks source link

Failed to listen on (localhost:port) #11

Open ROdoka opened 7 years ago

ROdoka commented 7 years ago

Hey :) I used the previous version since a few days ago and edited the code myself to use the correct worker. Now there's this new version and with this one I get

[!!] Failed to listen on 127.0.0.1:portnumber [!!] Check for other listening sockets or stopping mining - datecode

but the script seems to work I think. IMO it has to do with removing/altering the receive_first part, because I can't think of anything else?

extra info: I've edited the claymore epools.txt file and replaced all nanopool servers with "fake" ones, which I also added to the hosts file in Windows.

Any solution or reason why I see this message? BTW: I also re-added my previous change about entering the worker_name via command line, but this is not causing the message.

ROdoka commented 7 years ago

some more info: I just tried it on a different PC, same hosts file entries, same python-script and the message does not appear. What could be the issue?

ROdoka commented 7 years ago

after trying a lot of things I did the easiest of all: I rebooted -_- Problem gone ... Sorry for opening an issue case for nothing!

ROdoka commented 7 years ago

ok, I'll reopen this. no big issue, but I'm a bit helpless at the moment. The problem above occured again and I think I found the reason: it's due to python still being active if proxy was killed via ctrl+c after killing the process the error message does not come back.

How the script be closed correctly so that python closes itself, too?

drdada commented 7 years ago

Hello, Yes if you launch multiple instance of the script you will get this message because the localport is already in use. I guess you use Windows OS, if you want to close the python script, you just have to close its windows. If you want to make sure it's closed, go to task manager and check if you see python.exe process. CTRL+C isn't working on Windows at the moment. For linux users, CTRL+C will do the trick. I will flag the issue and see if i can handle CTRL+C in windows.

ROdoka commented 7 years ago

Hey :) I can't remember if I hit Ctrl+C or Ctrl+Break, somehow I think Ctrl+C was breaking it on one Windows PC. But that's the weird thing: after Ctrl+Break and closing the CMD window, Python still was visible in taskman until I killed it manually. But this didn't happen on my 2nd Windows PC (both run W7 x64).

Would it work if you listen to a key in the script, for example 'q'? I've never written anything in Python, so I don't know :D

drdada commented 7 years ago

You should try to disable the QuickEdit option in the CMD properties. FYI in python the CTRL+Break close the script.