[gentoo-user] HEADS UP - postfix-2.9.0 is broken

[gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Helmut Jarausch]

Hi,

beware of installing postfix-2.9.0
When started it tries to access /usr/lib/postfix but files have been 
installed into /usr/libexec/postfix

And after re-emerging postfix-2.8.8 I couldn't do 
/etc/init.d/postfix restart

since openrc was thinking it's still running.
Since it was urgent I rebooted my system.

Does anybody where openrc stores the info that a daemon is running?

Thanks,
Helmut.

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Hinnerk van Bruinehsen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06.02.2012 12:06, Helmut Jarausch wrote:
> Hi,
> 
> beware of installing postfix-2.9.0 When started it tries to access
> /usr/lib/postfix but files have been installed into
> /usr/libexec/postfix
> 
> And after re-emerging postfix-2.8.8 I couldn't do 
> /etc/init.d/postfix restart
> 
> since openrc was thinking it's still running. Since it was urgent I
> rebooted my system.
> 
> Does anybody where openrc stores the info that a daemon is
> running?
> 
> Thanks, Helmut.
> 

Hi,

as far, as I know it is searching for a pid-file. Many
start-up-scripts also have a "zap" option

If you run /etc/init.d/<startup-script> zap it resets the status to
stopped. I don't know, if postfix has that option though.

So long..
Hinnerk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPL7g8AAoJEJwwOFaNFkYcgPIH/1MVjvN6ra8smBiGFQHZbTvI
lCIVSYt6/Vkogjd93K03y7eKPobuEV+IaNWnNmB2pSHgAzg9M1yHEytqCWLo+Ska
8ixuPHea8NMl3gJYxsFAvcAnTZpH2xFlIw5IvY5XLHZ8pOrZ2oWdQsrFZu9DvYae
I8BNoJsgqiobd/K1HqG+pFs1BKeyh8+bXZKx34/SbatEcKArVvGsEYukb8ebZcxx
ZcB+vld/1bWCo34XehzA8SVsoC0cKMi93Pj+YLcW9W2U5AVSRnPx/pcG1LY4fpyA
c44g4iMS7t3dcYo5isMWvj1LILq90UrhLYNEvsDXzETdz1z72qAOaU56rA7dBio=
=j/Pl
-----END PGP SIGNATURE-----

[gentoo-user] Re: HEADS UP - postfix-2.9.0 is broken

[Holger Hoffstaette]

On Mon, 06 Feb 2012 12:23:40 +0100, Hinnerk van Bruinehsen wrote:

> If you run /etc/init.d/<startup-script> zap it resets the status to
> stopped. I don't know, if postfix has that option though.

Doesn't work in this case. Simply killing the postfix daemons manually
however does. The problem can also simply be fixed by editing the
daemon_directory setting in /etc/postfix/main.cf.
The version number is still funny though.

-h

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Paul Hartman]

On Mon, Feb 6, 2012 at 5:06 AM, Helmut Jarausch
<jarausch@igpm.rwth-aachen.de> wrote:
> Hi,
>
> beware of installing postfix-2.9.0
> When started it tries to access /usr/lib/postfix but files have been
> installed into /usr/libexec/postfix

Maybe a side-effect of bug 401911
https://bugs.gentoo.org/show_bug.cgi?id=401911

BTW postfix 2.9.0 also fails to emerge if USE="vda" because it tried
to apply the patch for 2.8.5. (patch for 2.9.0 has not yet been
released)

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Stefan G. Weichinger]

Am 06.02.2012 16:42, schrieb Paul Hartman:
> On Mon, Feb 6, 2012 at 5:06 AM, Helmut Jarausch
> <jarausch@igpm.rwth-aachen.de> wrote:
>> Hi,
>>
>> beware of installing postfix-2.9.0
>> When started it tries to access /usr/lib/postfix but files have been
>> installed into /usr/libexec/postfix
> 
> Maybe a side-effect of bug 401911
> https://bugs.gentoo.org/show_bug.cgi?id=401911
> 
> BTW postfix 2.9.0 also fails to emerge if USE="vda" because it tried
> to apply the patch for 2.8.5. (patch for 2.9.0 has not yet been
> released)


I also rolled back to 2.8.8 for now ... 2.9.0 was working already, -r1
messed things up and after that even 2.9.0 didn't work again!

Cleaning up for now and masked >=2.9.0 for a start.

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Volker Armin Hemmann]

Am Montag, 6. Februar 2012, 12:06:41 schrieb Helmut Jarausch:
> Hi,
> 
> beware of installing postfix-2.9.0
> When started it tries to access /usr/lib/postfix but files have been
> installed into /usr/libexec/postfix


