Mavericks Server Log Question

Question

Level 1

0 points

Mavericks Server Log Question

Does anyone know how to correct these errors in the log. I know it has to do something with LDAP but I'm not using LDAP right now. Not sure what's going on with the WebKit.Networking. I've tried to google and couldn't find much.

my server name has been replaced with "myservername"

LDAP

Jul 8 15:54:01 myservername PasswordService[36153]: -[PasswordServerPrefsObject getSearchBase]: Unable to locate search base: -1 Can't contact LDAP server

Jul 8 15:54:01 myservername PasswordService[36153]: -[PasswordServerPrefsObject saveXMLData]: ldap_modify_ext_s of the passwordserver config record's plist attribute: -1 Can't contact LDAP server

Jul 8 15:56:11 myservername PasswordService[36153]: int pwsf_GetPublicKey(char *): ldap_search_ext_s cn=authdata for Public Key returned -1

Jul 8 15:56:11 ns1 com.apple.launchd[1] (com.apple.PasswordService[36153]): Exited with code: 1

Jul 8 15:56:11 myservername PasswordService[36294]: -[PasswordServerPrefsObject getSearchBase]: Unable to locate search base: -1 Can't contact LDAP server

Webkit

Jul 8 13:16:46 myservernamecom.apple.WebKit.Networking[25948]: tcp_connection_destination_prepare_complete 20 connectx to 2600:1402:a:184::720#80 failed: 65 - No route to host

Jul 8 13:16:46 myservername com.apple.WebKit.Networking[25948]: tcp_connection_destination_prepare_complete 18 connectx to 2600:1402:a:184::720#80 failed: 65 - No route to host

Jul 8 13:16:46 myservername com.apple.WebKit.Networking[25948]: tcp_connection_handle_destination_prepare_complete 13 failed to connect

Jul 8 13:16:46 myservername com.apple.WebKit.Networking[25948]: tcp_connection_handle_destination_prepare_complete 14 failed to connect

Thanks in advance.

Posted on Jul 8, 2014 3:28 PM

Reply

Answer 1

crittle100 Author

Level 1

0 points

Jul 12, 2014 9:33 AM in response to crittle100

Anyone??

Reply

Answer 2

Jul 12, 2014 10:44 AM in response to crittle100

Properly-configured and functional DNS services are critical for proper operations of distributed authentication and network encryption; for Open Directory and various other OS X Server components.

Please verify local DNS on the server. Launch Terminal.app from Applications > Utilities, and issue the following harmless diagnostic command:

sudo changeip -checkhostname

You'll have to enter an administrative password for the sudo, might get a one-time message around the use of sudo, then some configuration information will display, and then an indication that no changes are required, or that there are issues with the network or DNS configuration.

Reply

Answer 3

crittle100 Author

Level 1

0 points

Jul 14, 2014 10:31 AM in response to MrHoffman

I had already performed this, but did again. Everything checks out good. Success.

Thank you for the response. Any other ideas?

Reply

Answer 4

Jul 14, 2014 10:41 AM in response to crittle100

You already said you are not trying to use LDAP, and it seems to be complaining that you are not trying to use LDAP.

If you are otherwise symptom-free, I suggest you ignore these messages. There are LOTS of ghosts in the console logs.

Reply

Answer 5

crittle100 Author

Level 1

0 points

Jul 14, 2014 10:47 AM in response to Grant Bennet-Alder

ok. I'm assuming then I can ignore. It just randomly started and was annoying because it is flooding the logs and makes it go very slow when trying to search through it.

Reply

Answer 6

Jul 14, 2014 12:01 PM in response to crittle100

Well, you could decide to use LDAP. It's interesting.

Reply

Answer 7

crittle100 Author

Level 1

0 points

Jul 14, 2014 3:45 PM in response to Grant Bennet-Alder

I actually have a mail server set up to use the LDAP. This is the only reason why I haven't set it up on the Mac Server. If I remember correctly, it was something about not being able to use activesync is why I chose not to use the mac mail service.

Thank you so much for your responses.

Reply

Answer 8

crittle100 Author

Level 1

0 points

Jul 17, 2014 5:03 AM in response to crittle100

It ended up being a corrupt LDAP database. I couldn't turn on Open Directory. Since I wasn't using LDAP, I didn't think to look.

I followed instructions here, using neocodesoftware's response ( but was still getting a database error in the terminal instead of success. )

Mac OS Server Open Directory Will Not Turn On

I found this link and followed this and the above errors stopped. I had to force shut down the system awhile back so I assume that it corrupted things.

http://rickcogley.blogspot.com/2009/10/corrupt-apple-leopard-server-open.html

Reply