Fixing Elastic Beanstalk Pip error on El Capitan

You want to upgrade the AWS Elastic Beanstalk CLI tool using pip on Mac El Capitan like this…

pip install --upgrade awsebcli

…and got this?

DEPRECATION: Uninstalling a distutils installed project (six) has been deprecated and will be removed in a future version. This is due to the fact that uninstalling a distutils project will only partially uninstall the project.

and an error which looks like this?

OSError: [Errno 1] Operation not permitted: ‘/tmp/pip-60cnQx-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/six-1.4.1-py2.7.egg-info’

 You can fix this using

pip install --upgrade awsebcli --ignore-installed six

Can’t re-install app from Apples App Store

Problem: I developed an application via Xcode and published it in the App Store. I then continued developing it and removed the application I had installed from the AppStore.

When I try to re-install it from the AppStore I got the following message:

“If you want to replace it with this version, move the existing app to the trash”

I deleted all the data for this application from

  • ~/Library/Containers
  • ~/Library/Application Support
  • ~/Library/Preferences
  • the application itself of course

But still. It was not possible to re-install it. Finally I stumbled across lsregister – a tool for the Launch Service Database and this command helped me:

/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain user

After that, the install worked.

Image Credit: dirty rotten apple 2 by Lara604 (CC BY 2.0)


Postfix rejection problem ‘454 4.7.0 TLS not available due to local problem’

For our service Melt Mail there happened to be a Postfix error which prohibits forwarding e-mails from Gmail. The SMTP server fails with the message

454 4.7.0 TLS not available due to local problem

The problem was the smtp daemon of Postfix

warning: TLS library problem: 24753:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:172:

The solution was to remove the


line in the file.

Maven missing in OS X Mavericks

mvn: command not found in OS X Mavericks

I have the preview version of Apples OS X Mavericks installed and got an error when trying to run maven:

-bash: mvn: command not found

This was little bit confusing because normally maven is pre-installed in OS X but “the world’s most advanced desktop operating system” comes without maven – at least in this preview version.

But Homebrew is our friend and makes it easy to install it:

brew install maven

and after that I got Apache Maven 3.0.5 installed and running on my system.

Couldn’t load myproject.xcodeproj because it is already opened from another project or workspace

I just had the problem, that I created a brand new project in Xcode and wanted to add CocoaPods to it. When I opened my newly created workspace I got the error:

Couldn’t load myproject.xcodeproj because it is already opened from another project or workspace

Only the Pods project was correctly listed in the workspace – myproject not. The solution was to close the project in Xcode and close Xcode before running

pod install

The steps to fix this issue:

  1. Create new project in XCode
  2. Close the project via “File > Close Project”
  3. Close XCode
  4. Go into the project directory
  5. add the Podfile
  6. run pod install
  7. Open the workspace



Spring Roo Exception: Row was updated or deleted by another transaction

While playing around with Spring roo I see this error while running the integration tests via

perform tests

roo org.springframework.orm.jpa.JpaOptimisticLockingFailureException: org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction

The problem was here, that my database table which stored the specific entities had a version column but only NULL values inside. I have replaced the NULLs with an numeric value and then it worked.

“Updating Maven Project”. Unsupported IClasspathEntry kind=4

I’m just playing around with Spring Roo and multi-module Maven projects. When I start to import a project into the STS I am getting the following error and the SDK is getting unresponsive:

“Updating Maven Project”. Unsupported IClasspathEntry kind=4

The problem is somehow related to the m2e plugin integrated in the STS.

So solve this select (right click) on the STS/Eclipse modules

Maven -> Disable Maven Nature
Maven Disable Maven Nature in STS (Eclipse)
Maven Disable Maven Nature in STS (Eclipse)

run in the terminal

mvn eclipse:clean

and select again in STS

Configure -> Convert to Maven Project