Delegates, please make sure you upgrade to 0.4.8 version

[king]

Hi,You can restore the voting for my delegate “mister”, and will vote transferred to “sun.delegate.service” and “moon.delegate.service”? I have updated to 0.4.9, and run nearly a month before the mister, the situation is very good, but after updating to 0.4.8, the vote was canceled, the original server is wasted.

[CoinHoarder]

To All delegates:

Please NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]

   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO
We will strongly recommend others to vote them out.

This might of been me, I apologize. I missed 8 blocks because I had my delegate account loaded on both the VPN and my personal computer. I have since deleted the delegate account on my personal computer and everything seems to be running smoothly now. Luckily I noticed I was missing blocks, otherwise I wouldn't of realized. I apologize for that... It was a noob mistake.

By the way.. this should be explained in the "How to setup a delegate Wiki" so others avoid making the same mistake. If it would have been explained there I would not have done it. http://wiki.bitshares.org/index.php/BitShares_X_Delegate_How-To

Just curios, how did you remove the delegate account from wallet? Did you create a new wallet and import all accounts but the delegate or is there a console command for removing accounts from wallet?

I dumped the private key for my main non-delegate account, then deleted this folder:
C:\Users\Adminnn\AppData\Roaming\BitShares X\wallets\default

Then re-downloaded the block chain, imported the main account's private key, and re-scanned the block chain.

It seems I got voted out for my error last night, so be careful and don't do that!!

[xeroc]

if you run "netstat -tulpen" you can see all ports the client is listening to ... (linux)

Code: [Select]

tcp        0      0 10.0.0.16:19988         0.0.0.0:*               LISTEN      1001       10885959    31115/bitshares_cli
tcp        0      0 0.0.0.0:1700            0.0.0.0:*               LISTEN      1001       10885961    31115/bitshares_cli
tcp        0      0 10.0.0.16:9988          0.0.0.0:*               LISTEN      1001       10885958    31115/bitshares_cli
udp        0      0 0.0.0.0:56861           0.0.0.0:*                           1001       10884327    31115/bitshares_cli

[puppies]

To All delegates:

Please NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]

   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO
We will strongly recommend others to vote them out.

This might of been me, I apologize. I missed 8 blocks because I had my delegate account loaded on both the VPN and my personal computer. I have since deleted the delegate account on my personal computer and everything seems to be running smoothly now. Luckily I noticed I was missing blocks, otherwise I wouldn't of realized. I apologize for that... It was a noob mistake.

By the way.. this should be explained in the "How to setup a delegate Wiki" so others avoid making the same mistake. If it would have been explained there I would not have done it. http://wiki.bitshares.org/index.php/BitShares_X_Delegate_How-To

Just curios, how did you remove the delegate account from wallet? Did you create a new wallet and import all accounts but the delegate or is there a console command for removing accounts from wallet?

no way to remove accounts.  I just use wallet_delegate_set_block_production <delegate name> false

[bitwiz]

I updated to the tag 0.4.8 but I don't know if the node is of any use since the delegate is not producing blocks. Does it help the network anyway?

If you not are running your node behind a firewall, so others can connect to you, then yes, you help the network.

I setup it with the suggested  command network_set_advanced_node_parameters (max 200 connections) and it has incoming connections.
What i see sometimes is

Code: [Select]

Peer xyz disconnected us: You offered us a block that we reject as invalid
Is it normal?

Yes that happens sometimes.... it will happen less frequently in the future.

Now there are about 120 incoming connections. Btw, is there a list of all the ports that must be open? Checked in the FAQs http://wiki.bitshares.org/index.php/FAQs but saw nothing. Or I just check the config.json file?
Thanks

[bitwiz]

To All delegates:

Please NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]

   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO
We will strongly recommend others to vote them out.

This might of been me, I apologize. I missed 8 blocks because I had my delegate account loaded on both the VPN and my personal computer. I have since deleted the delegate account on my personal computer and everything seems to be running smoothly now. Luckily I noticed I was missing blocks, otherwise I wouldn't of realized. I apologize for that... It was a noob mistake.

By the way.. this should be explained in the "How to setup a delegate Wiki" so others avoid making the same mistake. If it would have been explained there I would not have done it. http://wiki.bitshares.org/index.php/BitShares_X_Delegate_How-To

Just curios, how did you remove the delegate account from wallet? Did you create a new wallet and import all accounts but the delegate or is there a console command for removing accounts from wallet?

[CoinHoarder]

To All delegates:

Please NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]

   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO
We will strongly recommend others to vote them out.

This might of been me, I apologize. I missed 8 blocks because I had my delegate account loaded on both the VPN and my personal computer. I have since deleted the delegate account on my personal computer and everything seems to be running smoothly now. Luckily I noticed I was missing blocks, otherwise I wouldn't of realized. I apologize for that... It was a noob mistake.

By the way.. this should be explained in the "How to setup a delegate Wiki" so others avoid making the same mistake. If it would have been explained there I would not have done it. http://wiki.bitshares.org/index.php/BitShares_X_Delegate_How-To

[bytemaster]

