Skip to content
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

http 500 error during SendDeliveryReceiptJob #8659

Closed
4 tasks done
five-c-d opened this issue Mar 5, 2019 · 2 comments
Closed
4 tasks done

http 500 error during SendDeliveryReceiptJob #8659

five-c-d opened this issue Mar 5, 2019 · 2 comments
Labels

Comments

@five-c-d
Copy link

five-c-d commented Mar 5, 2019


Bug description

See details here, https://community.signalusers.org/t/proposing-clients-keep-eachother-informed-about-the-group/6489/16

Steps to reproduce

  • lose oldPhone
  • get new phone
  • receive incoming groupchat message, sent to a group that newPhone was unaware existed, or that it was already a member of

Actual result:

  • HTTP 500 error in debuglog, proximate to when that incoming groupchat message arrived (message details suggest 29 seconds elapsed from time message in question was sent to time it was received).
  • Additionally, recipient-device aka newPhone, fails to properly request-group-update ...possibly due to HTTP 500, possibly for some other root cause

Expected result:

  • No error, HTTP 500 or otherwise
  • request-update-group succeeds normally, groupchat-nickname is correct (not nameless group)

Screenshots

Device info

Device: motorola moto g(7) plus (lake_reteu_n)
Android version: 9 (b7d2f, PPW29.98-28) ...OS Host : ilclbld31
Signal version: 4.33.5

Link to debug log

https://debuglogs.org/868167aa7f44c8033afa3724d715824f7fe8270424aa97779cd423e9ad4c50ac

Some excerpts, see also some analysis in signalUsers:

AuthorizationFailedE, zxing.FormatE, HTTP 409, HTTP 500, No_connection, MismatchedDevicesE, GlideE “Failed to load resource”, HTTP 404, ioException “Write failed!”, HTTP 403, et cetera, etc

2019-02-26 15:27:47.585 CET W Job: [c9c8d18b-49c1-457d-836a-3d74abd39e2d] RotateCertificateJob :: Failing due to an exception. (Time since submission: 13309395 ms, Run attempt: 0, isStopped: false)
2019-02-26 15:27:47.585 CET W Job: org.whispersystems.signalservice.api.push.exceptions.AuthorizationFailedException: Authorization failed!
2019-02-26 15:28:30.226 CET W PushNotificationReceiveJob: org.whispersystems.signalservice.api.push.exceptions.AuthorizationFailedException: Authorization failed!
2019-02-26 15:28:30.261 CET W Job: [b20ef1c3-0ee3-418a-a6a6-da29aa895d99] PushNotificationReceiveJob :: Failing due to an exception. (Time since submission: 11737 ms, Run attempt: 0, isStopped: false)
2019-02-26 15:28:30.261 CET W Job: org.whispersystems.signalservice.api.push.exceptions.AuthorizationFailedException: Authorization failed!

2019-02-26 18:17:54.480 CET W ScanningThread: com.google.zxing.FormatException
2019-02-26 18:17:55.727 CET W ScanningThread: com.google.zxing.FormatException

2019-02-26 18:18:24.896 CET W SignalServiceMessageSender: java.io.IOException: Non-successful response: 409
2019-02-26 18:18:26.545 CET W SignalServiceMessageSender: java.io.IOException: Non-successful response: 409

2019-02-28 10:53:07.059 CET W Job: [85942772-de1e-4d50-a999-f2f798d432d4] SendDeliveryReceiptJob :: Failing due to an exception. (Time since submission: 581 ms, Run attempt: 0, isStopped: false)
2019-02-28 10:53:07.059 CET W Job: org.whispersystems.signalservice.api.push.exceptions.NonSuccessfulResponseCodeException: Bad response: 500 

2019-02-28 17:14:38.334 CET W RetrieveProfileJob: java.io.IOException: No connection!
2019-02-28 17:14:38.446 CET W PushServiceSocket: org.whispersystems.signalservice.api.push.exceptions.AuthorizationFailedException: Authorization failed!
2019-02-28 17:14:38.825 CET W RetrieveProfileJob: java.io.IOException: Non-successful response: 401
2019-02-28 17:14:38.935 CET W PushServiceSocket: org.whispersystems.signalservice.api.push.exceptions.AuthorizationFailedException: Authorization failed!

2019-02-28 18:26:43.388 CET W SignalServiceMessageSender: org.whispersystems.signalservice.internal.push.exceptions.MismatchedDevicesException

2019-03-02 08:58:26.244 CET W SignalServiceMessageSender: org.whispersystems.signalservice.internal.push.exceptions.MismatchedDevicesException
2019-03-02 08:58:26.280 CET W SignalServiceMessageSender: org.whispersystems.signalservice.internal.push.exceptions.MismatchedDevicesException

2019-03-02 08:58:28.922 CET W SingleRecipientNotificationBuilder: java.util.concurrent.ExecutionException: com.bumptech.glide.load.engine.GlideException: Failed to load resource
2019-03-02 08:58:28.922 CET W SingleRecipientNotificationBuilder: java.io.IOException(Couldn't load avatar for group: __textsecure_group__!b54ba46990577f25e5a67db9c39bc009)
2019-03-02 08:58:28.922 CET W SingleRecipientNotificationBuilder:  call GlideException#logRootCauses(String) for more detail
2019-03-02 08:58:28.922 CET W SingleRecipientNotificationBuilder: Caused by: com.bumptech.glide.load.engine.GlideException: Failed to load resource
2019-03-02 08:58:28.922 CET W SingleRecipientNotificationBuilder: java.io.IOException(Couldn't load avatar for group: __textsecure_group__!b54ba46990577f25e5a67db9c39bc009)
2019-03-02 08:58:28.922 CET W SingleRecipientNotificationBuilder:  call GlideException#logRootCauses(String) for more detail

2019-03-02 13:32:30.099 CET W RetrieveProfileJob: java.io.IOException: Non-successful response: 404

2019-03-02 17:19:23.207 CET W WebSocketConnection: java.io.IOException: Write failed!


Did not find any similar HTTP 500 errors in github, there are some MMS-telco-servers which give the usual "Internal Server Error" formulation, https://github.com/search?q=org%3Asignalapp+%22Bad+response%3A+500%22&type=Issues , and a couple old threads with "Bad response: 500", but none seem very similar. https://github.com/search?q=org%3Asignalapp+%22internal+server+error%22&type=Issues

p.s. For the HTTP 409 portion of this debuglog, there are some known problems

@Meteor0id
Copy link
Contributor

Thanks for investigating and writing this bug report five-c-d. ? If anyone requires additional information about the events leading up to this please tag me.

@stale
Copy link

stale bot commented Jan 28, 2022

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix label Jan 28, 2022
@stale stale bot closed this as completed Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants