Topic: Lunatics - LTSX - Rare like the Moon - CryptoNight Algo |CPU - GPU| - page 15. (Read 15719 times)
August 03, 2017, 06:16:38 PM
You cant connect Claykore because its only for pool!!! Only solo mining until we get pool
August 03, 2017, 06:14:03 PM
It made me remember good old days, and the adrenalin of start mining
Nice
Nice
August 03, 2017, 06:12:15 PM
I get this too, but it eventually reconnects.
Looks like mine finally dialed in as well.
run the daemon and then open the wallet to get your address. Then in the daemon window type start_mining
That will get you going. I, also, typed show_hr just to see that it is running.
Inside the folder that you unzipped, open the file daemon.exe. Run that before the wallet then setup the wallet.
August 03, 2017, 06:11:11 PM
Code:
Job timeout, disconnect, retry in 20 sec...
GPU0 t=44C fan=0%, GPU1 t=43C fan=0%
Stratum - connecting to '127.0.0.1' <127.0.0.1> port 31696 (unsecure)
Stratum - Connected (unsecure)
GPU0 t=44C fan=0%, GPU1 t=43C fan=0%
Job timeout, disconnect, retry in 20 sec...
GPU0 t=44C fan=0%, GPU1 t=42C fan=0%
Stratum - connecting to '127.0.0.1' <127.0.0.1> port 31696 (unsecure)
Stratum - Connected (unsecure)
GPU0 t=44C fan=0%, GPU1 t=42C fan=0%
Job timeout, disconnect, retry in 20 sec...
That's when trying to use the following as my config for Claymore:
Code:
-o daemon+tcp://127.0.0.1:31696
-u FUR7dJL-morelettersandnumbersandstuff
-p x
-allpools 1
-tt 76
August 03, 2017, 06:09:54 PM
Any airdrops for lunatics in sight?
August 03, 2017, 06:08:12 PM
For GPU maybe pool.
August 03, 2017, 06:06:35 PM
i got the same messages but you aslo can found blocks i found 1 bbut how we can min with gpu? 
bbut how we can min with gpu? August 03, 2017, 06:04:12 PM
I get this too, but it eventually reconnects.
Looks like mine finally dialed in as well.
run the daemon and then open the wallet to get your address. Then in the daemon window type start_mining
That will get you going. I, also, typed show_hr just to see that it is running.
August 03, 2017, 06:03:01 PM
I get this too, but it eventually reconnects.
Looks like mine finally dialed in as well.
run the daemon and then open the wallet to get your address. Then in the daemon window type start_mining
That will get you going. I, also, typed show_hr just to see that it is running.
August 03, 2017, 06:02:12 PM
no, you will mine nothing, because there is no peer there is no node
August 03, 2017, 05:59:14 PM
I get this too, but it eventually reconnects.
Looks like mine finally dialed in as well.
August 03, 2017, 05:54:04 PM
I get this too, but it eventually reconnects.
Looks like mine finally dialed in as well.
August 03, 2017, 05:53:38 PM
start_mining Start mining for specified address, start_mining [threads=1]
stop_mining Stop mining
there is not possible to run this commands in linux because forknoted version dont have mining in daemon What a noob dev, what a noob coin. Again scam and copy paste coin. Bye bye
stop_mining Stop mining
there is not possible to run this commands in linux because forknoted version dont have mining in daemon
What a noob dev, what a noob coin. Again scam and copy paste coin. Bye bye August 03, 2017, 05:50:10 PM
Well. . . . Doesn't seem to be blocked by firewall.
Code:
2017-Aug-03 17:40:30.821713 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:40:46.165590 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:40:46.177591 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:40:58.550299 ERROR [212.24.96.108:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connec
tion.
2017-Aug-03 17:40:58.561299 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:41:13.911177 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:41:13.922178 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:41:26.275885 ERROR [212.24.96.108:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connec
tion.
2017-Aug-03 17:41:26.287885 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:41:41.630763 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:41:41.641763 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:41:53.983469 ERROR [212.24.96.108:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connec
tion.
2017-Aug-03 17:41:53.997470 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:42:09.341348 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:42:09.350348 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:42:16.290745 WARNING [85.238.75.1:31695 OUT] Exception in connectionHandler: TcpConnection::read,
WSAGetOverlappedResult failed, result=10054, An existing connection was forcibly closed by the remote host.
I get this too, but it eventually reconnects.
August 03, 2017, 05:48:58 PM
Well. . . . Doesn't seem to be blocked by firewall.
have same problem Code:
2017-Aug-03 17:40:30.821713 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:40:46.165590 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:40:46.177591 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:40:58.550299 ERROR [212.24.96.108:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connec
tion.
2017-Aug-03 17:40:58.561299 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:41:13.911177 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:41:13.922178 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:41:26.275885 ERROR [212.24.96.108:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connec
tion.
2017-Aug-03 17:41:26.287885 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:41:41.630763 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:41:41.641763 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:41:53.983469 ERROR [212.24.96.108:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connec
tion.
2017-Aug-03 17:41:53.997470 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:42:09.341348 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:42:09.350348 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:42:16.290745 WARNING [85.238.75.1:31695 OUT] Exception in connectionHandler: TcpConnection::read,
WSAGetOverlappedResult failed, result=10054, An existing connection was forcibly closed by the remote host.
August 03, 2017, 05:47:12 PM
i got failed to handshake with peer error what to do?
August 03, 2017, 05:45:42 PM
WHERE TO SELL?
Currently this is a new born project, we don't have LTSX on any exchange for now.
Do you wanna sell? Still? PM me, I'll buy your coins for 0.05$ each!
Do you wanna buy? PM me, I sell those for 0.25$ each!
More pay for electric current
waste of time
Currently this is a new born project, we don't have LTSX on any exchange for now.
Do you wanna sell? Still? PM me, I'll buy your coins for 0.05$ each!
Do you wanna buy? PM me, I sell those for 0.25$ each!
More pay for electric current
waste of time
August 03, 2017, 05:45:23 PM
Well. . . . Doesn't seem to be blocked by firewall.
Code:
2017-Aug-03 17:40:30.821713 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:40:46.165590 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:40:46.177591 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:40:58.550299 ERROR [212.24.96.108:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connec
tion.
2017-Aug-03 17:40:58.561299 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:41:13.911177 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:41:13.922178 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:41:26.275885 ERROR [212.24.96.108:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connec
tion.
2017-Aug-03 17:41:26.287885 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:41:41.630763 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:41:41.641763 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:41:53.983469 ERROR [212.24.96.108:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connec
tion.
2017-Aug-03 17:41:53.997470 WARNING Failed to HANDSHAKE with peer 212.24.96.108:31695
2017-Aug-03 17:42:09.341348 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing conne
ction.
2017-Aug-03 17:42:09.350348 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-03 17:42:16.290745 WARNING [85.238.75.1:31695 OUT] Exception in connectionHandler: TcpConnection::read,
WSAGetOverlappedResult failed, result=10054, An existing connection was forcibly closed by the remote host.
August 03, 2017, 05:45:05 PM
2017-Aug-04 00:42:23.437385 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-04 00:42:27.821869 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-04 00:42:53.140564 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-04 00:42:53.145578 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-04 00:43:15.293107 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-04 00:43:20.500840 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-04 00:44:01.907511 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-04 00:44:01.914027 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-04 00:44:30.285066 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-04 00:44:34.107511 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-04 00:42:27.821869 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-04 00:42:53.140564 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-04 00:42:53.145578 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-04 00:43:15.293107 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-04 00:43:20.500840 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-04 00:44:01.907511 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-04 00:44:01.914027 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
2017-Aug-04 00:44:30.285066 ERROR [194.135.81.142:31695 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-04 00:44:34.107511 WARNING Failed to HANDSHAKE with peer 194.135.81.142:31695
August 03, 2017, 05:44:27 PM
For folks with the broken file problem:
Just figured it out. WinRAR5 was used to compress it. I had v4. Got a portable version of WinRAR 5.4 and it worked immediately.
Works. Ths. Just figured it out. WinRAR5 was used to compress it. I had v4. Got a portable version of WinRAR 5.4 and it worked immediately.
Jump to: