429 errors on like action in production.log

installation
1

I wonder which problem may be causing 429 error to appear in production.log.

I’m getting 99% of these in PostActionsController context.

Processing by PostActionsController#create as */*
  Parameters: {"id"=>"706335", "post_action_type_id"=>"2", "flag_topic"=>"false"}
Completed 429 Too Many Requests in 16ms (Views: 0.1ms | ActiveRecord: 0.0ms | Allocations: 5715)

I know that global rate limiting is done in layer above by nginx in the container and these type of errors end in /shared/standalone/log/var-log/nginx/error.log…

So the question is under which circumstances this error is thrown in production.log?

I’d like to get rid of these if possible…

Do you get some 429 (not caused by rate limiting) in your setups too?

2

post_action_type_id = 2 means this is a like. If a user is trying to like a post and they’ve used all their likes for the day, this will generate a 429 error. I’m going to guess that’s what is happening in this instance.

5 Likes
3

Haha, spot on… My users really like what they read! :nerd_face:

Thanks, that is relieving…!

2 Likes
4

Aha! I suspect that explains the 429s in a site that I manage. It’s a very busy site, and I was afraid that it was hitting some other kind of problem. This is great to know!

4 Likes
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.