Postfix Active: active (exited) - (code=exited, status=0/SUCCESS)

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Postfix Active: active (exited) - (code=exited, status=0/SUCCESS)

danjjde
Hi Friends,
on a VPS Debian Stretch, Postfix 3.1.9-0, Dovecot 2.2.27-3, rspamd
1.8.3-1, Clamav 0.100.2, postfix-mysql 3.1.9-0, dovecot-mysql 2.2.27-3

running "systemctl -l status postfix" obtain:


● postfix.service - Postfix Mail Transport Agent
    Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor
preset: enabled)
    Active: active (exited) since Thu 2019-03-21 22:04:46 CET; 18h ago
   Process: 4453 ExecReload=/bin/true (code=exited, status=0/SUCCESS)
   Process: 4644 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
  Main PID: 4644 (code=exited, status=0/SUCCESS)
     Tasks: 0 (limit: 4915)
    Memory: 0B
       CPU: 0
    CGroup: /system.slice/postfix.service


I've try to, reload (Postfix+Dovecot), restart (Postfix+Dovecot),
upgrade (Postfix) but the behavior stay the same.
The entire email server seems working fine, no error on
/var/log/mail.err and the various features seem to be operating.

Is this one referable to this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877992 ?

Could you suggest me how debug this issue, if problem is it?


Many thanks ;-)





Reply | Threaded
Open this post in threaded view
|

Re: Postfix Active: active (exited) - (code=exited, status=0/SUCCESS)

Scott Kitterman-4


On March 22, 2019 3:11:24 PM UTC, Davide Marchi <[hidden email]> wrote:

>Hi Friends,
>on a VPS Debian Stretch, Postfix 3.1.9-0, Dovecot 2.2.27-3, rspamd
>1.8.3-1, Clamav 0.100.2, postfix-mysql 3.1.9-0, dovecot-mysql 2.2.27-3
>
>running "systemctl -l status postfix" obtain:
>
>
>● postfix.service - Postfix Mail Transport Agent
>  Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor
>preset: enabled)
>    Active: active (exited) since Thu 2019-03-21 22:04:46 CET; 18h ago
>   Process: 4453 ExecReload=/bin/true (code=exited, status=0/SUCCESS)
>   Process: 4644 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
>  Main PID: 4644 (code=exited, status=0/SUCCESS)
>     Tasks: 0 (limit: 4915)
>    Memory: 0B
>       CPU: 0
>    CGroup: /system.slice/postfix.service
>
>
>I've try to, reload (Postfix+Dovecot), restart (Postfix+Dovecot),
>upgrade (Postfix) but the behavior stay the same.
>The entire email server seems working fine, no error on
>/var/log/mail.err and the various features seem to be operating.
>
>Is this one referable to this bug:
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877992 ?
>
>Could you suggest me how debug this issue, if problem is it?
>
>
>Many thanks ;-

First, this is a Debian specific question based on how we did systemd integration.  It's not a general issue.  For Debian specific questions, distro support resources are a better place to seek help.

Second, all is fine.  

The 'postfix' service starts each postfix instance postfix@[instance name] and then exits.  For the common case of a single instance, it is named '-'.  To get the status of a single running instance, try "systemctl -l status postfix@[instance name]".  For your single instance set up it would be:

systemctl -l status postfix@-

Nothing to troubleshoot.

Please review /usr/share/doc/postfix/README.Debian and if you have recommdations on how to better explain/document this, please file a bug in the Debian BTS and I'll see about updating the distro documentation.

Scott K
Reply | Threaded
Open this post in threaded view
|

Re: Postfix Active: active (exited) - (code=exited, status=0/SUCCESS)

B. Reino
In reply to this post by danjjde
On Fri, 22 Mar 2019, Davide Marchi wrote:

