Bug #13810: Reports fail to upload, Mysql2::Error: Out of range value for column 'id' (logs table) - Foreman

Custom queries

3.11.5 release DONE
3.11.5 release TODO
3.12.1 release DONE
3.12.1 release TODO
3.13.0 release DONE
3.13.0 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #13810

closed

Reports fail to upload, Mysql2::Error: Out of range value for column 'id' (logs table)

Added by Doug Forster almost 9 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Timo Goebel

Category:

Database

Target version:

1.15.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/4169

Fixed in Releases:

Found in Releases:

1.10.0

Red Hat JIRA:

Description

| ActiveRecord::StatementInvalid: Mysql2::Error: Out of range value for column 'id' at row 1: INSERT INTO `logs` (`created_at`, `level_id`, `message_id`, `report_id`, `source_id`, `updated_at`) VALUES ('2016-02-19 04:48:08', 1, 9, 128052331, 3, '2016-02-19 04:48:08')

Related issues 5 (0 open — 5 closed)

Related to Foreman - Bug #18130: Fail to import facts and reports - auto increment ID is no longer set on many reports and facts table.	Closed	Timo Goebel	01/18/2017	Actions
Has duplicate Foreman - Bug #17270: Running out of IDs in logs table	Duplicate		11/08/2016	Actions
Has duplicate Foreman - Feature #17251: Data type of the id on 'big' tables	Duplicate		11/07/2016	Actions
Has duplicate Foreman - Bug #17999: Fact values id exceeds mysql maximum	Duplicate		01/10/2017	Actions
Has duplicate Foreman - Bug #20423: Foreman DB logs index out of range	Duplicate		07/26/2017	Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Doug Forster almost 9 years ago

Foreman 1.10.0

Actions

Copy link

Updated by Dominic Cleal almost 9 years ago

Category set to Database

IIRC the default length is 4 bytes for an integer column, you might be able to alter the schema and widen the logs.id column as a workaround.

Actions

Copy link

Updated by Dominic Cleal almost 9 years ago

Subject changed from Puppet reports are no longer being processed to Reports fail to upload, Mysql2::Error: Out of range value for column 'id' (logs table)

Actions

Copy link

Updated by Jason Hane almost 9 years ago

We just ran into a similar issue. I noticed the ID columns are not unsigned so I altered the tables to make them so. I believe that should be the default. Also at some point since we're purging reports after 90 days we could probably reset the auto increment to 1. Would that cause any issues?

Actions

Copy link

Updated by Dominic Cleal almost 9 years ago

Jason, this is just a join table between reports/messages/sources, so they're not going to be referenced anywhere else. I don't know if MySQL will skip IDs that are already in use though if the logs aren't expired exactly in order, but I guess it's probably going to be OK.

Actions

Copy link