iChat jabberd errors

Question

realzcubed Author

Level 1

2 points

iChat jabberd errors

I'm getting a flood of jabberd errors "for non-existing host: server.local" under Server Admin>iChat.

May 18 06:23:46 server jabberd/c2s[317]: SASL callback for non-existing host: server.local

May 18 06:23:46 server jabberd/c2s[317]: [9] [::ffff:172.16.47.1, port=51800] disconnect jid=unbound, packets: 0

May 18 06:23:48 server jabberd/c2s[317]: [9] [::ffff:172.16.47.1, port=51801] connect

May 18 06:23:48 server jabberd/c2s[317]: SASL callback for non-existing host: server.local

May 18 06:23:48 server jabberd/c2s[317]: [9] [::ffff:172.16.47.1, port=51801] disconnect jid=unbound, packets: 0

May 18 06:23:51 server jabberd/c2s[317]: [9] [::ffff:172.16.47.1, port=51802] connect

May 18 06:23:51 server jabberd/c2s[317]: SASL callback for non-existing host: server.local

May 18 06:23:51 server jabberd/c2s[317]: [9] [::ffff:172.16.47.1, port=51802] disconnect jid=unbound, packets: 0

...

I believe that I've tried all the obvious, but the errors persist.

1. Check dns that iChat's specified Host Domain "computer.private" matches:

$ sudo changeip -checkhostname

Password:

Primary address = 10.0.1.98

Current HostName = server.computer.private

DNS HostName = server.computer.private

The names match. There is nothing to change.

dirserv:success = "success"

2. Use jabberd_autobudddy to move the server name to my FQDN. Turn off iChat and Push, then run:

$ sudo /usr/bin/jabber_autobuddy --move-domain server.local server.computer.private

Any ideas how to fix iChat would be greatly appreciated.

Mac mini, Mac OS X (10.6.7)

Posted on May 18, 2011 3:33 AM

Reply

Answer 1

Best reply

realzcubed Author

Level 1

2 points

May 18, 2011 11:56 AM in response to realzcubed

Fixed this by following the instructions here:

Specify "server.computer.private" as the Host Domain. Add the two A records in the DNS zone "computer.private." for "pubsub.server.computer.private." and "proxy65.server.computer.private." (FQDNs). Also, there related jabber issue of email push error logs being filled up with messages that look like: "[twistedcaldav.notify.XMPPNotificationFactory#warn] XMPP disconnected" can be solved here.

Success looks something like:

May 18 14:43:10 server servermgrd[75]: servermgr_jabber[N]: jabberd service startup completed.

May 18 14:43:10 server jabberd/router[20977]: [127.0.0.1, port=51268] connect

May 18 14:43:10 server jabberd/router[20977]: [127.0.0.1, port=51268] authenticated as proxy65.server.computer.private

May 18 14:43:10 server jabberd/router[20977]: [proxy65.server.computer.private] online (bound to 127.0.0.1, port 51268)

May 18 14:43:11 server jabberd/router[20977]: [127.0.0.1, port=51270] connect

May 18 14:43:11 server jabberd/router[20977]: [127.0.0.1, port=51270] authenticated as pubsub.computer.private

May 18 14:43:11 server jabberd/router[20977]: [pubsub.computer.private] online (bound to 127.0.0.1, port 51270)

May 18 14:46:20 server jabberd/c2s[20978]: [8] [::ffff:10.0.1.98, port=51301] connect

May 18 14:46:21 server jabberd/c2s[20978]: [8] SASL authentication succeeded: mechanism=DIGEST-MD5; authzid=com.apple.notificationuser@server.computer.private, TLS negotiated

May 18 14:46:21 server jabberd/c2s[20978]: od_auth_check_service_membership: checking user "com.apple.notificationuser" access for service "chat"

May 18 14:46:21 server jabberd/c2s[20978]: od_auth_check_service_membership: mbr_check_service_membership returned 2

May 18 14:46:21 server jabberd/c2s[20978]: od_auth_check_service_membership: no access restrictions found

May 18 14:46:21 server jabberd/c2s[20978]: [8] bound: jid=com.apple.notificationuser@server.computer.private/push_notify

May 18 14:46:21 server jabberd/sm[20976]: session started: jid=com.apple.notificationuser@server.computer.private/push_notify

Reply