Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #1401] postgresql: integer not big enough for bytes_processed #611

Closed
icinga-migration opened this issue Apr 12, 2011 · 6 comments
Milestone

Comments

@icinga-migration
Copy link

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)

Icinga Version: 1.10.0
OS Version: any

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:

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'

Changesets

2011-04-28 20:52:09 +00:00 by mfriedrich e914b5b

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

2011-05-03 20:36:10 +00:00 by Tommi c46e5e1

Fix int(11) to small #1173
Fix integer not big enough #1401
refs #1173,#1401

2011-05-03 20:59:45 +00:00 by Tommi 874e2ad

includes all patchesi and features in upgrade/*.sql
refs #1354,#1355,#1358,#1363,#1401,#1173

2011-05-03 21:04:22 +00:00 by Tommi be82317

fix int(11) to small #1173
fix int not large enogh #1401
drop constraints #1355
refs #1401,#1355,1173

2011-05-03 21:08:39 +00:00 by Tommi ed19196

includes all fixes from upgrade
refs #1401,#1173,#1355

2011-05-03 21:27:58 +00:00 by Tommi c74b02e

fixes for mysql int(11) to small #1173,
integer not big enough #1401
remove not null constraints #1355
refs #1355,#1401,#1173

2011-05-03 21:48:11 +00:00 by Tommi 2f773b2

includes all fixes from upgrade_1.4
remove unwanted characters
refs #1173,#1401,#1355

2011-05-04 16:52:26 +00:00 by Tommi 2b806b2

increase serveroutput buffer size to prevent buffer overflow #1173
refs #1173,#1401

Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-04-27 22:52:22 +00:00

  • Target Version set to 1.4

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-04-28 20:53:06 +00:00

  • Status changed from New to Feedback
  • Assigned to set to mfriedrich
  • Done % changed from 0 to 100

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-05-02 16:01:58 +00:00

  • Status changed from Feedback to Resolved

@icinga-migration
Copy link
Author

Updated by gschroll on 2012-01-05 13:35:30 +00:00

The changes are not reflected in the pgsql upgrade scripts. When upgrading from < 1.4 the bug still exists.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-01-05 13:40:18 +00:00

upgrades need to be done incremential, so when upgrading from let's say 1.3.0, you'll do the following (like the debian db-config does for you)

apply

1.3.0
1.4.0
1.5.0
1.6.0

done. more on that on the docs - http://docs.icinga.org/latest/en/upgrading\_idoutils.html

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!

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-12-08 14:35:48 +00:00

  • Project changed from 18 to Core, Classic UI, IDOUtils
  • Category changed from 24 to IDOUtils
  • Icinga Version set to 1
  • OS Version set to any

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant