After upgrade from 1.4.4 to 1.4.7 the search/reception mail is not more workable

[stephdl]

Hello

I am not sure it is a bug or a misconfiguration, what I did

• direct install 1.4.7 with container, send some emails, piler is workable
• direct install 1.4.4 with container, send some emails, piler is workable, upgrade to piler 1.4.7: piler stops to work

for what I saw after the upgrade

• the search is empty
• the counter of mails does not increase anymore when I send emails

Before the upgrade I can list few emails and when I send emails to piler I can see the counter increasing in the admin page.

moreover I can see in the postfix log the messages about sending the email to piler
May 05 17:11:31 R1-pve.rocky9-pve.org postfix/smtp[12050]: 9220613992F: to=<archive@piler10>, relay=10.5.4.1[10.5.4.1]:20004, delay=6.4, delays=6.4/0.01/0/0.01, dsn=2.0.0, status=sent (250 OK <LWJUJG85BALGVQM9>)

I took the time to diff all the configuration files in /etc/piler with a direct install and a piler upgrade and I have the same content.

What is puzzling me is that the same configuration but as a direct install is workable, so my configuration should be good

[stephdl]

hum so piler after the upgrade cannot connect to mysl :/

2025-05-06T14:34:18.483197+00:00 piler piler-smtp[70]: connected from 10.5.4.1:43902 on fd=6 (active connections: 1)
2025-05-06T14:34:18.493315+00:00 piler piler-smtp[70]: received: QNUG5YAPRY1G6N1R, from=stephane@rocky9-pve.org, size=2776, client=10.5.4.1, fd=6, fsync=8683
2025-05-06T14:34:18.493671+00:00 piler piler-smtp[70]: disconnected from 10.5.4.1 on fd=6, slot=0, reason=done (0 active connections)
2025-05-06T14:34:23.393675+00:00 piler piler[73]: ERROR: cant connect to mysql server
2025-05-06T14:34:23.393684+00:00 piler piler[75]: ERROR: cant connect to mysql server
2025-05-06T14:34:33.394274+00:00 piler piler[73]: ERROR: cant connect to mysql server
2025-05-06T14:34:33.394277+00:00 piler piler[75]: ERROR: cant connect to mysql server
2025-05-06T14:34:43.394874+00:00 piler piler[73]: ERROR: cant connect to mysql server
2025-05-06T14:34:43.394878+00:00 piler piler[75]: ERROR: cant connect to mysql server
2025-05-06T14:34:53.395506+00:00 piler piler[75]: ERROR: cant connect to mysql server
2025-05-06T14:34:53.395508+00:00 piler piler[73]: ERROR: cant connect to mysql server
2025-05-06T14:35:01.939435+00:00 piler piler: INDEXER INFO: indexing delta1 started
2025-05-06T14:35:01.940847+00:00 piler piler: INDEXER INFO: indexing delta1 finished
2025-05-06T14:35:03.396108+00:00 piler piler[75]: ERROR: cant connect to mysql server
2025-05-06T14:35:03.396113+00:00 piler piler[73]: ERROR: cant connect to mysql server
2025-05-06T14:35:06.943291+00:00 piler piler: INDEXER INFO: merging delta to dailydelta started
2025-05-06T14:35:06.944968+00:00 piler piler: INDEXER INFO: merging delta to dailydelta finished
2025-05-06T14:35:13.396673+00:00 piler piler[75]: ERROR: cant connect to mysql server
2025-05-06T14:35:13.396717+00:00 piler piler[73]: ERROR: cant connect to mysql server
2025-05-06T14:35:23.397290+00:00 piler piler[73]: ERROR: cant connect to mysql server
2025-05-06T14:35:23.397326+00:00 piler piler[75]: ERROR: cant connect to mysql server

[stephdl]

hum I suspect really a bug due to #278 and another one, because after the upgrade I have also
drwx------. 3 ubuntu ubuntu 16 May 5 09:08 store

what I did

rm -rf .my.cnf MANTICORE config-site.dist.php config-site.php manticore.conf manticore.conf.dist piler-nginx.conf piler-nginx.conf.dist piler.conf piler.conf.dist sphinx.conf.dist
then I restart the container
I got another messages in mail.log

