Monday, 9 April 2018
IBM Cloud Private - 504 Gateway Time-out
I was seeing this: -
when attempting to access the Admin Console of my newly-built iBM Cloud Private (ICP) 184.108.40.206 environment: -
This occurred after I started up the three VMs that comprise the ICP environment after a few days of downtime.
I kept an eye on the running Docker containers on the Boot node: -
docker ps -a|more
Apart from booting up the VMs, I didn't explicitly restart the Docker engine, as per this: -
systemctl restart kubelet docker
working on the assumption that the kubelet and docker services would autostart.
I did check that both services were running: -
systemctl -l|grep -i kubelet.service
kubelet.service loaded active running Kubelet Service
systemctl -l|grep -i docker.service
docker.service loaded active running Docker Application Container Engine
As it turns out, my patience was rewarded ….
In other words, it just started working.
In case it helps. this is also worth a look: -
which reminded me that I could've used this: -
journalctl -u kubelet -f
to see what was going on.
I was repeatedly seeing this: - java.lang.IllegalStateException: There is no body to invoke with a Jenkins Pipeline that I was executing...
I've just spent ~1 hour trying to get a pair of Powerline adapters to .... pair. This involved pressing a "Pair" button on one...
On IBM developerWorks here: - https://developer.ibm.com/cloudautomation/videos/ Use CAM to deploy Websphere Liberty into AWS Deploy MQ topol...
If you're running IBM Notes 9.0.1 and have updated to macOS 10.14 Mojave, be aware that you'll also need to install the most recent ...