smartcontractkit / chainlink

node of the decentralized oracle network, bridging on and off-chain computation
https://chain.link
Other
6.96k stars 1.69k forks source link

[NODE] Job run page fails to load: `You need to enable JavaScript to run this app` #14556

Closed MarcusWentz closed 6 days ago

MarcusWentz commented 1 week ago

Description

Chainlink node dashboard for job runs debugging at the following URL:

http://localhost:6688/runs/1

fails to load with a blank screen while the rest of the dashboard loads with no issues.

When inspecting the empty page, the following HTML error appears:

<noscript>You need to enable JavaScript to run this app.</noscript>

The Chainlink node version was upgraded from 2.2.0 to 2.16.0, and the error exists in both versions.

Basic Information

2024-09-25T00:13:41.323Z [WARN] Chain length supplied for re-org detection was shorter than the depth from the latest

head to the finalized head. Re-org protection is not working properly. This could indicate a problem with the remote

RPC endpoint, a compatibility issue with a particular blockchain, a bug with this particular blockchain, heads table

being truncated too early, remote node out of sync, or something else. If this happens a lot please raise a bug with

the Chainlink team including a log output sample and details of the chain and RPC endpoint you are using. txmgr/confirmer.go:1063 chainLength=26 latestFinalizedHeadnumber=6730872 logger=EVM.534351.Txm.Confirmer nConsecutiveBlocksChainTooShort=15 version=2.16.0@72a7d23



**Steps to Reproduce**

Run the steps described in the README for this GitHub repository:

https://github.com/MarcusWentz/chainlink-scroll-sepolia
MarcusWentz commented 6 days ago

Seems possibly related to the following issues: https://github.com/smartcontractkit/chainlink/issues/4882 https://github.com/smartcontractkit/chainlink/issues/5208 https://github.com/smartcontractkit/chainlink/issues/5263 https://github.com/smartcontractkit/chainlink/issues/5424

MarcusWentz commented 6 days ago

I am reading through these other issues noted here:

https://github.com/smartcontractkit/chainlink/issues/14556#issuecomment-2374155934

Maybe there is a syntax error in the TOML job specification causing this?

MarcusWentz commented 6 days ago

I think I found the issue.

I have a comment in section

observationSource

for

submit_tx

that I don't think is being detected as a comment. I tried to created a comment with character

#

Are comments allowed in this section? I will remove this comment:

submit_tx    [type="ethtx" to=<OPERATOR_ADDRESS> data="$(encode_tx)"] # Operator.sol contract address.

to have:

submit_tx    [type="ethtx" to=<OPERATOR_ADDRESS> data="$(encode_tx)"] 

then see if it works.

MarcusWentz commented 6 days ago

This fixed the issue: https://github.com/smartcontractkit/chainlink/issues/14556#issuecomment-2374431457 Closing this issue now.