2025-05-06T14:42:47.593385+00:00 piler piler-smtp[76]: cannot load private key from /etc/piler/piler.pem
2025-05-06T14:42:47.593390+00:00 piler piler-smtp[76]: ERROR: init_ssl()
2025-05-06T14:42:47.597939+00:00 piler piler-smtp[76]: received: XP9HF9DTIXRC1RE5, from=stephane@rocky9-pve.org, size=3015, client=10.5.4.1, fd=6, fsync=4070
2025-05-06T14:42:47.598183+00:00 piler piler-smtp[76]: disconnected from 10.5.4.1 on fd=6, slot=0, reason=done (0 active connections)
2025-05-06T14:42:47.793062+00:00 piler piler[79]: 50000000681a1ff12f392644009ca2a9978a: mkdir /var/piler/store/00/681/97/8a: error=Permission denied
2025-05-06T14:42:47.793072+00:00 piler piler[79]: 50000000681a1ff12f392644009ca2a9978a: cannot open: /var/piler/store/00/681/97/8a/50000000681a1ff12f392644009ca2a9978a.m
2025-05-06T14:42:47.793074+00:00 piler piler[79]: ERROR: 50000000681a1ff12f392644009ca2a9978a: failed to store message: 50000000681a1ff12f392644009ca2a9978a.m
2025-05-06T14:42:47.793115+00:00 piler piler[79]: 0/XP9HF9DTIXRC1RE5: moved to /var/piler/error/XP9HF9DTIXRC1RE5
2025-05-06T14:42:47.793126+00:00 piler piler[79]: 0/XP9HF9DTIXRC1RE5: 50000000681a1ff12f392644009ca2a9978a, size=3015/0, attachments=0, reference=<2e1d0a9cfb9cd6a62158bddefb22b4c8@rocky9-pve.org>, message-id=<957940843925fb61b01be213cb2708d5@rocky9-pve.org>, retention=2557, folder=0, delay=0.0008, status=error

I check the permissions

root@piler:/etc/piler# ls -la /var/piler/      
total 4
drwxr-xr-x.  1 root   root       30 Dec 20 19:34 .
drwxr-xr-x.  1 root   root       41 Dec 20 19:34 ..
drwx--x--x.  1 piler  piler      54 May  6 14:42 error
drwx------.  2 piler  www-data    6 Dec 20 19:33 export
drwx------.  2 piler  piler       6 Dec 20 19:33 imap
drwx------.  2 piler  piler       6 Dec 20 19:33 manticore
drwxr-xr-x.  2 piler  piler       6 Dec 20 19:33 stat
drwx------.  3 ubuntu ubuntu     16 May  5 09:08 store
drwx--x--x.  1 piler  piler      24 May  6 14:42 tmp
drwxr-xr-x. 13 root   root     4096 Dec 20 19:34 www

I set the permissions to piler:piler on store with -R and everything is up and workable b ut I am not sure that I have the old index, I need maybe to wait the cron

[stephdl]

relative to the error on

2025-05-06T14:42:47.593385+00:00 piler piler-smtp[76]: cannot load private key from /etc/piler/piler.pem
2025-05-06T14:42:47.593390+00:00 piler piler-smtp[76]: ERROR: init_ssl()

I have

root@piler:/# ls /etc/piler/ -la
total 72
drwxr-xr-x. 3 root   root   4096 May  6 14:40 .
drwxr-xr-x. 1 root   root   4096 Dec 20 19:34 ..
-rw-------. 1 piler  piler   115 May  6 14:40 .my.cnf
-rw-r--r--. 1 root   root      0 May  6 14:40 MANTICORE
-rw-r--r--. 1 root   root    428 May  6 14:40 config-site.dist.php
-rw-r--r--. 1 root   root   1330 May  6 14:40 config-site.php
-rwxr-xr-x. 1 root   root   8493 May  6 14:40 manticore.conf
-rwxr-xr-x. 1 root   root   8525 May  6 14:40 manticore.conf.dist
-rw-r--r--. 1 root   root   2351 May  6 14:40 piler-nginx.conf
-rw-r--r--. 1 root   root   2343 May  6 14:40 piler-nginx.conf.dist
-rw-r--r--. 1 root   root   1257 May  6 14:40 piler.conf
-rw-r-----. 1 root   root   1380 May  6 14:40 piler.conf.dist
-rw-------. 1 ubuntu ubuntu   56 May  5 09:07 piler.key
-rw-------. 1 ubuntu ubuntu 5272 May  5 09:07 piler.pem
drwxr-xr-x. 2 ubuntu ubuntu   32 Feb 18  2024 sites

