Jelastic related Problems

Jelastic has sometime its moments. Let’s see some symptoms of things that we saw can go wrong:

Environment creation stucks

You know you are in trouble when jelastic interface don’t display any displayName and run “Installing …” forever. Your lovely hosters can’t do anything to stop the operation, you will need to wait for the environment to be failed after some hours.

Impact: low We are using parking system, and as we already have a buffer of environment ready, this kind of problems don’t stuck the application. It will just create new environment if it can not interact with this one.

[jem init] fails to start, no container is running

This error may appears when you look at your logs (/var/logs/run.log). The better is to look at the jem.log file to see what is going wrong.

Impact: high. An instance that has been stopped by the user and want to run again may not be able to restart. The only solution is to stop and start it again (from the voca UI or from jelastic).

Remediation: Restart the server sometimes works.

Unix permissions after restart

It is possible unix permissions are erased after restart. As we bind volumes to a file container, depending on the start it may erase the permission. This should not be a problem anymore as we check permissions on entrypoints.

SSH access asks for password

Sometimes, the SSH connexion to your container, to debug locally won’t work and will ask you for a password. This happens more on debian based containers like decidim container. To fix this, you can reset password in the container, and use the password you receive by email to connect to your container.

Remember to add your public ssh key in your Jelastic Account

All your environments are down

💰 Check your balance, you may have no money left.

Impact: High.

Concurrent actions

If you remove an environment before it has been deployed, it probably block your environment and you will need to wait Jelastic internals timeout to get back a normal situation. Same with most of the operations on one environment, try to avoid concurrent actions as much as possible.