e-Mail Content empty after upgrade from piler 1.3.11 to 1.4.3
Hi Janos,
I upgraded our Ubuntu from 20 to 22 via do-release-upgrade. I removed piler (not the config) and installed the deb package for jammy (1.4.3).
I installed nginx php8.1-fpm php-mysql, adjusted the config.
When i log in as auditor@local search results are presented…. so far so good.
But when i want to see the content of an e-Mail it is empty, see screenshot.
The only error i can make out is acutally just the following warning from /var/log/nginx/error.log:
2023/05/23 10:43:04 [error] 1072#1072: *5 FastCGI sent in stderr: "PHP message: PHP Warning: Uninitialized string offset 0 in /var/piler/www/system/helper/mime.php on line 239PHP message: PHP Warning: Uninitialized string offset 0 in /var/piler/www/system/helper/mime.php on line 239PHP message: PHP Warning: Uninitialized string offset 0 in /var/piler/www/system/helper/mime.php on line 239PHP message: PHP Warning: Uninitialized string offset 0 in /var/piler/www/system/helper/mime.php on line 239PHP message: PHP Warning: Uninitialized string offset 0 in /var/piler/www/system/helper/mime.php on line 239PHP message: PHP Warning: Uninitialized string offset 0 in /var/piler/www/system/helper/mime.php on line 239" while reading response header from upstream, client: 10.0.3.23, server: pilertest.mydomain.com, request: "POST /message.php HTTP/2.0", upstream: "fastcgi://unix:/run/php/php8.1-fpm.sock:", host: "pilertest.mydomain.com", referrer: "https://pilertest.mydomain.com/search.php"
What can I do to fix this?
Comments (4)
-
repo owner -
reporter I think i solved, at least it works in my test environment (clone) now. It was a simple misconfiguration.
In the config-site.php there we were pointing to binaries which did not exist in that place any more after the upgrade…
had to remove the “local”:
$config['DECRYPT_BINARY'] = '/usr/local/bin/pilerget'; $config['DECRYPT_ATTACHMENT_BINARY'] = '/usr/local/bin/pileraget'; $config['PILER_BINARY'] = "/usr/local/sbin/piler";
-
reporter - marked as trivial
-
repo owner - changed status to closed
OK, then case is closed.
- Log in to comment
Well, check the mail.log as well. There must be something wrong or some clue in it.