I suspect that the issue here is that the config file was modified
(values set) during install, and then the file changed outside of
debconf later, and then installed again, resulting in postfix honoring
the debconf values it had been told to enforce.
There are several values that postfix expects
I'm not setting any values in debconf, I'm only installing the package
(non-interactive) and doing configuration in puppet also.
You are right that puppet will re-enforce our configuration, however, we are
not using the puppet agent, so resetting the value might take up to a few
weeks,
Thank you for your further investigations. I appreciate that this could
be a bug. But since I still can't see how we might reproduce your issue,
I don't think that we yet have clarity on the set of circumstances that
might cause your problem. Without this clarity, I don't think that we
can
Today I had to install postfix again, but manually (entering apt-get install on
commandline) and saw in the console output the following lines:
setting inet_interfaces: loopback-only
This reminded me of this issue and gave me a clue where the problem is.
I think the problem is not directly with
I think that's not a supported configuration. I'm not sure how you got
it installed that way to begin with.
** Changed in: postfix (Ubuntu)
Importance: High = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in
As you can read in the first posting, I simply installed it with puppet.
Doesn't seem like such a rare scenario to me. I think any company with a
substantial amount of servers should be using some form of configuration
management. I think any completely non-interactive installation method
will end
Re debconf, thats not really a factor. Not answering the questions just
uses defaults, but debconf and the maintainer scripts that use it do not
change their behavior. Indeed, I think this issue doesn't seem to have
much helpful information. I'm going to close it as Invalid.
** Changed in: puppet
Marking Incomplete, since others have tried failed to reproduce, and it
seems likely that this is a local configuration issue rather than a bug
in Postfix.
If you can provide exact steps to reproduce without using puppet, then
please do so and re-open.
** Changed in: puppet (Ubuntu)
Even though I have the suspicion it is caused by not doing debconf (as puppet
does not ask questions, but just installs with default values), I too can't
reproduce it on a test-VM with the exact same debconf values as one of our
servers.
I have no idea what puppet does to cause this behavior
** Changed in: puppet (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1027061
Title:
Postfix upgrade to 2.9.3-2~12.04.1 changes configuration
I installed postfix, set inet_interfaces to loopback_only, restarted
postfix, then reinstalled with dpkg -i /var/cache/apt/archives/postf*.
The inet_interfaces line did not get re-written.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Setting back to New. Somebody needs to try the suggested test case of
installing postfix, changing the config file, and then upgrading, to see
if the file is changed. Of course, the config file belongs to postfix,
so if force-confnew is in use, that would make sense too, so it would
be good to get
If this is any help, here is the installation log
(/var/log/apt/history.log) from the package upgrade that changed the
config file:
Start-Date: 2012-07-20 06:39:28
Commandline: apt-get -qq -y upgrade
Upgrade: postfix:amd64 (2.9.1-5, 2.9.3-2~12.04.1)
End-Date: 2012-07-20 06:39:31
This is not an
Oops missed a previous comment. I don't think this is a problem with
puppet though. Puppet ensures the state of that file, it won't change
values unless the manifest was changed by the user.
** Changed in: puppet (Ubuntu)
Status: New = Incomplete
--
You received this bug notification
I've never seen anything like this with postfix before. If someone can
give me a way to reproduce it when puppet is not involved, then I could
trouble shoot that, but I don't think this is a postfix issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1027061
Title:
Postfix upgrade to 2.9.3-2~12.04.1 changes configuration files
To manage
I can't replicate this with postfix and apt, so I suspect the puppet
involvement being where the issue is.
BTW, while I agree that configurations shouldn't be mucked with, there's
no security issue here as postfix is not an open relay by default. It
takes some work to get it to behave that way.
Thanks for having a look, Scott. I'm unsubscribing ubuntu-security and
marking this as a regular, non-security bug.
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in
It should be easy to reproduce this. Simply installing postfix on a
fresh server installation in the background (so without any use
interaction) and then chenging the configuration file should do it.
Puppet does nothing special with the package. Also, it uses aptitude to
install it, if that makes
19 matches
Mail list logo