postfix 2.9.0 works fine for me.

But I also run cfg-update after the update and made sure to merge the ._ file 
correctly.

-- 
#163933

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Stefan G. Weichinger]

Am 06.02.2012 18:08, schrieb Volker Armin Hemmann:
> Am Montag, 6. Februar 2012, 12:06:41 schrieb Helmut Jarausch:
>> Hi,
>>
>> beware of installing postfix-2.9.0
>> When started it tries to access /usr/lib/postfix but files have been
>> installed into /usr/libexec/postfix
> 
> 
> postfix 2.9.0 works fine for me.
> 
> But I also run cfg-update after the update and made sure to merge the ._ file 
> correctly.

Yep, same here for postfix 2.9.0-r1 now.

Had to kill the master-process manually ... this sorted things out in
the end ...

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Michael Mol]

On Mon, Feb 6, 2012 at 12:29 PM, Stefan G. Weichinger <lists@xunil.at> wrote:
> Am 06.02.2012 18:08, schrieb Volker Armin Hemmann:
>> Am Montag, 6. Februar 2012, 12:06:41 schrieb Helmut Jarausch:
>>> Hi,
>>>
>>> beware of installing postfix-2.9.0
>>> When started it tries to access /usr/lib/postfix but files have been
>>> installed into /usr/libexec/postfix
>>
>>
>> postfix 2.9.0 works fine for me.
>>
>> But I also run cfg-update after the update and made sure to merge the ._ file
>> correctly.
>
> Yep, same here for postfix 2.9.0-r1 now.
>
> Had to kill the master-process manually ... this sorted things out in
> the end ...

So, to avoid this, when upgrading from < 2.9.0-r1 to 2.9.0-r1, one
should stop postfix, do the upgrade, and then start postfix again?
that's how I read it.

Alternately, copy the old init script prior to upgrade, use that
script to bring postfix down, and use the new script to bring postfix
up?


-- 
:wq

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Andrea Conti]

> BTW postfix 2.9.0 also fails to emerge if USE="vda" because it tried
> to apply the patch for 2.8.5. (patch for 2.9.0 has not yet been
> released)

And it also fails to start if have maps in hash format and emerge with
USE=-berkdb.

Luckily the error messages are informative enough... but let's say that
a word of caution in the emerge message would have been welcomed.

andrea

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Volker Armin Hemmann]

Am Montag, 6. Februar 2012, 12:47:45 schrieb Michael Mol:
> On Mon, Feb 6, 2012 at 12:29 PM, Stefan G. Weichinger <lists@xunil.at> 
wrote:
> > Am 06.02.2012 18:08, schrieb Volker Armin Hemmann:
> >> Am Montag, 6. Februar 2012, 12:06:41 schrieb Helmut Jarausch:
> >>> Hi,
> >>> 
> >>> beware of installing postfix-2.9.0
> >>> When started it tries to access /usr/lib/postfix but files have been
> >>> installed into /usr/libexec/postfix
> >> 
> >> postfix 2.9.0 works fine for me.
> >> 
> >> But I also run cfg-update after the update and made sure to merge the ._
> >> file correctly.
> > 
> > Yep, same here for postfix 2.9.0-r1 now.
> > 
> > Had to kill the master-process manually ... this sorted things out in
> > the end ...
> 
> So, to avoid this, when upgrading from < 2.9.0-r1 to 2.9.0-r1, one
> should stop postfix, do the upgrade, and then start postfix again?
> that's how I read it.
> 
> Alternately, copy the old init script prior to upgrade, use that
> script to bring postfix down, and use the new script to bring postfix
> up?

I just upgraded and did /etc/init.d/postfix restart and it worked.

-- 
#163933

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Michael Mol]

On Mon, Feb 6, 2012 at 1:00 PM, Volker Armin Hemmann
<volkerarmin@googlemail.com> wrote:
> Am Montag, 6. Februar 2012, 12:47:45 schrieb Michael Mol:
>> On Mon, Feb 6, 2012 at 12:29 PM, Stefan G. Weichinger <lists@xunil.at>
> wrote:
>> > Am 06.02.2012 18:08, schrieb Volker Armin Hemmann:
>> >> Am Montag, 6. Februar 2012, 12:06:41 schrieb Helmut Jarausch:
>> >>> Hi,
>> >>>
>> >>> beware of installing postfix-2.9.0
>> >>> When started it tries to access /usr/lib/postfix but files have been
>> >>> installed into /usr/libexec/postfix
>> >>
>> >> postfix 2.9.0 works fine for me.
>> >>
>> >> But I also run cfg-update after the update and made sure to merge the ._
>> >> file correctly.
>> >
>> > Yep, same here for postfix 2.9.0-r1 now.
>> >
>> > Had to kill the master-process manually ... this sorted things out in
>> > the end ...
>>
>> So, to avoid this, when upgrading from < 2.9.0-r1 to 2.9.0-r1, one
>> should stop postfix, do the upgrade, and then start postfix again?
>> that's how I read it.
>>
>> Alternately, copy the old init script prior to upgrade, use that
>> script to bring postfix down, and use the new script to bring postfix
>> up?
>
> I just upgraded and did /etc/init.d/postfix restart and it worked.