I updated to the tag 0.4.8 but I don't know if the node is of any use since the delegate is not producing blocks. Does it help the network anyway?

If you not are running your node behind a firewall, so others can connect to you, then yes, you help the network.

I setup it with the suggested  command network_set_advanced_node_parameters (max 200 connections) and it has incoming connections.
What i see sometimes is

Code: [Select]

Peer xyz disconnected us: You offered us a block that we reject as invalid
Is it normal?

Yes that happens sometimes.... it will happen less frequently in the future.

[bitwiz]

I updated to the tag 0.4.8 but I don't know if the node is of any use since the delegate is not producing blocks. Does it help the network anyway?

If you not are running your node behind a firewall, so others can connect to you, then yes, you help the network.

I setup it with the suggested  command network_set_advanced_node_parameters (max 200 connections) and it has incoming connections.
What i see sometimes is

Code: [Select]

Peer xyz disconnected us: You offered us a block that we reject as invalid
Is it normal?

[DACSunlimited]

I updated to the tag 0.4.8 but I don't know if the node is of any use since the delegate is not producing blocks. Does it help the network anyway?

If you not are running your node behind a firewall, so others can connect to you, then yes, you help the network.

[bitwiz]

I updated to the tag 0.4.8 but I don't know if the node is of any use since the delegate is not producing blocks. Does it help the network anyway?

[emski]

I think there should be an official thread with procedures that should be used for updating, backup etc.
Some of the backup solutions I saw in the forum might produce forks as well.
And another important thing - Lets not auto-start delegate block production if we open a wallet containing a delegate.

[DACSunlimited]

Code: [Select]

317471
     6577fbeaf475af4b774ce2d93436dccf541975a8               delegate.webber              0       166 2014-08-26T01:24:00         0     YES                  NO
     e581cf924baad1620225d9e38e17505538fe2e72               delegate.webber              0       166 2014-08-26T01:24:00         0     YES                 YES
         318451
     2b209be2bed88aff819f42d059ed260eceb67b5f            delegate.coolspeed              1       459 2014-08-26T04:19:10         0     YES                  NO
     75bd917bd0eb492357d5e984e488d0bb0cac3139            delegate.coolspeed              1       459 2014-08-26T04:19:10         0     YES                 YES
         318509
     286b9dfab1ea659e7fcbf73f92dfe6fb8a4d249f            delegate.coolspeed              2       575 2014-08-26T04:29:30         0     YES                 YES
     5dc37c10b3c708df717e0fe2cafce47ae1c57657            delegate.coolspeed              2       575 2014-08-26T04:29:30         0     N/A                  NO
         318558
     3bf3cd34a3deabb46dc1a60e34391a937fd1ea37            delegate.coolspeed              0       166 2014-08-26T04:38:00         0     YES                 YES
     92e537244b51e897927356106c85eb889f48cec3            delegate.coolspeed              0       166 2014-08-26T04:38:00         0     N/A                  NO
         318653
     b492e7846934ca82078ad7601917d5c87e77d94f            delegate.coolspeed              0       166 2014-08-26T04:54:50         0     YES                 YES
     b02c3b7413dbb09edb5c8bfbeb063139e3873bf8            delegate.coolspeed              0       166 2014-08-26T04:54:50         1     N/A                  NO
         318709
     771c86fa54dacedd58379e08d6486f5988e15a99            delegate.coolspeed              1       410 2014-08-26T05:05:00         0     YES                  NO
     81f74d223e79c0d46e194e69301e8a82de27b6fe            delegate.coolspeed              1       410 2014-08-26T05:05:00         0     YES                 YES
         321979
     ef96dea7b653c7292c790935114360eee84708c7                        e.coin              1       766 2014-08-26T14:17:10         0     YES                 YES
     7aad16dc0e47e06a093888568bf268a1f2c1a188                        btsnow             13      3857 2014-08-26T14:29:20         0     N/A                  NO
         322117
     f402e661aeff4ba1704dc59441e7ba05b4d83981         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         0     YES                 YES
     44cc35cf2a4afe38a3e8a4480e7c8f0953991e5a         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         0     N/A                  NO
         322131
     133db0ce1040b169226753ee8d2dc7735ff2a3b5             google.helloworld              1       402 2014-08-26T14:42:50         0     YES                 YES
     0fad4bd06f03ab6c98a3d1b1094ac331f2d78b03             google.helloworld              1       402 2014-08-26T14:42:50         0     N/A                  NO
         322136
     8208884d226913d653520c52e65c75e58dcdb14f          microsoft.helloworld              0       166 2014-08-26T14:43:40         0     YES                  NO
     3e4d2d05f9d86382eaeb5c320c73323e5a2b6add          microsoft.helloworld              0       166 2014-08-26T14:43:40         0     YES                 YES
         322139
     c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.ebit              0       166 2014-08-26T14:44:10         0     YES                 YES
     4322211b2f74a2d43183a17042c057da64c4486c                        x.ebit              0       166 2014-08-26T14:44:10         0     N/A                  NO
         322198
     e64105edec9022457b8e32aea2324cf3f3f37b63          microsoft.helloworld              0       166 2014-08-26T14:54:00         0     YES                 YES
     fb57deaf9791dd4df98ce64580f88643d6fe72fa          microsoft.helloworld              0       166 2014-08-26T14:54:00         0     N/A                  NO
         322234
     316c578e31967e7ac461a64cf73ae0f135da2840         btsx.chinesecommunity              0       166 2014-08-26T15:00:00         0     YES                 YES
     58b8d6edede2e3f6d0af09ab2e22aa3a665d8b4e         btsx.chinesecommunity              0       166 2014-08-26T15:00:00         0     N/A                  NO
         322241
     3fc9e6af6d0b6008996522d99a55129fe1cf8cd2                        x.ebit              3       643 2014-08-26T15:01:10         0     YES                  NO
     f9cfd3fb9d4b5d5409f3681a3b0ac57a58573a02                        x.ebit              3       643 2014-08-26T15:01:10         0     YES                 YES
         322258
     41f8c713e634d09a8490558f7abc5fd5de7a7050             google.helloworld              2       598 2014-08-26T15:04:00         0     YES                 YES
     d0ffa6be3af5a0c4ee30b11975bef4c8b8672c9b             google.helloworld              2       598 2014-08-26T15:04:00         0     N/A                  NO
         322332
     55b18ee36c75aa0377281f394ea03c83fe3cfdd8             google.helloworld              0       166 2014-08-26T15:16:30         0     YES                 YES
     a66d0af3bb8348a364a859b3724f9332eb655a7e             google.helloworld              2       687 2014-08-26T15:16:30         0     N/A                  NO
         322337
     5197cd8686df7a458f062b8c0d42c20b5675b2e8          microsoft.helloworld              0       166 2014-08-26T15:17:20         0     YES                 YES
     c27e0ac3d894cb4ebe67471a147e5908c0b42f6f          microsoft.helloworld              3     19889 2014-08-26T15:17:20         1     N/A                  NO
         322344
     8b255df0fc064e2741ed43ceee13c071d6aaf7ae         btsx.chinesecommunity              0       166 2014-08-26T15:18:30         0     YES                 YES
     14a9ff428c0b62e212bddb7faa9525defa59a2db         btsx.chinesecommunity              2       672 2014-08-26T15:18:30         0     N/A                  NO
         322365
     17efde50edfeb41ba629e128452cf3645bffde83                        x.ebit              0       166 2014-08-26T15:22:10         0     YES                 YES
     715e169f1945cf1da68b8575fd22894691dd92b7                        x.ebit              2       626 2014-08-26T15:22:10         1     N/A                  NO
         322423
     098f2698ca545aa68dc4971f50bc1a8685adb20a                        x.ebit              0       166 2014-08-26T15:31:50         0     YES                 YES
     7340ed6d65c9e5c9a6b669ac1c37ba1e5cbe0ead                        x.ebit              1       478 2014-08-26T15:31:50         0     N/A                  NO

