Dear piler users,

I was pretty unfortunate when putting the finishing touches to 0.1.24.

I created some sql wrapper functions for the piler binaries, however
it turned out that I had not been careful enough to handle NULL values properly.

Like I said I was unfortunate because the mysql client libraries on my archives (including the demo site) survived this flaw. Otherwise I could have spotted and
fixed the error.

However on some platforms (most notably on centos and ubuntu) the bug segfaulted the piler daemon (and probably other binaries as well) preventing you to start
it at all.

I managed to spot and fix the issue last night, so if you are affected by this issue, then please download the latest master branch (https://bitbucket.org/jsuto/piler/get/master.tar.gz),
and upgrade.

If you don't want to upgrade the gui, then you may skip updating the sql scheme of the piler database (ie. in that case you don't have to run the following command:
mysql -u piler -p piler < util/db-upgrade-0.1.24-vs-0.1.25.sql).


If you are affected and don't want to upgrade for any reason then the you may use the following workaround: you may either delete all entries from both retention_rule and archiving_rule
tables, or replace any NULL values with an empty '' value.

Note that 0.1.23 and older versions are not affected.

If you have any questions, still experiencing issues, then let me know.

Best regards,
Janos

Reply via email to