These are chat archives for fossasia/open-event-server

15th
Aug 2016
Rafał Kowalski
@rafalkowalski
Aug 15 2016 08:37
@/all we have error on dev heroku. I've added issue fossasia/open-event-orga-server#2223
Mario Behling
@mariobehling
Aug 15 2016 17:42
@rafalkowalski @shivamMg Any updates on the admin page issue?
Mario Behling
@mariobehling
Aug 15 2016 17:56
@niranjan94 @SaptakS Do you have any idea about the application error?
Saptak Sengupta
@SaptakS
Aug 15 2016 17:56
I have been checking it... It gives some memory quota exceeded...
Been trying to find whats the problem..
It gives an error of "memory quota exceeded"
Niranjan Rajendran
@niranjan94
Aug 15 2016 18:35
@mariobehling I can't check right now... Away from laptop..
Mario Behling
@mariobehling
Aug 15 2016 18:39
ok
Saptak Sengupta
@SaptakS
Aug 15 2016 20:52
I did a little searching on the error.. It's a problem of heroku kindof..... Due to some reason the memory quota to be used is exceeding.... It can be due to various reasons.. Some of the reasons I found out was too many migrations.... Too much memory used in runtime due to too many service workers....
but this error seems to arrive mainly for ruby on rails or NodeJS codes... no such issue reported for flask...
So I am a little confused what is the exact reason for this happening..

And then in a blog I found this as well:

I’ve been pulling my hair out wondering why my video processing worker dynos are getting R14 “Memory Quota” exceeded warnings, and only after I instrumented my code to take memory snapshots (ps -ef + cat /proc/meminfo at relevant timings) I got to suspecting that buffer cache is counted against me in my memory quota (why isn’t this documented? why can’t Heroku’s support resolve my ticket asking for explanations regarding my ps -ef outputs for a few weeks now?). We get false R14 positives all the time.

