Bitcoin Forum
April 19, 2019, 05:40:11 PM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 [81] 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 ... 219 »
  Print  
Author Topic: [ANN] DERO: DAG + Cryptonote + Bulletproofs + SSL + POW + Smart Contracts  (Read 80902 times)
cotinco
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
March 01, 2018, 10:58:05 AM
 #1601

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Sad Regardless of that, the rest of network is probably synchronized.

Did you delete or replace data.mdb as I emphasized a page back?


It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.
1555695611
Hero Member
*
Offline Offline

Posts: 1555695611

View Profile Personal Message (Offline)

Ignore
1555695611
Reply with quote  #2

1555695611
Report to moderator
1555695611
Hero Member
*
Offline Offline

Posts: 1555695611

View Profile Personal Message (Offline)

Ignore
1555695611
Reply with quote  #2

1555695611
Report to moderator
1555695611
Hero Member
*
Offline Offline

Posts: 1555695611

View Profile Personal Message (Offline)

Ignore
1555695611
Reply with quote  #2

1555695611
Report to moderator
100% New Software
PC, Mac, Android, & HTML5 Clients
Krill Rakeback
Low Rake
Bitcoin Poker 3.0
Bad Beat Jackpot
SwC Poker Relaunch
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1555695611
Hero Member
*
Offline Offline

Posts: 1555695611

View Profile Personal Message (Offline)

Ignore
1555695611
Reply with quote  #2

1555695611
Report to moderator
1555695611
Hero Member
*
Offline Offline

Posts: 1555695611

View Profile Personal Message (Offline)

Ignore
1555695611
Reply with quote  #2

1555695611
Report to moderator
1555695611
Hero Member
*
Offline Offline

Posts: 1555695611

View Profile Personal Message (Offline)

Ignore
1555695611
Reply with quote  #2

1555695611
Report to moderator
MagicSmoker
Full Member
***
Offline Offline

Activity: 420
Merit: 175



View Profile
March 01, 2018, 11:02:17 AM
 #1602

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Sad Regardless of that, the rest of network is probably synchronized.

Did you delete or replace data.mdb as I emphasized a page back?


It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.

Oh, it seems I am the one that should have read more carefully!  Tongue

You are referring to external nodes - including some in Speedie's priority network - as still being out of sync. Hmm, we have now reached my level of incompetency so I'll defer to the experts but my suspicion is that this is a non-issue for now, though the only evidence I have for that is my daemon/wallet is still sync'ed up and working fine.


--Serena--
Member
**
Offline Offline

Activity: 224
Merit: 11


View Profile
March 01, 2018, 11:39:38 AM
 #1603

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Sad Regardless of that, the rest of network is probably synchronized.

Did you delete or replace data.mdb as I emphasized a page back?


It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.

Hi Cotinco,

It's a little bit early here so I'm sorry if I missed anything. I've been looking into the priority nodes and they appear to be in sync at the moment.

I ran into the blockchain sync issue myself yesterday and found that deleting the p2pstate.bin and the imbd file did it for me. However, YMMV and I'm willing to do what it takes to help you get up and running to your satisfaction. It's still about 3am here so when I'm online in 4 - 5 hours I will be available again for the day on Slack at your convenience.

It sounds like your file may be corrupted. I just resynced my blockchain before I started this post to confirm that it's updating correctly with the new nodes. Perhaps try running the following in your command interface when you're ready to start fresh.

derod.exe --add-priority-node 89.38.97.110:18090 --add-priority-node 212.8.242.60:18090 --add-priority-node 85.217.170.245:18090 --add-priority-node 89.38.96.169:18090 --add-priority-node 45.63.6.91:18090 --add-priority-node 108.61.220.229:18090 --add-priority-node 207.148.5.250:18090 --add-priority-node 45.77.89.64:18090  --add-priority-node 45.76.42.165:18090  --add-priority-node 45.77.242.137:18090
Speedie
Sr. Member
****
Offline Offline

