Difference between revisions of "Proxyd logs"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
ERROR | ERROR | ||
* <code>[[error forwarding request to backend]]</code> | * <code>[[error forwarding request to backend]]</code> | ||
| Line 8: | Line 5: | ||
* <code>[[error proxying websocket]]</code> | * <code>[[error proxying websocket]]</code> | ||
* <code>[[error writing clientConn message]]</code> | * <code>[[error writing clientConn message]]</code> | ||
| − | |||
WARN | WARN | ||
| Line 19: | Line 15: | ||
* <code>[[error updating backend]]</code> | * <code>[[error updating backend]]</code> | ||
* <code>[[backend broke consensus]]</code> | * <code>[[backend broke consensus]]</code> | ||
| + | * <code>[[WARN: XFF header will not contain the proxyd ip address]]</code> | ||
INFO | INFO | ||
| Line 30: | Line 27: | ||
| − | + | ||
Latest revision as of 13:50, 21 October 2024
ERROR
error forwarding request to backendError forwarding RPC batcherror serving requestserror proxying websocketerror writing clientConn message
WARN
backend request failed, trying againbackend banned - not healthybackend banned - unexpected block tagsproxied requests' XFF header will not contain the proxyd ip addresspeer count responded with 200 and 0 peersfailed requesterror updating backendbackend broke consensusWARN: XFF header will not contain the proxyd ip address
INFO
starting proxydUpdating CA certificates.Running CMD.INFO Forwarded RPC requestINFO Received RPC requestINFO Empty routing strategy provided for backend group, using fallback strategy
See also[edit]
Advertising:
