Greg Jalbert

Q: OS X Server Calendar service stopped working for CalDAV. Here are the Console messages

OS X Server Calendar service stopped working for CalDAV. Here are the Console messages.

This is on Mavericks 10.9.4 Build 13E28, Server version 3.1.2 (12S4517)

I normally use OS X Server to operate as a CalDAV server, but it stopped working. The Contacts server is also set up the same way and is also not working. What can I do to get CalDAV working?

In Console, these two messages appear every 9 seconds or so:


2014-08-20 11:33:58.464 PM com.apple.launchd[1]: (org.calendarserver.agent[1025]) Exited with code: 1

2014-08-20 11:33:58.464 PM com.apple.launchd[1]: (org.calendarserver.agent) Throttling respawn: Will start in 9 seconds


OS X Server Calendar view comes up turned OFF. I turn the server ON, and the Access Status: says Starting… for a while, then the Access Status: message reverts back to Offline - Turn on service to host calendars. There are very long (many seconds) delays when opening the Server and Server Calendar views before the view contents actually appears. Also getting these errors in Console related to starting Calendar service in OS X Server:


2014-08-20 11:01:20.297 PM Server[727]: Error starting Calendar service

2014-08-20 11:01:20.297 PM Server[727]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'setState' in plug-in: 'servermgr_calendar'. Error: Error Domain=XSActionErrorDomain Code=499 "The network connection was lost." UserInfo=0x608000c752c0 {NSLocalizedDescription=The network connection was lost., originalError=Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo=0x6000000f5a00 {NSUnderlyingError=0x608000a4f990 "The network connection was lost.", NSErrorFailingURLStringKey=https://127.0.0.1:311/commands/servermgr_calendar, NSErrorFailingURLKey=https://127.0.0.1:311/commands/servermgr_calendar, NSLocalizedDescription=The network connection was lost.}}

2014-08-20 11:01:20.348 PM Server[727]: Error reading data store for Calendar service

2014-08-20 11:01:20.348 PM Server[727]: error reading data stores for servermgr_calendar = Error Domain=XSActionErrorDomain Code=499 "The network connection was lost." UserInfo=0x608000c73240 {NSLocalizedDescription=The network connection was lost., originalError=Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo=0x6080002f8680 {NSUnderlyingError=0x608000a4f270 "The network connection was lost.", NSErrorFailingURLStringKey=https://127.0.0.1:311/commands/servermgr_calendar, NSErrorFailingURLKey=https://127.0.0.1:311/commands/servermgr_calendar, NSLocalizedDescription=The network connection was lost.}}

2014-08-20 11:01:20.349 PM Server[727]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'readSettings' in plug-in: 'servermgr_calendar'. Error: Error Domain=XSActionErrorDomain Code=499 "The network connection was lost." UserInfo=0x608000c73240 {NSLocalizedDescription=The network connection was lost., originalError=Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo=0x6080002f8680 {NSUnderlyingError=0x608000a4f270 "The network connection was lost.", NSErrorFailingURLStringKey=https://127.0.0.1:311/commands/servermgr_calendar, NSErrorFailingURLKey=https://127.0.0.1:311/commands/servermgr_calendar, NSLocalizedDescription=The network connection was lost.}}

MacBook Pro with Retina display, OS X Mavericks (10.9), iMac (10.9)

Posted on Aug 21, 2014 12:09 PM

Close

Q: OS X Server Calendar service stopped working for CalDAV. Here are the Console messages

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Aug 21, 2014 8:25 PM in response to Greg Jalbert
    Level 10 (207,995 points)
    Applications
    Aug 21, 2014 8:25 PM in response to Greg Jalbert

    You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.

    The primary DNS server used by the server must be 127.0.0.1 (that is, itself) unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.

  • by ~morgen,

    ~morgen ~morgen Sep 22, 2014 9:53 AM in response to Greg Jalbert
    Level 1 (140 points)
    Sep 22, 2014 9:53 AM in response to Greg Jalbert

    What's showing up in /var/log/caldavd/error.log?

  • by Greg Jalbert,Solvedanswer

    Greg Jalbert Greg Jalbert Sep 22, 2014 1:44 PM in response to ~morgen
    Level 1 (5 points)
    Sep 22, 2014 1:44 PM in response to ~morgen

    The caldavd-system.plist got zeroed out (corrupted) when the system ran out of disk space. Restoring the caldavd-system.plist from the backup restored CalDAV service. I'm lucky it was backed up by the system!

     

    I executed these commands in Terminal to restore CalDAV service in OS X Server.

     

    cd ‘/Library/Server/Calendar and Contacts/Config’

    sudo cp -p caldavd-system.plist.changeip.bak caldavd-system.plist

     

    Linc Davis and ~morgan, thanks for responding. By the way, Linc, my CalDAV system in OS X Server works fine with the server name in this format: 'myname.local'.