Tonight I made an absolut clean and fresh install of Leopard. Everything configured to run (OD, Certs, iCal...).
Worked perfectly! Update to Lion. And he struggled at exact the same position with OD!
Apple has to do a lot of work here.
Thanks for your kind words, but I need an 100% up and running OD, or I will struggle with the clients.
me respectively my server too.
First after upgrade it works (except cpu-/network-traffic-statistic graphs), but now after a necessary restore from backup "Profile Mangar" is broken. No start in Admin, no connect with Safari.
BTW: Statistics furthermore won't work.
And now: fresh install of SL-Server, Update to 10.6.8 and then Lion Update and Lion server upgrade? Too many steps, too many possible source of trouble.
Why i din't secured the Lion Update to disk???? ;(
afp548.com has some great Lion Server videos. I just clean installed Lion Server and followed the Profile Manager setup video and am easily managing several devices (iOS and Mac). The only error I encountered during the entire process was a "Connect to Server" error after promoting my server to OD Master - rebooting the server fixed that. I'm using the SSL cert that was created during OD Master creation.
After 48 hours of struggle with this same issue and 6 clean re-installs of Lion Server I have found the bug in Lion Server causing all ruby based collaboration services (Device Manager, Wiki, ical, some adress book features ie: major screw up in services around server admin tools and server app). The most visible one is in Profile Manager because as you all pointed out it even says sometimes "Error Reading Settings". And if you take a look at the logs its even worst...full of errors...
that's how I found out, yes reading all the logs took time:
Basically they all fail because they use Postgresql database.
At first I did 2 clean re-installs and noticed everytime, after having spent some time configuring the server (open directory/kerneros, creating accounts/mailboxes, profiles etc.). I would do a reboot and everything would break.
Now I won't go over all the diggin I did but I finally manage to understand why Postgres at some point was failing.
it seems there is a bug.
If you turn "Dedicate Resources to Server Services" in the Server.app Hardware Section (next to Push Notifications switch", postgres doesn't start and all depending services (lots) fail.
The Solution: Just turn that OFF as shown below and restart. Everything should get back in order. If you still see some "push_notify: not connected" erros in you console logs (it happened to me even thoug all servcies were restored) the solution is easy. Hit change and redo the setup with you appleid. You'll be issued new certs by Apple and everything shoudl work fine.
Hope this helps the many people that are frustrated like I was. Now that everything works, it's the perfect server for a mini Cloud. You'll love Profile Manager for provisioning payload to your devices. Elegant, efficient and simple, yet very flexible with the openDirectory backend.
Cheers everyone !
The Solution: Just turn that OFF as shown in the screenshot and restart.
Everything should get back in order. If you still see some "push_notify: not connected" erros in you console logs (it happened to me even thoug all servcies were restored) the solution is easy. Hit change and redo the setup with you appleid. You'll be issued new certs by Apple and everything shoudl work fine
Also I think full server restores from TimeMachine are a bit dodgy.
many files were not restored (Log files etc. and the services fail to start because of a permission denied or missing files)
Check you system.log and see what is the problem, then fix it manualy from terminal.
I fixed most of the services that way. By creating missing files/folders and good permissions...
Hope this helps.
This didn't work for me, any other ideas?
My relevant log messages are still:
11-08-01 11:05:21.791 PM com.apple.collabd.notifications: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)
11-08-01 11:05:21.791 PM com.apple.collabd.notifications: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
11-08-01 11:05:21.791 PM com.apple.collabd.notifications: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'
11-08-01 11:05:21.791 PM com.apple.collabd.notifications: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'
11-08-01 11:05:21.791 PM com.apple.collabd.notifications: from notifications.rb:145:in `initialize'
11-08-01 11:05:21.791 PM com.apple.collabd.notifications: from notifications.rb:439:in `new'
11-08-01 11:05:21.791 PM com.apple.collabd.notifications: from notifications.rb:439
11-08-01 11:05:21.809 PM com.apple.launchd: (com.apple.collabd.notifications) Exited with code: 1
11-08-01 11:05:21.000 PM kernel: nstat_lookup_entry failed: 2
it's work perfectly and get 600 Macs and 400 IOS devices manages by this way without any problems just need a clean Install and if want you can make a clean install with some tools like just take care do not aply some profile per group and the same per system it will make double config in Mail per exemple and double account...
I do a Clean Install with
I clone my disk just after clean install in case off...
I do other clone at each step and now I just need some minutes to restore my server...
do the same U will enjoy !
Lion DiskMaker is made by Gete gete.net a french IT
I've been trying all these differen kinds of solutions all over the web and finally solved it now without them.
In 2011 I installed Server but didn't really know where i'd use it and furthermore how.
So now in 2013 I know a lot more about "computer stuff" and made a clean installation but i messed up with the certificates for the services. I decided to do a clean installation again. But for no reason I kept getting these failures with the profilemanager and also of course with the wiki. After 14 different types of clean installations, where i also tried to do a complete installation from the ground up by starting with snow leopard...(what a waste of time), i tried to remeber what i had done differently by the first clean instal. I just did it that and now it works.
I installed the server by just being connected to the web via wifi and turning the Ethernet connection off.
I know for most you guys this isn't an acceptable solution because of its low network speed but perhaps it's a good hint for someone to find the bug and solve it.
Perhaps this helps someone now in 2013