Skip to content

Upgrading#

This documentation applies to Piler enterprise edition 2.1.0

Revision #2

Publication date: 2025-NOV-23

The 2.x version ships a brand new web app that is not compatible with the old one, has a different configuration mechanism, and has a few prerequisites

Prerequisites#

  • real time index
  • dynamic indexes when using a multi-tenant deployment

Upgrade steps#

Fix permissions#

chmod 750 /var/piler/store/
chmod 750 /var/piler/astore/

Run the migrations#

Run mysql migrations on each piler related mysql database:

for i in /usr/share/piler/migrations/sql/*.sql; do
   mariadb --defaults-file=/etc/piler/.my.cnf piler < $i
done

Run manticore migrations for each tenant: In case of a multi-tenant deployment, be sure to use the tenant id

for i in /usr/share/piler/migrations/manticore/*.sql; do
   sed 's/TENANTID/piler/g' "$i" | mariadb -h0 -P9306
done

For a multi-tenant deployment, run the mysql migrations for all piler databases, also run the manticore migrations for all tenant ids as well, and replace "piler" in the sed command with the tenant id, eg.

sed 's/TENANTID/example001/g' ....

Update the passwords#

Piler uses the bcrypt password hashing algorithm, so the passwords in the local database must be fixed.

The below statement updates the built-in admin user's password to pilerrocks

mariadb --defaults-file=/etc/piler/.my.cnf piler <<< 'update user set password="$2y$10$dEzUkJcI824suvEp4p.87u5IT7JitTzpMiMkBtOo7/RZvCYO5b8tC" where uid=1'