No route matches [POST] "/" about active-elastic-job HOT 8 CLOSED

it can also happen if you forgot to set PROCESS_ACTIVE_ELASTIC_JOBS to true

from active-elastic-job.

Hi, thanks for reporting the issue.

Please check these two settings:

• The gem is added to to bundle and deployed to the worker environment.
• The environment variable DISABLE_SQS_CONSUMER in the worker environment is not set at all or set to false.

If both settings comply, then I'd ask you to post the content of var/app/support/logs/access.log.

The general problem is that the middleware does not intercept the requests from the aws-sqs daemon and the request it passed through to your rails app.

from active-elastic-job.

Hi,

Thanks for getting back to me. I verified that the Gem does exist in the worker environment (version 1.4.3). I also verified that the environment variable DISABLE_SQS_CONSUMER does NOT exist in the worker environment.

I wasn’t able to find the log file you mentioned on AWS. There isn’t a support direction under /var/app. Only containerfiles and current directories. I looked inside of both and could not find a access.log.

FYI, the environment is Ruby 2.0 (puma).

Any thoughts?

Thanks
Mike

On Apr 1, 2016, at 5:15 AM, Tawan Sierek <[email protected]mailto:[email protected]> wrote:

Hi, thanks for reporting the issue.

Please check these two settings:

• The gem is added to to bundle and deployed to the worker environment.
• The environment variable DISABLE_SQS_CONSUMER in the worker environment is not set at all or set to false.

If both settings comply, then I'd ask you to post the content of var/app/support/logs/access.log.

The general problem is that the middleware does not intercept the requests from the aws-sqs daemon and the request it passed through to your rails app.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-204374145

from active-elastic-job.

most of the logs can be found in /var/log or through the eb console from my understanding. i'm assuming you're running on nginx so your access.log would be at /var/log/nginx/access.log

from active-elastic-job.

Hi,

Yes, I found the logs in /var/log/nginx/access.log. Here are the contents:

127.0.0.1 - - [01/Apr/2016:19:42:21 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" "-"
127.0.0.1 - - [01/Apr/2016:19:47:21 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" "-"
127.0.0.1 - - [01/Apr/2016:22:55:40 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" "-"
127.0.0.1 - - [01/Apr/2016:23:00:40 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" "-"
127.0.0.1 - - [01/Apr/2016:23:05:40 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" "-"
127.0.0.1 - - [01/Apr/2016:23:10:40 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" "-"
127.0.0.1 - - [01/Apr/2016:23:15:40 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" "-"
127.0.0.1 - - [01/Apr/2016:23:20:40 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" "-"
127.0.0.1 - - [01/Apr/2016:23:21:43 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" "-"
127.0.0.1 - - [01/Apr/2016:23:26:43 +0000] "POST / HTTP/1.1" 404 1318 "-" "aws-sqsd/1.1" “-"

Here's a view of my production.log file when this occurs in the Worker environment:

I, [2016-04-02T00:10:17.618111 #25152] INFO -- : Started POST "/" for 127.0.0.1 at 2016-04-02 00:10:17 +0000
F, [2016-04-02T00:10:17.625417 #25152] FATAL -- :
ActionController::RoutingError (No route matches [POST] "/"):
actionpack (4.2.5.2) lib/action_dispatch/middleware/debug_exceptions.rb:21:in call' rollbar (1.5.3) lib/rollbar/middleware/rails/show_exceptions.rb:22:incall_with_rollbar'
actionpack (4.2.5.2) lib/action_dispatch/middleware/show_exceptions.rb:30:in call' railties (4.2.5.2) lib/rails/rack/logger.rb:38:incall_app'
railties (4.2.5.2) lib/rails/rack/logger.rb:20:in block in call' activesupport (4.2.5.2) lib/active_support/tagged_logging.rb:68:inblock in tagged'
activesupport (4.2.5.2) lib/active_support/tagged_logging.rb:26:in tagged' activesupport (4.2.5.2) lib/active_support/tagged_logging.rb:68:intagged'
railties (4.2.5.2) lib/rails/rack/logger.rb:20:in call' actionpack (4.2.5.2) lib/action_dispatch/middleware/request_id.rb:21:incall'
rack (1.6.4) lib/rack/methodoverride.rb:22:in call' rack (1.6.4) lib/rack/runtime.rb:18:incall'
activesupport (4.2.5.2) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in call' actionpack (4.2.5.2) lib/action_dispatch/middleware/static.rb:116:incall'
rack (1.6.4) lib/rack/sendfile.rb:113:in call' railties (4.2.5.2) lib/rails/engine.rb:518:incall'
railties (4.2.5.2) lib/rails/application.rb:165:in call' rack (1.6.4) lib/rack/deflater.rb:35:incall'
puma (3.0.2) lib/puma/configuration.rb:221:in call' puma (3.0.2) lib/puma/server.rb:561:inhandle_request'
puma (3.0.2) lib/puma/server.rb:406:in process_client' puma (3.0.2) lib/puma/server.rb:271:inblock in run'
puma (3.0.2) lib/puma/thread_pool.rb:111:in call' puma (3.0.2) lib/puma/thread_pool.rb:111:inblock in spawn_thread'

Thanks
Mike

On Apr 1, 2016, at 2:28 PM, Chris Changchien <[email protected]mailto:[email protected]> wrote:

most of the logs can be found in /var/log or through the eb console from my understanding. i'm assuming you're running on nginx so your access.log would be at /var/log/nginx/access.log

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-204570659

from active-elastic-job.

Your worker environment still uses the AWS SQS daemon version 1 -> aws-sqsd/1.1
This gem makes use of message attributes, but these are only supported by version 2. Is it possible for you to switch to a newer platform? I tried the Ruby 2.0 (Puma) but with the newest Amazon Linux 2015 v.2.0.8. and it worked fine.

from active-elastic-job.

Once again, thanks for your help tracking the issue down. It may be a challenge for us to move our application to the latest and greatest AWS, but we will give it a try. Thanks again.

from active-elastic-job.

it can also happen if you forgot to set PROCESS_ACTIVE_ELASTIC_JOBS to true

Hi @lucienLopez
It really helped me a lot. Thanks a lot

from active-elastic-job.