Failed INSERT INTO Server_Stats

Current Development version likely to have breaking changes
Post Reply
Anna.N
Posts: 12
Joined: Sun Feb 25, 2024 10:55 am

Failed INSERT INTO Server_Stats

Post by Anna.N »

Since a few days my log is filled with the following message every minute.

Failed INSERT INTO Server_Stats (ServerId, TimeStamp, CpuLoad, CpuUserPercent, CpuNicePercent, CpuSystemPercent, CpuIdlePercent, CpuUsagePercent, TotalMem, FreeMem, TotalSwap, FreeSwap) VALUES ('',NOW(),?,?,?,?,?,?,?,?,?,?) :Data truncated for column 'CpuLoad' at row 1

I have no clue where to look for. For the time being I just commented the lines out in zmstats.pl

(1.37.56~20240320.53-bookworm amd64)
Detlef Paschke
Posts: 27
Joined: Tue Sep 12, 2023 6:14 pm

Re: Failed INSERT INTO Server_Stats

Post by Detlef Paschke »

t's the same here under Debian12, since today's update (1.37.56~20240320.53-bookworm) via (1.37.55~20240315.181-bookworm).

Best regards
Detlef Paschke
Anna.N
Posts: 12
Joined: Sun Feb 25, 2024 10:55 am

Re: Failed INSERT INTO Server_Stats

Post by Anna.N »

Remark: it only happens on debian bookworm on a amd64 PC. Even on a clean install. No problem on armhf and arm64 with bookworm.
Anna.N
Posts: 12
Joined: Sun Feb 25, 2024 10:55 am

Re: Failed INSERT INTO Server_Stats

Post by Anna.N »

After further investigation changing system locale from de_DE to en_US seem to have solved the problem.
Obviously the different decimal separator used in Germany caused the problem.
User avatar
iconnor
Posts: 2904
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: Failed INSERT INTO Server_Stats

Post by iconnor »

Turn on debug logging, it should log the values being sent.
Anna.N
Posts: 12
Joined: Sun Feb 25, 2024 10:55 am

Re: Failed INSERT INTO Server_Stats

Post by Anna.N »

As Expected:
de_DE Cpuload: 0,88 0,60 0,27
en_US Cpuload: 0.92 0.71 0.37
User avatar
iconnor
Posts: 2904
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: Failed INSERT INTO Server_Stats

Post by iconnor »

Current builds should have this fixed.
Post Reply