Currently Being ModeratedJan 21, 2012 3:12 PM (in response to Chazz Layne)
Thanks for sharing, I enjoyed reading your story.
I bought a Mac Mini Server with Lion pre-installed. It worked the way it was supposed to for about about 10 minutes and than it decided it was done for today. Looking for answers to the behaviour of the Mac Mini Server I ended up here. After having read your story, my answer to the crapy engineering on Apple's part is that I'll let the Mac be returned and the payment be reimbursed.
Lion Server was released way too early in my humble opinion.
Currently Being ModeratedJan 23, 2012 5:29 AM (in response to Chazz Layne)
I fixed all my problems by making sure my DNS was solid and resetting Apache.
The following articles were used:
Solid DNS appearantly is the foundation on which everything falls back in OS X Server.
Hope this helps anyone...
p.s. The Mac Mini Server is NOT going back. 10.7.3 is also close to release, so I'm confident that it'll all work out for the better.
Currently Being ModeratedJan 23, 2012 9:07 AM (in response to Mark23)
Thanks for the input Mark. Did DNS actually help prevent the corruption of user permissions? I've been avoiding both DNS and DHCP on the Lion server because of the gigantic mess it caused last time (the original plan was for it to act like a Windows Domain Controller, only for a network of Macs).
This issue has become so bad that we're abandoning all the additional functionality this "server" was supposed to provide, and sticking to just file sharing and FileMaker (neither of which work right now, because the permissions won't hold).
Currently Being ModeratedJan 23, 2012 9:36 AM (in response to Chazz Layne)
My DHCP isn't handled by the OS X Lion Server either, but the DNS should be the way the first link describes, just read it from Step-by-Step onwards.
The only thing I did outside the zones tab in Server Admin involved adding Google's DNS servers (126.96.36.199 and 188.8.131.52) and my router to forwarder IP Adresses.
Then as per Hoffman's directions for testing I entered the (DNS) server's IP as the only DNS server within Network preferences at my administration computer.
Clearly Apple has a lot to do before Mr. Hoffman get's out of work...
Another helpful resuorce turned out to be http://help.apple.com/advancedserveradmin/mac/10.7/
Currently Being ModeratedJan 24, 2012 8:59 AM (in response to Chazz Layne)
It turned out that my mail server didn't work the way it should, corrupted files, etc -- all because I tried too many options to fix what essentially wasn't even broken, I just had to fix DNS.
Running a 10.7.2 combo update didn't fix anything for me, nor did fixing permissions through Disk Utility.
DNS should be set the correct way both internally (local network), and if you have it, with a domain name hosting provider. If Lion Server can not find a DNS server on the same subnet as the lion server installation, it sets up the DNS service on Lion Server at install-time
If you want to be reachable from the outside, make sure the router has all corresponding ports open (port forwarding) at your router and that your external DNS is ok (at Godaddy for example). Set one A-record (e.g. server.example.com) and CNAME records for all others (e.g. mail.example.com) if you want to point them to the same machine.
Ports that need to be open for a service to work:
MAKE BACKUPS OF ALL IMPORTANT DATA BEFORE PROCEEDING
After doing all this work, I rebooted and held the alt-key while booting physically on the server (I hooked it up on a monitor, keyboard and mouse), after which I could choose the Recovery partition to boot from. Within recovery I chose Disk Utility, selected the partition, clicked the erase tab and erased the partition.
Then I quit Disk Utility, came back to the previous screen, there I chose to re-install Lion. Since this is a Mac Mini Server (as purchased from the Online Store) it bypasses the App Store completely and just reinstalls Lion Server.
Because my DNS is now in a far better condition than it was before (I dare not say that it is good just yet ) installing Lion also configured all services in the correct manner.
From being in the verge of quiting on Lion Server, to the best feeling in the world because everything now works all thanks to a solid DNS, I didn't think that DNS would be such a big issue
Hope this helps!
Currently Being ModeratedJan 24, 2012 5:37 PM (in response to Chazz Layne)
Permissions have been applying and removing themselves at random all day. Over a matter of seconds I could command-I, command-W, command-I and watch them change around... craziness.
I did make some progress though: I finally have control over the DNS again (I couldn't get into it before with Server Admin due to an "unknown" error). This required completely wiping out the config(s) for it via terminal, fairly simple to do after a quick refresher courtesy of http://www.johnkitzmiller.com/blog/2011/9/28/how-to-start-fresh-with-dns-in-os-x -server-v-107-lion.html.
With access to DNS once more, I've completed a Hoff-style setup of the system. I'll begin stripping and reapplying permissions tomorrow.
Currently Being ModeratedJan 25, 2012 9:28 AM (in response to Chazz Layne)
Permissions finally seem to be holding, and for the first time I can open our FileMaker database without a permissions issue.
It still takes several, dozens, or even hundreds of times to get a user/group to stick in the permissions list, and about the same to get their permissions level to change, but at least now when it finally does stick it stays put.
Currently Being ModeratedJan 26, 2012 12:14 PM (in response to Chazz Layne)
Nope, they're all still Lion-related.
FileMaker simply wouldn't let us edit the database due to write errors. Now that the permissions are straight it works fine (except IWP, but I haven't tackled the Apache fixes linked above just yet).
Currently Being ModeratedJan 26, 2012 2:07 PM (in response to Chazz Layne)
Yep, a heart-of-Unix is about the only thing saving this "server" from a one-way ticket back to Apple.
Liberal use of chmod -R -N, followed by new permissions from scratch has things pretty much normalized now.