-
Notifications
You must be signed in to change notification settings - Fork 226
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
Fault 500: 'Connection to the APNS server could not be made.' #33
Comments
Installing python-epoll fixed it for me. |
Installing I can reproduce the error by running the example listed in the README.md after checking out the repository at that version. |
When I run the example, the first request comes back with an error, the second request times out, and every subsequent request prints It seems that it's possible for Twisted to invoke a callback with a |
Will this work with py-kqueue? Maybe that is my problem. |
kqueue is the BSD/Os X equivalent for Linux epoll, so yes it should solved your problem if you are running mac os x or a BSD OS |
I get this error, but only on occasion. Usually the messages go through. Is that anybody else's experience, or does this library just not work at all for those of you with the error?
@nhooey Do you mean to say that this only happens after an error and a timeout? I wonder if this means that I'm having errors and timeouts right before this error. Here's one thing I just discovered looking a bit more closely at my logs. This happened to me 5 times today. All 5 times, it had the following sequence:
Of note: it's just starting up ( Unfortunately (for the sake of clarity), even though all 5 I'll keep looking into what |
I dug in a bit and figured out the following: When you register a callback with Twisted, the value passed into your callback function is the return value of the previously registered callback function. The exception of course is the first callback, which gets its argument from the call to In our case the callback function is a lambda which calls I think the idea here is that one message can be sent to the server and queued up to be executed when we finally have a client established. What was not considered is the possibility that two or more messages can be similarly queued. Or if it was considered, it wasn't handled properly. So, bottom line, what needs to happen is for the lambda to be replaced with a function that does the same, but also returns the same client that was passed in. |
Got same problem Today. |
Haven't really resolved it. |
@scari ^ |
Thanks for the update @dkrol-basis |
The XML-RPC client got error <Fault 500: 'Connection to the APNS server could not be made.'>
Server logs:
I suspect the relevant piece is <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'sendMessage'
The text was updated successfully, but these errors were encountered: