Warning: file_get_contents(/data/phpspider/zhask/data//catemap/2/ruby-on-rails/59.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181

Warning: file_get_contents(/data/phpspider/zhask/data//catemap/3/heroku/2.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Ruby on rails Heroku上的R15问题,但不超过内存限制_Ruby On Rails_Heroku_Imagemagick_Paperclip - Fatal编程技术网

Ruby on rails Heroku上的R15问题,但不超过内存限制

Ruby on rails Heroku上的R15问题,但不超过内存限制,ruby-on-rails,heroku,imagemagick,paperclip,Ruby On Rails,Heroku,Imagemagick,Paperclip,我有一个RubyonRails站点运行在Heroku的performance-M dynamo上,自动缩放设置为5台dynamo 最近,我们在网站上收到突然的R15和H12错误。在此期间,内存使用情况显示在dynamo允许的内存配额之下 以下是日志中显示的错误: 2019-09-16T10:12:08.523336+00:00 app[scheduler.2787]: Command :: identify -format '%wx%h,%[exif:orientation]' '/tmp/89

我有一个RubyonRails站点运行在Heroku的performance-M dynamo上,自动缩放设置为5台dynamo

最近,我们在网站上收到突然的R15和H12错误。在此期间,内存使用情况显示在dynamo允许的内存配额之下

以下是日志中显示的错误:

2019-09-16T10:12:08.523336+00:00 app[scheduler.2787]: Command :: identify -format '%wx%h,%[exif:orientation]' '/tmp/897302823996a945884a1d912c28d59520190916-4-1bn5w9k.jpg[0]' 2>/dev/null
2019-09-16T10:12:16.022212+00:00 heroku[scheduler.2787]: Process running mem=1022M(199.7%)
2019-09-16T10:12:16.022295+00:00 heroku[scheduler.2787]: Error R14 (Memory quota exceeded)
2019-09-16T10:12:16.365725+00:00 heroku[router]: at=info method=GET path="/favicon-16x16.png" host=www.site.com request_id=8755a947-ace9-471d-a192-a236785505b4 fwd="45.195.5.37" dyno=web.1 connect=1ms service=2ms status=200 bytes=928 protocol=https
2019-09-16T10:12:19.103405+00:00 heroku[scheduler.2787]: Process running mem=1279M(250.0%)
2019-09-16T10:12:19.103405+00:00 heroku[scheduler.2787]: Error R15 (Memory quota vastly exceeded)
2019-09-16T10:12:19.103405+00:00 heroku[scheduler.2787]: Stopping process with SIGKILL
2019-09-16T10:12:19.427029+00:00 heroku[scheduler.2787]: State changed from up to complete
2019-09-16T10:12:19.388039+00:00 heroku[scheduler.2787]: Process exited with status 137
正如您所见,就在R15错误之前,曲别针试图压缩图像

以下屏幕截图中图表的开头显示了受影响期间Heroku度量的状态:

有人能帮我弄清楚R15错误是如何发生的吗?R15错误与内存泄漏有关,而指标显示内存在极限范围内?任何关于如何阻止这种情况再次发生的帮助都会很有帮助


谢谢。

您的R15错误发生在由创建的上,与您的web dynos完全分离。您的请求超时似乎与计划任务中的内存问题无关

计划的任务似乎正在1X dyno上运行(
mem=1022M(199.7%)
)。要更改此设置,请启动Heroku Scheduler插件并更改dyno类型

对于您的请求超时,请查看Scout或New Relic,以找到有问题的端点以及堆栈中的哪些位置需要很长时间

2019-09-16T10:13:07.886016+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/favicon.ico" host=www.site.com request_id=c7cea0a2-7345-44c6-926e-3ad5a0eb2066 fwd="45.195.5.37" dyno=web.2 connect=1ms service=30000ms status=503 bytes=0 protocol=https