[ZBX-24649] After upgrade 6.4.15 to 7.0 - cannot convert value from double to uint64 Created: 2024 Jun 12  Updated: 2024 Dec 01  Resolved: 2024 Jul 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 7.0.0
Fix Version/s: 7.0.1rc1, 7.2.0alpha1

Type: Problem report Priority: Major
Reporter: Wellington Silva Assignee: Dmitrijs Goloscapovs
Resolution: Fixed Votes: 15
Labels: preprocessing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 001.png     JPEG File image-2024-06-13-17-08-42-914.png     PNG File image-2024-06-15-11-45-47-296.png     PNG File same.PNG     JPEG File zabbix-error.jpg     Text File zabbix_server.log     File zabbix_server.log-3-2     File zabbix_server.log.gz    
Team: Team A
Sprint: S24-W28/29
Story Points: 0.3

 Description   

After upgrading from 6.4.15 to version 7.0 I see these messages in the Zabbix Server log

My Config:

O.S: Debian 12

DB: MariaDB 10.11

Forum Topic: https://www.zabbix.com/forum/zabbix-help/485404-problem-after-upgrade-from-6-4-to-7-0

 

Wellington

 

 



 Comments   
Comment by Yury Larin [ 2024 Jun 13 ]

I have the same issue.

O.S: Debian 12

DB: MariaDB 10.11

Comment by Sergey Sadovnikov [ 2024 Jun 13 ]

i have the same issue 

OS: RedOS 8

DB: psql (PostgreSQL) 16.3 / ClickHouse server version 22.9.7.34 via flask custom app

Comment by Roy Sigurd Karlsbakk [ 2024 Jun 13 ]

Same issue here

OS: Debian 12
DB: PostgreSQL 15.6

Comment by David Stone [ 2024 Jun 13 ]

Same  here.

OS: Ubuntu 22.04

DB: PostgreSQL 16.3

$ tail -6 zabbix_server.log
285258:20240613:113318.002 [3] cannot convert value from double to uint64
285258:20240613:113355.865 [2] cannot convert value from double to uint64
285258:20240613:113455.248 [1] cannot convert value from double to uint64
285258:20240613:113820.004 [3] cannot convert value from double to uint64
285258:20240613:113856.865 [2] cannot convert value from double to uint64
285258:20240613:113955.246 [1] cannot convert value from double to uint64
Comment by Edgar Akhmetshin [ 2024 Jun 13 ]

Please clarify process type printing this messages (history syncer or preprocessing*)?

Use 'ps aux' output to find PID and compare with:  

285258:
285258:
285258:
285258:
285258:
285258:

Increase debug level to level 4 for a related process type and provide log to the issue. 

https://www.zabbix.com/documentation/current/en/manual/concepts/server

 

Comment by Roy Sigurd Karlsbakk [ 2024 Jun 13 ]

  1165:20240613:165045.403 [2] cannot convert value from double to uint64

  1. ps 1233
        PID TTY      STAT   TIME COMMAND
       1233 ?        Sl     3:55 /usr/sbin/zabbix_server: agent poller #1 [got 153 values, queued 153 in 5 sec]

zabbix_server -R log_level_increase='preprocessing manager'

This produced a ton of logs, none of which I found relevant

Comment by Edgar Akhmetshin [ 2024 Jun 13 ]
  1165:20240613:165045.403 [2] cannot convert value from double to uint64

and you are showing the result for:

   1233 ?        Sl     3:55 /usr/sbin/zabbix_server: agent poller #1 [got 153 values, queued 153 in 5 sec]

What is running under 1165 PID? 

Comment by Roy Sigurd Karlsbakk [ 2024 Jun 13 ]
# ps 1165
    PID TTY      STAT   TIME COMMAND
   1165 ?        Sl     1:31 /usr/sbin/zabbix_server: preprocessing manager #1 [queued 62, processed 293 values, idle 5.025887 sec during 5.032369 sec]
# 

 

Comment by Faisal Hariri [ 2024 Jun 13 ]

I am Facing the same issue and pointing also to preprocessing manager #1

 

OS: Redhar 9

DB: mysqld 8.0.37

Comment by David Stone [ 2024 Jun 13 ]
$ ps -fp285258
UID          PID    PPID  C STIME TTY          TIME CMD
zabbix    285258  285226  0 Jun12 ?        00:01:31 /usr/sbin/zabbix_server: preprocessing manager #1 [queued 3, processed 8 values, idle 5.026769 sec during 5
Comment by David Stone [ 2024 Jun 13 ]

