Atix
Newbie
Offline
Activity: 36
Merit: 0
|
|
January 18, 2018, 08:22:36 AM |
|
Synchronisation seems to be stuck 09:20:57.177369 INFO Block <7b6a37885f3108c60435e8cffa163e5801f979ba4d2c9b9422b23ea1c7c28cff> has at least one transaction with wrong inputs: <f8eac773a1882a670fa0d77c644e0496b5297756425f9a50dd6ce0ab115b21a4>
|
|
|
|
entropy0
Full Member
Offline
Activity: 412
Merit: 100
Que sera sera
|
|
January 18, 2018, 12:29:52 PM |
|
well... hoping this is still going
created pool @ http://egano.cryptonight.me/there seem to be issues with the source as mentioned above 12:35:06.675863 INFO Block <339d9b8c5339614b44cdf4d8a39d9426dec0ceddb8b9749572d804fd20f9225f> has at least one transaction with wrong inputs: <eef6894b93a5df7660028a5fc6f675601ec9c01c493803ebd06a9b3a63d5b882> 2018-01-18 12:37:09 [pool] (Thread 2) Error submitting block at height 29062 from [s]abcd1@123[/s], share type: "trusted" - {"code":-7,"message":"Block not accepted"}
|
|
|
|
egano (OP)
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 18, 2018, 02:51:25 PM |
|
well... hoping this is still going
created pool @ http://egano.cryptonight.me/there seem to be issues with the source as mentioned above 12:35:06.675863 INFO Block <339d9b8c5339614b44cdf4d8a39d9426dec0ceddb8b9749572d804fd20f9225f> has at least one transaction with wrong inputs: <eef6894b93a5df7660028a5fc6f675601ec9c01c493803ebd06a9b3a63d5b882> 2018-01-18 12:37:09 [pool] (Thread 2) Error submitting block at height 29062 from [s]abcd1@123[/s], share type: "trusted" - {"code":-7,"message":"Block not accepted"} Thanks for the hard work on this. One of our nodes got stuck too while other kept syncing. See latest release of the daemon, added a lot of improvements, mostly previous fixes already applied to Bytecoin. Re-sync using the new version and you should be able to continue on height 29063. The solo mining feature was moved from eganod daemon to miner executable.
|
|
|
|
egano (OP)
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 18, 2018, 03:00:12 PM Last edit: January 18, 2018, 03:26:49 PM by egano |
|
Synchronisation seems to be stuck 09:20:57.177369 INFO Block <7b6a37885f3108c60435e8cffa163e5801f979ba4d2c9b9422b23ea1c7c28cff> has at least one transaction with wrong inputs: <f8eac773a1882a670fa0d77c644e0496b5297756425f9a50dd6ce0ab115b21a4>
Seems to be the mempool issue. After deleting everything from /home/user/.egano except blocks.dat and p2pstate.bin the sync should continue. You may get warnings of invalid transactions, those can be ignored, will be removed from any mempool they come from after one day. Anyway, use the new version of the daemon released today.
|
|
|
|
MrCross
Newbie
Offline
Activity: 9
Merit: 0
|
|
January 18, 2018, 06:26:31 PM |
|
I updated the daemon (eganod) and the wallet (simplewallet), but now i have no balance anymore in my wallet!! how can this be? is it a other chain?! I'm getting an Error now:
root@Powerstation:/home/egano# ./simplewallet --wallet-file wallet.bin 2018-Jan-18 19:22:53.588262 INFO egano wallet v1.2.1 (cb69fc5-dirty) password: *************** 2018-Jan-18 19:23:00.262901 INFO Loading wallet... 2018-Jan-18 19:23:00.289744 INFO Opened wallet: abcd1wxyz5QbwthtATNeP4fwiu9MGL2dxbv63cji7vbrjmqCPGu5NyYjUXs4zZCJt1UsDvVa5mGqEJK Mro1zZrWdeJec4dkTDWY2FBLb 2018-Jan-18 19:23:00.290579 INFO ********************************************************************** Use "help" command to see the list of available commands. ********************************************************************** 2018-Jan-18 19:23:00.297307 ERROR [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error
[wallet abcd1w]: 2018-Jan-18 19:25:10.664143 ERROR [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error
AND in the daemon: root@Powerstation:/home/egano# ./eganod 2018-Jan-18 19:29:38.406739 INFO egano v1.2.1 (cb69fc5-dirty) 2018-Jan-18 19:29:38.407183 INFO Module folder: ./eganod 2018-Jan-18 19:29:38.407602 INFO Opening DB in /root/.egano/DB 2018-Jan-18 19:29:38.418592 INFO DB opened in /root/.egano/DB 2018-Jan-18 19:29:38.420637 INFO Initializing core... 2018-Jan-18 19:29:38.423122 INFO Core initialized OK 2018-Jan-18 19:29:38.423354 INFO Initializing p2p server... 2018-Jan-18 19:29:38.519823 ERROR Failed to resolve host name 'seed1.egano.net': Ipv4Resolver::resolve, getaddrinfo failed, result=-2, Unknown error -2 2018-Jan-18 19:29:38.600955 ERROR Failed to resolve host name 'seed2.egano.net': Ipv4Resolver::resolve, getaddrinfo failed, result=-2, Unknown error -2 2018-Jan-18 19:29:38.681747 ERROR Failed to resolve host name 'seed3.egano.net': Ipv4Resolver::resolve, getaddrinfo failed, result=-2, Unknown error -2 2018-Jan-18 19:29:38.682565 INFO Binding on 0.0.0.0:47767 2018-Jan-18 19:29:38.682920 INFO Net service bound on 0.0.0.0:47767 2018-Jan-18 19:29:38.683099 INFO Attempting to add IGD port mapping. 2018-Jan-18 19:29:41.823252 INFO UPnP device was found but not recoginzed as IGD. 2018-Jan-18 19:29:41.823674 INFO P2p server initialized OK 2018-Jan-18 19:29:41.824229 INFO Starting core rpc server on address 127.0.0.1:47867 2018-Jan-18 19:29:41.824556 INFO Core rpc server started ok 2018-Jan-18 19:29:41.824758 INFO Starting p2p net loop... 2018-Jan-18 19:29:41.824991 INFO Starting node_server
|
|
|
|
egano (OP)
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 18, 2018, 06:30:32 PM |
|
I updated the daemon (eganod) and the wallet (simplewallet), but now i have no balance anymore in my wallet!! how can this be? is it a other chain?!
Use reset command in simplewallet. It should recalculate the balance.
|
|
|
|
MrCross
Newbie
Offline
Activity: 9
Merit: 0
|
|
January 18, 2018, 06:32:44 PM |
|
I updated the daemon (eganod) and the wallet (simplewallet), but now i have no balance anymore in my wallet!! how can this be? is it a other chain?!
Use reset command in simplewallet. It should recalculate the balance. "Reset completed succesfully" - but no balance... with "list_transfers" I get "2018-Jan-18 19:30:55.127301 INFO No transfers"... I had > 0.002 !!!
|
|
|
|
egano (OP)
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 18, 2018, 06:37:41 PM |
|
AND in the daemon: root@Powerstation:/home/egano# ./eganod 2018-Jan-18 19:29:38.406739 INFO egano v1.2.1 (cb69fc5-dirty) 2018-Jan-18 19:29:38.407183 INFO Module folder: ./eganod 2018-Jan-18 19:29:38.407602 INFO Opening DB in /root/.egano/DB 2018-Jan-18 19:29:38.418592 INFO DB opened in /root/.egano/DB 2018-Jan-18 19:29:38.420637 INFO Initializing core... 2018-Jan-18 19:29:38.423122 INFO Core initialized OK 2018-Jan-18 19:29:38.423354 INFO Initializing p2p server... 2018-Jan-18 19:29:38.519823 ERROR Failed to resolve host name 'seed1.egano.net': Ipv4Resolver::resolve, getaddrinfo failed, result=-2, Unknown error -2 2018-Jan-18 19:29:38.600955 ERROR Failed to resolve host name 'seed2.egano.net': Ipv4Resolver::resolve, getaddrinfo failed, result=-2, Unknown error -2 2018-Jan-18 19:29:38.681747 ERROR Failed to resolve host name 'seed3.egano.net': Ipv4Resolver::resolve, getaddrinfo failed, result=-2, Unknown error -2 2018-Jan-18 19:29:38.682565 INFO Binding on 0.0.0.0:47767 2018-Jan-18 19:29:38.682920 INFO Net service bound on 0.0.0.0:47767 2018-Jan-18 19:29:38.683099 INFO Attempting to add IGD port mapping. 2018-Jan-18 19:29:41.823252 INFO UPnP device was found but not recoginzed as IGD. 2018-Jan-18 19:29:41.823674 INFO P2p server initialized OK 2018-Jan-18 19:29:41.824229 INFO Starting core rpc server on address 127.0.0.1:47867 2018-Jan-18 19:29:41.824556 INFO Core rpc server started ok 2018-Jan-18 19:29:41.824758 INFO Starting p2p net loop... 2018-Jan-18 19:29:41.824991 INFO Starting node_server
This is part of normal startup, disregard the three node errors. Use set_log 3 (or 4) command for verbose logging if it hung there. Did you see syncing on first run? Don't be afraid of the wallet, as long as you have wallet file, you are safe, there is no other chain.
|
|
|
|
MrCross
Newbie
Offline
Activity: 9
Merit: 0
|
|
January 18, 2018, 06:43:02 PM |
|
AND in the daemon: root@Powerstation:/home/egano# ./eganod 2018-Jan-18 19:29:38.406739 INFO egano v1.2.1 (cb69fc5-dirty) 2018-Jan-18 19:29:38.407183 INFO Module folder: ./eganod 2018-Jan-18 19:29:38.407602 INFO Opening DB in /root/.egano/DB 2018-Jan-18 19:29:38.418592 INFO DB opened in /root/.egano/DB 2018-Jan-18 19:29:38.420637 INFO Initializing core... 2018-Jan-18 19:29:38.423122 INFO Core initialized OK 2018-Jan-18 19:29:38.423354 INFO Initializing p2p server... 2018-Jan-18 19:29:38.519823 ERROR Failed to resolve host name 'seed1.egano.net': Ipv4Resolver::resolve, getaddrinfo failed, result=-2, Unknown error -2 2018-Jan-18 19:29:38.600955 ERROR Failed to resolve host name 'seed2.egano.net': Ipv4Resolver::resolve, getaddrinfo failed, result=-2, Unknown error -2 2018-Jan-18 19:29:38.681747 ERROR Failed to resolve host name 'seed3.egano.net': Ipv4Resolver::resolve, getaddrinfo failed, result=-2, Unknown error -2 2018-Jan-18 19:29:38.682565 INFO Binding on 0.0.0.0:47767 2018-Jan-18 19:29:38.682920 INFO Net service bound on 0.0.0.0:47767 2018-Jan-18 19:29:38.683099 INFO Attempting to add IGD port mapping. 2018-Jan-18 19:29:41.823252 INFO UPnP device was found but not recoginzed as IGD. 2018-Jan-18 19:29:41.823674 INFO P2p server initialized OK 2018-Jan-18 19:29:41.824229 INFO Starting core rpc server on address 127.0.0.1:47867 2018-Jan-18 19:29:41.824556 INFO Core rpc server started ok 2018-Jan-18 19:29:41.824758 INFO Starting p2p net loop... 2018-Jan-18 19:29:41.824991 INFO Starting node_server
This is part of normal startup, disregard the three node errors. Use set_log 3 (or 4) command for verbose logging if it hung there. Did you see syncing on first run? Don't be afraid of the wallet, as long as you have wallet file, you are safe, there is no other chain. I just resyncd the whole chain - no errors in daemon anymore. BUT wallet still says, that there are no transfers (list_transfers), no balance (balance) and a reset doesn't change anything. current bc_height 29076... PLEASE HELP! mining also does not work anymore... I want the old version back.
|
|
|
|
egano (OP)
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 18, 2018, 06:51:18 PM |
|
I just resyncd the whole chain - no errors in daemon anymore. BUT wallet still says, that there are no transfers (list_transfers), no balance (balance) and a reset doesn't change anything. current bc_height 29076... PLEASE HELP! mining also does not work anymore... I want the old version back. That's weird. Reset usually takes few minutes to rescan all blocks. Close wallet, stop daemon. Open wallet, reset, close wallet. Run daemon again and once it is up open wallet and give it a few minutes to scan the chain.
|
|
|
|
|
MrCross
Newbie
Offline
Activity: 9
Merit: 0
|
|
January 18, 2018, 06:57:03 PM |
|
I just resyncd the whole chain - no errors in daemon anymore. BUT wallet still says, that there are no transfers (list_transfers), no balance (balance) and a reset doesn't change anything. current bc_height 29076... PLEASE HELP! mining also does not work anymore... I want the old version back. That's weird. Reset usually takes few minutes to rescan all blocks. Close wallet, stop daemon. Open wallet, reset, close wallet. Run daemon again and once it is up open wallet and give it a few minutes to scan the chain. don't know why, but this method helped! THANK YOU VERY MUCH! now there's only the problem with mining: [wallet abcd1w]: start_mining 4 2018-Jan-18 19:55:49.450566 ERROR Error: Failed to invoke rpc method: HTTP status: 1
|
|
|
|
egano (OP)
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 18, 2018, 06:59:17 PM |
|
now there's only the problem with mining: [wallet abcd1w]: start_mining 4 2018-Jan-18 19:55:49.450566 ERROR Error: Failed to invoke rpc method: HTTP status: 1
That's intentional (but not fixed in the daemon) Use miner from the post above
|
|
|
|
Jucrypto
Newbie
Offline
Activity: 18
Merit: 10
|
|
January 18, 2018, 07:02:02 PM |
|
Hello all, @egano Do you need german translation ? (WP, ANN,WWW). Thanks
|
|
|
|
entropy0
Full Member
Offline
Activity: 412
Merit: 100
Que sera sera
|
|
January 18, 2018, 08:21:22 PM Last edit: January 18, 2018, 10:23:19 PM by entropy0 |
|
Good job dev, seem to have fixed the chain However it seems to be issues with found blocks http://egano.cryptonight.me/#pool_blocksFrom daemon: 2018-Jan-18 20:47:52.032865 WARNING Transaction b1f9ed39f37cce35871414092572ad4c593f849621ed87ca11c0f5986568b42b is not valid. Reason: Transaction uses spent key image 2018-Jan-18 20:47:52.032927 INFO [185.34.216.108:47767 OUT] Tx verification failed
|
|
|
|
egano (OP)
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 19, 2018, 10:34:01 AM |
|
Hello all, @egano Do you need german translation ? (WP, ANN,WWW). Thanks Yes, this is planned further. Chinese would be a bit more effective, this is not ICO so it might be accepted by Asian community too. PM me with your offer. Before spreading to more general public, a lot of development has to be done though.
|
|
|
|
egano (OP)
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 19, 2018, 10:42:33 AM |
|
Good job dev, seem to have fixed the chain However it seems to be issues with found blocks http://egano.cryptonight.me/#pool_blocksFrom daemon: 2018-Jan-18 20:47:52.032865 WARNING Transaction b1f9ed39f37cce35871414092572ad4c593f849621ed87ca11c0f5986568b42b is not valid. Reason: Transaction uses spent key image 2018-Jan-18 20:47:52.032927 INFO [185.34.216.108:47767 OUT] Tx verification failed Chain seems fixed indeed and both version 1.1 and 1.2 of daemon now can sync, 28 blocks mined earlier around 29056-29084 became orphaned. Anyone who sent transactions yesterday should reset their wallet in the way MrCross did few posts above. Don't worry of the invalid tx, it will be rejected until it completely disappears by expiring from the last mempool. We are now above 31000. Thanks everyone for mining!
|
|
|
|
entropy0
Full Member
Offline
Activity: 412
Merit: 100
Que sera sera
|
|
January 19, 2018, 01:13:26 PM |
|
Good job dev, seem to have fixed the chain However it seems to be issues with found blocks http://egano.cryptonight.me/#pool_blocksFrom daemon: 2018-Jan-18 20:47:52.032865 WARNING Transaction b1f9ed39f37cce35871414092572ad4c593f849621ed87ca11c0f5986568b42b is not valid. Reason: Transaction uses spent key image 2018-Jan-18 20:47:52.032927 INFO [185.34.216.108:47767 OUT] Tx verification failed Chain seems fixed indeed and both version 1.1 and 1.2 of daemon now can sync, 28 blocks mined earlier around 29056-29084 became orphaned. Anyone who sent transactions yesterday should reset their wallet in the way MrCross did few posts above. Don't worry of the invalid tx, it will be rejected until it completely disappears by expiring from the last mempool. We are now above 31000. Thanks everyone for mining! well i tried to, seems like simplewallet cant open the wallet file... the issue with Tx fail is that pool sees it as invalid and therefore can not pay miners
|
|
|
|
MrCross
Newbie
Offline
Activity: 9
Merit: 0
|
|
January 19, 2018, 04:51:18 PM |
|
Seems like this pool ( http://egano.cryptonight.me/) got every Single Block in the last time. I would mine at this pool, but it seems like it's not paying. Am I right?
|
|
|
|
egano (OP)
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 19, 2018, 05:10:30 PM Last edit: January 19, 2018, 06:19:57 PM by egano |
|
Good job dev, seem to have fixed the chain However it seems to be issues with found blocks http://egano.cryptonight.me/#pool_blocksFrom daemon: 2018-Jan-18 20:47:52.032865 WARNING Transaction b1f9ed39f37cce35871414092572ad4c593f849621ed87ca11c0f5986568b42b is not valid. Reason: Transaction uses spent key image 2018-Jan-18 20:47:52.032927 INFO [185.34.216.108:47767 OUT] Tx verification failed Chain seems fixed indeed and both version 1.1 and 1.2 of daemon now can sync, 28 blocks mined earlier around 29056-29084 became orphaned. Anyone who sent transactions yesterday should reset their wallet in the way MrCross did few posts above. Don't worry of the invalid tx, it will be rejected until it completely disappears by expiring from the last mempool. We are now above 31000. Thanks everyone for mining! well i tried to, seems like simplewallet cant open the wallet file... the issue with Tx fail is that pool sees it as invalid and therefore can not pay miners What happens when you manually send payment from one of your wallets to another? Does it say Money successfully sent, Transaction too big, Internal node error or sth else? My experience from one of my wallets is that when it generates a tx, it is accepted by the daemon but another node logs invalid transaction. The transaction gets to the mempool and is mined by the cryptonight pool. We will look into this further anyway, the blockchain cannot have double spends mined, at least not in the future.
|
|
|
|
|