I think we have a bug somewhere with the upgrade @jsuto

[jsuto]

I think the problem is that the ubuntu 24.04 docker image ships the ubuntu user who's uid is the same as it was piler's in the the sutoj/piler:1.4.4 image that was built on ubuntu 22.04. The fix could be either running chown piler:piler for these files and directories, or fix /etc/piler/piler.conf username variable to run as user ubuntu. Not sure which is easier in your environment. I'm biased to keep piler as the running user.

[jsuto]

Or I may run userdel -r ubuntu before I install piler, and create a new image, and let's hope it will work, and the ubuntu user is not really needed.

[stephdl]

I can test if you want if you provide a container, what about to change the UID of ubuntu or piler. I admit it is not easy

[stephdl]

Hello

I got with my environment the way to trigger actions during upgrade, before and after the restart of the service, so I did after the service restart a chown myself, unfortunately it is not enough and piler cannot connect to mysql, until I restart piler a second time after the upgrade :p

[stephdl]

I think the ownership of this ubuntu should be fixed @jsuto, maybe by changing the UID/GID of piler itself, or by removing the ubuntu user but probably piler needs to become a sudo user itself

The upgrade is not easy I understand, but it is something we have to do/follow

[jsuto]

I've just created a fixed docker image, sutoj/piler:1.4.7b that has piler user with uid/gid: 1000/1000, just as with the previous release based on ubuntu 22.04. Let me know how it goes. If the upgrade is successful, then I'll release 1.4.8.

[stephdl]

a big thank you @jsuto, I am going to test it

[stephdl]

at the first tests it seems OK, thank a lot, can you consider also to move the tempates you are using outside of /etc/piler that is a recommended mounting volume. I mean all *.dist files

since it is a mounted volume, we keep the previous version and when you change for example the version of php8.1 to 8.3 in piler-nginx.conf.dist we continue to use the version 81, the container upgrade does not change the file piler-nginx.conf.dist

These templates files should not be in a mounted volume

I continue my tests

[stephdl]

ok now the upgrade is not more affected by the ownership issue, however all the previous searches that were available in the auditor view are removed. we have a no search view. If I send new emails to piler they are indexed correctly and I can see them

Is that an expected behavior @jsuto after the upgrade or I missed and I need to fix something

[jsuto]

Can you please elaborate the "we have no search view" issue? Losing the index data after the upgrade is not expected.
However, in 1.4.7 there was a change, and manticore has been removed from the image, instead the docker/docker-compose.yaml file has a dedicated manticore service. So the problem most likely is that you have the manticore index data in piler's volume, however, the new manticore service is not aware of it. That's why you can see the new data after the upgrade, but not before the upgrade. The trivial fix would be to move the manticore volume from the piler service to the (new) manticore service. Again there may be ownership issues that must be fixed.

[stephdl]

good idea, it is exactly what is occurring I think. Please Where do you think the manticore index is located ?????

many thanks in advance

[stephdl]

in the piler container we have this ID

manticore:x:104:106::/home/manticore:/bin/false

in the manticore container we have this ID

manticore:x:999:999::/home/manticore:/bin/sh

So yes definitely we have some conflicts, this explain why I need to use U --volume piler_manticore:/var/lib/manticore:U,Z \ in the new version but it did not fix my issue

[stephdl]

noob question @jsuto

this is what I found in the old container 1.4.4, I think I use RT=0