This is the only link I found in heroku about R14 https://devcenter.heroku.com/articles/error-codes#r14-memory-quota-exceeded
Mario Behling
@mariobehling
Aug 15 2016 21:02
ok, but it could also be that we are indeed using a lot of memory. I have not looked through the recent commits, but there was work on testing with lots of events and other work on import/exports.
@SaptakS Please look into this and maybe check which PR could be responsible.
Also, file an issue with Heroku, please and share the link with us.
Saptak Sengupta
@SaptakS
Aug 15 2016 21:03
Yeah.... the problem is since the error doesn't occur in local deployments and only in heroku deployment, I can't actually check in which PR it is occuring..
Rafał Kowalski
@rafalkowalski
Aug 15 2016 21:03
@mariobehling do you know when it's happend?
Saptak Sengupta
@SaptakS
Aug 15 2016 21:03
I and @rafalkowalski are still trying to find the PR which might have caused it..
Mario Behling
@mariobehling
Aug 15 2016 21:04
:+1:
Saptak Sengupta
@SaptakS
Aug 15 2016 21:06
2016-08-15T20:44:29.679383+00:00 heroku[web.1]: Process running mem=524M(102.4%)
2016-08-15T20:44:29.679531+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2016-08-15T20:44:50.925820+00:00 heroku[web.1]: Process running mem=534M(104.3%)
2016-08-15T20:44:50.925894+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2016-08-15T20:44:38+00:00 app[heroku-redis]: source=HEROKU_REDIS_BLUE sample#active-connections=1 sample#load-avg-1m=0.13 sample#load-avg-5m=0.08 sample#load-avg-15m=0.075 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15664884.0kB sample#memory-free=12355324.0kB sample#memory-cached=435956kB sample#memory-redis=333472bytes sample#hit-rate=0.41841 sample#evicted-keys=0
2016-08-15T20:44:43+00:00 app[heroku-redis]: source=REDIS sample#active-connections=12 sample#load-avg-1m=0.06 sample#load-avg-5m=0.045 sample#load-avg-15m=0.05 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15664884.0kB sample#memory-free=13732316.0kB sample#memory-cached=417796kB sample#memory-redis=535808bytes sample#hit-rate=0.34037 sample#evicted-keys=0
2016-08-15T20:45:12.084207+00:00 heroku[web.1]: Process running mem=541M(105.8%)
2016-08-15T20:45:12.084207+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2016-08-15T20:45:17.535920+00:00 app[web.1]: Fantastico Concerto
2016-08-15T20:45:17.457146+00:00 app[web.1]: BAWHHH GAWWWD
2016-08-15T20:45:17.688250+00:00 app[web.1]: PayPal Payment Test Event
2016-08-15T20:45:17.612078+00:00 app[web.1]: sddfs
2016-08-15T20:45:17.750381+00:00 app[web.1]: PayPal and Stripe Payment Test Event
2016-08-15T20:45:17.835682+00:00 app[web.1]: Cool HK event
2016-08-15T20:45:17.910709+00:00 app[web.1]: Some Event
2016-08-15T20:45:17.989760+00:00 app[web.1]: Stripe Payment Test Event
2016-08-15T20:45:18.118415+00:00 app[web.1]: Aayush
2016-08-15T20:45:18.257221+00:00 app[web.1]: jaja
2016-08-15T20:45:32.880223+00:00 heroku[web.1]: Process running mem=548M(106.9%)
2016-08-15T20:45:32.880360+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2016-08-15T20:45:54.183378+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2016-08-15T20:45:54.183260+00:00 heroku[web.1]: Process running mem=548M(106.9%)
2016-08-15T20:45:57+00:00 app[heroku-redis]: source=HEROKU_REDIS_BLUE sample#active-connections=1 sample#load-avg-1m=0.06 sample#load-avg-5m=0.07 sample#load-avg-15m=0.07 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15664884.0kB sample#memory-free=12355040.0kB sample#memory-cached=435956kB sample#memory-redis=333472bytes sample#hit-rate=0.41841 sample#evicted-keys=0
2016-08-15T20:46:14.889039+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2016-08-15T20:46:14.888944+00:00 heroku[web.1]: Process running mem=548M(106.9%)
2016-08-15T20:46:03+00:00 app[heroku-redis]: source=REDIS sample#active-connections=12 sample#load-avg-1m=0.04 sample#load-avg-5m=0.045 sample#load-avg-15m=0.05 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15664884.0kB sample#memory-free=13732556.0kB sample#memory-cached=417796kB sample#memory-redis=535808bytes sample#hit-rate=0.34037 sample#evicted-keys=0
@aviaryan can you please look into the error... I think it might have something to do with redis... Not sure... Just have a feeling because the error was shown right after it tried to execute redis command I guess..
I am not sure though...
Please do check..
Saptak Sengupta
@SaptakS
Aug 15 2016 21:15
@rafalkowalski @niranjan94 @aviaryan @mariobehling this is something I found:
https://www.reddit.com/r/node/comments/2dwu0o/going_over_heroku_memory_quota_and_not_sure/
Not sure about the solutions... But maybe of help..
Rafał Kowalski
@rafalkowalski
Aug 15 2016 21:19
maybe we can install new relic to check memory leaks ?
Saptak Sengupta
@SaptakS
Aug 15 2016 21:19
@rafalkowalski don't know how to do that.. Can you do it?
Rafał Kowalski
@rafalkowalski
Aug 15 2016 21:19
ok :D
it's 14 days trial, i will check how to install it
Saptak Sengupta
@SaptakS
Aug 15 2016 21:20
I am trying to find out if there is some PR which caused this..
Rafał Kowalski
@rafalkowalski
Aug 15 2016 21:21
ok
Arnav Gupta
@championswimmer
Aug 15 2016 22:31
@/all hey guys, can you help me with a bit of info on this fossasia/open-event-orga-server#2234 thank you