Std::bad_alloc error

[bbergstein]

We're having an issue with the JAMF binary. It seems that every time we attempt to update the policies on any client machine, it ends with an error that says:
terminate called after throwing an instance of 'std::bad_alloc'
what (): std::bad_alloc
Abort trap

I tried to reinstall the binaries, but with no success. It does seem to be running some policies such as installing self service, but it does not report any logs to the server, and any newer policies do not execute.

Any idea?

Thanks for the help,

--benji

Benji Bergstein | iPod touch/iPad Support | Giant Eagle, Inc. | Benji.Bergstein at gianteagle.com | 412.963.6200 x21386

[bentoms]

Are these new 10.6.6 MacBook Pro's?

Regards,
Ben Toms
IT Support Analyst GREY Group
The Johnson Building, 77 Hatton Garden, London, EC1N 8JS
T: +44 (0) 20-3037-3819 |
Main: +44 (0) 20 3037 3000 | IT Helpdesk: +44 (0) 20 3037 3883

[bbergstein]

They are all running 10.6.6, but there are a few different kinds of machines, including 2 iMacs, an older (mid/late 07) MacBook Pro, and a late-09 MacBook Pro.

[#4]

If you're certain your JAMF binary is intact, it's a bug in the binary. Check your MD5 checksum of the binary against mine:

mec087602:~ burban$ md5 /Applications/Casper Suite 7.31/Recon.app/Contents/Support/jamf
MD5 (/Applications/Casper Suite 7.31/Recon.app/Contents/Support/jamf) = 5a15975014578a19feefad8f1c8619e8
mec087602:~ burban$ md5 /Applications/Casper Suite 8.0/Recon.app/Contents/Support/jamf
MD5 (/Applications/Casper Suite 8.0/Recon.app/Contents/Support/jamf) = 6f8e03f2054a0da441bccf60a3b7e2d0
mec087602:~ burban$

Which one you should compare against depends on which version you have; I happen to have both available on this computer, but the one you need to check is /usr/sbin/jamf. If your checksum doesn't match, try finding a copy of the binary that does, and install that.