Hello,
We are running theforman 1.11.4 on a centos 6.8.
I very often get this event log in the production.log file, and it seems to
be related to several problems we encountered on performances.
Do you know if it's due to a known bug or a configuration problem on our
side ?
2016-10-13 12:06:05 [app] [I] Started GET "/mod_status?auto" for 127.0.0.1
at 2016-10-13 12:06:05 +0200
*2016-10-13 12:06:05 [app] [F] *
- | ActionController::RoutingError (No route matches [GET] "/mod_status"):*
- | actionpack (4.1.5)
lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'*
- | actionpack (4.1.5)
lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'*
- | railties (4.1.5) lib/rails/rack/logger.rb:38:in `call_app'*
- | railties (4.1.5) lib/rails/rack/logger.rb:22:in `call'*
- | actionpack (4.1.5) lib/action_dispatch/middleware/request_id.rb:21:in
`call'*
- | rack (1.5.2) lib/rack/methodoverride.rb:21:in `call'*
- | rack (1.5.2) lib/rack/runtime.rb:17:in `call'*
- | activesupport (4.1.5)
lib/active_support/cache/strategy/local_cache_middleware.rb:26:in `call'*
- | actionpack (4.1.5) lib/action_dispatch/middleware/static.rb:64:in
`call'*
- | rack (1.5.2) lib/rack/sendfile.rb:112:in `call'*
- | railties (4.1.5) lib/rails/engine.rb:514:in `call'*
- | railties (4.1.5) lib/rails/application.rb:144:in `call'*
- | railties (4.1.5) lib/rails/railtie.rb:194:in `public_send'*
- | railties (4.1.5) lib/rails/railtie.rb:194:in `method_missing'*
- | rack (1.5.2) lib/rack/builder.rb:138:in `call'*
- | rack (1.5.2) lib/rack/urlmap.rb:65:in `block in call'*
- | rack (1.5.2) lib/rack/urlmap.rb:50:in `each'*
- | rack (1.5.2) lib/rack/urlmap.rb:50:in `call'*
- |
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in
`process_request'*
- |
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:140:in
`accept_and_process_next_request'*
- |
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:108:in
`main_loop'*
- |
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler.rb:441:in
`block (3 levels) in start_threads'*
- | logging (1.8.2) lib/logging/diagnostic_context.rb:323:in `call'*
- | logging (1.8.2) lib/logging/diagnostic_context.rb:323:in `block in
create_with_logging_context'*
many thanks for helping.
> Hello,
>
> We are running theforman 1.11.4 on a centos 6.8.
> I very often get this event log in the production.log file, and it seems
> to be related to several problems we encountered on performances.
Please use the foreman-users mailing list for questions and support,
this list is for development discussions only, which this isn't.
(http://groups.google.com/group/foreman-users,
Foreman :: Support)
> Do you know if it's due to a known bug or a configuration problem on our
> side ?
>
> /
> /
> /2016-10-13 12:06:05 [app] [I] Started GET "/mod_status?auto" for
> 127.0.0.1 at 2016-10-13 12:06:05 +0200/
> /2016-10-13 12:06:05 [app] [F] /
> / | ActionController::RoutingError (No route matches [GET] "/mod_status")
This is a request being made against your server, not one that Foreman
knows how to handle. It looks like a monitoring system trying to access
an Apache mod_status page, check for load balancers or tools such as
Nagios & collectd that may be configured to monitor your host.
I doubt a 404 response has much impact on performance unless it's very
frequent.
···
On 13/10/16 11:17, Jonathan Del Campo wrote:
–
Dominic Cleal
dominic@cleal.org
many Thanks for helping Dominic,
The request is happening every 10s and not visible on the apache logs …
it only appeared on the foreman production.log.
You was perfectly right, it's due to the collectd demon. I now will have to
check why …
thanks again.
J
···
On Thursday, October 13, 2016 at 12:40:03 PM UTC+2, Dominic Cleal wrote:
>
> On 13/10/16 11:17, Jonathan Del Campo wrote:
> > Hello,
> >
> > We are running theforman 1.11.4 on a centos 6.8.
> > I very often get this event log in the production.log file, and it seems
> > to be related to several problems we encountered on performances.
>
> Please use the foreman-users mailing list for questions and support,
> this list is for development discussions only, which this isn't.
>
> (http://groups.google.com/group/foreman-users,
> https://theforeman.org/support.html#Mailinglists)
>
> > Do you know if it's due to a known bug or a configuration problem on our
> > side ?
> >
> > /
> > /
> > /2016-10-13 12:06:05 [app] [I] Started GET "/mod_status?auto" for
> > 127.0.0.1 at 2016-10-13 12:06:05 +0200/
> > /2016-10-13 12:06:05 [app] [F] /
> > / | ActionController::RoutingError (No route matches [GET]
> "/mod_status"):/
>
> This is a request being made against your server, not one that Foreman
> knows how to handle. It looks like a monitoring system trying to access
> an Apache mod_status page, check for load balancers or tools such as
> Nagios & collectd that may be configured to monitor your host.
>
> I doubt a 404 response has much impact on performance unless it's very
> frequent.
>
> --
> Dominic Cleal
> dom...@cleal.org
>