Activity: 504
Merit: 254


View Profile
March 01, 2018, 11:47:53 AM
 #1604

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Sad Regardless of that, the rest of network is probably synchronized.

Did you delete or replace data.mdb as I emphasized a page back?


It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.

Good morning! Just checked all 6 nodes and they're at the same height as the official pool. Are you still seeing something different?
MagicSmoker
Full Member
***
Offline Offline

Activity: 420
Merit: 175



View Profile
March 01, 2018, 11:59:26 AM
 #1605

It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.

Good morning! Just checked all 6 nodes and they're at the same height as the official pool. Are you still seeing something different?


You typed too soon, methinks... I've got 7 alternate chains showing up in my daemon (alt_chain_info) and the main pool is once again not updating stats. However, mining still seems to be working there and I just received a payment a few minutes ago.

--Serena--
Member
**
Offline Offline

Activity: 224
Merit: 11


View Profile
March 01, 2018, 12:07:29 PM
 #1606

Height: 40674/40674 (100.0%) on mainnet, not mining, net hash 4.55 MH/s, v6, update needed, 8(out)+13(in) connections, uptime 0d 0h 33m 54s

The worker stats on the official pool aren't related to a daemon sync issue but I have let support know

The official priority nodes, including the ones Speedie added appear to be in sync at this time. We do understand that there may still be some hiccups and are diligently working to provide effective solutions to anyone who may still need assistance.

I'm here for as long as anyone needs me.
cotinco
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
March 01, 2018, 12:40:21 PM
 #1607

Height: 40674/40674 (100.0%) on mainnet, not mining, net hash 4.55 MH/s, v6, update needed, 8(out)+13(in) connections, uptime 0d 0h 33m 54s

The worker stats on the official pool aren't related to a daemon sync issue but I have let support know

The official priority nodes, including the ones Speedie added appear to be in sync at this time. We do understand that there may still be some hiccups and are diligently working to provide effective solutions to anyone who may still need assistance.

I'm here for as long as anyone needs me.


Can I just throw a hypothesis? I'm not sure that it is true because I'm very new to the cryptocurrency world, but at least an idea.
Seems that using --add-priority-node decreases diversity the network and creates heavy load on these priority nodes added by a lot of participants, so they could not handle the large traffic.
Is it possible that the network is better without any priority nodes?
May the problems had been arisen (or the things got worse) when the first bunch of priority nodes appeared?
How other networks based on monero (e.g. sumo, etn) do exist without any priority nodes and with a quite number of alternatives according to daemons' logs?

P.S. Sorry for writing this early morning but seems we're in completely different time zones.
--Serena--
Member
**
Offline Offline

Activity: 224
Merit: 11


View Profile
March 01, 2018, 12:50:24 PM
Last edit: March 01, 2018, 01:48:09 PM by --Serena--
 #1608

Height: 40674/40674 (100.0%) on mainnet, not mining, net hash 4.55 MH/s, v6, update needed, 8(out)+13(in) connections, uptime 0d 0h 33m 54s

The worker stats on the official pool aren't related to a daemon sync issue but I have let support know

The official priority nodes, including the ones Speedie added appear to be in sync at this time. We do understand that there may still be some hiccups and are diligently working to provide effective solutions to anyone who may still need assistance.

I'm here for as long as anyone needs me.


Can I just throw a hypothesis? I'm not sure that it is true because I'm very new to the cryptocurrency world, but at least an idea.
Seems that using --add-priority-node decreases diversity the network and creates heavy load on these priority nodes added by a lot of participants, so they could not handle the large traffic.
Is it possible that the network is better without any priority nodes?
May the problems had been arisen (or the things got worse) when the first bunch of priority nodes appeared?
How other networks based on monero (e.g. sumo, etn) do exist without any priority nodes and with a quite number of alternatives according to daemons' logs?

P.S. Sorry for writing this early morning but seems we're in completely different time zones.

