I'm a bit new to this so apologies in advance if this question is bit vague or ill-defined, but I'm trying to set up a new Chainlink OCR node and add a job to it. I have the node running and can successfully add a job but almost immediately see the error:
TrackConfig: error during LatestConfigDetails()
Has anyone experienced this, or know even what config details it's referring to? I'm not sure where to even start trying to trouble shoot. Thanks so much!
Typically, this means that there is an issue with the OCR configuration on-chain, or you ETH node is out of sync.
Please test your node is up to date.
Related
Hello I was following this tutorial: https://docs.elrond.com/developers/tutorials/your-first-dapp/
With the help of: https://www.youtube.com/watch?v=IdkgvlK3rb8
But I think there is some difference between the dApp repository and the tutorial, first the src/config.devnet.tsx disappeared we now have an src/config.tsx already present (not a big deal).
I'm blocked when I try to do the ping, in the console I got the error Sender not allowed with value erd1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq6gq4hu.
So my guess is that I've done something wrong deploying the contract, but I tried to redeploy other contracts I always ended up with the same error.
I tried natively on my ubuntu 20.04, and then in a devcontainer using an Ubuntu 22.04 image.
I'm pretty new to Elrond, Crypto (and also Node) so I might be missing something.
Thanks for your help!
I've just completed the tutorial and I think that you put the wrong SC address in src/config.tsx. The address you provided is the SC that handles other SC deployments. You have to replace it with your SC's address generated after deployment.
I am using elasticsearch in a liferay portal (sidecar). Unfortunately, elasticsearch can only be startet as root user. Otherwise, I get a java native error in
org.elasticsearch.bootstrap.JNANatives.trySetMaxNumberOfThreads on bootstrapping:
V [libjvm.so+0x687142] InterpreterRuntime::resolve_invoke(JavaThread*, Bytecodes::Code)+0x1b2
j org.elasticsearch.bootstrap.JNANatives.trySetMaxNumberOfThreads()V+20
j org.elasticsearch.bootstrap.Natives.trySetMaxNumberOfThreads()V+17
j org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Ljava/nio/file/Path;ZZZ)V+75
I have checked/updated the ulimits for the current user, but it seems like JNANatives is not allowed to execute this methods. The service starts fine as root, but I want to avoid any root processes on the server. Does someone had a similar problem? How can I debug this? What could be the issue here?
Many thanks
Now, I found the problem and want to share it here, so that anyone has a similar issues finds a possible hint.
I figured out that some folders up the hierarchy, there was a mount involved causing some permission issues. This causes a hotspot JVM native error in org.elasticsearch.bootstrap.JNANatives.trySetMaxNumberOfThreads().
Liferay reports java.io.StreamCorruptedException: invalid type code: 23 for elasticsearch.
I thought it was due to a ulimit, but it wasn't. Fixing mount/folder permissions on a top level folder, resolved the bootstrapping issues.
Cross-posting from https://groups.google.com/forum/#!topic/kythe/86kNuSCeorI, since I was directed here by Beam faq for Beam questions.
In short, I run a job written using the golang sdk successfully using the direct runner, but trying to use the dataflow runner I get the following error in the google cloud console:
2019-02-17 (12:03:53) Step with name e19 already exists. Duplicates
are not allowed.
I attach the plan that was printed to the stderr at https://pastebin.com/vpu3U52j. Grepping for e19: https://pastebin.com/L24L1guT.
I'm not very familiar with beam yet. I wonder which part is responsible for generating the step names? What are likely causes of a collision?
Thank you!
It was a bug actually, sent PR to beam.
first of all sorry for my English, as it's not my mother tongue I am not used to it and it might be hard to understand.
I am trying to connect my spike application to heroku in order to get long-term glucose data.
I success all the step without "deploy the branch" step.
(deploy the github branch)
I checked all the API secret (no blanck, qualified with letter length), mongo uri.. I even delete all account (github, heroku) and re-register.. but I could not solve the problem.
I do not know anything about logs and any other server lanugage (do not know even how to call javascript things..)
Can you tell me how to solve this problem?
I will attach the picture in case of you guys do not understand my words..
Thank you!! :)
Try logging into your Heroku account and then select your application and finally click on view logs.
and check the logs that will help you to figure your mistake
I tried to play with LowCardinality setting, I got a message saying that this is an experimental feature and I have to SET allow_experimental_low_cardinality_type = 1 in order to use it.
I executed this command inside clickhouse-client and then I restarted the server. But I got
clickhouse-server.service: Unit entered failed state
Now I am trying to find out how to disable this setting and make my clickhouse-server start again.
Can you help with this please ?
PS: The version I use is the 18.12.17 and I installed it on Linux Ubuntu 16.04
ClickHouse has different layers for settings. If you used SET <setting> = <value> then you set it for current session. You don't need to restart ClickHouse. Please, take a look here.
I suppose you faced with another problem during starting your server. There a bunch of reasons why. So, firstly try to recollect what were done in configs since last restart (because you have just applied changes by restarting server).
Digging into logs also an awesome idea. Don't hesitate to check other similar issues on github.com, for example like this one