General description

Three instances of OFBiz run on the OFBiz demo VM at

  • trunk: the trunk version
  • stable: the last stable version (currently 18.12)
  • next: the next stable version (currently 22.01)

This is the 3rd instance of VM we use hence the 3 in its domain name. The root of is the so called bigfiles directory which is actually at /var/www/ofbiz/big-files.

We own 3 Apache sub domains

The Puppet configuration is at It‘s currently impossible to directly modify, it’s a private Github repo. Just create an Infra Jira asking for the wanted change...and be patient ;)

Actions on demos

SSH to server (a VM actualy), then follow the below procedure. You will need to use OTP (One Time Password). For documentation on how to use OPIE (One time Passwords In Everything), see this page.

Note: Only run the ofbiz demos using the ‘ofbizDemo’ user, never run as root.

You need to be registered as a sudoer (ask Infra).

Then sudo to the ofbizDemo user:

sudo -s -u ofbizDemo -H

Sudo uses OTP. Use a tool like to generate the OTP
You can then start/stop as required.

To check if the demos are being run as the ofbizDemo user:

ps aux | grep ofbizDemo

The first column on the left tell you the username the demo is
being run as - it should say ofbizDemo (UID).

Type 'exit' to exit the ofbizDemo user and return to your username.

Also note that the demos are usually updated and started/stopped automatically using the script in this directory. It is run by an ofbizDemo cron job every 24 hours at 3 AM. You should therefore only need to start/stop manually if there is a problem.

Upgrade stable and next demos

You need first to create a directory under the ofbizDemo directory and to clone the related in this new directory. Then to copy and apply the patches contained in the and files, read the comments in these files for details.

Looking at the Puppet configuration (see above) you will see that you only need to change the and files to upgrade stable and next demos. Because they are defined in the Puppet configuration by respectively

stable: ProxyPass / ajp://localhost:18009/
next   : ProxyPass / ajp://localhost:28009/

Finally you need to kill the current stable and next processes before running again the demos using


Letsencrypt certificate update

It was a time when every 3 months we needed to manually update our Letsencrypt certificate. It was automated before, it‘s now again, so no worries. Anyway, if necessary it’s quite easy to do so. Simply connect to the demo VM and run

sudo certbot renew

I got this message today (2020-04-17):

Processing /etc/letsencrypt/renewal/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert not yet due for renewal
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
The following certs are not due for renewal yet:
  /etc/letsencrypt/live/ expires on 2020-06-08 (skipped)
No renewals were attempted.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

and always since: it‘s OK. Nothing to do, it’s automated. :)

Current restriction

If you want to restart only a single instance you can respectively use This does not work.See why at So you need to use ./ from ofbizDemo From time to time (every months?) better to delete nohup.out.

Keep the VM clean

From time to time (I‘d say when it’s hundreds of MB) we need to delete the nohup.out file. It's used when you manually start the demos and acts as an issues history. Then simply sign in as ofbizDemo user and delete the file.

Also, it's OK for months but at some point I had to clean the Gradle cache. For now just verify with “df” command that we are not graping too much memory, around 50% on /dev/xvda1 is OK