No worries about the time zone thing, I actually really just enjoy helping people when I can so I don't mind at all Smiley (Plus my dogs love to hang out in the middle of the night)

We're using priority nodes for now because it's a smaller network but they shouldn't be needed in the future for the average person. They can make life easier for some people like pool operators though.

The first priority nodes didn't cause any problems but we've had a large influx of new connections lately so we (thank you -->Speedie!<--) added more priority nodes to reduce the load per node, increase geographical diversity, and generally help support the network while it's in its infancy. The nodes should help keep each other in sync for now.

Edit: I forgot to add that the load per node is very low right now and they're setup to handle a massive influx of new connections.
cryptoRX
Member
**
Offline Offline

Activity: 196
Merit: 10


View Profile
March 01, 2018, 02:30:59 PM
 #1609

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

▰   SEMUX   -   An innovative high-performance blockchain platform   ▰
■▬▬▬▬▬      Powered by Semux BFT consensus algorithm      ▬▬▬▬▬■
Github   -   Discord   -   Twitter   -   Telegram   -   Get Free Airdrop Now!
Speedie
Sr. Member
****
Offline Offline

Activity: 504
Merit: 254


View Profile
March 01, 2018, 02:39:52 PM
 #1610

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.
cryptoRX
Member
**
Offline Offline

Activity: 196
Merit: 10


View Profile
March 01, 2018, 03:22:02 PM
 #1611

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.


That worked like a charm. Thank you.

▰   SEMUX   -   An innovative high-performance blockchain platform   ▰
■▬▬▬▬▬      Powered by Semux BFT consensus algorithm      ▬▬▬▬▬■
Github   -   Discord   -   Twitter   -   Telegram   -   Get Free Airdrop Now!
bineva17
Member
**
Offline Offline

Activity: 131
Merit: 11


View Profile
March 01, 2018, 05:22:30 PM
 #1612

Just a warning, don't withdrawal DERO from Stock Exchange. I have a reasonable amount lock under "withdrawal error" (balance is now zero). Placed a ticket and support says the dev will look into it (about 24 hours ago, no change).

Will let you know of any update....Hopefully I haven't lost my coins :/

Follow up, Stock Exchange returned all my coins (took about 48 hours)....

On another note, is it still safe to use the GUI wallet or should I switch to the latest command line wallet due to the issue with block change syncing? Thanks.

Hi Tron, I'm relieved to hear that Stocks.Exchange is starting to respond to the tickets from the community. The GUI wallet was cloned by a community member and is not the official GUI wallet due to be released further into the roadmap. To date I have not had anyone report any issues with the current GUI wallet and the community member who made it remains a respected member.


I asked the same question and think it's safe to use Denis' beautiful Gui wallet v0.0.2. It works like a charm. Anyway, have successfully tested the withdrawal amount of 29,39,49 and 59 coins, error at 69. Our devs are working on it and hope we'll soon find a solution.

@Serena: I adore your talents. Normally community managers can only do the typing work, but not only you are a clever and devoted one, but also clearly understands how blockchain technology works and restlessly supports the Slack mining community of Dero. Not to mention you are female, a rare specie in crypto space and technical world. So good luck and keep doing the great job!
cotinco
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
March 01, 2018, 06:01:21 PM
 #1613

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.


Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.
Speedie
Sr. Member
****
Offline Offline

Activity: 504
Merit: 254


View Profile
March 01, 2018, 06:11:50 PM
 #1614

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.


Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.

They have around 40 - 50 connections each, total, in and out. Loads are averaging 0.05 across the 6 nodes, so it isn't a load problem.

cryptopool.space and the block explorer are off on a higher block than pool.dero.live, dero.tech, dero.miner.rocks, and the 6 nodes. The question being why.


cotinco
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
March 01, 2018, 06:19:47 PM
 #1615

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.


Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.

They have around 40 - 50 connections each, total, in and out. Loads are averaging 0.05 across the 6 nodes, so it isn't a load problem.

