MyThinkPond

On Java, Python, Groovy, Grails, Spring, Node.js, Linux, Arduino, ARM, Embedded Devices & Web

  • Recent Posts

    August 2017
    M T W T F S S
    « Jul    
     123456
    78910111213
    14151617181920
    21222324252627
    28293031  
  • Subscribe Options

  • Awards

    JavaCodeGeeks
  • Most Valuable Blogger @ DZone
  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 173 other followers

  • Follow MyThinkPond on WordPress.com
  • Blog Stats

    • 364,698 hits
  • General Options

Archive for the ‘Mac OS X’ Category

Mac OS X iDRAC7 FileNotFoundException .java/deployment/security/trusted.certs

Posted by Venkatt Guhesan on November 17, 2016

macosx_blogarticle_100pxWhen you connect with a Dell iDRAC virtual console you may encounter the following exception on a Mac OS X

FileNotFoundException ~/.java/deployment/security/trusted.certs

Here is a simple fix for this:

 

 

mkdir -p ~/.java/deployment/security
cp ~/Library/Application\ Support/Oracle/Java/Deployment/security/trusted.certs ~/.java/deployment/security/

Cheers.

Posted in Mac OS X | Tagged: , , , , | Leave a Comment »

Solved: git status failed with code 69 error when opening SourceTree in Mac OS X

Posted by Venkatt Guhesan on September 24, 2015

If you receive the following error when opening SourceTree or other applications installed in your Mac OS X, then here is how you can solve it. Sometimes people make things more cryptic than it needs to be.

Error encountered

‘git status’ failed with code 69:’

Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.

and here is the example of the screenshot:

2015-09-24_14-50-56

Solution:

What that message is telling you is that you need to open the application XCode on your Mac OS X and since it hasn’t run since the last update, you need to accept the new license EULA agreement that’s part of the updated XCode. Once you accept the license and close the XCode application and then go back to your other application that was throwing the error and try opening it. The error no longer happens.

Cheers

Posted in Mac OS X | Tagged: | 2 Comments »