I just restarted the server with DebugLevel 4 and ran for a moment.

zabbix_server.log.gz

 

Comment by Roy Sigurd Karlsbakk [ 2024 Jun 13 ]

it's easier to just

 

zabbix_server -R log_level_increase="preprocessing manager" 

so that you don't get all the debug info from all the others

Comment by Steve [ 2024 Jun 14 ]

Here’s mine.  From the server log, it was a preprocessing manager so I increased logging level for that. Nothing interesting seemed to be logged so I ran a few discoveries for laughs and giggles. (Sorry if this image is huge, I’m doing this from a tablet and can’t resize it.)

Running on  

  • Ubuntu 22.04.4 LTS
  • PostgreSQL 16.3 (Ubuntu 16.3-1.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
  • TimeScaleDB 2.15.1 (I was using 2.13.1 and got the “cannot convert value from double to uint64” message; TSDB was upgraded the last time I ran apt upgrade and these messages persist)

Edit: OS and DB version info

zabbix_server.log

 

 

Comment by Yury Larin [ 2024 Jun 14 ]

Has everyone updated proxies to 7.0?

When I tried to update server - I did not finish with proxies and rollback due to error.

May be it is old data from proxies?

Comment by David Stone [ 2024 Jun 14 ]

I am not using any proxies.  I am using timescaledb, but the errors occurred both before and after adding it.

Comment by Steve [ 2024 Jun 15 ]

I noticed one of my network interface speed items was displaying a double to uint64 conversion error in the user interface, so I went into the template and changed the data type from integer to float and now the item is supported.  

Not sure if this provides any insight or provides a realistic workaround.

Comment by Roy Sigurd Karlsbakk [ 2024 Jun 15 ]

Please see attached file. I can see the same here
Preprocessing failed for: -1
1. Failed: cannot apply multiplier "1000000" to value of type "string": cannot convert value from double to uint64

I have not changed the template (yet)

Comment by maryam [ 2024 Jun 18 ]

same problem here for me !!

Comment by Pierre C [ 2024 Jun 24 ]

Same issue here with https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/cctv/hikvision?at=release/7.0 template.

 
cannot convert value from double to uint64
 

Comment by Jack Cheng [ 2024 Jul 02 ]

Hi Hawk128
I updated proxies to 7.0 . The error still there after two weeks.

Comment by Pierre C [ 2024 Jul 02 ]

pirateunclejack please feel free to contribute and fix the issue yourself if you are not happy in the resolution delays (of a open source project).

Comment by Roy Sigurd Karlsbakk [ 2024 Jul 02 ]

PC Last I checked, Zabbix rarely (or never) accept pull requests, so please stop trolling.

Comment by Pierre C [ 2024 Jul 02 ]

Prove it. Do the PR, well talk after that.

Comment by Justin Clift [ 2024 Jul 02 ]

PC Dude, you don't seem to have contributed anything either.

Regardless of that, please stop being an a-hole, filling up people's mail boxes with bad attitude.

Comment by user185953 [ 2024 Jul 03 ]

Yeah, would be nice if log message could hint what item's preprocessing is creating this.

Debian 12, PostgreSQL 15 - double and primary key patches done, no partitioning, no proxies

Comment by Masahide NAKAMURA [ 2024 Jul 04 ]

os     Rocky Linux 9.4 (Blue Onyx)
host   OpenStack Nova 25.0.0
kernel 5.14.0-427.22.1.el9_4.x86_64

I have the same problem, but I found out that The same error was displayed on the Web interface.

following values are weird.

 

[root@host ~]# cat /sys/class/net/eth0/speed
-1

 

Then I disabled the interface speed item and the error disappeared.

Comment by Dmitrijs Goloscapovs [ 2024 Jul 05 ]

Available in versions:

Comment by user185953 [ 2024 Jul 12 ]

So, the solution is removing the warning from log.

Can someone hint how to find all my bad preprocessing rules?

Comment by rrr [ 2024 Jul 22 ]

In my cases, the error was also triggered by the preprocessing manager.
However, this only affected items for which a custom error-handling option was activated.

To narrow down the items in question, the following SQL command may be useful:

SELECT itemid,name,hostid from items WHERE itemid in (SELECT itemid FROM item_preproc WHERE error_handler != 0);
Comment by Bence Mihály Kévés [ 2024 Dec 01 ]

The error is still there, the error has not been resolved for me.

Zabbix version 7.0.6

 

How 

Generated at Sat Apr 26 04:49:34 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.