Are they all running multiple instances?
You know how long the list is ?

This might be list in recent two days, some confusions from other nodes or users can avoid if delegates are doing a good job.

[emski]

Code: [Select]

317471
     6577fbeaf475af4b774ce2d93436dccf541975a8               delegate.webber              0       166 2014-08-26T01:24:00         0     YES                  NO
     e581cf924baad1620225d9e38e17505538fe2e72               delegate.webber              0       166 2014-08-26T01:24:00         0     YES                 YES
         318451
     2b209be2bed88aff819f42d059ed260eceb67b5f            delegate.coolspeed              1       459 2014-08-26T04:19:10         0     YES                  NO
     75bd917bd0eb492357d5e984e488d0bb0cac3139            delegate.coolspeed              1       459 2014-08-26T04:19:10         0     YES                 YES
         318509
     286b9dfab1ea659e7fcbf73f92dfe6fb8a4d249f            delegate.coolspeed              2       575 2014-08-26T04:29:30         0     YES                 YES
     5dc37c10b3c708df717e0fe2cafce47ae1c57657            delegate.coolspeed              2       575 2014-08-26T04:29:30         0     N/A                  NO
         318558
     3bf3cd34a3deabb46dc1a60e34391a937fd1ea37            delegate.coolspeed              0       166 2014-08-26T04:38:00         0     YES                 YES
     92e537244b51e897927356106c85eb889f48cec3            delegate.coolspeed              0       166 2014-08-26T04:38:00         0     N/A                  NO
         318653
     b492e7846934ca82078ad7601917d5c87e77d94f            delegate.coolspeed              0       166 2014-08-26T04:54:50         0     YES                 YES
     b02c3b7413dbb09edb5c8bfbeb063139e3873bf8            delegate.coolspeed              0       166 2014-08-26T04:54:50         1     N/A                  NO
         318709
     771c86fa54dacedd58379e08d6486f5988e15a99            delegate.coolspeed              1       410 2014-08-26T05:05:00         0     YES                  NO
     81f74d223e79c0d46e194e69301e8a82de27b6fe            delegate.coolspeed              1       410 2014-08-26T05:05:00         0     YES                 YES
         321979
     ef96dea7b653c7292c790935114360eee84708c7                        e.coin              1       766 2014-08-26T14:17:10         0     YES                 YES
     7aad16dc0e47e06a093888568bf268a1f2c1a188                        btsnow             13      3857 2014-08-26T14:29:20         0     N/A                  NO
         322117
     f402e661aeff4ba1704dc59441e7ba05b4d83981         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         0     YES                 YES
     44cc35cf2a4afe38a3e8a4480e7c8f0953991e5a         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         0     N/A                  NO
         322131
     133db0ce1040b169226753ee8d2dc7735ff2a3b5             google.helloworld              1       402 2014-08-26T14:42:50         0     YES                 YES
     0fad4bd06f03ab6c98a3d1b1094ac331f2d78b03             google.helloworld              1       402 2014-08-26T14:42:50         0     N/A                  NO
         322136
     8208884d226913d653520c52e65c75e58dcdb14f          microsoft.helloworld              0       166 2014-08-26T14:43:40         0     YES                  NO
     3e4d2d05f9d86382eaeb5c320c73323e5a2b6add          microsoft.helloworld              0       166 2014-08-26T14:43:40         0     YES                 YES
         322139
     c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.ebit              0       166 2014-08-26T14:44:10         0     YES                 YES
     4322211b2f74a2d43183a17042c057da64c4486c                        x.ebit              0       166 2014-08-26T14:44:10         0     N/A                  NO
         322198
     e64105edec9022457b8e32aea2324cf3f3f37b63          microsoft.helloworld              0       166 2014-08-26T14:54:00         0     YES                 YES
     fb57deaf9791dd4df98ce64580f88643d6fe72fa          microsoft.helloworld              0       166 2014-08-26T14:54:00         0     N/A                  NO
         322234
     316c578e31967e7ac461a64cf73ae0f135da2840         btsx.chinesecommunity              0       166 2014-08-26T15:00:00         0     YES                 YES
     58b8d6edede2e3f6d0af09ab2e22aa3a665d8b4e         btsx.chinesecommunity              0       166 2014-08-26T15:00:00         0     N/A                  NO
         322241
     3fc9e6af6d0b6008996522d99a55129fe1cf8cd2                        x.ebit              3       643 2014-08-26T15:01:10         0     YES                  NO
     f9cfd3fb9d4b5d5409f3681a3b0ac57a58573a02                        x.ebit              3       643 2014-08-26T15:01:10         0     YES                 YES
         322258
     41f8c713e634d09a8490558f7abc5fd5de7a7050             google.helloworld              2       598 2014-08-26T15:04:00         0     YES                 YES
     d0ffa6be3af5a0c4ee30b11975bef4c8b8672c9b             google.helloworld              2       598 2014-08-26T15:04:00         0     N/A                  NO
         322332
     55b18ee36c75aa0377281f394ea03c83fe3cfdd8             google.helloworld              0       166 2014-08-26T15:16:30         0     YES                 YES
     a66d0af3bb8348a364a859b3724f9332eb655a7e             google.helloworld              2       687 2014-08-26T15:16:30         0     N/A                  NO
         322337
     5197cd8686df7a458f062b8c0d42c20b5675b2e8          microsoft.helloworld              0       166 2014-08-26T15:17:20         0     YES                 YES
     c27e0ac3d894cb4ebe67471a147e5908c0b42f6f          microsoft.helloworld              3     19889 2014-08-26T15:17:20         1     N/A                  NO
         322344
     8b255df0fc064e2741ed43ceee13c071d6aaf7ae         btsx.chinesecommunity              0       166 2014-08-26T15:18:30         0     YES                 YES
     14a9ff428c0b62e212bddb7faa9525defa59a2db         btsx.chinesecommunity              2       672 2014-08-26T15:18:30         0     N/A                  NO
         322365
     17efde50edfeb41ba629e128452cf3645bffde83                        x.ebit              0       166 2014-08-26T15:22:10         0     YES                 YES
     715e169f1945cf1da68b8575fd22894691dd92b7                        x.ebit              2       626 2014-08-26T15:22:10         1     N/A                  NO
         322423
     098f2698ca545aa68dc4971f50bc1a8685adb20a                        x.ebit              0       166 2014-08-26T15:31:50         0     YES                 YES
     7340ed6d65c9e5c9a6b669ac1c37ba1e5cbe0ead                        x.ebit              1       478 2014-08-26T15:31:50         0     N/A                  NO

