Benches macOS

7

Server Admin Tools freezing

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I've been running OS X Server 10.5.8 for a while with no issues. Today, I installed 10.6.0. After installing, I used software update to install 10.6.1, and then tried to launch Server Admin. It froze. Workgroup Manager did the same. I then re-erased the hard drive, installed again, and the same thing happened.

I have 10.5.8 on one hard drive, and was trying to install 10.6 on the second hard drive. There is 500 GB free. The machine is a 2 x 2.8 GHz Quad-Core Intel Xeon MacPro (MacPro 3,1).

Any suggestions?

7 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've had the same thing happen. I have 2 ppc xserves and when i open WGM the whole machines freeze. I managed to fix the ClaimAV problem thanks to an apple tech that either doesn't know xml or just didn't check the typo.

    I have a feeling something in the Security Update 2009-005 broke it. I am paranoid about Apple not testing their updates and it makes me laugh to think i used to make fun of Microsoft not doing any UAT.

    I have a back up i can go back to. As a rule i have a secondary disk in my Xserves and use SuperDuper to clone the OS to the backup Drive then i can perform one of these nasty security updates and roll back if needed.

    I have gotten stung with this before and it's not fun rebuilding a server. At this moment i don't know what is causing it. I will let you know once i have booted from my backup and see if it works

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Slowness is typical of 10.6 Server Admin when the local DNS isn't configured entirely correctly, and it's easy for that case to arise; when I saw that, I ended up cleaning out DNS and re-loading it, and things got far better.

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I think this may have played a role here. I shut everything down, waited several minutes, then began again. I specifically set up nothing at all, and Server Admin now worked. I then was able to update to 10.6.1, and start configuring services.

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm having a similar problem -- SLS runs ok for a few minutes after booting, then completely clogs up. I can't even ssh in from terminal. We have a separate DNS servers -- can I just disable DNS on SLS?

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    If you have separate DNS servers operating here, then you should have your Mac OS X Server box "aimed" at those for DNS name resolution; you should likely not be running (another) DNS Server locally on your Mac OS X Server box. Just configure the standard DNS forwarding on your NICs and aimed at your production DNS Server(s) running on the other box(es) on your network.

    And if your dedicated DNS Server boxes are not correctly configured and regardless of the host platform underneath your DNS Server(s), then you can and often will have network issues.

    DNS must be configured, and DNS must work, and DNS errors must be resolved.

    This irregardless of whether you are running the client or server versions of Mac OS X Tiger, Leopard or Snow Leopard, or running Windows or Windows Server, or OpenVMS, Tru64 Unix, Linux, BSD, Solaris, [insert your other preferred OS here] or any other operating system.

    DNS is fundamental to correct IP network operations.

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have the same problem, admin tools don't run since i tried to stop DNS service.
    How it is possible to resolve the problem ? thank you for your help. (sorry for my english , i'am a french user)

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Mac OS X Server and its tools need to have DNS running, which means you need to figure out how to reestablish the DNS services that were stopped. Getting DNS going again depends greatly on what happened; if it's just stopped and the tools are really slow, then you can wait through the glacial slowness to get DNS restarted. If there's something wrong with DNS, then things get more interesting, and a longer description of what happened to shut down DNS and what is showing up in the DNS server logs can be necessary.