Embedded MariaDB4j unable to load openssl lib 1.0.0 (Mac OS Catalina)

On my Mac (Mac OS Catalina 10.15.3), after a `brew update & brew upgrade` the openssl lib was updated from 1.0 to 1.1.

Sadly, the embedded MariaDB(j) I‘m using for Java Application UnitTests seems currently not to be compatible with opelssl 1.1.

Caused by: ch.vorburger.exec.ManagedProcessException: Program [/.../MariaDB4j/base/bin/mysql_install_db, ...) failed, exitValue=1, last 100 lines of console:
dyld: Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
Referenced from: /private/var/folders/ws/b6yxxmzj3hb20lkqndwws27r0000gp/T/MariaDB4j/base/bin/my_print_defaults
Reason: image not found

A similar issue reported here: https://github.com/vorburger/MariaDB4j/issues/48 and more specific in a comment from January 19th https://github.com/vorburger/MariaDB4j/issues/48#issuecomment-573946677

My (temporary) solution was to switch openssl back to lastest 1.0:
$ brew switch openssl 1.0.2t
Cleaning /usr/local/Cellar/openssl/1.0.2t
Opt link created for /usr/local/Cellar/openssl/1.0.2t

Mac OS – integrierter WLAN Scanner

Ab OS-X 10.13 (Sierra) und höher ist der Scanneraufruf wie folgt zu erreichen:

  1. Mit gedrückter alt Taste auf das WLAN Symbol klicken
  2. In den sich erweiternden Auswahlmöglichkeiten „Diagnose für drahtlose Umgebung“ auswählen
  3. Im sich öffnenden Fenster NICHT auf „Fortfahren“ klicken!
  4. Die cmd Taste und option Taste gedrückt halten und je nach gewünschter Diagnose die Ziffern 1-4 drücken.

Für ältere Mac OS-X Versionen gelten lediglich andere Tastenkombinationen im letzten Schritt (4.). GGf. einfach über das Menü „Fenster“ die gewünschte Diagnostik aufrufen.

Kubernetes helm error: UPGRADE FAILED: „{RELEASE-NAME}“ has no deployed releases

Sometimes after a failed or canceled Kubernetes helm release `install` or `upgrade` a repetition failes with the following error message

Kubernetes helm error: UPGRADE FAILED: "{RELEASE-NAME}" has no deployed releases

In this case you can either delete and purge your installed release, but be aware that this will also delete the complete history of the release.

Or, the better way, you can repeat your `install` or `upgrade` command with `–force`.

$ helm upgrade {RELEASE-NAME} --install .
Kubernetes helm error: UPGRADE FAILED: "{RELEASE-NAME}" has no deployed releases
...
$ helm upgrade {RELEASE-NAME} --install --force .

Reset Minikube on MacOS (VirtualBox VM) to the initial IP

In case your Minikube does not get the inital IP 192.168.99.100 assigned from the VirtualBox VM manager but it increases on next minikube start to 192.168.99.101 or higher, you can reset to the initial IP as follows:

Assuming: Mac OS, VirtualBox VM

$ minikube ip
192.168.99.110

$ minikube stop
$ rm ~/Library/VirtualBox/HostInterfaceNetworking-vboxnet*
$ minikube start

$ minikube ip
192.168.99.100