On the server score pages there is the following error message, after the Client distribution title:
Metrics error: JSON.parse: unexpected character at line 1 column 1 of the JSON data
It looks like the same issue is there for the beta and production server score pages.
I see the same, but only on the ones with IPv6 addresses.
I get: “Metrics error: Unexpected token ‘s’, "sql: Scan "… is not valid JSON”
Digging deeper, this seems to be the underlying error message:
“sql: Scan error on column index 1, name “netspeed_active”: converting driver.Value type uint8 (“2318251396”) to a int32: value out of range”
Maybe there’s some IPv6 server that has an invalid netspeed setting, causing the “sum of netspeeds across all servers” calculation to fail.
I see this message for all my pool servers, all IPv6:
Metrics error: The string did not match the expected pattern
As I mentioned at Metrics error: The string did not match the expected pattern.
Have you installed the latest monitor and JSON file?
Mybe they are corrupted? Or create a new token.
When I have problems, I create a new token and/or reinstall the monitor.
Often that solves the problem.
This does not seem to be a client side issue at all.
Fixed – the total netspeed in the database started to exceed 32-bits (and with MySQL sqlc defaults to 32-bit numbers without some help sometimes)! Another reason, other than the database outages, to get the database switched to Postgres.
(In the database the netspeed is stored approximately as “kbps”)
