Project

General

Profile

Bug #8294

Warning! Infinity

Added by David LeVene almost 5 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Settings
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Viewing any page in puppet report in detail apart from the dashboard reports this error.

This foreman instance is being used for yaml reports only and facts (not ENC)

Started GET "/reports?search=eventful+%3D+true" for IPv6 Address at 2014-11-06 11:08:01 +1030
Processing by ReportsController#index as HTML
Parameters: {"search"=>"eventful = true"}
Rendered reports/_list.html.erb (132.4ms)
Rendered reports/index.html.erb within layouts/application (143.7ms)
Operation FAILED: Infinity
Rendered common/500.html.erb within layouts/application (6.3ms)
Rendered layouts/base.html.erb (2.8ms)
Completed 500 Internal Server Error in 333ms (Views: 12.9ms | ActiveRecord: 5.5ms)

FloatDomainError
Infinity
app/helpers/layout_helper.rb:236:in `page_entries_info'
app/views/reports/_list.html.erb:38:in `_app_views_reports__list_html_erb___3954372958302584947_59000000'
app/views/reports/index.html.erb:3:in `_app_views_reports_index_html_erb___1614328706684788426_57442080'
app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'
lib/middleware/catch_json_parse_errors.rb:9:in `call'


Related issues

Related to Foreman - Bug #7579: Session reset after each page request, idle_timeout set to zeroResolved2014-09-22

History

#1 Updated by David LeVene almost 5 years ago

This was a fresh installation yesterday, and has only had reports being provided to it overnight

#2 Updated by Dominic Cleal almost 5 years ago

Could you perhaps check entries_per_page is set to a reasonable number under Adminster > Settings? If you can't get to it, you may have to check the database or set :entries_per_page: 20 in /etc/foreman/settings.yaml instead.

#3 Updated by David LeVene almost 5 years ago

Thanks - that resolved it, there were several other issues being experienced and they were due to other settings being set to 0 as well (like puppet report expiry to 0 minutes)

Would it be worth considering a check on foreman install that if these values are set to 0 to throw a warning at the end of the install process or set them to what should be defaults?

#4 Updated by Dominic Cleal almost 5 years ago

  • Related to Bug #7579: Session reset after each page request, idle_timeout set to zero added

#5 Updated by Dominic Cleal almost 5 years ago

  • Category changed from Inventory to Settings

Hm okay, that sounds a bit like #7579 which is another setting that's set to zero after installation. Which OS are you using, and did you use the default installer options with PostgreSQL?false

#6 Updated by David LeVene almost 5 years ago

Dominic Cleal wrote:

Hm okay, that sounds a bit like #7579 which is another setting that's set to zero after installation. Which OS are you using, and did you use the default installer options with PostgreSQL?false

Using scientific Linux 6.5, fresh install. For the installer used all the defaults, but didn't install a puppet master. I did run the installer twice as the first time it had issues with yum repos which were unrealted.

Since then i did drop the db and recreated it by running the installer again, but had same issue. The fix you recommended worked.

If you want more details happy to provide, but im not at work right now.

#7 Updated by Stephen Repetski over 4 years ago

I ran into this issue as well on CentOS 7.1 and Foreman 1.8.0-RC2. Setting the entries_per_page config fixed the issue.

#8 Updated by Stephen Benjamin about 4 years ago

User popped by on #katello with the same problem, entries_per_page somehow was reset to 0, and as far as they know it wasn't them that changed that particular setting

#9 Updated by Michael Moll over 2 years ago

  • Status changed from New to Resolved

should be resolved by now

Also available in: Atom PDF