-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on periodic request #8
Comments
I've been testing the worker environment and it is working. Please, can you create a full snapshot of the beanstalk logs and send them to me? ([email protected]) http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.logging.html |
Here you go. |
I don't see those errors in the logs, in any case I've uploaded a new version, can you redeploy the cloudformation template? |
Yes thanks, Will update you soon. On Tue, May 24, 2016 at 3:09 PM, Javier ros [email protected]
|
Still not getting any recommendations. On Tue, May 24, 2016 at 3:10 PM, Travis Stevens [email protected] wrote:
|
So you're not getting any recommendation in the web, that's not related with the periodic job. Do you see any line in the Summary in red?, are the instances in other AZ or instance type to move the unused RIs? |
So currently we do not have any reserve instances. We were hoping the tool On Wed, May 25, 2016 at 9:27 AM, Javier ros [email protected]
|
WHen the s3importer tries to run i see this I, [2016-05-25T14:07:59.262114 #3255] INFO -- : Started POST "/s3importer" On Wed, May 25, 2016 at 9:54 AM, Travis Stevens [email protected] wrote:
|
No, the tool doesn't recommend new reserved instances, this tool helps to maintain the reserved instances used. For recommendations you can use trusted advisor. |
Ok that that helps. What format do you need to use for the DBR bucket name? On Wed, May 25, 2016 at 10:10 AM, Javier ros [email protected]
|
I am getting this on the worker node.
[2016-05-23T20:13:23.367950 #22356] INFO -- : Started GET "/periodicworker" for 127.0.0.1 at 2016-05-23 20:13:23 +0000
F, [2016-05-23T20:13:23.369923 #22356] FATAL -- :
ActionController::RoutingError (No route matches [GET] "/periodicworker"):
actionpack (4.2.1) lib/action_dispatch/middleware/debug_exceptions.rb:21:in
call' actionpack (4.2.1) lib/action_dispatch/middleware/show_exceptions.rb:30:in
call'railties (4.2.1) lib/rails/rack/logger.rb:38:in
call_app' railties (4.2.1) lib/rails/rack/logger.rb:20:in
block in call'activesupport (4.2.1) lib/active_support/tagged_logging.rb:68:in
block in tagged' activesupport (4.2.1) lib/active_support/tagged_logging.rb:26:in
tagged'activesupport (4.2.1) lib/active_support/tagged_logging.rb:68:in
tagged' railties (4.2.1) lib/rails/rack/logger.rb:20:in
call'actionpack (4.2.1) lib/action_dispatch/middleware/request_id.rb:21:in
call' rack (1.6.4) lib/rack/methodoverride.rb:22:in
call'rack (1.6.4) lib/rack/runtime.rb:18:in
call' activesupport (4.2.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in
call'rack (1.6.4) lib/rack/sendfile.rb:113:in
call' railties (4.2.1) lib/rails/engine.rb:518:in
call'railties (4.2.1) lib/rails/application.rb:164:in
call' passenger (4.0.59) lib/phusion_passenger/rack/thread_handler_extension.rb:74:in
process_request'passenger (4.0.59) lib/phusion_passenger/request_handler/thread_handler.rb:141:in `accept_and_process_next_request'
The text was updated successfully, but these errors were encountered: