Consensys / quorum-kubernetes

Helm charts for Hyperledger Besu and GoQuorum
Apache License 2.0
119 stars 129 forks source link

Elixir Error in consensys/blockscout:v4.1.5-beta #170

Closed MaximilianIML closed 2 years ago

MaximilianIML commented 2 years ago

Hello everyone. I successfully added consensys/blockscout:v4.0.0-beta-Image to my GoQuorum network on Openshift cluster.

Unfortunatelly Blockscout is not able to index a transaction. Instead I got an error with the following message: {:unknown_key, %{key: "isPrivacyMarkerTransaction", value: false}} This problem is already discribed in https://github.com/blockscout/blockscout/issues/4995.

So I tried the same tutorial (https://consensys.net/docs/goquorum/en/latest/tutorials/kubernetes/deploy-charts/#9-blockchain-explorer) with the newer image consensys/blockscout:v4.1.5-beta. But now I run in an Elixir error:

** (Mix) Could not start application explorer: Explorer.Application.start(:normal, []) returned an error: shutdown: failed to start child: Explorer.Repo
    ** (EXIT) an exception was raised:
        ** (Protocol.UndefinedError) protocol Enumerable not implemented for nil of type Atom. This protocol is implemented for the following type(s): DBConnection.PrepareStream, DBConnection.Stream, Date.Range, Ecto.Adapters.SQL.Stream, File.Stream, Floki.HTMLTree, Flow, Function, GenEvent.Stream, HashDict, HashSet, IO.Stream, Indexer.BoundQueue, Jason.OrderedObject, List, Map, MapSet, Postgrex.Stream, Range, Stream, Timex.Interval
            (elixir 1.13.1) lib/enum.ex:1: Enumerable.impl_for!/1
            (elixir 1.13.1) lib/enum.ex:143: Enumerable.reduce/3
            (elixir 1.13.1) lib/enum.ex:4144: Enum.reverse/1
            (elixir 1.13.1) lib/keyword.ex:186: Keyword.new/2
            (explorer 0.0.1) lib/explorer/repo/config_helper.ex:34: Explorer.Repo.ConfigHelper.extract_parameters/1
            (explorer 0.0.1) lib/explorer/repo/config_helper.ex:25: Explorer.Repo.ConfigHelper.get_db_config/1
            (explorer 0.0.1) lib/explorer/repo.ex:20: Explorer.Repo.init/2
            (ecto 3.7.1) lib/ecto/repo/supervisor.ex:25: Ecto.Repo.Supervisor.runtime_config/4

Do you have any idea how I could solve one these issues? I do not care, if I use 4.0.0 or 4.1.5, I just want Blockscout to show transactions.

joshuafernandes commented 2 years ago

Hi @MaximilianIML, thankyou for raising this. Unfortunately, this is something we don't provide support for and recommend you raise this on the Blockscout issues page here: https://github.com/blockscout/blockscout/issues. Would be worth reopening #4995 with steps to reproduce

CurralesDragon commented 2 years ago

Did you ever find a solution for this?

MaximilianIML commented 2 years ago

@nicwhitts No, unfortunately the problem persists.

CurralesDragon commented 2 years ago

I downgraded to 4.0.0 and it got me a working build. But I didn’t have your other error

On 4 Nov 2022, at 20:32, MaximilianIML @.***> wrote:

 @nicwhitts No, unfortunately the problem persists.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

CurralesDragon commented 2 years ago

Actually i do have the same error!

YounesBM commented 1 year ago

Hi guys,

I know it's a little bit late but i'm running blockscout v5.0.0-beta, and I had the same issue.

You need to provide a DATABASE_URL that matches this regex:

https://github.com/blockscout/blockscout/blob/e8e52edb47f2ab9884d9383127c736ceb0e21c93/apps/explorer/lib/explorer/repo/config_helper.ex#L45

Therefore, you probably need to add the port for postgresql like this:

ecto://postgres_user>:<postgres_password>@<pod_name:/

Hope this helps :)