Looking through the logs of a small-to-mid-size active forum using the translator plugin, I’m seeing intermittent server-side exceptions at the point the translator attempts to parse the JSON result from the translator service (Google in this case): discourse-translator/google.rb at master · discourse/discourse-translator · GitHub
Strack trace
Summary
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/json-2.2.0/lib/json/common.rb:156:in parse' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/json-2.2.0/lib/json/common.rb:156:inparse’
/var/www/discourse/plugins/discourse-translator/services/discourse_translator/google.rb:83:in result' /var/www/discourse/plugins/discourse-translator/services/discourse_translator/google.rb:52:indetect’
/var/www/discourse/plugins/discourse-translator/plugin.rb:106:in block in execute' /var/www/discourse/lib/distributed_mutex.rb:40:insynchronize’
/var/www/discourse/lib/distributed_mutex.rb:10:in synchronize' /var/www/discourse/plugins/discourse-translator/plugin.rb:105:inexecute’
/var/www/discourse/app/jobs/base.rb:230:in block (2 levels) in perform' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rails_multisite-2.0.6/lib/rails_multisite/connection_management.rb:63:inwith_connection’
/var/www/discourse/app/jobs/base.rb:219:in block in perform' /var/www/discourse/app/jobs/base.rb:215:ineach’
/var/www/discourse/app/jobs/base.rb:215:in perform' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:185:inexecute_job’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:167:in block (2 levels) in process' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/middleware/chain.rb:128:inblock in invoke’
/var/www/discourse/lib/sidekiq/pausable.rb:136:in call' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/middleware/chain.rb:130:inblock in invoke’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/middleware/chain.rb:133:in invoke' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:166:inblock in process’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:137:in block (6 levels) in dispatch' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/job_retry.rb:108:inlocal’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:136:in block (5 levels) in dispatch' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq.rb:37:inblock in module:Sidekiq’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:132:in block (4 levels) in dispatch' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:243:instats’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:127:in block (3 levels) in dispatch' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/job_logger.rb:8:incall’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:126:in block (2 levels) in dispatch' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/job_retry.rb:73:inglobal’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:125:in block in dispatch' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/logging.rb:48:inwith_context’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/logging.rb:42:in with_job_hash_context' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:124:indispatch’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:165:in process' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:83:inprocess_one’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:71:in run' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/util.rb:16:inwatchdog’
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.5/lib/sidekiq/util.rb:25:in `block in safe_thread’
The responses that are failing to parse are html error pages of two types.
Bad Requests 400
Summary
Job exception: 785: unexpected token at ’
Error 400 (Bad Request)!!1 *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}400. That’s an error.
Your client has issued a malformed or illegal request. That’s all we know.
Request Too Large 413
Summary
Job exception: 785: unexpected token at ’
Error 413 (Request Entity Too Large)!!1 *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}413. That’s an error.
Your client issued a request that was too large. That’s all we know.
A few questions / issues:
-
Is this something of concern?
-
Perhaps the JSON parsing should be in a begin / rescue?
