Model Name: Xserve
Model Identifier: Xserve2,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 1
Total Number Of Cores: 4
L2 Cache: 12 MB
Memory: 6 GB
Bus Speed: 1.6 GHz
Boot ROM Version: XS21.006C.B06
SMC Version (system): 1.26f3
LOM Revision: 1.1.2
The same here on two xserves!
Running SoftwarUpdate from the GUI!
Software Update Package Authoring: my.result.title and my.result.message not defined or empty Software Update IFJS_PropertyListConvertToType() called with type=3 com.apple.launchd (com.apple.suhelperd) Exited with exit code: 2 com.apple.launchd.peruser.501 ([0x0-0x4b04b].com.apple.SoftwareUpdate) Job appears to have crashed: Segmentation fault
I also get a message like this from ServerAdmin every minute in console:
servermgr_info: unexpected Software Update state: crashed
The crashreport says:
Thread 7 Crashed: Dispatch queue: com.apple.root.default-priority
3 ??? 0x000025f96ea04573 0 + 41753233081715
5 ??? 0x00000001024ba9e0 0 + 4333480416
If full crashreport is required, I can mail it!
Any ideas to get Softwareupdate running again?
I have been like crazy for two days over the issue. Removed RAM, used a backup logic board, all thinking it could be a hardware problem.
Booting from an external HD with 10.6.8 client + Safari 5.1.4 produces the same problem. Early 2008 XServe. We have both Early 2008 and Early 2009 servers. On the 2009 ones the issue does not appear.
Let's wait and hope Apple solves the problem soon.
I tried to switch off softwareupdate notifications in serveradmin to stop the crash of softwareupdate every minute reported in console with messages like "servermgr_info: unexpected Software Update state: crashed".
After a restart of the server the crashes startet new early (2:00) in the morning.
It would be nice to get a workaround for this until apple fixes the prob.
Peter Borbonus wrote:
If you can tell me how I can report the bug directly to apple, I will do it. Give me the link please.
I reported it to apple (go to bugreport.apple.com, log in using your usual appleID). It is bug #11048593, and marked as a duplicate of #11034745, so apparently I wasn't the first one to report it. They responded by email asking for the crash report, which I emailed back to them.
Fortunately for us, we have a pair of these, not yet in service (we bought them to create a dual-dual virtual machine server). So it's trivial to take one, run the update, crash software update, and then use the other machine's disk (without update) to restore the machine to the state without the safari update.
Hmmm... I bet I should install the 5.1.2 safari update, though, so we aren't at the version that shipped on the original osx server dvd...