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
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
I get the following error in my log after running icinga for a few days:
2011-04-10 05:46:21 CEST [c=::1 u=icinga d=icinga] ERROR: value "4094872926" is out of range for type integer at character 69
2011-04-10 05:46:21 CEST [c=::1 u=icinga d=icinga] STATEMENT: UPDATE icinga_conninfo SET last_checkin_time=NOW(), bytes_processed='4094872926', lines_processed='357263247', entries_processed='9716166' WHERE conninfo_id='1'
idoutils: fix postgresql: integer not big enough for bytes_processed (Stig Sandbeck) #1401
add upgrade scripts for pgsql/mysql too.
fix minor compiler warning.
refs #1401
Note
If you are upgrading from an older version and there are other versions in between be advised that you need to apply those upgrade files with incremental steps!
This issue has been migrated from Redmine: https://dev.icinga.com/issues/1401
Created by ssm on 2011-04-12 10:56:23 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2011-05-02 16:01:58 +00:00)
Target Version: 1.4
Last Update: 2014-12-08 14:35:48 +00:00 (in Redmine)
It looks like the "integer" type is not big enough for icinga_conninfo.bytes_processed. Please consider using "bigint" instead, re http://www.postgresql.org/docs/9.0/static/datatype-numeric.html
I get the following error in my log after running icinga for a few days:
Changesets
2011-04-28 20:52:09 +00:00 by mfriedrich e914b5b
2011-05-03 20:36:10 +00:00 by Tommi c46e5e1
2011-05-03 20:59:45 +00:00 by Tommi 874e2ad
2011-05-03 21:04:22 +00:00 by Tommi be82317
2011-05-03 21:08:39 +00:00 by Tommi ed19196
2011-05-03 21:27:58 +00:00 by Tommi c74b02e
2011-05-03 21:48:11 +00:00 by Tommi 2f773b2
2011-05-04 16:52:26 +00:00 by Tommi 2b806b2
Relations:
The text was updated successfully, but these errors were encountered: