-
All replies
-
Helpful answers
-
Mar 18, 2014 9:32 AM in response to fkick1by fkick1,When starting devicemgr from the terminal I get the following errors:
2014-03-18 09:30:40.264 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:30:42.294 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:30:44.334 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:30:46.366 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:30:50.800 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:30:52.834 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:30:55.487 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:30:57.514 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:30:59.563 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:31:01.588 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:31:03.600 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:31:05.613 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:31:07.625 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:31:09.642 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
2014-03-18 09:31:14.284 serveradmin[3097:4e1f] NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
Thanks
-
-
Mar 18, 2014 2:12 PM in response to fkick1by P_Reventlow,Same problem here - after update from server 3.0.3 all services work except Profile Manager that won't start. No special cpu load to speak of.
-
Mar 18, 2014 2:35 PM in response to fkick1by welikeit,My Profile Manager service starts, but it won't let me sign configuration profiles anymore. ??? And now there's no Trust Profile available for download. ???
Ugh. I thought Apple was ironing this stuff out better. NOPE.
-
Mar 18, 2014 2:41 PM in response to Linc Davisby fkick1,Hi Linc,
Following the instructions in that post had no effect under 3.1, even though those systems were the same once devicemgr started from the command line.
Thankfully I had a Carbon Copy backup of my profile manger folder and server app from right before the update, so I was able to restore back down to 3.0.3. (Delete the profile manger folder from the Library/Server folder, and remove the Server.app 3.1, the copy both back over from the backup and reinitialize Server.app to bring everything back).
Unfortunately it doesn't look like 3.1 is an option for us right now.
-
Mar 18, 2014 2:53 PM in response to fkick1by Linc Davis,There are other reports of problems with Profile Manager in this release. I don't know what's causing them.
-
-
Mar 18, 2014 7:26 PM in response to welikeitby ajm_from_WA,yikes. well what did 3.1 fix? It sounds to me like its not worth it for me to even try it. I've been using profile manager as much as possible and it sounds like 3.1 might even be a step backward
-
Mar 18, 2014 10:44 PM in response to fkick1by MalcolmIncognito,I was worried ours was broken also.
A previous update killed our last one, I didnt want to have this happen again, turns out we just needed to restart.
It would appear there is no longer the option for profile manager to be a security option to enable for users and groups, but when I tried to enrol a few users it wasn't letting them in.
Restarted server and everything worked ok.
Might have a go with the air print settings, which apparently was a part of the fix.
-
Mar 19, 2014 1:06 AM in response to fkick1by James.Rainey,We are experiencing this same issue, unfortunately i don't have another machine to copy the server.app from, can you think of another option that may assist us while we wait for Apple Support.
-
Mar 19, 2014 5:48 AM in response to fkick1by andydvsn1824,Same issue here, but I'm now back up and running. Thought I'd try to unbreak it before restoring the backup.
To get back into action I shut down any services in Server.app, then made a .tgz of my previously working /Library/Server/ProfileManager area. Then I moved /Library/Server/ProfileManager to another location and deleted Server.app. I downloaded a fresh copy from the App Store and fired it up - a new /Library/Server/ProfileManager directory appeared. I closed Server.app, deleted the new /Library/Server/ProfileManager directory, moved my original one back into place and performed a permissions repair (just in case).
Fired up Server.app again and it began with the 'first setup' style messages. It motored through that in no time and I could then turn Profile Manager back on (it retained all my previous settings). Then it was just a case of going back through and re-enabling the other services I had switched off.
Not had chance to play with the new features, but everything looks to be back and working. It pushed out updated Profiles straight away and all looks well.
All this just as I had started to gain just a tiny bit of confidence in this Apple Server software again. Bring back Server Admin and Workgroup Manager!
-
Mar 19, 2014 9:30 AM in response to fkick1by fkick1,★HelpfulFor those running into the issue of the ever increasing log files, mscott_mdm suggested the following solution (though it may only be temporary until Apple releases a patch).
I think this should stop this problem for one month:
sudo psql -U _devicemgr -d devicemgr_v2m0 -h /Library/Server/ProfileManager/Config/var/PostgreSQL -c "UPDATE devices SET last_update_info_time = dm_current_timestamp() + '1 month'"
Copy the above and paste it into Terminal (or remote ssh shell) on the server as an admin user. You'll almost certainly be prompted to enter your admin password.
Note that until a proper fix is released by Apple, it would appear that enrolling a number of new devices could lead to this problem recurring in less than a month, but you can always run the above command again.
Please let me know if this seems to bring things "under control" for you. (It won't be immediate, but it should show signs of working within a few minutes.)
For me this has stopped the issue of the ever growing log file and things seem to be running smoother.
-
Mar 19, 2014 10:37 AM in response to fkick1by mscott_mdm,I would also recommend that you run this command, to keep newly-enrolled devices from causing the same problem after a couple of days:
sudo psql -U _devicemgr -d devicemgr_v2m0 -h /Library/Server/ProfileManager/Config/var/PostgreSQL -c "ALTER TABLE devices ALTER COLUMN last_update_info_time SET DEFAULT dm_current_timestamp() + '1 month'"
-
Mar 19, 2014 2:05 PM in response to andydvsn1824by P_Reventlow,Thanks for your tip Andy. I was able to restore server 3.0.3 as you outlined and profile manager is back in business.