You reported success with 2.9.0. People are reporting difficulties
with 2.9.0-r1. Two different versions, or so I assumed.

-- 
:wq

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Paul Hartman]

On Mon, Feb 6, 2012 at 12:00 PM, Volker Armin Hemmann
<volkerarmin@googlemail.com> wrote:
> Am Montag, 6. Februar 2012, 12:47:45 schrieb Michael Mol:
>> On Mon, Feb 6, 2012 at 12:29 PM, Stefan G. Weichinger <lists@xunil.at>
> wrote:
>> > Am 06.02.2012 18:08, schrieb Volker Armin Hemmann:
>> >> Am Montag, 6. Februar 2012, 12:06:41 schrieb Helmut Jarausch:
>> >>> Hi,
>> >>>
>> >>> beware of installing postfix-2.9.0
>> >>> When started it tries to access /usr/lib/postfix but files have been
>> >>> installed into /usr/libexec/postfix
>> >>
>> >> postfix 2.9.0 works fine for me.
>> >>
>> >> But I also run cfg-update after the update and made sure to merge the ._
>> >> file correctly.
>> >
>> > Yep, same here for postfix 2.9.0-r1 now.
>> >
>> > Had to kill the master-process manually ... this sorted things out in
>> > the end ...
>>
>> So, to avoid this, when upgrading from < 2.9.0-r1 to 2.9.0-r1, one
>> should stop postfix, do the upgrade, and then start postfix again?
>> that's how I read it.
>>
>> Alternately, copy the old init script prior to upgrade, use that
>> script to bring postfix down, and use the new script to bring postfix
>> up?
>
> I just upgraded and did /etc/init.d/postfix restart and it worked.

The installation path was changed without an ebuild version number
bump, so if you installed before that change, it would have had the
same path as the old version.

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Volker Armin Hemmann]

Am Montag, 6. Februar 2012, 12:05:38 schrieb Paul Hartman:
> On Mon, Feb 6, 2012 at 12:00 PM, Volker Armin Hemmann
> 
> <volkerarmin@googlemail.com> wrote:
> > Am Montag, 6. Februar 2012, 12:47:45 schrieb Michael Mol:
> >> On Mon, Feb 6, 2012 at 12:29 PM, Stefan G. Weichinger <lists@xunil.at>
> > 
> > wrote:
> >> > Am 06.02.2012 18:08, schrieb Volker Armin Hemmann:
> >> >> Am Montag, 6. Februar 2012, 12:06:41 schrieb Helmut Jarausch:
> >> >>> Hi,
> >> >>> 
> >> >>> beware of installing postfix-2.9.0
> >> >>> When started it tries to access /usr/lib/postfix but files have been
> >> >>> installed into /usr/libexec/postfix
> >> >> 
> >> >> postfix 2.9.0 works fine for me.
> >> >> 
> >> >> But I also run cfg-update after the update and made sure to merge the
> >> >> ._
> >> >> file correctly.
> >> > 
> >> > Yep, same here for postfix 2.9.0-r1 now.
> >> > 
> >> > Had to kill the master-process manually ... this sorted things out in
> >> > the end ...
> >> 
> >> So, to avoid this, when upgrading from < 2.9.0-r1 to 2.9.0-r1, one
> >> should stop postfix, do the upgrade, and then start postfix again?
> >> that's how I read it.
> >> 
> >> Alternately, copy the old init script prior to upgrade, use that
> >> script to bring postfix down, and use the new script to bring postfix
> >> up?
> > 
> > I just upgraded and did /etc/init.d/postfix restart and it worked.
> 
> The installation path was changed without an ebuild version number
> bump, so if you installed before that change, it would have had the
> same path as the old version.


there was something about libexec when I ran cfg-update:

/etc/postfix/main.cf:daemon_directory = /usr/libexec/postfix

