• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Dash Platform v1.5.1 - important update

splawik21

splawik21

Yeah, it's me....
Staff member
Dash Core Group
Foundation Member
Dash Support Group

New binaries are out.​

It fix the recent chain stall and DB.​

Update as soon as possible.​

github.com

Release Dash Platform v1.5.1 · dashpay/platform

Bug Fixes drive: apply batch is not using transaction in remove_all_votes_given_by_identities (#2309) drive: uncommitted state if db transaction fails (#2305)
github.com github.com

​

Dash Platform v1.5.0 >> v1.5.1​

Latest


@shumkov
shumkov released this 16 hours ago
v1.5.0
8aa624e

⚠ BREAKING CHANGES​

  • drive: rotate always to top quorum. This is a breaking change requiring a HF. (#2290)
  • sdk: SDK methods which broadcasting transactions will return SdkError::protocol(ProtocolError::Consensus(..)) instead of DapiClientError(String) in case of validation errors. (#2274)
  • sdk: serialized consensus error moved to a separate gRPC header dash-serialized-consensus-error-bin (#2274)
  • sdk: DapiRequestExecutor::execute and DapiRequest::execute now returns ExecutionResult (#2259)
  • sdk: returned objects are IndexMap/IndexSet instead of previous BTreeMap (#2207)

Features​

  • dashmate: add protocol version to the status command (#2255)
  • sdk: added transfer transition to rs-sdk (#2289)
  • sdk: detect stale nodes (#2254)
  • sdk: provide request execution information (#2259)
  • sdk: return consensus errors from broadcast methods (#2274)
  • sdk: sdk-level retry logic for fetch and fetch_many (#2266)
  • dashmate: cleanup zerossl certs command (#2298)

Bug Fixes​

  • dashmate: invalid mount path from helper (#2296)
  • dashmate: zero ssl certificate draft not saved (#2297)
  • platform: rotate always to top quorum (#2290)
  • dapi: invalid state transition failed with already in chain error (#2270)
  • dashmate: invalid drive status check (#2248)
  • dashmate: invalid platform version in the status command (#2249)
  • document query start to support pagination (#2284)
  • sdk: AddressListError is private (#2278)
  • sdk: opposite retry trigger (#2265)
  • sdk: wrong order of objects returned by Drive (#2207)
  • seed nodes aren't responding (#2276)

Code Refactoring​

  • platform version refactoring into sub versions (#2269)

Miscellaneous Chores​

  • add partial eq to document query (#2253)
  • dashmate: report port check errors (#2245)
  • move BLS Sigs import to Rust Dash Core (#2252)
  • update to latest rust dash core with x11 optional (#2251)
 
Last edited:
@daf

AMD64/x86 (linux):

wget https://github.com/dashpay/platform/releases/download/v1.5.0/dashmate_1.5.0.8aa624e3e-1_amd64.deb
sudo apt update
sudo apt install ./dashmate_1.5.0.8aa624e3e-1_amd64.deb
dashmate stop --platform
dashmate update
dashmate start --platform

ARM64 (linux):

wget https://github.com/dashpay/platform/releases/download/v1.5.0/dashmate_1.5.0.8aa624e3e-1_arm64.deb
sudo apt update
sudo apt install ./dashmate_1.5.0.8aa624e3e-1_arm64.deb
dashmate stop --platform
dashmate update
dashmate start --platform

We also have a new command that you may run after this process. We recommend running it once per ZeroSSL account after updating. This will clean up ssl certificates that were not issued.
Click to expand...

dashmate ssl cleanup
 
  • Like
Reactions: daf
qwizzie said:
@daf

AMD64/x86 (linux):

wget https://github.com/dashpay/platform/releases/download/v1.5.0/dashmate_1.5.0.8aa624e3e-1_amd64.deb
sudo apt update
sudo apt install ./dashmate_1.5.0.8aa624e3e-1_amd64.deb
dashmate stop --platform
dashmate update
dashmate start --platform

ARM64 (linux):

wget https://github.com/dashpay/platform/releases/download/v1.5.0/dashmate_1.5.0.8aa624e3e-1_arm64.deb
sudo apt update
sudo apt install ./dashmate_1.5.0.8aa624e3e-1_arm64.deb
dashmate stop --platform
dashmate update
dashmate start --platform



dashmate ssl cleanup
Click to expand...
DashMate 1.5.0 or Dash Platform 1.5.0 ?
 
Hello! I have some trouble after update to 1.5.0
FAIL_platform1.5.0.png


I have multiple IPs on my server. I think this is a reason because INVALID_IP notification is showed.
With platform 1.4.0 I also received this notification, but all working well.

"dashmate ssl cleanup" command is also failed
FAIL_ssl_cleanup.png


Please give me any instructions how can I solve this problem.
 
CryptoRoller said:
Hello! I have some trouble after update to 1.5.0
View attachment 12696

I have multiple IPs on my server. I think this is a reason because INVALID_IP notification is showed.
With platform 1.4.0 I also received this notification, but all working well.

"dashmate ssl cleanup" command is also failed
View attachment 12697

Please give me any instructions how can I solve this problem.
Click to expand...
https://www.dash.org/forum/index.php?threads/evonode-upgrade-tutorial.55124/page-3#post-239981
 
CryptoRoller said:
"dashmate ssl cleanup" command is also failed
View attachment 12697

Please give me any instructions how can I solve this problem.
Click to expand...
I think if your ssl cert is not yet expired / active (mine still has a month to go before its very first expire/auto-renew moment), it will return
output to 'dashmate ssl cleanup' like that 'Some certificate were not cancelled (0 /1 /1) please try again' because of your still valid cert / nothing there to clean up. I saw the same message. So just ignore it, if it is showing 0 / 1 / 1).

With regards to Platform chain halt, when there is more information it will be posted here i am sure.
 
Last edited:
Update from Quantum:

The Odyssey of our first chain halt is coming to an end. We identified the issue and corrected it so it would not happen again. Please upgrade as soon as possible, those that do not upgrade are at risk of experiencing a stall.

AMD64/x86 (linux):

Code: 
wget https://github.com/dashpay/platform/releases/download/v1.5.1/dashmate_1.5.1.8f924cc0a-1_amd64.deb
sudo apt update
sudo apt install ./dashmate_1.5.1.8f924cc0a-1_amd64.deb
dashmate stop --platform
dashmate update
dashmate start --platform

ARM64 (linux):
Code: 
wget https://github.com/dashpay/platform/releases/download/v1.5.1/dashmate_1.5.1.8f924cc0a-1_arm64.deb
sudo apt update
sudo apt install ./dashmate_1.5.1.8f924cc0a-1_arm64.deb
dashmate stop --platform
dashmate update
dashmate start --platform
Click to expand...
 
what could this be about?

Start mainnet node
✖ Docker Compose error: Container dashmate_dbb2a15d_mainnet-core-1 Created
Container dashmate_dbb2a15d_mainnet-gateway_rate_limiter_redis-1 Created
Container dashmate_dbb2a15d_mainnet-dashmate_helper-1 Created
Container dashmate_dbb2a15d_mainnet-dapi_core_streams-1 Created
Container dashmate_dbb2a15d_mainnet-drive_tenderdash-1 Created
Container dashmate_dbb2a15d_mainnet-gateway_rate_limiter-1 Created
Container dashmate_dbb2a15d_mainnet-gateway-1 Created
Container dashmate_dbb2a15d_mainnet-core-1 Starting
Container dashmate_dbb2a15d_mainnet-gateway_rate_limiter_redis-1 Starting
Container dashmate_dbb2a15d_mainnet-dashmate_helper-1 Starting
Container dashmate_dbb2a15d_mainnet-dapi_core_streams-1 Starting
Container dashmate_dbb2a15d_mainnet-drive_abci-1 Starting
Container dashmate_dbb2a15d_mainnet-dapi_core_streams-1 Started
Container dashmate_dbb2a15d_mainnet-core-1 Started
Container dashmate_dbb2a15d_mainnet-gateway_rate_limiter_redis-1 Started
Container dashmate_dbb2a15d_mainnet-dashmate_helper-1 Started
Error response from daemon: driver failed programming external connectivity on endpoint dashmate_dbb2a15d_mainne…
 
ServiceIsNotRunningError: Service drive_abci for mainnet is not running. Please run the service first.

I figured it out, drive_abci uses port 29090 the same one used by beldex storage server all I had to do was change the port in storage server to 29091
 
The following only concerns Evonodes running version 1.6.1 on older intel machines.In 1.6.x we had enabled some optimizations in order to give a small performance boost in our lower level data processing, however older intel cpus do not support this optimization. Since we did not announce this change, we have decided to revert this optimization, and create a new version 1.6.2 which we will release by tomorrow. We will reenable the optimization in version 1.8.x, so Evonodes on older intel CPUs should have about 2 months or so to upgrade to a more modern cpu.1.6.2 will also have an extra Dashmate fix for some affected nodes. If your node is working fine, there's nothing to do, and there's no need to update to 1.6.2 when we release it.

Original post from Quantum here:
discord.com

Discord - Group Chat That’s All Fun & Games

Discord is great for playing games and chilling with friends, or even building a worldwide community. Customize your own space to talk, play, and hang out.
discord.com discord.com
 
You must log in or register to reply here.
Back
Top