Engine logs are filled with errors "integer out of range"

Solution Verified - Updated -

Issue

  • Starting Virtual Machines configured with 2TB of RAM or more make engine.log fill up with errors.
  • Engine logs are filled with errors "integer out of range" on VmsMonitoring.
2021-09-21 04:00:08,904+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-67) [] Exception:: org.springframework.dao.DataIntegrityViolationException: ConnectionCallback; ]; Batch entry 0 select * from public.updatevmstatistics(CAST (0.8 AS numeric),CAST (38.61 AS numeric),CAST (314053.0 AS numeric),CAST (0 AS int4),CAST (3 AS int4),CAST (3 AS int4),CAST ('[]' AS text),CAST ('eec0bb72-92eb-464e-8545-ab0a6f3949a6'::uuid AS uuid),CAST (393296 AS int8),CAST (3222083280 AS int8)) as result was aborted: ERROR: integer out of range

Environment

  • Red Hat Virtualization 4.4.8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content