root@piler:/# cat /var/piler/manticore/             
binlog.001         dailydelta1.spi    delta1.spe         delta1.spt         main1.spl          main2.spi          main3.sph          main4.spd          main4.spp          note1.spidx        tag1.sph
binlog.lock        dailydelta1.spidx  delta1.sph         main1.spa          main1.spm          main2.spidx        main3.sphi         main4.spe          manticore.log      note1.spl          tag1.sphi
binlog.meta        dailydelta1.spl    delta1.sphi        main1.spd          main1.spp          main2.spl          main3.spi          main4.sph          note1.spa          note1.spm          tag1.spi
dailydelta1.spa    dailydelta1.spm    delta1.spi         main1.spe          main2.spa          main2.spm          main3.spidx        main4.sphi         note1.spd          note1.spp          tag1.spidx
dailydelta1.spd    dailydelta1.spp    delta1.spidx       main1.sph          main2.spd          main2.spp          main3.spl          main4.spi          note1.spe          query.log          tag1.spl
dailydelta1.spe    dailydelta1.spt    delta1.spl         main1.sphi         main2.spe          main3.spa          main3.spm          main4.spidx        note1.sph          tag1.spa           tag1.spm
dailydelta1.sph    delta1.spa         delta1.spm         main1.spi          main2.sph          main3.spd          main3.spp          main4.spl          note1.sphi         tag1.spd           tag1.spp
dailydelta1.sphi   delta1.spd         delta1.spp         main1.spidx        main2.sphi         main3.spe          main4.spa          main4.spm          note1.spi          tag1.spe   

This is what I find in the version 1.4.7b with RT=1

manticore@piler:/var/lib/manticore$ ls 
audit1.lock  audit1.ram  binlog.lock  manticore.log  note1.lock  note1.ram    piler1.meta  query.log  tag1.meta
audit1.meta  binlog.001  binlog.meta  manticore.pid  note1.meta  piler1.lock  piler1.ram   tag1.lock  tag1.ram

Do you think it is compatible, since I do not use the same RT options ?????

[stephdl]

Do you think it is compatible, since I do not use the same RT options ?????

I would answer myself, I would state no

[stephdl]

after the upgrade from 1.4.4 to 1.4.7b I find well the files to /var/lib/manticore with the good ownership

