Apple Event: May 7th at 7 am PT

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

Level 1

65 points

Who got caldav and carddav push running successful on lion server?

Hello everybody,

I am running OS X Server since 10.5 server which I upgraded to 10.6 server in the past without problems, upgrading 10.6 to 10.7 was is a mess and none of my serveral upgrades attempts were leading into a "stable" lion server so I ended up with manual upgrading my data into a clean install of lion server.

After data migration most of my services are working as usual (some profilemanager quirks but that don't bother me for now).

Only when it comes to push for calendar and addressbook services I am getting frustrated!

Push mail is running fine for my iDevices (Push is listed on my iPhone and iPad and Mac) but for caldav and carddav my caldavd error.logs are throwing error messages like this if I access iCal or addressbook via Mac or iDevice (no Push available on iPhone or iPad neither on my Mac).

Those for caldav

2011-09-23 11:29:18+0200 [-] [caldav-0] [-] [twistedcaldav.notify.Notifier#warn] Could not create node /CalDAV/myserver.fqdn/FEF253F7-9A6C-4242-A990-88960832BF5F/

2011-09-23 11:29:18+0200 [-] [notifications] 2011-09-23 11:29:18+0200 [XmlStream,client] [twistedcaldav.notify.XMPPNotifier#error] PubSub node configuration error: <error code='403' type='auth'><forbidden xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error>

and those for carddav

2011-09-23 11:24:35+0200 [-] [caldav-1] [-] [twistedcaldav.notify.Notifier#warn] Could not create node /CardDAV/myserver.fqdn/FEF253F7-9A6C-4242-A990-88960832BF5F/

2011-09-23 11:24:35+0200 [-] [notifications] 2011-09-23 11:24:35+0200 [XmlStream,client] [twistedcaldav.notify.XMPPNotifier#error] PubSub node configuration error: <error code='403' type='auth'><forbidden xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error>

I tried several thing (changing serveradmin settings, plist and other configuration files, checking passwords, renew apple push certificates etc.) but that changed nothing, so if one got those push services running correctly I would appreciate if one could share his configuration so I can compare it with mine.

I think those files and output are interesting for the configuration, if some other files are important please note them.

If one feel afraid to post his configuration for security reasons etc. please ask for my email address

Output of terminal command:

sudo serveradmin settings calendar

sudo serveradmin settings addressbook

sudo serveradmin settings notification

sudo serveradmin jabber

plist and other configuration files of interest

/etc/caldavd/caldavd.plist

/etc/jabberd/*

/etc/jabberd_notification/*

Best regards,

Eldrik

Posted on Sep 23, 2011 2:58 AM

37 replies

Feb 29, 2012 7:10 AM in response to _morgen__

Well...

sudo serveradmin settings calendar:Notifications:Services:XMPPNotifier:Port

comes with

calendar:Notifications:Services:XMPPNotifier:Port = 5218

That seems ok.

sudo lsof -Pi | grep 5218

leads to

mDNSRespo 18 _mdnsresponder 368u IPv6 0xffffff800dca5218 0t0 UDP *:*

push_noti 95 root 9u IPv4 0xffffff80148a5de0 0t0 TCP example.com:53930->example.com:5218 (ESTABLISHED)

c2s 83403 _jabber 7u IPv6 0xffffff800ecea700 0t0 TCP *:5218 (LISTEN)

c2s 83403 _jabber 8u IPv6 0xffffff800eceb240 0t0 TCP example.com:5218->example.com:53947 (ESTABLISHED)

c2s 83403 _jabber 9u IPv6 0xffffff800ece9080 0t0 TCP example.com:5218->example.com:53930 (ESTABLISHED)

Python 83821 _calendar 7u IPv4 0xffffff800dca8880 0t0 TCP example.com:53947->example.com:5218 (ESTABLISHED)

and

tail -f /var/log/caldavd/error.log

shows

2012-02-29 15:05:47+0100 [-] [caldav-0] [-] [twistedcaldav.notify.Notifier#warn] Could not create node /CalDAV/example.com/777E0522-1372-409E-B309-4A06A94FFCF4/

And lots of those....

_morgen__

Level 1

140 points

Feb 29, 2012 9:06 AM in response to mightymartin

Try resetting your notification databases as described here:

https://discussions.apple.com/thread/3416916?answerId=16520307022#16520307022

Mar 2, 2012 12:32 AM in response to _morgen__

Will do, but I just ran another check according to a tip I found above. Tried the monitor_calendarserver_notifications command and it showed:

Error: Unable to determine xmpp server name

Does that ring any bell?

_morgen__

Level 1

140 points

Mar 2, 2012 8:35 AM in response to mightymartin

That's just another indicator that your notification server has a problem and is not allowing calendar server to publish XMPP nodes. I bet resetting your notification databases will fix this. Did you by chance ever change this server's domain name?

Mar 19, 2012 2:31 PM in response to pandine

Hi !

Push notification are working fine (as long as I'm not disconnected from Apple Servers) for mail and calendar, but the push option is not offered in iOS for addressbook.

Any idea?

Jun 9, 2012 2:10 AM in response to _morgen__

HI,

on my side I noticed that the addressbook entry is missing in the notification configuration.

the

sudo serveradmin settings notification

commande returns the following list

[...]

notification:configuredServices:_array_index:0:service = "calendar"

notification:configuredServices:_array_index:0:hostName = "127.0.0.1"

notification:configuredServices:_array_index:1:service = "mail"

notification:configuredServices:_array_index:1:hostName = "127.0.0.1"

notification:verbose = 0

[...]

Any clue how to add addressbook?

thanks !

cj00

Level 1

10 points

Oct 29, 2013 6:54 AM in response to Fred de Gembloux

[...]

notification:configuredServices:_array_index:0:service = "calendar"

notification:configuredServices:_array_index:0:hostName = "127.0.0.1"

notification:configuredServices:_array_index:1:service = "mail"

notification:configuredServices:_array_index:1:hostName = "127.0.0.1"

notification:verbose = 0

[...]

Any clue how to add addressbook?

Adding the addressbook to serveradmin notification settings

Can be done by:

1. Exporting the notification settings to a temporary text file:

$ sudo serveradmin settings notification > notification.txt

2. Opening up this temporary file in your favourite editor, for example using nano:

$ nano notification.txt

3. Inserting the addressbook lines after the line starting with "notification:configuredServices:_array_index:1:hostName" and before the line starting with "notification:verbose":

notification:configuredServices:_array_index:2:service = "addressbook"

notification:configuredServices:_array_index:2:hostName = "127.0.0.1"

4. Save the edited temporary settings file and close your text editor.

5. Import the updates settings into serveradmin:

$ sudo serveradmin settings < notification.txt

6. And finally clean up by erasing the text file containing the temporary settings.

$ rm notification.txt

Who got caldav and carddav push running successful on lion server?