-- 
#163933

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Pandu Poluan]

On Tue, Feb 7, 2012 at 01:05, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Mon, Feb 6, 2012 at 12:00 PM, Volker Armin Hemmann
> <volkerarmin@googlemail.com> wrote:
>> Am Montag, 6. Februar 2012, 12:47:45 schrieb Michael Mol:
>>> On Mon, Feb 6, 2012 at 12:29 PM, Stefan G. Weichinger <lists@xunil.at>
>> wrote:
>>> > Am 06.02.2012 18:08, schrieb Volker Armin Hemmann:
>>> >> Am Montag, 6. Februar 2012, 12:06:41 schrieb Helmut Jarausch:
>>> >>> Hi,
>>> >>>
>>> >>> beware of installing postfix-2.9.0
>>> >>> When started it tries to access /usr/lib/postfix but files have been
>>> >>> installed into /usr/libexec/postfix
>>> >>
>>> >> postfix 2.9.0 works fine for me.
>>> >>
>>> >> But I also run cfg-update after the update and made sure to merge the ._
>>> >> file correctly.
>>> >
>>> > Yep, same here for postfix 2.9.0-r1 now.
>>> >
>>> > Had to kill the master-process manually ... this sorted things out in
>>> > the end ...
>>>
>>> So, to avoid this, when upgrading from < 2.9.0-r1 to 2.9.0-r1, one
>>> should stop postfix, do the upgrade, and then start postfix again?
>>> that's how I read it.
>>>
>>> Alternately, copy the old init script prior to upgrade, use that
>>> script to bring postfix down, and use the new script to bring postfix
>>> up?
>>
>> I just upgraded and did /etc/init.d/postfix restart and it worked.
>
> The installation path was changed without an ebuild version number
> bump, so if you installed before that change, it would have had the
> same path as the old version.
>

Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ?

Rgds,
-- 
FdS Pandu E Poluan
~ IT Optimizer ~

 • LOPSA Member #15248
 • Blog : http://pepoluan.tumblr.com
 • Linked-In : http://id.linkedin.com/in/pepoluan

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Eray Aslan]

On Tue, Feb 07, 2012 at 01:58:33PM +0700, Pandu Poluan wrote:
> Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ?

Yes, it should be OK as long as you run etc-update/dispatch-conf/similar
after the upgrade.  Postfix daemons now live under /usr/libexec/postfix
(not under /usr/lib{,64)/postfix).  Adjust your main.cf accordingly.
I'll add a warning to the ebuild.

-- 
Eray Aslan <eras@gentoo.org>

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Eray Aslan]

On Mon, Feb 06, 2012 at 06:51:51PM +0100, Andrea Conti wrote:
> Luckily the error messages are informative enough... but let's say that
> a word of caution in the emerge message would have been welcomed.

There is a warning printed if you emerged without the berkdb flag when
you upgraded from <postfix-2.9.  Please let me know if it did not work
for you.

-- 
Eray Aslan <eras@gentoo.org>

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 569 bytes --]

On Feb 7, 2012 2:39 PM, "Eray Aslan" <eras@gentoo.org> wrote:
>
> On Tue, Feb 07, 2012 at 01:58:33PM +0700, Pandu Poluan wrote:
> > Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ?
>
> Yes, it should be OK as long as you run etc-update/dispatch-conf/similar
> after the upgrade.  Postfix daemons now live under /usr/libexec/postfix
> (not under /usr/lib{,64)/postfix).  Adjust your main.cf accordingly.
> I'll add a warning to the ebuild.
>

Ah, thanks for the explanation!

I'll be certain to pay undivided attention to postfix ebuild warnings.

Rgds,

[-- Attachment #2: Type: text/html, Size: 781 bytes --]

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Tanstaafl]

On 2012-02-07 2:36 AM, Eray Aslan <eras@gentoo.org> wrote:
> On Tue, Feb 07, 2012 at 01:58:33PM +0700, Pandu Poluan wrote:
>> Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ?

> Yes, it should be OK as long as you run
> etc-update/dispatch-conf/similar after the upgrade.

I was concerned about this at first, but if this was indeed the cause of 
the OP and others' problem (as opposed to an actual bug in the ebuild), 
then they did it to themselves, because what you said - running 
etc-update (or dispatch-conf) is *always* required for packages like 
postfix.

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Tanstaafl]

On 2012-02-07 2:36 AM, Eray Aslan <eras@gentoo.org> wrote:
> Postfix daemons now live under /usr/libexec/postfix
> (not under /usr/lib{,64)/postfix).

I'm curious - is there a good reason for this change?

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Alan McKinnon]

