Project

General

Profile

Actions
Copy link

Bug #38949

closed

Log file count can reach max int for `logs_id_seq`

Added by Quinn James 4 months ago. Updated 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Logging
Target version:
-
Difficulty:
trivial
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/10801, https://github.com/theforeman/foreman/pull/10743
Fixed in Releases:
3.18.0
Found in Releases:
Nightly
Red Hat JIRA:
SAT-38813

Description

For users with many hosts running for a long time, we can reach the integer limit for the log id sequence (logs_id_seq). We can safely change this integer to a bigint with no worries (see linked thread for fix). Example error message: 

Error importing log messages for report ID: XXXXX: PG::SequenceGeneratorLimitExceeded: ERROR:  nextval: reached maximum value of sequence "logs_id_seq" (XXXXX)
XXXXX

This bug was discovered in this support thread by Jeff Sparrow: https://community.theforeman.org/t/pg-error-nextval-reached-maximum-value-of-sequence-logs-id-seq-2147483647/45095

Actions
Copy link
 #1

Updated by The Foreman Bot 4 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/10801 added
Actions
Copy link
 #2

Updated by Ewoud Kohl van Wijngaarden 4 months ago

  • Red Hat JIRA set to SAT-38813
Actions
Copy link
 #3

Updated by The Foreman Bot 3 months ago

  • Fixed in Releases 3.18.0 added
Actions
Copy link
 #4

Updated by Anonymous 3 months ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link
 #5

Updated by The Foreman Bot 2 months ago

  • Pull request https://github.com/theforeman/foreman/pull/10743 added
Actions
Copy link

Also available in: Atom PDF