push isn't delivered unless daemon is restarted about dovecot-xaps-daemon HOT 8 CLOSED

Looking into this. I'm experiencing the same problem.

from dovecot-xaps-daemon.

I have the same problem.

from dovecot-xaps-daemon.

Could be related to #7 - Investigating

from dovecot-xaps-daemon.

Note to self, I restarted my deployment at 2014-11-12 21:59. Let's see if the error from #7 appears when this stops working.

from dovecot-xaps-daemon.

@maiksd @patricks Can you grep for APNSProtocol.dataReceived in your log files?

from dovecot-xaps-daemon.

How to I enable logging? I don't have any log files for the daemon.

EDIT:

I also log my daemon output now into a log file. So maybe I can get you so some data in a few days.

from dovecot-xaps-daemon.

I use this script to start the daemon, which then writes a logfile as well as outputting everything to the console:

#!/bin/bash
LOG=$HOME/xapsd.log 
cd $HOME/dovecot-xaps-daemon
twistd -n xapsd --key=$HOME/key.pem --certificate=$HOME/certificate.pem --database=$HOME/xapsd.json --socket=/var/run/dovecot/xaps/xapsd.sock 2>&1 | tee -a $LOG

$ grep APNSProtocol.dataReceived xapsd.log
2014-10-29 19:59:56+0100 [APNSProtocol (TLSMemoryBIOProtocol),client] APNSProtocol.dataReceived: 080a00000000

That's it. The daemon has been running for weeks without problems now. Logfile has 6648 lines.

from dovecot-xaps-daemon.

Pretty sure the fix i just pushed will do the trick. Auto-reconnect was broken due to bad code.

Now when the server loses the connection to the APNS service, it will try to reconnect after a minute. Notifications within that timeframe should be queued and will go out when the reconnect was successful.

There is one issue: the notification that failed is not pushed back on the queue. I'll file a bug to fix that.

from dovecot-xaps-daemon.