[piler1@R1-pve state]$ podman exec -ti manticore-app bash
manticore@piler:/var/lib/manticore$ ls -n 
total 300
-rw-------. 1 999 999    0 Jun 17 15:45 audit1.lock
-rw-------. 1 999 999  807 Jun 17 15:45 audit1.meta
-rw-------. 1 999 999   36 Jun 17 15:45 audit1.ram
-rw-------. 1 999 999    8 Jun 17 15:35 binlog.001
-rw-------. 1 999 999    8 Jun 17 15:45 binlog.002
-rw-------. 1 999 999    0 Jun 17 15:45 binlog.lock
-rw-------. 1 999 999   12 Jun 17 15:45 binlog.meta
-rw-r--r--. 1 999 999  140 Jun 17 15:35 dailydelta1.spa
-rw-r--r--. 1 999 999  306 Jun 17 15:35 dailydelta1.spd
-rw-r--r--. 1 999 999    1 Jun 17 15:35 dailydelta1.spe
-rw-r--r--. 1 999 999 1446 Jun 17 15:35 dailydelta1.sph
-rw-r--r--. 1 999 999  281 Jun 17 15:35 dailydelta1.sphi
-rw-r--r--. 1 999 999  282 Jun 17 15:35 dailydelta1.spi
-rw-r--r--. 1 999 999  480 Jun 17 15:35 dailydelta1.spidx
-rw-------. 1 999 999    0 Jun 17 15:35 dailydelta1.spl
-rw-r--r--. 1 999 999    4 Jun 17 15:35 dailydelta1.spm
-rw-r--r--. 1 999 999  485 Jun 17 15:35 dailydelta1.spp
-rw-r--r--. 1 999 999   46 Jun 17 15:35 dailydelta1.spt
-rw-r--r--. 1 999 999    0 Jun 17 15:35 delta1.spa
-rw-r--r--. 1 999 999    1 Jun 17 15:35 delta1.spd
-rw-r--r--. 1 999 999    1 Jun 17 15:35 delta1.spe
-rw-r--r--. 1 999 999 1329 Jun 17 15:35 delta1.sph
-rw-r--r--. 1 999 999  177 Jun 17 15:35 delta1.sphi
-rw-r--r--. 1 999 999    1 Jun 17 15:35 delta1.spi
-rw-r--r--. 1 999 999  141 Jun 17 15:35 delta1.spidx
-rw-------. 1 999 999    0 Jun 17 15:35 delta1.spl
-rw-r--r--. 1 999 999    0 Jun 17 15:35 delta1.spm
-rw-r--r--. 1 999 999    1 Jun 17 15:35 delta1.spp
-rw-r--r--. 1 999 999    0 Jun 17 14:34 main1.spa
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main1.spd
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main1.spe
-rw-r--r--. 1 999 999 1329 Jun 17 14:34 main1.sph
-rw-r--r--. 1 999 999  177 Jun 17 14:34 main1.sphi
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main1.spi
-rw-r--r--. 1 999 999  141 Jun 17 14:34 main1.spidx
-rw-------. 1 999 999    0 Jun 17 14:34 main1.spl
-rw-r--r--. 1 999 999    0 Jun 17 14:34 main1.spm
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main1.spp
-rw-r--r--. 1 999 999    0 Jun 17 14:34 main2.spa
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main2.spd
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main2.spe
-rw-r--r--. 1 999 999 1329 Jun 17 14:34 main2.sph
-rw-r--r--. 1 999 999  177 Jun 17 14:34 main2.sphi
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main2.spi
-rw-r--r--. 1 999 999  141 Jun 17 14:34 main2.spidx
-rw-------. 1 999 999    0 Jun 17 14:34 main2.spl
-rw-r--r--. 1 999 999    0 Jun 17 14:34 main2.spm
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main2.spp
-rw-r--r--. 1 999 999    0 Jun 17 14:34 main3.spa
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main3.spd
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main3.spe
-rw-r--r--. 1 999 999 1329 Jun 17 14:34 main3.sph
-rw-r--r--. 1 999 999  177 Jun 17 14:34 main3.sphi
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main3.spi
-rw-r--r--. 1 999 999  141 Jun 17 14:34 main3.spidx
-rw-------. 1 999 999    0 Jun 17 14:34 main3.spl
-rw-r--r--. 1 999 999    0 Jun 17 14:34 main3.spm
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main3.spp
-rw-r--r--. 1 999 999    0 Jun 17 14:34 main4.spa
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main4.spd
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main4.spe
-rw-r--r--. 1 999 999 1329 Jun 17 14:34 main4.sph
-rw-r--r--. 1 999 999  177 Jun 17 14:34 main4.sphi
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main4.spi
-rw-r--r--. 1 999 999  141 Jun 17 14:34 main4.spidx
-rw-------. 1 999 999    0 Jun 17 14:34 main4.spl
-rw-r--r--. 1 999 999    0 Jun 17 14:34 main4.spm
-rw-r--r--. 1 999 999    1 Jun 17 14:34 main4.spp
-rw-------. 1 999 999 8482 Jun 17 15:45 manticore.log
-rw-------. 1 999 999    2 Jun 17 15:45 manticore.pid
-rw-------. 1 999 999    0 Jun 17 15:45 note1.lock
-rw-------. 1 999 999  680 Jun 17 15:45 note1.meta
-rw-------. 1 999 999   20 Jun 17 15:45 note1.ram
-rw-r--r--. 1 999 999    0 Jun 17 15:30 note1.spa
-rw-r--r--. 1 999 999    1 Jun 17 15:30 note1.spd
-rw-r--r--. 1 999 999    1 Jun 17 15:30 note1.spe
-rw-r--r--. 1 999 999 1068 Jun 17 15:30 note1.sph
-rw-r--r--. 1 999 999  128 Jun 17 15:30 note1.sphi
-rw-r--r--. 1 999 999    1 Jun 17 15:30 note1.spi
-rw-r--r--. 1 999 999  114 Jun 17 15:30 note1.spidx
-rw-------. 1 999 999    0 Jun 17 15:30 note1.spl
-rw-r--r--. 1 999 999    0 Jun 17 15:30 note1.spm
-rw-r--r--. 1 999 999    1 Jun 17 15:30 note1.spp
-rw-------. 1 999 999    0 Jun 17 15:45 piler1.lock
-rw-------. 1 999 999 1037 Jun 17 15:45 piler1.meta
-rw-------. 1 999 999   68 Jun 17 15:45 piler1.ram
-rw-------. 1 999 999  464 Jun 17 15:25 query.log
-rw-------. 1 999 999    0 Jun 17 15:45 tag1.lock
-rw-------. 1 999 999  679 Jun 17 15:45 tag1.meta
-rw-------. 1 999 999   20 Jun 17 15:45 tag1.ram
-rw-r--r--. 1 999 999    0 Jun 17 15:30 tag1.spa
-rw-r--r--. 1 999 999    1 Jun 17 15:30 tag1.spd
-rw-r--r--. 1 999 999    1 Jun 17 15:30 tag1.spe
-rw-r--r--. 1 999 999 1067 Jun 17 15:30 tag1.sph
-rw-r--r--. 1 999 999  128 Jun 17 15:30 tag1.sphi
-rw-r--r--. 1 999 999    1 Jun 17 15:30 tag1.spi
-rw-r--r--. 1 999 999  114 Jun 17 15:30 tag1.spidx
-rw-------. 1 999 999    0 Jun 17 15:30 tag1.spl
-rw-r--r--. 1 999 999    0 Jun 17 15:30 tag1.spm
-rw-r--r--. 1 999 999    1 Jun 17 15:30 tag1.spp
manticore@piler:/var/lib/manticore$ id
uid=999(manticore) gid=999(manticore) groups=999(manticore)