Are they all running multiple instances?
You know how long the list is ?

[DACSunlimited]

*confirmed*
works great thatway ..

I personally use 2 different VPS instances to do that ..
and wrote a little python script to simplify 'switching' of active delegates

Appreciate that, switching between two process is good enough to go without introducing extra hardware cost.
Do NOT forget to lock the old one.

[xeroc]

*confirmed*
works great thatway ..

I personally use 2 different VPS instances to do that ..
and wrote a little python script to simplify 'switching' of active delegates

[emski]

That is my current procedure.

[DACSunlimited]

Regardless of possible bug in the client, this behavior is still harmful to the network, topics related to this have already been discussed in the DPOS thread.

We should start a new thread and reflag delegates that are produce forks ...
not missing blocks is VERY easy that way but does no good to the network! You just fail your responsibilities against the network ..

I see missing a block A LOT less harmful for the network than producing forks!!

The block must be in the same block number, and be produced by the same delegate, here is a example just taken.

Even though falling into a fork might be a bug in latest version, but we definitely need to enable the auto fire operation.

   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
         321979
     ef96dea7b653c7292c790935114360eee84708c7                        e.coin              1       766 2014-08-26T14:17:10       169     YES                 YES
     7aad16dc0e47e06a093888568bf268a1f2c1a188                        btsnow             13      3857 2014-08-26T14:29:20         0     N/A                  NO
         322117
     f402e661aeff4ba1704dc59441e7ba05b4d83981         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         0     YES                 YES
     44cc35cf2a4afe38a3e8a4480e7c8f0953991e5a         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         1     N/A                  NO
         322131
     133db0ce1040b169226753ee8d2dc7735ff2a3b5             google.helloworld              1       402 2014-08-26T14:42:50         0     YES                 YES
     0fad4bd06f03ab6c98a3d1b1094ac331f2d78b03             google.helloworld              1       402 2014-08-26T14:42:50         1     N/A                  NO
         322136
     8208884d226913d653520c52e65c75e58dcdb14f          microsoft.helloworld              0       166 2014-08-26T14:43:40         0     YES                 YES
     3e4d2d05f9d86382eaeb5c320c73323e5a2b6add          microsoft.helloworld              0       166 2014-08-26T14:43:40         1     N/A                  NO
         322139
     c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.ebit              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.ebit              0       166 2014-08-26T14:44:10         1     N/A                  NO

