Upgrade 1.2.x to 1.3.x

[Thomas Helmrich]

Hey there,

i want to upgrade my piler instance from 1.2 to 1.3.

Whats the best case to proceed it?

And by the way. In the RELEASE_NOTES is a line with:

Removed PDF support

What does this means in detail?

Thanks!

[Janos SUTO]

The pdf support removal means that piler gui won't export any emails to pdf format. I used to use tcpdf for that purpose, however it turned out there were some issues in certain cases. Indexing pdf files are still supported via pdftotext utility

[Janos SUTO]

Regarding the upgrade, please read this email: http://www.mail-archive.com/[e-mail]/msg01186.html

[Thomas Helmrich]

Great - Thanks!

[alu-one]

Hi, I just tried to upgrade piler from v1.2 to 1.3. Unfortunately, afterwards it cannot connect to MySQL anymore.

My current system: Pre-installed Debian OVA with Piler v1.2, from 2016-11

Because of an SSO issue (#519), I have changed to Apache. In addition, I am using a samba path for /var/piler/store (similar to your NFS tutorial). Regarding this, is there anything to consider during upgrade?

Could you please tell me which ./configure parameters need to be used when upgrading from the original/previous VM image? After "make install", is there anything I have to copy manually in addition? According to #239, I tried to modify some mysql config parameters, but with no success yet.

Regarding general OS upgrade, is there anything to consider besides the common commands (aptitude update, aptitude upgrade, ...)?

Thank you, best regards

(Edit, from mail.log, after upgrading: Sep 29 16:22:56 mailarchiv piler[2621]: cannot connect to mysql server Sep 29 16:22:56 mailarchiv piler[2621]: cannot read keyfile: /usr/local/etc/piler/piler.key )

[Janos SUTO]

Check the contents of /usr/local/etc/piler/piler.conf file, especially the mysql* parameters. Try to connect to mysql using the cli (=the "mysql" command) with the same parameters. If your configs are in /usr/local/etc (and not in /usr/local/etc/piler) then move them to /usr/local/etc/piler (provided that ).

When you upgrade you should the same exact parameters for configure as the last time. See piler -V output for that. But after the upgrade it would NOT reflect to your previous setup. Do you still have the 1.2.0 source dir of piler? If so, then check inside the beginning of config.log file.

[Aleksey87]

Janos SUTO Tell me if you want to upgrade from version 1.2.0 to version 1.3.1?

tar zxvf piler-1.3.1.tar.gz
cd piler-1.3.1
./configure \
        --localstatedir=/var \
        --with-database=mysql \
    --enable-tcpwrappers

make
su -c 'make install'
ldconfig

Huge gratitude for the support of this project.

[Janos SUTO]

Hello Aleksey, I'm not sure what you mean. Are you asking me if I wanted to upgrade from 1.2.0 to 1.3.1? Regarding my personal archive and the demo site, definitely. In fact I have already done so. Please clarify what you mean,

[Aleksey87]

Hello I update how do I upgrade from version 1.2.0 to version 1.3.1 ? as for new installations ?

./configure \
        --localstatedir=/var \
        --with-database=mysql \
    --enable-tcpwrappers

make
su -c 'make install'