[stephdl]

I use the default configuration

manticore@piler:/var/lib/manticore$ cat /etc/manticoresearch/manticore.conf
    index piler1
    {
        type = rt
        path = /var/lib/manticore/piler1
        rt_mem_limit = 512M
        stored_fields =
        min_word_len = 1
        min_prefix_len = 5
        rt_field = sender
        rt_field = rcpt
        rt_field = senderdomain
        rt_field = rcptdomain
        rt_field = subject
        rt_field = body
        rt_field = attachment_types
        rt_attr_bigint = arrived
        rt_attr_bigint = sent
        rt_attr_uint = size
        rt_attr_uint = direction
        rt_attr_uint = folder
        rt_attr_uint = attachments
    }

    index tag1
    {
        type = rt
        path = /var/lib/manticore/tag1
        rt_mem_limit = 16M
        stored_fields = tag
        min_word_len = 2
        min_prefix_len = 5
        rt_field = tag
        rt_attr_bigint = mid
        rt_attr_uint = uid
    }

    index note1
    {
        type = rt
        path = /var/lib/manticore/note1
        rt_mem_limit = 16M
        stored_fields = note
        min_word_len = 2
        min_prefix_len = 5
        rt_field = note
        rt_attr_bigint = mid
        rt_attr_uint = uid
    }

    index audit1
    {
        type = rt
        path = /var/lib/manticore/audit1
        rt_mem_limit = 16M
        stored_fields = *
        min_word_len = 2
        min_prefix_len = 5
        rt_field = email
        rt_field = ipaddr
        rt_field = description
        rt_attr_bigint = ts
        rt_attr_bigint = meta_id
        rt_attr_uint = action
    }

    searchd
    {
        listen                  = 0.0.0.0:9312
        listen                  = 0.0.0.0:9306:mysql
        listen                  = 0.0.0.0:9307:mysql_readonly
        log                     = /var/lib/manticore/manticore.log
        binlog_max_log_size     = 256M
        binlog_path             = /var/lib/manticore
        binlog_flush            = 2
        query_log               = /var/lib/manticore/query.log
        network_timeout         = 5
        pid_file                = /var/lib/manticore/manticore.pid
        seamless_rotate         = 1
        preopen_tables          = 1
        unlink_old              = 1
        thread_stack            = 512k
        buddy_path              =
        rt_flush_period         = 300
    }

[stephdl]

for the record, I fixed my issue by starting again to index the emails to piler after the change of the manticore to a standalone container

podman exec -w /var/piler/imap piler-app reindex -a -p

NethServer/ns8-piler#37