On Wed, 8 Feb 2012 00:11:26 +0700
Pandu Poluan <pandu@poluan.info> wrote:

> On Feb 7, 2012 2:39 PM, "Eray Aslan" <eras@gentoo.org> wrote:
> >
> > On Tue, Feb 07, 2012 at 01:58:33PM +0700, Pandu Poluan wrote:
> > > Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ?
> >
> > Yes, it should be OK as long as you run
> > etc-update/dispatch-conf/similar after the upgrade.  Postfix
> > daemons now live under /usr/libexec/postfix (not
> > under /usr/lib{,64)/postfix).  Adjust your main.cf accordingly.
> > I'll add a warning to the ebuild.
> >
> 
> Ah, thanks for the explanation!
> 
> I'll be certain to pay undivided attention to postfix ebuild warnings.
> 
> Rgds,

ALWAYS pay special attention to ALL ebuild warnings. Not just the ones
from postfix.

Those warnings are there for a reason - it's how devs let you know that
stuff has changed, that the change will make stuff break, and how to
fix or prevent it. They are not there for decoration or fluff.

You should set the ELOG options in make.conf to store these warnings in
some persistent place (log files, mail them, whatever) so you can go
through them at your leisure. 

My usual routine for doing a global update is

emerge -avuND world
conf-update
emerge -av @preserved-rebuild
revdep-rebuild -p -i (then without -p if something is found)
emerge -a --depclean
view portage logs and do what they say
often followed by doing one or more steps again to ensure all is clean

I haven't been adversely hit by an upgrade for over a year now. I put
it down to using the portage tools correctly in the way they were
designed to be used.

-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]

On Feb 8, 2012 2:38 AM, "Alan McKinnon" <alan.mckinnon@gmail.com> wrote:
>
> On Wed, 8 Feb 2012 00:11:26 +0700
> Pandu Poluan <pandu@poluan.info> wrote:
>
> > On Feb 7, 2012 2:39 PM, "Eray Aslan" <eras@gentoo.org> wrote:
> > >
> > > On Tue, Feb 07, 2012 at 01:58:33PM +0700, Pandu Poluan wrote:
> > > > Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ?
> > >
> > > Yes, it should be OK as long as you run
> > > etc-update/dispatch-conf/similar after the upgrade.  Postfix
> > > daemons now live under /usr/libexec/postfix (not
> > > under /usr/lib{,64)/postfix).  Adjust your main.cf accordingly.
> > > I'll add a warning to the ebuild.
> > >
> >
> > Ah, thanks for the explanation!
> >
> > I'll be certain to pay undivided attention to postfix ebuild warnings.
> >
> > Rgds,
>
> ALWAYS pay special attention to ALL ebuild warnings. Not just the ones
> from postfix.
>

Always do that, actually. But Eray's explanation about postfix's new 'home'
is especially important in the context of this thread and my situation (I'm
using postfix as production email server in my office).

> Those warnings are there for a reason - it's how devs let you know that
> stuff has changed, that the change will make stuff break, and how to
> fix or prevent it. They are not there for decoration or fluff.
>
> You should set the ELOG options in make.conf to store these warnings in
> some persistent place (log files, mail them, whatever) so you can go
> through them at your leisure.
>

I recommend also to install an elog parser/viewer. I personally use elogv,
an ncurses-based utility. There are GUI-based ones, but I'm running
text-mode exclusively.

> My usual routine for doing a global update is
>
> emerge -avuND world
> conf-update
> emerge -av @preserved-rebuild
> revdep-rebuild -p -i (then without -p if something is found)
> emerge -a --depclean
> view portage logs and do what they say
> often followed by doing one or more steps again to ensure all is clean
>

Shouldn't revdep-rebuild be ran *after* emerge --depclean?

Rgds,

[-- Attachment #2: Type: text/html, Size: 2756 bytes --]

Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken

[Alan McKinnon]

On Wed, 8 Feb 2012 09:05:20 +0700
Pandu Poluan <pandu@poluan.info> wrote:

> > My usual routine for doing a global update is
> >
> > emerge -avuND world
> > conf-update
> > emerge -av @preserved-rebuild
> > revdep-rebuild -p -i (then without -p if something is found)
> > emerge -a --depclean
> > view portage logs and do what they say
> > often followed by doing one or more steps again to ensure all is
> > clean
> >
> 
> Shouldn't revdep-rebuild be ran *after* emerge --depclean?
> 

Strictly speaking, yes I suppose it should

-- 
Alan McKinnnon
alan.mckinnon@gmail.com