-
-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting push rate-limiting on a loop #318
Comments
Interesting, this is happening on failed stream resumption?
…--
Anurodh Pokharel
Sent from my iPhone
> On Dec 28, 2019, at 7:39 AM, Licaon_Kter ***@***.***> wrote:
11:36:04.291 [info] ***@***.***_c2s:process_auth_result:271 (tls|<0.10234.0>) Accepted c2s PLAIN authentication for ***@***.*** by sql backend from hidden_by_ejabberd
11:36:04.400 [info] ***@***.***_stream_mgmt:handle_resume:435 (tls|<0.10234.0>) Resumed session for ***@***.***/Monal-iOS.87
11:36:04.469 [info] ***@***.***_push:enable:311 Enabling push notifications for ***@***.***/Monal-iOS.87
11:36:30.936 [info] ***@***.***_stream_mgmt:transition_to_pending:451 (tls|<0.10234.0>) Closing c2s connection for ***@***.***/Monal-iOS.87: Connection failed: connection closed; waiting 300 seconds for stream resumption
11:36:40.723 [info] ***@***.***_c2s:process_auth_result:271 (tls|<0.10235.0>) Accepted c2s PLAIN authentication for ***@***.*** by sql backend from hidden_by_ejabberd
11:36:40.849 [info] ***@***.***_stream_mgmt:handle_resume:435 (tls|<0.10235.0>) Resumed session for ***@***.***/Monal-iOS.87
11:36:40.962 [info] ***@***.***_push:enable:311 Enabling push notifications for ***@***.***/Monal-iOS.87
11:37:07.399 [info] ***@***.***_stream_mgmt:transition_to_pending:451 (tls|<0.10235.0>) Closing c2s connection for ***@***.***/Monal-iOS.87: Connection failed: connection closed; waiting 300 seconds for stream resumption
11:37:13.772 [info] ***@***.***_c2s:process_auth_result:271 (tls|<0.10239.0>) Accepted c2s PLAIN authentication for ***@***.*** by sql backend from hidden_by_ejabberd
11:37:13.884 [info] ***@***.***_stream_mgmt:handle_resume:435 (tls|<0.10239.0>) Resumed session for ***@***.***/Monal-iOS.87
11:37:13.949 [info] ***@***.***_push:enable:311 Enabling push notifications for ***@***.***/Monal-iOS.87
11:37:40.137 [info] ***@***.***_stream_mgmt:transition_to_pending:451 (tls|<0.10239.0>) Closing c2s connection for ***@***.***/Monal-iOS.87: Connection failed: connection closed; waiting 300 seconds for stream resumption
11:37:46.633 [info] ***@***.***_c2s:process_auth_result:271 (tls|<0.10241.0>) Accepted c2s PLAIN authentication for ***@***.*** by sql backend from hidden_by_ejabberd
11:37:46.757 [info] ***@***.***_stream_mgmt:handle_resume:435 (tls|<0.10241.0>) Resumed session for ***@***.***/Monal-iOS.87
11:37:46.866 [info] ***@***.***_push:enable:311 Enabling push notifications for ***@***.***/Monal-iOS.87
11:38:13.690 [info] ***@***.***_stream_mgmt:transition_to_pending:451 (tls|<0.10241.0>) Closing c2s connection for ***@***.***/Monal-iOS.87: Connection failed: connection closed; waiting 300 seconds for stream resumption
11:59:26.879 [info] ***@***.***_push:notify:454 push.monal.im rejected notification for ***@***.*** (xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) temporarily: Ratelimit reached (resource-constraint)
...7 seconds pass...the cycle starts again...
Monal 4.2, 6S, iOS 12.4.4
Server ejabberd HEAD (config)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I dunno when, this is level 4 info and I'd rather not go to full stanza verbose :) The device is not in my possession to just test. |
i think what is happening here is there are many stale devices. there was a fix to the push moduel in prosody i need to deploy that may resolve this. |
Any news?
|
@anurodhp did you update the appserver? |
anu updated the appserver recently, so this bug can be closed now |
@licaon-kter if there is anything weird again dont hesitate to comeback. |
Recently meaning today at 05AM UTC (my logs says SERVERRESTART for the pushserver)? Then it's too soon to call this fixed... Eg. On June 18 this was still happening. |
@licaon-kter: @anurodhp told me about the update on 2020-06-14... |
Could you reopen?
(these are the types of messages that I see, after grep/sort/uniq) iOS 12 (or 13 on the second one), Monal 4.6 (616) from App store |
Any news? :( |
@tmolitor-stud-tu do you have any further ideas on this? |
yes: wait for the push server upgrade |
@tmolitor-stud-tu The server has been updated, still seeing this error. |
I upgraded the ratelimit module used in the appserver, this should be fixed now (already in production) |
Haven't seen this for a week so maybe it's fixed, thanks. |
I still see those messages
|
Best to file a new issue. The original issue was files against Monal 4.2 on iOS 12. |
...7 seconds pass...the cycle starts again...
Monal 4.2, 6S, iOS 12.4.4
Server ejabberd HEAD (config)
The text was updated successfully, but these errors were encountered: