Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Lion Server push notifications to iOS 5 only partially working

I'm attempting to enable push notifications from my 10.7.2 Lion Server to my iOS 5 and Lion clients. All services (OD, Calendar Server, Mail, DNS, etc.) are running off of the same server. Push for Lion clients works fine for IMAP and CalDAV. I see "Push" in iCal preferences -> account settings.


For iOS 5 however I only see push enabled for Mail. I have confirmed it works as well. However, Calendars and Contacts show "fetch" in Settings -> Mail, Contacts, Calendars -> "Fetch New Data" -> Advanced.


iChat is running. I've verified all the iChat related ports are opened in the firewall.


I have a "real" certificate for my domain and clients are pointed to that domain name.


There are no errors in the logs. The caldavd configuration file in /etc/caldavd/ looks fine.


I'd appreciate any ideas where else to look!

iPhone 4, Mac OS X (10.7.2)

Posted on Oct 20, 2011 12:02 PM

Reply
37 replies

Oct 26, 2011 7:39 AM in response to _morgen__

The complete output is now


sqlite> select * from nodes;

1|/myhost/|1|1|open

2|/CalDAV/myhost/43732BBB-264E-48A1-8A0B-7AAE9E62E9D5/|1|1|open

3|/CalDAV/myhost/wiki-ldapmigratieru/|1|1|open

4|/CalDAV/myhost/wiki-ldapmigratieru/calendar/|1|1|open

5|/CalDAV/myhost/wiki-tudelftpwm/|1|1|open

6|/CalDAV/myhost/wiki-tudelftpwm/calendar/|1|1|open

7|/CalDAV/myhost/43732BBB-264E-48A1-8A0B-7AAE9E62E9D5/calendar/|1|1|open

8|/CalDAV/myhost/42080DC3-FB3A-4E22-8CE1-94A294348AE2/|1|1|open

9|/CardDAV/myhost/43732BBB-264E-48A1-8A0B-7AAE9E62E9D5/|1|1|open

10|/CardDAV/myhost/43732BBB-264E-48A1-8A0B-7AAE9E62E9D5/addressbook/|1|1|open

11|/CalDAV/myhost/ba8f4b37-3da4-4ea7-b666-a0c1ecb31912/|1|1|open

12|/CardDAV/myhost/42080DC3-FB3A-4E22-8CE1-94A294348AE2/|1|1|open


in pubsub.db.orig there were much more entries.

Jan 11, 2012 9:53 AM in response to _morgen__

Hi there.

This seems to be almost exactly the problem I've been fighting with for days now. But there is one crucial difference:

Using "calendarserver_monitor_notifications myuser" results in an error "Unable to determin xmpp server name" and leads to entries in the caldav-error-log "Could not create node /CalDAV/myhost/myuid" and ""Could not create node /CardDAV/myhost/myuid"

I checked and rechecked every configuration file I could find regarding the notification services and can't find what's causing this. I renamed pubsub.db, items.db and apnbridge.db - they all got recreated, but don't contain any nodes and the mailserver is flooding my log with "push_notify: discarting message; not connected to notification server"


Any ideas?

Jan 13, 2012 9:33 AM in response to SmartMarc

Is the notification server running? Try this:


# ps aux | grep jabberd_notification


You should see several matching processes:


_jabber 171 0.0 0.1 2451408 5180 ?? S 8Nov11 15:31.14 /usr/libexec/jabberd/s2s -c /etc/jabberd_notification/s2s.xml

_jabber 169 0.0 0.1 2451380 5292 ?? S 8Nov11 15:41.96 /usr/libexec/jabberd/c2s -c /etc/jabberd_notification/c2s.xml

_jabber 168 0.0 0.1 2437448 4916 ?? S 8Nov11 0:40.77 /usr/libexec/jabberd/router -c /etc/jabberd_notification/router.xml

_jabber 167 0.0 0.1 2451960 5588 ?? S 8Nov11 15:23.40 /usr/libexec/jabberd/sm -c /etc/jabberd_notification/sm.xml

_jabber 94 0.0 0.1 2438536 4248 ?? Ss 8Nov11 0:00.07 perl -w -x /usr/libexec/jabberd/jabberd -c /etc/jabberd_notification/jabberd.cfg

root 58572 0.0 0.0 2425480 184 s003 R+ 9:27AM 0:00.00 egrep jabberd_notification


Someone else just mentioned to me that they had recently updated their SSL cert using Server.app and that hadn't updated the jabberd_notification configuration. Are you seeing a message like this in /var/log/caldavd/error.log by chance:


XMPP Initialization failed: [Failure instance: Traceback: <class 'twisted.words.protocols.jabber.xmlstream.FeatureNotAdvertized'>


Also check /var/log/system.log for errors if you haven't already, since that is where the notification server sends its output.

Jan 13, 2012 9:57 AM in response to _morgen__

Yeah, the processes are all running and yes, the "FeatureNotAdvertized" error did pop up but has been gone since I reconfigured our SSL configuration, which caused Apache to go nuts (but I fixed that, too).

/var/log/system.log just keeps repeating

server push_notify [2047]: notification server connect failed, will retry in 300 seconds

and

server push_notify [2047]: discarding message; not connected to notification server

but also errors like

server jabberd/s2s [2800]; [7] [192.168.0.x, port=5269] write error: Broken pipe (32)

which pop up irregularly

Lion Server push notifications to iOS 5 only partially working

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.