Have you considered the possibility of BUG in the client?
What if it exists prior 0.4.8 ?

If it is a bug in the client then how replacing the delegate will help the network ?

Build and run your client in another screen process first, input

Code: [Select]

info
to get the "wallet_next_block_production_time"

Catch a good operation time window, lock one, and unlock another.

[emski]

Regardless of possible bug in the client, this behavior is still harmful to the network, topics related to this have already been discussed in the DPOS thread.

We should start a new thread and reflag delegates that are produce forks ...
not missing blocks is VERY easy that way but does no good to the network! You just fail your responsibilities against the network ..

I see missing a block A LOT less harmful for the network than producing forks!!

The block must be in the same block number, and be produced by the same delegate, here is a example just taken.

Even though falling into a fork might be a bug in latest version, but we definitely need to enable the auto fire operation.

   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
         321979
     ef96dea7b653c7292c790935114360eee84708c7                        e.coin              1       766 2014-08-26T14:17:10       169     YES                 YES
     7aad16dc0e47e06a093888568bf268a1f2c1a188                        btsnow             13      3857 2014-08-26T14:29:20         0     N/A                  NO
         322117
     f402e661aeff4ba1704dc59441e7ba05b4d83981         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         0     YES                 YES
     44cc35cf2a4afe38a3e8a4480e7c8f0953991e5a         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         1     N/A                  NO
         322131
     133db0ce1040b169226753ee8d2dc7735ff2a3b5             google.helloworld              1       402 2014-08-26T14:42:50         0     YES                 YES
     0fad4bd06f03ab6c98a3d1b1094ac331f2d78b03             google.helloworld              1       402 2014-08-26T14:42:50         1     N/A                  NO
         322136
     8208884d226913d653520c52e65c75e58dcdb14f          microsoft.helloworld              0       166 2014-08-26T14:43:40         0     YES                 YES
     3e4d2d05f9d86382eaeb5c320c73323e5a2b6add          microsoft.helloworld              0       166 2014-08-26T14:43:40         1     N/A                  NO
         322139
     c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.ebit              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.ebit              0       166 2014-08-26T14:44:10         1     N/A                  NO

Have you considered the possibility of BUG in the client?
What if it exists prior 0.4.8 ?

If it is a bug in the client then how replacing the delegate will help the network ?
This was discussed extensively indeed. And there are a lot of people using backups and simultaneous instances. That is harmful.

[DACSunlimited]

Regardless of possible bug in the client, this behavior is still harmful to the network, topics related to this have already been discussed in the DPOS thread.

We should start a new thread and reflag delegates that are produce forks ...
not missing blocks is VERY easy that way but does no good to the network! You just fail your responsibilities against the network ..

I see missing a block A LOT less harmful for the network than producing forks!!

The block must be in the same block number, and be produced by the same delegate, here is a example just taken.

