search

livepeer / go-livepeer

Official Go implementation of the Livepeer protocol
http://livepeer.org
MIT License
546 stars 173 forks source link

Header Missing when Attempting to Send Livepeer Orchestrator Configuration #1955

Open GistKen opened 3 years ago

GistKen commented 3 years ago

Describe the bug Encounter HTTP error of being unable to find http header when sending orchestrator configuration

To Reproduce Steps to reproduce the behavior:

Expected behavior Encounter HTTP error of being unable to find http header when sending orchestrator configuration

Screenshots


Jul 15 14:55:03 LivepeerOrchestratorEast livepeer[3428]: I0715 14:55:03.689767    3428 webserver.go:1235] Price per pixel set to 800 wei for 1 pixels
Jul 15 14:55:03 LivepeerOrchestratorEast livepeer[3428]: I0715 14:55:03.698395    3428 webserver.go:42] Storing service URI https://23.23.26.25:8935 in service registry...
Jul 15 14:55:03 LivepeerOrchestratorEast geth[2982]: WARN [07-15|14:55:03.793] Served eth_getCode                       conn=127.0.0.1:36226 reqid=57 t="46.276µs"    err="header not found"
Jul 15 14:55:03 LivepeerOrchestratorEast livepeer[3428]: E0715 14:55:03.793410    3428 webserver.go:46] header not found
Jul 15 14:55:03 LivepeerOrchestratorEast livepeer[3428]: E0715 14:55:03.793432    3428 webserver.go:449] header not found
Jul 15 14:55:03 LivepeerOrchestratorEast livepeer[3428]: E0715 14:55:03.793440    3428 handlers.go:26] HTTP Response Error 500: header not found
Jul 15 14:55:08 LivepeerOrchestratorEast geth[2982]: INFO [07-15|14:55:08.546] Imported new block headers               count=1    elapsed=5.674ms   number=```

**Desktop (please complete the following information):**
 - OS: Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-1038-aws x86_64)
 - Livepeer version 0.5.18-41ebbc66
yondonfu commented 3 years ago

Looks like the "header not found" error originates from geth. Are you running a full node or light node? Can you also confirm that geth was fully synced when the error occurred?

GistKen commented 3 years ago

I was running with a light geth node that was synced. I believe Chia also runs with a light geth node. Let me ask in discord

GistKen commented 3 years ago

It appears that you're correct. It is associated with running a geth node in light mode. When running with a full geth node and I do not get that issue. It seemed one individual was seeing the message as well and one person was not seeing that issue.