Just an FYI -
This is in Foreman 1.12. Not sure if it's fixed in later versions.
If you see this in your postgresql log:
2017-07-24 07:03:49 PDT
[sess:5974bf14.47da,pid:18394,vitd:9/4891447,tid:0,db:myforemandb]ERROR:
integer out of range
2017-07-24 07:03:49 PDT
[sess:5974bf14.47da,pid:18394,vitd:9/4891447,tid:0,db:myforemandb]STATEMENT:
INSERT INTO "logs" ("message_id", "source_id", "report_id", "level_id",
"created_at", "updated_at") VALUES ($1, $2, $3, $4, $5, $6) RETURNING "id"
You might want to check the log id #:
myforemandb=> select * from logs order by created_at desc limit 2;
id | source_id | message_id | report_id | level_id |
created_at | updated_at
------------+-----------+------------+-----------+----------+----------------------------+----------------------------
2147483647 | 321 | 1807107 | 292344055 | 2 | 2017-07-24
12:08:01.668757 | 2017-07-24 12:08:01.668757
2147483646 | 23451033 | 18001958 | 292344087 | 2 | 2017-07-24
12:08:01.663546 | 2017-07-24 12:08:01.663546
(2 rows)
That first id listed is 2^31-1. It turns out that "id" is a signed int,
meaning it's 32-bit. I cannot write more logs to the logs table now :)
(And before someone brings up my other question - locking issues are
unrelated to hitting this limit, they were happening before this happened.)
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