Even though falling into a fork might be a bug in latest version, but we definitely need to enable the auto fire operation.

   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
         321979
     ef96dea7b653c7292c790935114360eee84708c7                        e.coin              1       766 2014-08-26T14:17:10       169     YES                 YES
     7aad16dc0e47e06a093888568bf268a1f2c1a188                        btsnow             13      3857 2014-08-26T14:29:20         0     N/A                  NO
         322117
     f402e661aeff4ba1704dc59441e7ba05b4d83981         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         0     YES                 YES
     44cc35cf2a4afe38a3e8a4480e7c8f0953991e5a         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         1     N/A                  NO
         322131
     133db0ce1040b169226753ee8d2dc7735ff2a3b5             google.helloworld              1       402 2014-08-26T14:42:50         0     YES                 YES
     0fad4bd06f03ab6c98a3d1b1094ac331f2d78b03             google.helloworld              1       402 2014-08-26T14:42:50         1     N/A                  NO
         322136
     8208884d226913d653520c52e65c75e58dcdb14f          microsoft.helloworld              0       166 2014-08-26T14:43:40         0     YES                 YES
     3e4d2d05f9d86382eaeb5c320c73323e5a2b6add          microsoft.helloworld              0       166 2014-08-26T14:43:40         1     N/A                  NO
         322139
     c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.ebit              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.ebit              0       166 2014-08-26T14:44:10         1     N/A                  NO

Have you considered the possibility of BUG in the client?
What if it exists prior 0.4.8 ?

[xeroc]

The block must be in the same block number, and be produced by the same delegate, here is a example just taken.

That is perfectly clear

Even though falling into a fork might be a bug in latest version, but we definitely need to enable the auto fire operation

*agreed* .. but be prepared to loose some active delegates ... maybe also consider a fired-window such that delegates are not fired indefinitely for skrewing up once ...

much like a 2 weeks penalty .. or kind of

[emski]

We should start a new thread and reflag delegates that are produce forks ...
not missing blocks is VERY easy that way but does no good to the network! You just fail your responsibilities against the network ..

I see missing a block A LOT less harmful for the network than producing forks!!

The block must be in the same block number, and be produced by the same delegate, here is a example just taken.

Even though falling into a fork might be a bug in latest version, but we definitely need to enable the auto fire operation.

   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
         321979
     ef96dea7b653c7292c790935114360eee84708c7                        e.coin              1       766 2014-08-26T14:17:10       169     YES                 YES
     7aad16dc0e47e06a093888568bf268a1f2c1a188                        btsnow             13      3857 2014-08-26T14:29:20         0     N/A                  NO
         322117
     f402e661aeff4ba1704dc59441e7ba05b4d83981         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         0     YES                 YES
     44cc35cf2a4afe38a3e8a4480e7c8f0953991e5a         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         1     N/A                  NO
         322131
     133db0ce1040b169226753ee8d2dc7735ff2a3b5             google.helloworld              1       402 2014-08-26T14:42:50         0     YES                 YES
     0fad4bd06f03ab6c98a3d1b1094ac331f2d78b03             google.helloworld              1       402 2014-08-26T14:42:50         1     N/A                  NO
         322136
     8208884d226913d653520c52e65c75e58dcdb14f          microsoft.helloworld              0       166 2014-08-26T14:43:40         0     YES                 YES
     3e4d2d05f9d86382eaeb5c320c73323e5a2b6add          microsoft.helloworld              0       166 2014-08-26T14:43:40         1     N/A                  NO
         322139
     c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.ebit              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.ebit              0       166 2014-08-26T14:44:10         1     N/A                  NO

Have you considered the possibility of BUG in the client?
What if it exists prior 0.4.8 ?

[DACSunlimited]

We should start a new thread and reflag delegates that are produce forks ...
not missing blocks is VERY easy that way but does no good to the network! You just fail your responsibilities against the network ..

I see missing a block A LOT less harmful for the network than producing forks!!

The block must be in the same block number, and be produced by the same delegate, here is a example just taken.

Even though falling into a fork might be a bug in latest version, but we definitely need to enable the auto fire operation.

   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
         321979
     ef96dea7b653c7292c790935114360eee84708c7                        e.coin              1       766 2014-08-26T14:17:10       169     YES                 YES
     7aad16dc0e47e06a093888568bf268a1f2c1a188                        btsnow             13      3857 2014-08-26T14:29:20         0     N/A                  NO
         322117
     f402e661aeff4ba1704dc59441e7ba05b4d83981         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         0     YES                 YES
     44cc35cf2a4afe38a3e8a4480e7c8f0953991e5a         btsx.chinesecommunity              0       166 2014-08-26T14:40:30         1     N/A                  NO
         322131
     133db0ce1040b169226753ee8d2dc7735ff2a3b5             google.helloworld              1       402 2014-08-26T14:42:50         0     YES                 YES
     0fad4bd06f03ab6c98a3d1b1094ac331f2d78b03             google.helloworld              1       402 2014-08-26T14:42:50         1     N/A                  NO
         322136
     8208884d226913d653520c52e65c75e58dcdb14f          microsoft.helloworld              0       166 2014-08-26T14:43:40         0     YES                 YES
     3e4d2d05f9d86382eaeb5c320c73323e5a2b6add          microsoft.helloworld              0       166 2014-08-26T14:43:40         1     N/A                  NO
         322139
     c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.ebit              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.ebit              0       166 2014-08-26T14:44:10         1     N/A                  NO

[xeroc]

We should start a new thread and reflag delegates that are produce forks ...
not missing blocks is VERY easy that way but does no good to the network! You just fail your responsibilities against the network ..

I see missing a block A LOT less harmful for the network than producing forks!!

