GMC crashes on block submision about go-musicoin HOT 16 CLOSED

I have not seen an issue with the release compiled from source as of yet. I seems to be an issue with pre-compile release v1.5.0.

from go-musicoin.

I've also had the same issue with the binary release of GMC v1.5.0. But after I compiled from source with go 1.6.2, the problem's gone for now.

from go-musicoin.

which build you were using?

from go-musicoin.

Same issue. It happens a couple times a day. I was using the standard release binary, but have recompiled with go1.7.1. See if it happens there

from go-musicoin.

How about Go 1.6x?

from go-musicoin.

This happens on both recent releases (v1.1.0 and v1.5.0). We use build provided in Releases section on GitHub.

Please fix this issue ASAP because it makes mining very unstable.

@EtherNinja any resolution to this problem using GMC recompiled with different go version?

We will try moving back to v1.0.1 and report progress.

@immartian Somewhere on github I read that you use Parity on MC Orbiter. Is it possible to use it for mining as a temporary workaround for this issue?

from go-musicoin.

received several report on crashing with different reasons.
We need to make a thorough investigation on different Go versions(mostly the problem come from).

For Parity, yes, it's stabler for this version of blockchain, but we are going to make big change in next version. So won't be able to support Parity any more.

from go-musicoin.

Can you provide config .json file for Parity ?

We are currently loosing 1/3 of our blocks and orphan rate is still increasing.

from go-musicoin.

under https://github.com/Musicoin/orbiter https://github.com/Musicoin/orbiter/blob/master/mc.json (under Parity 1.5) and https://github.com/Musicoin/orbiter/blob/master/mc_parity16.json (1.6+)

from go-musicoin.

Using 1.5.0 compiled from source (Ubuntu 16.04LTS default Go). No problems.

from go-musicoin.

The binary release used Go 1.7.3, need to check if there introduced any new memory leaks from other communities.

from go-musicoin.

Are you sure Go 1.7.3 ?
$ gmc version
GMC
Version: 1.5.0-stable-c937d2e6
Protocol Versions: [63 62]
Network Id: 7762959
Go Version: go1.8.3
OS: linux
GOPATH=
GOROOT=/usr/local/go

The problem was caused by Go developers. They introduced more strict validation of concurrency errors (especially read write race error) in application code that cause GMC crashes. Iin previous Go versions those errors are logged as warning or ignored, now they cause fatal errors resulting in application crash. As temporal solution we all can compile GMC using old Go version. But for future development those concurrency errors in GMC code should be fixed.

I also confirm that Parity 1.6.10 as workaround works pretty well for mining.

from go-musicoin.

@zet-tech let's have chat in slack, I wonder if there are some other issues we can collaborate.

from go-musicoin.

There's a problem with Go1.8 which is still open (directory structure was made stricter), so for the time being, please use Go1.7 and lower and it should work fine. Worst case, Go1.6 should work as mentioned earlier in the thread.

from go-musicoin.

@zet-tech I found the reason of Go version check because when we build with `make gmc-cross", it goes to docker instead of using local golang compiler. We will build with 1.7.3 for the upcoming release though.

from go-musicoin.

Hi guys, please help test new release of GMC on different platform. I have configured with Go 1.7.3 and all should be smoother this time, if you can help validate. Thanks and close this by now.

from go-musicoin.