> Hi Friends,
> on a VPS Debian Stretch, Postfix 3.1.9-0, Dovecot 2.2.27-3, rspamd 1.8.3-1,
> Clamav 0.100.2, postfix-mysql 3.1.9-0, dovecot-mysql 2.2.27-3
>
> running "systemctl -l status postfix" obtain:
>
>
> ● postfix.service - Postfix Mail Transport Agent
>   Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor
> preset: enabled)
>   Active: active (exited) since Thu 2019-03-21 22:04:46 CET; 18h ago
>  Process: 4453 ExecReload=/bin/true (code=exited, status=0/SUCCESS)
>  Process: 4644 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
> Main PID: 4644 (code=exited, status=0/SUCCESS)
>    Tasks: 0 (limit: 4915)
>   Memory: 0B
>      CPU: 0
>   CGroup: /system.slice/postfix.service
>
>
> I've try to, reload (Postfix+Dovecot), restart (Postfix+Dovecot), upgrade
> (Postfix) but the behavior stay the same.
> The entire email server seems working fine, no error on /var/log/mail.err and
> the various features seem to be operating.
>
> Is this one referable to this bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877992 ?
>
> Could you suggest me how debug this issue, if problem is it?
It is not an issue.
Try systemctl status postfix@-

Postfix is configured as a multi-instance unit, or whatever systemd calls
it.

Nothing to worry about.
Reply | Threaded
Open this post in threaded view
|

Re: Postfix Active: active (exited) - (code=exited, status=0/SUCCESS)

Wietse Venema
In reply to this post by danjjde
Davide Marchi:
> Hi Friends,
> on a VPS Debian Stretch, Postfix 3.1.9-0, Dovecot 2.2.27-3, rspamd
> 1.8.3-1, Clamav 0.100.2, postfix-mysql 3.1.9-0, dovecot-mysql 2.2.27-3
>
> running "systemctl -l status postfix" obtain:
>

Perhaps surprisingly, Postfix logs why it terminates.

http://www.postfix.org/DEBUG_README.html#logging

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: Postfix Active: active (exited) - (code=exited, status=0/SUCCESS)

danjjde
In reply to this post by Scott Kitterman-4
Scott Kitterman ha scritto:
> First, this is a Debian specific question based on how we did systemd
> integration.  It's not a general issue.  For Debian specific questions,
> distro support resources are a better place to seek help. [..]

Yes, I had done it, then (two days later) I posted in ML

B. Reino ha scritto:

> On Fri, 22 Mar 2019, Davide Marchi wrote:
>
>> [..]
>>
>>
>> ● postfix.service - Postfix Mail Transport Agent
>>   Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor
>> preset: enabled)
>>   Active: active (exited) since Thu 2019-03-21 22:04:46 CET; 18h ago
>>  Process: 4453 ExecReload=/bin/true (code=exited, status=0/SUCCESS)
>>  Process: 4644 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
>> Main PID: 4644 (code=exited, status=0/SUCCESS)
>>    Tasks: 0 (limit: 4915)
>>   Memory: 0B
>>      CPU: 0
>>   CGroup: /system.slice/postfix.service
>>
>>
>> [..]
>
> It is not an issue.
> Try systemctl status postfix@-
>
> Postfix is configured as a multi-instance unit, or whatever systemd
> calls it.
>
> Nothing to worry about.

...feeew!!! :-D

This is my first "Postfix 3.1.x" and didn't know this feature, not
present on Postfix 2.1.x to what it seems:

 From Postfix 2.1.x ->


systemctl status postfix@-
[hidden email]
    Loaded: not-found (Reason: No such file or directory)
    Active: inactive (dead)


Many thanks Reino, you gave a few more years of life to my heart :-D

Wietse Venema ha scritto:
> Perhaps surprisingly, Postfix logs why it terminates.
>
> http://www.postfix.org/DEBUG_README.html#logging
>
> Wietse
>
Much interesting, I sign it among the important notes of Postfix, thanks
Wietse!


Thanks again to all!