[DACSunlimited]

To All delegates:

Please NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]

   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO
We will strongly recommend others to vote them out.

[xeroc]

only when I opened the backup json file with an txt editor and erased the last coma ( , ) from the last page, saved the file and tried again I managed to restore my backup...
(I read it here on the forum somewhere as a solution and it worked, in case you don't read/found it yet)

Backup procedure had a bug in the last version .. (the comma at the end)
The bug was fixed in the new version ... so just create a NEW backup ... that should work well

[liondani]

only when I opened the backup json file with an txt editor and erased the last coma ( , ) from the last page, saved the file and tried again I managed to restore my backup...
(I read it here on the forum somewhere as a solution and it worked, in case you don't read/found it yet)

[emski]

My seed node has been crashing and forking like nothing else.

When you have wallet open with enabled block production for a delegate (it doesn't need to be in top 101) it synchronizes.

[puppies]

My seed node has been crashing and forking like nothing else.

[svk]

Website client had more connections this morning but was still stuck, but --rebuild-index got it back on the good fork now, apologies to people trying to use the site over the last few hours.

[tonyk]

Both .. the main and the backupdelegate segfaulted over night ...
Gonna restart them and hope they run longer the day as I am off with family

I've seen 1 crash on one delegate. Running it in gdb ever since. It doesn't happen while I'm watching....

That is what you suspect.. you just scare them...

[emski]

Both .. the main and the backupdelegate segfaulted over night ...
Gonna restart them and hope they run longer the day as I am off with family

I've seen 1 crash on one delegate. Running it in gdb ever since. It doesn't happen while I'm watching....

[bytemaster]

Both .. the main and the backupdelegate segfaulted over night ...
Gonna restart them and hope they run longer the day as I am off with family

Yeah... this issue is driving us nuts. 

[xeroc]

Both .. the main and the backupdelegate segfaulted over night ...
Gonna restart them and hope they run longer the day as I am off with family

[liondani]

on linux cli 0.4.8 with "wallet_account_balance" I can't see my 9.9999 bitUSD that  I could see on win gui (blockchain on linux  rescanned)

[clout]

Updated

[bytemaster]

network_add_node 107.170.30.182:1776

[yinchanggong]

Anyone else having a hard time getting more than 1 or 2 connections?

I have 6 connections... starting a new seed node now.

My linux wallet has about 100 connections, but WIN GUI only has less than 3 connections and adding nodes doesn't help.

[alt]

I have 100 connects

[bytemaster]

Anyone else having a hard time getting more than 1 or 2 connections?

I have 6 connections... starting a new seed node now. 

[puppies]

Anyone else having a hard time getting more than 1 or 2 connections?

[bytemaster]

Code: [Select]


  "blockchain_head_block_num": 317148,
  "blockchain_head_block_age": "4 seconds old",
  "blockchain_head_block_timestamp": "2014-08-26T00:24:50",
  "blockchain_average_delegate_participation": "93.52 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "169,735.07740 BTSX",
  "blockchain_delegate_pay_rate": "1.40323 BTSX",
  "blockchain_share_supply": "1,999,936,650.66592 BTSX",
  "blockchain_blocks_left_in_round": 93,
  "blockchain_next_round_time": "at least 15 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-26T00:40:20",
  "blockchain_random_seed": "a3d67ecf082d8150902f1db110d58959dcab04e4",
  "client_data_dir": "/home/riverhead/.BitSharesX",
  "client_version": "0.4.8",
  "network_num_connections": 18,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-26T00:24:54",


Nice.  When did they add the version info to get_info?

In the 0.4.8 release.

[puppies]

Code: [Select]


  "blockchain_head_block_num": 317148,
  "blockchain_head_block_age": "4 seconds old",
  "blockchain_head_block_timestamp": "2014-08-26T00:24:50",
  "blockchain_average_delegate_participation": "93.52 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "169,735.07740 BTSX",
  "blockchain_delegate_pay_rate": "1.40323 BTSX",
  "blockchain_share_supply": "1,999,936,650.66592 BTSX",
  "blockchain_blocks_left_in_round": 93,
  "blockchain_next_round_time": "at least 15 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-26T00:40:20",
  "blockchain_random_seed": "a3d67ecf082d8150902f1db110d58959dcab04e4",
  "client_data_dir": "/home/riverhead/.BitSharesX",
  "client_version": "0.4.8",
  "network_num_connections": 18,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-26T00:24:54",


Nice.  When did they add the version info to get_info?

[liondani]

upgraded and running on 0.4.8

even USD price feeds published 


liondani
liondani-delegate-1
 

[emski]

When I open a wallet containing delegates on my seed node it synchronizes.
I'll let it open with blocks production disabled.
Time to sleep.

[bytemaster]

My client for the website is stuck as well at block 317208, trying to rebuild the index..

We are looking into these stuck blocks as our next high priority issue... the blockchain shouldn't get stuck on these forks.

[svk]

My client for the website is stuck as well at block 317208, trying to rebuild the index..

[emski]

I've updated and delegates are working properly.
However seed node was stuck synchronizing.
Chain server didn't help at all.
I'm showing the logs:

Code: [Select]

Starting fast-sync of blocks from 316927
Finished fast-syncing 0 blocks at 0.000000000000 blocks/sec.
Listening for P2P connections on port 42577
Attempting to connect to peer 178.62.50.61:1776
Attempting to connect to peer 178.62.50.61:1777
Attempting to connect to peer 178.62.50.61:1778
Attempting to connect to peer 80.240.133.79:1776
Attempting to connect to peer 80.240.133.79:1777
Attempting to connect to peer 5.101.106.138:1777
Attempting to connect to peer 5.101.106.138:1778
Attempting to connect to peer 128.199.137.122:1776
Attempting to connect to peer 128.199.137.122:1777
Attempting to connect to peer 95.85.33.16:8764
Attempting to connect to peer 180.153.142.120:1777
Attempting to connect to peer 84.238.140.192:42577
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
(wallet closed) >>> info
{
  "blockchain_head_block_num": 316926,
  "blockchain_head_block_age": "39 minutes old",
  "blockchain_head_block_timestamp": "2014-08-25T23:44:20",
  "blockchain_average_delegate_participation": "29.53 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "169,960.26492 BTSX",
  "blockchain_delegate_pay_rate": "1.40509 BTSX",
  "blockchain_share_supply": "1,999,936,714.40159 BTSX",
  "blockchain_blocks_left_in_round": 12,
  "blockchain_next_round_time": "at least 2 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-26T00:25:40",
  "blockchain_random_seed": "c236f0bdeb181574bbc6f15b76e4e6ac40ebf95f",
  "client_version": "0.4.8",
  "network_num_connections": 3,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-26T00:23:40",
  "ntp_time_error": -0.0024220000000000001,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}
--- there are now 4 active connections to the p2p network
--- syncing with p2p network, 7449 blocks left to fetch
--- there are now 5 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- in sync with p2p network
--- there are now 5 active connections to the p2p network
(wallet closed) >>> info
{
  "blockchain_head_block_num": 316926,
  "blockchain_head_block_age": "40 minutes old",
  "blockchain_head_block_timestamp": "2014-08-25T23:44:20",
  "blockchain_average_delegate_participation": "29.36 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "169,960.26492 BTSX",
  "blockchain_delegate_pay_rate": "1.40509 BTSX",
  "blockchain_share_supply": "1,999,936,714.40159 BTSX",
  "blockchain_blocks_left_in_round": 12,
  "blockchain_next_round_time": "at least 2 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-26T00:26:00",
  "blockchain_random_seed": "c236f0bdeb181574bbc6f15b76e4e6ac40ebf95f",

  "client_version": "0.4.8",
  "network_num_connections": 5,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-26T00:24:01",
  "ntp_time_error": -0.0024229999999999998,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

I'm now trying --resync-blockchain.... Didn't help.

UPDATE:
I'm trying to sync only with the delegate now... Its OK now.

UPDATE:
I've copied the synchronized data dir from my delegate to the seed node.
It stuck again few blocks after...
Dont know what else I can do about that.

UPDATE:
Copied chain folder from delegate again. It is synchronized ... for now.

[Riverhead]

Code: [Select]


  "blockchain_head_block_num": 317148,
  "blockchain_head_block_age": "4 seconds old",
  "blockchain_head_block_timestamp": "2014-08-26T00:24:50",
  "blockchain_average_delegate_participation": "93.52 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "169,735.07740 BTSX",
  "blockchain_delegate_pay_rate": "1.40323 BTSX",
  "blockchain_share_supply": "1,999,936,650.66592 BTSX",
  "blockchain_blocks_left_in_round": 93,
  "blockchain_next_round_time": "at least 15 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-26T00:40:20",
  "blockchain_random_seed": "a3d67ecf082d8150902f1db110d58959dcab04e4",
  "client_data_dir": "/home/riverhead/.BitSharesX",
  "client_version": "0.4.8",
  "network_num_connections": 18,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-26T00:24:54",


[svk]

Looks good to me, mine's the same.

Code: [Select]

{
  "bitshares_toolkit_revision": "f9612af57c24b5831936bbd2c7d155d4eb2d8af8",
  "bitshares_toolkit_revision_age": "73 minutes ago",
  "fc_revision": "198d858d590f9f968f554a6036275cbbd7f78907",
  "fc_revision_age": "30 hours ago",
  "compile_date": "compiled on Aug 25 2014 at 19:48:47"
}


[spartako]

spartako,spartako1,spartako2 upgraded and running

[puppies]

Code: [Select]

wallet (unlocked) >>> about
{
  "bitshares_toolkit_revision": "f9612af57c24b5831936bbd2c7d155d4eb2d8af8",
  "bitshares_toolkit_revision_age": "70 minutes ago",
  "fc_revision": "198d858d590f9f968f554a6036275cbbd7f78907",
  "fc_revision_age": "30 hours ago",
  "compile_date": "compiled on Aug 25 2014 at 19:45:48"
}
wallet (unlocked) >>>
 
Is what I get.  Is that the correct toolkit and fc revision?

[DACSunlimited]

https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.8