Let it be known that updating from 10.11.3 to 10.11.4 Server could hang on updating Web Services rendering some services useless. Nothing I've tried fixes this issue. If anyone has a solution please let me know sooner than later. Thanks!
Mac mini, OS X El Capitan (10.11.4), Update fro 10.11.3
So after the 4th forced reboot the server update finished. I see lots of of errors in the logs but not sure if those are normal. I will test the system services from network devices and will post results.
I just did an (10.11.4) update and although the System runs the internet connection is dead! I can connect to the unit remotely so the Ethernet/WiFi is all working fine and I can see it on the local network, but can't connect to anything outside the office.
Right now the Server app is being updated, so will wait to see if that helps, but hearing this (above) I'm a little worried. The Server app has been downloaded, but now waiting for the 'Web Service' to do it's thing, so will wait and see how this goes for a little while.
Will see how it goes and report back.
Yup, same here. Any solution?
Another stupid thing that Apple did was only allow the latest server software, 5.1, to run on this version of OS X. So i have a server, and as typical I updated the OS first, then the server. But once you update the OS, the server will no longer run, which includes the DNS server. I thought this is what was preventing the OS from getting the Internet, but I guess not. So now Internet doesn't work, and i can't update or run the server because no Internet. Thanks Apple.
Yeah, that's burned me more than once when that happened with DNS.
What I did awhile ago is to put one of Google's DNS servers in the network preference of the server.
So if your server is 192.168.1.1 put a public DNS after it (Google or OpenDNS or even your ISP).
Your server will always use the local (first one) unless it can't be reached. This works great for situations like the above, it'll fail to the public one and allow Server to be installed/updated.
Are you sure about the order? Apple had switched it up at some point so that it used the addresses randomly, which totally screwed with some setups. Did they switch it back to in-order DNS server querying? Just having a public address will still work since if it tried to query the local service and it failed it would then try another service (similar to in-order querying), but if you get service back up and running the DNS queries could go to either the internal (probably the desired behavior under most scenarios) or it might query the external server which might not be ideal for internal resolution (eg for an internal resource like laserjet.insidedomain.com).
Reasonably. The resolver docs state that the name servers are tried in the order entered. If one times out, the next is used.
I've been doing it that way since 10.9 (now on 10.11) and have never had an internal resource not resolve to internal domain names.
Maybe I'm just lucky! 😊
OS X El Capitan 10.11.3 to 10.11.4 Server Update Fails
