You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Heimdall seems running seamless, Bor is in sync and no issues as far as I can tell, suddenly getting many ERRORs which if my assumption is correct are not really errors but just WARNINGs.
In case it's normal and does not cause serious issues why at first place they are ERRORs? Such strong severity without a strong particular reason leads to a lot of false positive alerts in case automated log analysis is used, it's basically triggers anomaly alerts.
Could you please consider changing severities or is it signaling that node is sick?
I can tell the same about Bor which does the opposite (borrowed from Bor issues):
WARN [11-30|11:10:27.352] Synchronisation failed, dropping peer peer=1673b28af0061121f1ec941aae813b2c5907d3b7fcde0746aee66d28ce2e8247 err="retrieved hash chain is invalid: invalid merkle root (remote: 55f9a3e801a05d3330f06aa1a9ba9a09fe7979230d50846bb9d886c96383755e local: e18a8fbe060ebefdc86cd2f2a5d0c14f70f6dfcc7252efe232c4c867ef37a01f) dberr: %!w(<nil>)"
WARN [11-30|11:10:27.352] Synchronisation failed, retrying peer=1673b28af0061121f1ec941aae813b2c5907d3b7fcde0746aee66d28ce2e8247 err="peer is unknown or unhealthy"
INFO [11-30|11:10:34.342] Got new milestone from heimdall start=50,570,307 end=50,570,319 hash=0xf1d3d69bd5d203c84d9e697a47ef078b91bea1b230508f3e6013aefde6a6aa1f
WARN [11-30|11:10:34.343] unable to handle whitelist milestone err="missing blocks"
INFO [11-30|11:10:46.343] Got new milestone from heimdall start=50,570,307 end=50,570,319 hash=0xf1d3d69bd5d203c84d9e697a47ef078b91bea1b230508f3e6013aefde6a6aa1f
WARN [11-30|11:10:46.343] unable to handle whitelist milestone err="missing blocks"
INFO [11-30|11:10:58.343] Got new milestone from heimdall start=50,570,307 end=50,570,319 hash=0xf1d3d69bd5d203c84d9e697a47ef078b91bea1b230508f3e6013aefde6a6aa1f
WARN [11-30|11:10:58.343] unable to handle whitelist milestone err="missing blocks"
If synchronisation fails it's a serious issue and its severity must be ERROR.
The text was updated successfully, but these errors were encountered:
v1.0.5
Heimdall seems running seamless, Bor is in sync and no issues as far as I can tell, suddenly getting many
ERROR
s which if my assumption is correct are not really errors but justWARNING
s.In case it's normal and does not cause serious issues why at first place they are
ERROR
s? Such strong severity without a strong particular reason leads to a lot of false positive alerts in case automated log analysis is used, it's basically triggers anomaly alerts.Could you please consider changing severities or is it signaling that node is sick?
I can tell the same about Bor which does the opposite (borrowed from Bor issues):
If synchronisation fails it's a serious issue and its severity must be
ERROR
.The text was updated successfully, but these errors were encountered: