We can probably get rid of the tempory debug output code, can't we?
-Patrick
On 22.02.2021 13:17, s...@acts.hu wrote:
Hello,
thank you for both of your feedbacks. As much as I dislike systemd,
it allows you to restart piler-smtp in case it crashes. But hopefully
it won't happen in the
Janos, Patrick,
thanks for this. I also run piler on Ubuntu 18.04 and ran into the same issue.
My 'solution' was to start piler-smtp automatically via monitoring if it goes
down :-(.
Janos, I wonder if you will provide updated .deb packages for dpkg-installs?
Thanks and regards,
Claudio
Thanks Janos,
I'd updated and replaced the piler-smtp binary on 2021-02-16, and while
I can see that my monitoring still shows SMTP timeouts on the piler port
sometimes between 02:30 and 02:40, no further outright crashes / SIGSEGV
occur, so archiving continues without any need to restart
On 2021-02-22 14:19, Wagner, Patrick wrote:
We can probably get rid of the tempory debug output code, can't we?
Yes. Either remove them for yourself or get the master branch,
and recompile, then overwrite the piler-smtp binary.
Janos
On 22.02.2021 13:17, s...@acts.hu wrote:
Hello,
Hello,
thank you for both of your feedbacks. As much as I dislike systemd,
it allows you to restart piler-smtp in case it crashes. But hopefully
it won't happen in the future after this fix.
Also I've merged it to the master branch, and I'll release a bugfix
version 1.3.11, and I'll make a