cryptopool.space and the block explorer are off on a higher block than pool.dero.live, dero.tech, dero.miner.rocks, and the 6 nodes. The question being why.




Seems that they forked due to an alternative at 40770.
Unfortunately, the dero daemon handles alternatives very strangely, sometimes it enters in a loop with exception cryptonote::BLOCK_DNE instead of choosing the correct block chain.
air133
Newbie
*
Offline Offline

Activity: 212
Merit: 0


View Profile
March 01, 2018, 06:26:04 PM
 #1616

Today and now i have problem with pool http://pool.dero.io/ I do not see my stats, write Connection error.
Speedie
Sr. Member
****
Offline Offline

Activity: 504
Merit: 254


View Profile
March 01, 2018, 06:27:54 PM
 #1617

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.


Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.

They have around 40 - 50 connections each, total, in and out. Loads are averaging 0.05 across the 6 nodes, so it isn't a load problem.

cryptopool.space and the block explorer are off on a higher block than pool.dero.live, dero.tech, dero.miner.rocks, and the 6 nodes. The question being why.




Seems that they forked due to an alternative at 40770.
Unfortunately, the dero daemon handles alternatives very strangely, sometimes it enters in a loop with exception cryptonote::BLOCK_DNE instead of choosing the correct block chain.

Yes, I noticed that when all 6 nodes simultaneously went beserk and I had to replicate a good DB across them all. At the moment it's a case of holding things together as much as possible until the devs can get a fix in place.
cotinco
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
March 01, 2018, 06:54:10 PM
 #1618

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.


Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.

They have around 40 - 50 connections each, total, in and out. Loads are averaging 0.05 across the 6 nodes, so it isn't a load problem.

cryptopool.space and the block explorer are off on a higher block than pool.dero.live, dero.tech, dero.miner.rocks, and the 6 nodes. The question being why.




Seems that they forked due to an alternative at 40770.
Unfortunately, the dero daemon handles alternatives very strangely, sometimes it enters in a loop with exception cryptonote::BLOCK_DNE instead of choosing the correct block chain.

Yes, I noticed that when all 6 nodes simultaneously went beserk and I had to replicate a good DB across them all. At the moment it's a case of holding things together as much as possible until the devs can get a fix in place.

dero.miner.rocks is on a longer chain. stocks.exchange seems to be also there. It's very like the same that was happened yesterday - pool.dero.live is building its own blockchain regardless of others. May be it's because of its heavy load?
miner.rocks
Jr. Member
*
Offline Offline

Activity: 166
Merit: 2


View Profile WWW
March 01, 2018, 07:00:28 PM
 #1619

We would suggest everyone to stop mining DERO, until fork issues will be solved.  Angry

Yesterday our pool appeared on a forked chain for 3 times, the last one for 3 hours, we fully cover loses of our loyal miners.
Today our pool appeared on a forked chain, and we learned about it only after 2 hours, we will not cover loses anymore.

We suggest dev team to cover all miners loses, caused by these everyday forks, until issue will be solved.

https://miner.rocks pplns cryptonote pools with email alerts and workers stats
cpmcgrat
Member
**
Offline Offline

Activity: 226
Merit: 21

DCAB


View Profile
March 01, 2018, 07:04:24 PM
 #1620

We would suggest everyone to stop mining DERO, until fork issues will be solved.  Angry

Yesterday our pool appeared on a forked chain for 3 times, the last one for 3 hours, we fully cover loses of our loyal miners.
Today our pool appeared on a forked chain, and we learned about it only after 2 hours, we will not cover loses anymore.

We suggest dev team to cover all miners loses, caused by these everyday forks, until issue will be solved.

I think at this point we need a full RCA from the devs as to why forks are happening constantly. I’d like to know the technical reason behind these issues. I’m going to keep supporting this coin, but some transparency here would go a long way. Then maybe I, or another community member could help fix it.

Member, Dero Community Advisory Board (DCAB)
Pages: « 1 ... 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 [81] 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 ... 219 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!