-
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal: bind 127.0.0.1 port 25: Address already in use #90
Comments
The problem probably is, that we are calling I'd suggest to do a hard restart (i.e. stop && start) on configuration changes per default, and additionally provide an Exec like, e.g. exec { 'reload postfix configuration':
command => $::postfix::params::reload_cmd,
refreshonly => true,
} which can then be triggered from, e.g. An even easier approch could be to do a hard |
I've run into the same problem on RHEL 6.6 with the following manifest include ::augeas
class { 'postfix':
satellite => true,
smtp_listen => '127.0.0.1',
relayhost => 'relayhost.example.com',
} I have to run puppet twice for this manifest to work. There are no errors in the puppet logs, but the reload fails and after the puppet run is completed, the service is in a 'stopped' state. Below are the postfix logs.
@rauchrob - Have you thought about creating a PR with one of your suggestions? Thanks, |
I have set up a couple of Ubuntu 14.04 machines with Postfix, simply by including this module without further parameters. The following Puppet run is succesful, but the postfix service is not running afterwards. There is an error message in
/var/log/mail.err
:After the second Puppet run, everything works as expected.
The text was updated successfully, but these errors were encountered: