![]() Hi & for the update on that! We did know there were occasional issues with AFP and memory use in 10.7.5 and 10.8.x, but hadn’t heard reports of it happening still in 10.9.x. Hopefully Apple fixes this with 10.9.3 and a new version of the Server app. The app is not that so ideal, but I don't have to constantly purge the box when inactive memory gets thank you for posting and if you find a better solution on afp or see improvements, let us know. On that secondary box, I'm running the memory cleaner app. I then configured a secondary DP on an OS X box to balance things out on different floors when executing policies with large files. Separate from a Casper/JSS perspective, I even mounted a share hosted on this box to several clients and copied about 10GB of data simultaneously on 5 clients, and while the copying was taking place, yep again, the RAM was swallowed up leaving the system with only 200+ MB of free RAM.įor my production JSS (8.73 & 10.9.2 with 16GB of RAM), I ended up removing DP services all together. On my test JSS, 16GB, i7, running both 10.8.5 and then 10.9.2 under JSS 8.73 and now 9.3, the inactive memory issue is unbearable. this issue is primarily attributed to afp. I'll let you and the rest of the folks here. Personally I was waiting until to do the upgrade until this summer, but now my hand seems forced. From what I'm reading, 10.9 seems to have the least issues when running 9.x. I would contact JAMF support BEFORE upgrading to any version of 9 on a 10.7 box. OH, 10.7.x is apparently known for this type of AFP issue. Regardless, I should be able to verify this as a solution by tomorrow morning. That said, There are folks running 9.3 on 10.9.2 and NOT having this issue. I had over 7k sitting in there the other day and now we're floating around the 80ish range after about 24 hours of watching. Helping clear out any build up APNs as I've mentioned before. I've been doing some database cleanup and the like. The box still runs, but the services are toast. Once memory fills the java _appserver eats up 1000%+ CUP usage and the server locks up effectively. The first of which being that the computer runs up "inactive memory" but cannot release it as the AFP connections are still open. AFP connections to the JSS are not being released.I've come around to the following diagnosis. ![]() In any event, I've tried most quick things off the top of my head and am probably about to call my friends over at JAMF but, I figured that I'd throw this out there as well!Īhhh yes. Mid 2010 MacPro w/8GB RAM running 10.9.2 and server 3.1.1Īlso, running a very fast Arecra Internal RAID for NetBoot and SUS/Caching Server The Primary DP is running on an Arecra Internal RAID. ![]() The Boot device happens to run the JSSs MySQL DB but that's a nice OWC SSD. ![]() ![]() Mid 2010 MacPro w/8GB RAM running 10.8.5 and server 2.2.2 Imaging a dozen computers will lock up the machine (Showing full inactive memory and _appserver CPU utilization) within seconds.Īnyone else seeing this type of behavior? Running Casper Imaging will lock up the JSS within a few minuets. Users utilizing "Self-Service" now cause a noticeable jump in CPU usage and enough RAM(inactive) so that if I don't watch it (think purge command) it will eventually lock up. Since updating to JSS 9.3 (we've made each and every small jump since 9RC1) I've noticed (alright, I've been bashed over the head) Java's _appserver eating over 1000% CPU and running up inactive memory until the whole JSS locks up. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |