Bug #2217: Successfull run of reports:expire produces warnings - Foreman

Actions

Copy link

Bug #2217

closed

Successfull run of reports:expire produces warnings

Added by Igor Galić about 11 years ago. Updated about 11 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Dominic Cleal

Category:

Packaging

Target version:

1.2.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

/usr/local/share/foreman/vendor/ruby/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:10: warning: already initialized constant ENC_NONE
/usr/local/share/foreman/vendor/ruby/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:11: warning: already initialized constant ENC_EUC
/usr/local/share/foreman/vendor/ruby/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:12: warning: already initialized constant ENC_SJIS
/usr/local/share/foreman/vendor/ruby/1.8/gems/ruby_parser-2.3.1/lib/ruby_parser_extras.rb:13: warning: already initialized constant ENC_UTF8

While this seems innocuous at first, when running this from cron in an environment of hundreds and hundreds of servers it can become noisy, desensitise and most importantly drown out when there's a real issue, because people just start ignoring everything that comes from that server

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Dominic Cleal about 11 years ago

Status changed from New to Closed

This is a bug in the older ruby_parser gem we use, it's been fixed in ruby_parser 3.x which is in Foreman 1.1. We're also redirecting cron output to a log in future packages which should help.

Actions

Copy link