Migrating 2.11 to 3.2

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Migrating 2.11 to 3.2

Nikolaos Milas
Hello,

We are moving to a new (virtual) server (from CentOS 5 with Postfix
2.11.6 to CentOS 7 with Postfix 3.2.2).

I have moved the original configuration to the new server and Postfix
won't start; I am getting:

# systemctl status postfix
  postfix.service - Postfix Mail Transport Agent
    Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled;
vendor preset: disabled)
    Active: failed (Result: exit-code) since Thu 2017-07-27 12:25:14
EEST; 12min ago
   Process: 21895 ExecStart=/usr/sbin/postfix start (code=exited,
status=1/FAILURE)
   Process: 21893 ExecStartPre=/usr/libexec/postfix/chroot-update
(code=exited, status=0/SUCCESS)
   Process: 21890 ExecStartPre=/usr/libexec/postfix/aliasesdb
(code=exited, status=0/SUCCESS)
  Main PID: 14815 (code=killed, signal=TERM)

Jul 27 12:25:12 vmail2.noa.gr postfix[21895]: /usr/sbin/postconf:
warning: /etc/postfix/main.cf: unused parameter:
127.0.0.1:10040_time_limit=3600
Jul 27 12:25:12 vmail2.noa.gr postfix[21895]: /usr/sbin/postconf:
warning: /etc/postfix/main.cf: unused parameter:
127.0.0.1:10040_time_limit=3600
Jul 27 12:25:12 vmail2.noa.gr postfix[21895]: /usr/sbin/postconf:
warning: /etc/postfix/main.cf: unused parameter:
127.0.0.1:10040_time_limit=3600
Jul 27 12:25:12 vmail2.noa.gr postfix[21895]:
/usr/libexec/postfix/post-install: Error: /etc/postfix/postfix-files is
not a file.
Jul 27 12:25:12 vmail2.noa.gr postfix/postfix-script[21913]: fatal:
unable to create missing queue directories
Jul 27 12:25:13 vmail2.noa.gr postfix/postfix-script[21914]: fatal:
Postfix integrity check failed!
Jul 27 12:25:14 vmail2.noa.gr systemd[1]: postfix.service: control
process exited, code=exited status=1
Jul 27 12:25:14 vmail2.noa.gr systemd[1]: Failed to start Postfix Mail
Transport Agent.
Jul 27 12:25:14 vmail2.noa.gr systemd[1]: Unit postfix.service entered
failed state.
Jul 27 12:25:14 vmail2.noa.gr systemd[1]: postfix.service failed.

I also tried:

# /usr/libexec/postfix/post-install create-missing
postconf: warning: /etc/postfix/main.cf: unused parameter:
127.0.0.1:10040_time_limit=3600
/usr/libexec/postfix/post-install: Error: /postfix-files is not a file.

Can you please let me know what may be the issue here?

I have checked the queue directory: /var/spool/postfix/ and I don't see
anything different between the two installations.

Here is my config details:

# postconf -n
alias_database = hash:/etc/postfix/aliases,
hash:/etc/postfix/aliases.d/virtual_aliases
alias_maps = hash:/etc/aliases
allowed_gein = check_client_access
cidr:/etc/postfix/gein_admin_ips.cidr,reject
allowed_iaasars = check_client_access
cidr:/etc/postfix/iaasars_admin_ips.cidr,reject
allowed_list1 = check_sasl_access
hash:/etc/postfix/allowed_groupmail_users,reject
allowed_list2 = permit_mynetworks,reject
allowed_meteo = check_client_access
cidr:/etc/postfix/meteo_admin_ips.cidr,reject
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
controlled_senders = check_sender_access hash:/etc/postfix/blocked_senders
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
default_process_limit = 25
delay_logging_resolution_limit = 3
deliver_lock_attempts = 40
dovecot_destination_recipient_limit = 1
gwcheck = reject_unverified_recipient, reject_unauth_destination
home_mailbox = Maildir/
html_directory = no
inet_interfaces = all
inet_protocols = ipv4, ipv6
local_header_rewrite_clients = static:all
mail_name = NOA Mail Srv XAPITI XPICTOY
mail_owner = postfix
mailbox_command = /usr/lib/dovecot/deliver
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
message_size_limit = 41943040
milter_default_action = accept
mydestination = $myhostname, localhost.$mydomain, localhost
mydomain = noa.gr
myhostname = vmail2.noa.gr
mynetworks = 195.251.204.0/24, 195.251.202.0/23, 194.177.194.0/23,
127.0.0.0/8, 10.201.0.0/16, [2001:648:2011::]/48, 83.212.5.24/29,
[2001:648:2ffc:1115::]/64, 62.217.124.0/29, [2001:648:2ffc:126::]/64
myorigin = $mydomain
newaliases_path = /usr/bin/newaliases.postfix
non_smtpd_milters = $smtpd_milters
parent_domain_matches_subdomains =
postfwdcheck = check_policy_service inet:127.0.0.1:10040
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES
recipient_canonical_maps = hash:/etc/postfix/domainrecipientmap
relay_domains = $mydestination
sample_directory = /usr/share/doc/postfix-2.3.3/samples
sender_canonical_maps = hash:/etc/postfix/domainsendermap
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
smtp_tls_security_level = may
smtpd_client_restrictions =
permit_mynetworks,permit_sasl_authenticated,reject
smtpd_delay_reject = yes
smtpd_end_of_data_restrictions = check_client_access
cidr:/etc/postfix/postfwdpolicy.cidr
smtpd_milters = inet:127.0.0.1:8891
smtpd_recipient_restrictions = check_recipient_access
hash:/etc/postfix/protected_destinations permit_sasl_authenticated
reject_unverified_recipient reject_unauth_destination
smtpd_restriction_classes =
controlled_senders,allowed_list1,allowed_list2,
allowed_iaasars,allowed_meteo,allowed_gein,postfwdcheck,gwcheck
smtpd_sasl_auth_enable = yes
smtpd_sasl_path = /var/spool/postfix/private/auth
smtpd_sasl_security_options = noanonymous
smtpd_sasl_type = dovecot
smtpd_tls_CAfile = /etc/pki/tls/certs/DigiCertCA.crt
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = /etc/pki/tls/certs/star_noa_gr-1243437.crt
smtpd_tls_exclude_ciphers = DES,3DES,MD5,aNULL,AES128,CAMELLIA128
smtpd_tls_key_file = /etc/pki/tls/private/star_noa_gr-1243437.key
smtpd_tls_loglevel = 1
smtpd_tls_mandatory_ciphers = high
smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3
smtpd_tls_received_header = yes
smtpd_tls_security_level = may
smtpd_tls_session_cache_timeout = 3600s
smtpd_use_tls = yes
tls_preempt_cipherlist = yes
tls_random_source = dev:/dev/urandom
transport_maps = hash:/etc/postfix/transport
unknown_local_recipient_reject_code = 550
unverified_recipient_reject_code = 550
virtual_alias_maps = hash:/etc/postfix/aliases,
hash:/etc/postfix/aliases.d/virtual_aliases,
proxy:ldap:/etc/postfix/ldap-alias-vacation.cf,
proxy:ldap:/etc/postfix/ldap-aliases.cf
virtual_gid_maps = static:500
virtual_mailbox_base = /home/vmail/
virtual_mailbox_domains = $mydomain, space.$mydomain, admin.$mydomain,
nestor.$mydomain, gein.$mydomain, meteo.$mydomain, technet.$mydomain,
astro.$mydomain, hesperia-space.eu
virtual_mailbox_limit = 0
virtual_mailbox_maps = proxy:ldap:/etc/postfix/ldap-users.cf
virtual_transport = dovecot
virtual_uid_maps = static:500
postconf: warning: /etc/postfix/main.cf: unused parameter:
127.0.0.1:10040_time_limit=3600
[root@vmail2 postfix]#
[root@vmail2 postfix]# postconf -n
alias_database = hash:/etc/postfix/aliases,
hash:/etc/postfix/aliases.d/virtual_aliases
alias_maps = hash:/etc/aliases
allowed_gein = check_client_access
cidr:/etc/postfix/gein_admin_ips.cidr,reject
allowed_iaasars = check_client_access
cidr:/etc/postfix/iaasars_admin_ips.cidr,reject
allowed_list1 = check_sasl_access
hash:/etc/postfix/allowed_groupmail_users,reject
allowed_list2 = permit_mynetworks,reject
allowed_meteo = check_client_access
cidr:/etc/postfix/meteo_admin_ips.cidr,reject
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
controlled_senders = check_sender_access hash:/etc/postfix/blocked_senders
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
default_process_limit = 25
delay_logging_resolution_limit = 3
deliver_lock_attempts = 40
dovecot_destination_recipient_limit = 1
gwcheck = reject_unverified_recipient, reject_unauth_destination
home_mailbox = Maildir/
html_directory = no
inet_interfaces = all
inet_protocols = ipv4, ipv6
local_header_rewrite_clients = static:all
mail_name = NOA Mail Srv XAPITI XPICTOY
mail_owner = postfix
mailbox_command = /usr/lib/dovecot/deliver
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
message_size_limit = 41943040
milter_default_action = accept
mydestination = $myhostname, localhost.$mydomain, localhost
mydomain = noa.gr
myhostname = vmail2.noa.gr
mynetworks = 195.251.204.0/24, 195.251.202.0/23, 194.177.194.0/23,
127.0.0.0/8, 10.201.0.0/16, [2001:648:2011::]/48, 83.212.5.24/29,
[2001:648:2ffc:1115::]/64, 62.217.124.0/29, [2001:648:2ffc:126::]/64
myorigin = $mydomain
newaliases_path = /usr/bin/newaliases.postfix
non_smtpd_milters = $smtpd_milters
parent_domain_matches_subdomains =
postfwdcheck = check_policy_service inet:127.0.0.1:10040
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES
recipient_canonical_maps = hash:/etc/postfix/domainrecipientmap
relay_domains = $mydestination
sample_directory = /usr/share/doc/postfix-2.3.3/samples
sender_canonical_maps = hash:/etc/postfix/domainsendermap
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
smtp_tls_security_level = may
smtpd_client_restrictions =
permit_mynetworks,permit_sasl_authenticated,reject
smtpd_delay_reject = yes
smtpd_end_of_data_restrictions = check_client_access
cidr:/etc/postfix/postfwdpolicy.cidr
smtpd_milters = inet:127.0.0.1:8891
smtpd_recipient_restrictions = check_recipient_access
hash:/etc/postfix/protected_destinations permit_sasl_authenticated
reject_unverified_recipient reject_unauth_destination
smtpd_restriction_classes =
controlled_senders,allowed_list1,allowed_list2,
allowed_iaasars,allowed_meteo,allowed_gein,postfwdcheck,gwcheck
smtpd_sasl_auth_enable = yes
smtpd_sasl_path = /var/spool/postfix/private/auth
smtpd_sasl_security_options = noanonymous
smtpd_sasl_type = dovecot
smtpd_tls_CAfile = /etc/pki/tls/certs/DigiCertCA.crt
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = /etc/pki/tls/certs/star_noa_gr-1243437.crt
smtpd_tls_exclude_ciphers = DES,3DES,MD5,aNULL,AES128,CAMELLIA128
smtpd_tls_key_file = /etc/pki/tls/private/star_noa_gr-1243437.key
smtpd_tls_loglevel = 1
smtpd_tls_mandatory_ciphers = high
smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3
smtpd_tls_received_header = yes
smtpd_tls_security_level = may
smtpd_tls_session_cache_timeout = 3600s
smtpd_use_tls = yes
tls_preempt_cipherlist = yes
tls_random_source = dev:/dev/urandom
transport_maps = hash:/etc/postfix/transport
unknown_local_recipient_reject_code = 550
unverified_recipient_reject_code = 550
virtual_alias_maps = hash:/etc/postfix/aliases,
hash:/etc/postfix/aliases.d/virtual_aliases,
proxy:ldap:/etc/postfix/ldap-alias-vacation.cf,
proxy:ldap:/etc/postfix/ldap-aliases.cf
virtual_gid_maps = static:500
virtual_mailbox_base = /home/vmail/
virtual_mailbox_domains = $mydomain, space.$mydomain, admin.$mydomain,
nestor.$mydomain, gein.$mydomain, meteo.$mydomain, technet.$mydomain,
astro.$mydomain, hesperia-space.eu
virtual_mailbox_limit = 0
virtual_mailbox_maps = proxy:ldap:/etc/postfix/ldap-users.cf
virtual_transport = dovecot
virtual_uid_maps = static:500
postconf: warning: /etc/postfix/main.cf: unused parameter:
127.0.0.1:10040_time_limit=3600

Thanks,
Nick

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Paul Menzel
Dear Nikolaos,


On 07/27/17 11:54, Nikolaos Milas wrote:

> We are moving to a new (virtual) server (from CentOS 5 with Postfix
> 2.11.6 to CentOS 7 with Postfix 3.2.2).
>
> I have moved the original configuration to the new server and Postfix
> won't start; I am getting:
>
> # systemctl status postfix
>   postfix.service - Postfix Mail Transport Agent
>     Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled;
> vendor preset: disabled)
>     Active: failed (Result: exit-code) since Thu 2017-07-27 12:25:14
> EEST; 12min ago
>    Process: 21895 ExecStart=/usr/sbin/postfix start (code=exited,
> status=1/FAILURE)
>    Process: 21893 ExecStartPre=/usr/libexec/postfix/chroot-update
> (code=exited, status=0/SUCCESS)
>    Process: 21890 ExecStartPre=/usr/libexec/postfix/aliasesdb
> (code=exited, status=0/SUCCESS)
>   Main PID: 14815 (code=killed, signal=TERM)
>
> Jul 27 12:25:12 vmail2.noa.gr postfix[21895]: /usr/sbin/postconf:
> warning: /etc/postfix/main.cf: unused parameter:
> 127.0.0.1:10040_time_limit=3600
> Jul 27 12:25:12 vmail2.noa.gr postfix[21895]: /usr/sbin/postconf:
> warning: /etc/postfix/main.cf: unused parameter:
> 127.0.0.1:10040_time_limit=3600
> Jul 27 12:25:12 vmail2.noa.gr postfix[21895]: /usr/sbin/postconf:
> warning: /etc/postfix/main.cf: unused parameter:
> 127.0.0.1:10040_time_limit=3600
> Jul 27 12:25:12 vmail2.noa.gr postfix[21895]:
> /usr/libexec/postfix/post-install: Error: /etc/postfix/postfix-files is
> not a file.
> Jul 27 12:25:12 vmail2.noa.gr postfix/postfix-script[21913]: fatal:
> unable to create missing queue directories
> Jul 27 12:25:13 vmail2.noa.gr postfix/postfix-script[21914]: fatal:
> Postfix integrity check failed!
> Jul 27 12:25:14 vmail2.noa.gr systemd[1]: postfix.service: control
> process exited, code=exited status=1
> Jul 27 12:25:14 vmail2.noa.gr systemd[1]: Failed to start Postfix Mail
> Transport Agent.
> Jul 27 12:25:14 vmail2.noa.gr systemd[1]: Unit postfix.service entered
> failed state.
> Jul 27 12:25:14 vmail2.noa.gr systemd[1]: postfix.service failed.
>
> I also tried:
>
> # /usr/libexec/postfix/post-install create-missing
> postconf: warning: /etc/postfix/main.cf: unused parameter:
> 127.0.0.1:10040_time_limit=3600
> /usr/libexec/postfix/post-install: Error: /postfix-files is not a file.
>
> Can you please let me know what may be the issue here?

Please post the output of the commands below.

```
$ ls -l /etc/postfix/
$ file /etc/postfix/postfix-files
```

[…]


Kind regards,

Paul
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Pintér Tibor (tibyke)-2


On 07/27/2017 11:59 AM, Paul Menzel wrote:

> Dear Nikolaos,
>
>
> On 07/27/17 11:54, Nikolaos Milas wrote:
>
>> We are moving to a new (virtual) server (from CentOS 5 with Postfix
>> 2.11.6 to CentOS 7 with Postfix 3.2.2).
>>
>> I have moved the original configuration to the new server and Postfix
>> won't start; I am getting:
>>
>> # systemctl status postfix
>>   postfix.service - Postfix Mail Transport Agent
>>     Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled;
>> vendor preset: disabled)
>>     Active: failed (Result: exit-code) since Thu 2017-07-27 12:25:14
>> EEST; 12min ago
>>    Process: 21895 ExecStart=/usr/sbin/postfix start (code=exited,
>> status=1/FAILURE)
>>    Process: 21893 ExecStartPre=/usr/libexec/postfix/chroot-update
>> (code=exited, status=0/SUCCESS)
>>    Process: 21890 ExecStartPre=/usr/libexec/postfix/aliasesdb
>> (code=exited, status=0/SUCCESS)
>>   Main PID: 14815 (code=killed, signal=TERM)
>>
>> Jul 27 12:25:12 vmail2.noa.gr postfix[21895]: /usr/sbin/postconf:
>> warning: /etc/postfix/main.cf: unused parameter:
>> 127.0.0.1:10040_time_limit=3600
>> Jul 27 12:25:12 vmail2.noa.gr postfix[21895]: /usr/sbin/postconf:
>> warning: /etc/postfix/main.cf: unused parameter:
>> 127.0.0.1:10040_time_limit=3600
>> Jul 27 12:25:12 vmail2.noa.gr postfix[21895]: /usr/sbin/postconf:
>> warning: /etc/postfix/main.cf: unused parameter:
>> 127.0.0.1:10040_time_limit=3600
>> Jul 27 12:25:12 vmail2.noa.gr postfix[21895]:
>> /usr/libexec/postfix/post-install: Error: /etc/postfix/postfix-files
>> is not a file.
>> Jul 27 12:25:12 vmail2.noa.gr postfix/postfix-script[21913]: fatal:
>> unable to create missing queue directories
>> Jul 27 12:25:13 vmail2.noa.gr postfix/postfix-script[21914]: fatal:
>> Postfix integrity check failed!
>> Jul 27 12:25:14 vmail2.noa.gr systemd[1]: postfix.service: control
>> process exited, code=exited status=1
>> Jul 27 12:25:14 vmail2.noa.gr systemd[1]: Failed to start Postfix
>> Mail Transport Agent.
>> Jul 27 12:25:14 vmail2.noa.gr systemd[1]: Unit postfix.service
>> entered failed state.
>> Jul 27 12:25:14 vmail2.noa.gr systemd[1]: postfix.service failed.
>>
>> I also tried:
>>
>> # /usr/libexec/postfix/post-install create-missing
>> postconf: warning: /etc/postfix/main.cf: unused parameter:
>> 127.0.0.1:10040_time_limit=3600
>> /usr/libexec/postfix/post-install: Error: /postfix-files is not a file.
>>
>> Can you please let me know what may be the issue here?
>
> Please post the output of the commands below.
>
> ```
> $ ls -l /etc/postfix/
> $ file /etc/postfix/postfix-files
> ```
>
> […]
>
>
> Kind regards,
>
> Paul
# rpm -ql postfix | grep files
/usr/libexec/postfix/postfix-files

t
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Peter Ajamian
In reply to this post by Nikolaos Milas
On 27/07/17 21:54, Nikolaos Milas wrote:
> Hello,
>
> We are moving to a new (virtual) server (from CentOS 5 with Postfix
> 2.11.6 to CentOS 7 with Postfix 3.2.2).

Where did you get Postfix 3.2 from?


Peter
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Postfix User-2
On Thu, 27 Jul 2017 22:20:36 +1200, Peter stated:

>On 27/07/17 21:54, Nikolaos Milas wrote:
>> Hello,
>>
>> We are moving to a new (virtual) server (from CentOS 5 with Postfix
>> 2.11.6 to CentOS 7 with Postfix 3.2.2).  
>
>Where did you get Postfix 3.2 from?
>
>
>Peter


You might try one of these URLs:

http://ghettoforge.org/index.php/Packages

ftp://ftp.reverse.net/pub/postfix/index.html

--
Jerry
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Peter Ajamian
On 27/07/17 22:44, Postfix User wrote:
> You might try one of these URLs:
>
> http://ghettoforge.org/index.php/Packages

Right, that one is highly recommended, much better than attempting to
install from source.

Once again, though, I'd like to know where the OP got his postfix from,
I get the feeling he installed it from source directly.


Peter
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Nikolaos Milas
In reply to this post by Pintér Tibor (tibyke)-2
On 27/7/2017 1:02 μμ, Pinter Tibor wrote:

> # rpm -ql postfix | grep files
> /usr/libexec/postfix/postfix-files

Thank you all for your responses. Please see below:

    # rpm -ql postfix | grep files
    /usr/share/postfix/postfix-files

    rpm -qa postfix | grep postfix
    postfix-3.2.2-2.el7.centos.appletech.x86_64

I've built postfix myself, using:

    http://repos.oostergo.net/7/SRPMS/postfix-3.2.2-1.el7.centos.src.rpm

having adapted it slightly to get built using the ltb openldap libraries
(see https://ltb-project.org/download) which I use on all my systems for
years.

Postfix worked fine after the package installation (with the default
config); However it presents this problem when I try to start it with
the config I copied from the initial server.

Any suggestions on how to correct things without having to rebuild the
software?

Cheers,
Nick
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Nikolaos Milas
In reply to this post by Peter Ajamian
On 27/7/2017 1:50 μμ, Peter wrote:

>> http://ghettoforge.org/index.php/Packages
> Right, that one is highly recommended, much better than attempting to
> install from source.

OK, I followed your advice and I rebuilt the rpm(s) using:

    http://mirror.ghettoforge.org/distributions/gf/el/7Server/plus/SRPMS/postfix3-3.2.2-4.gf.el7.src.rpm

I uninstalled postfix and re-installed using the new builds; then I
copied the migrated (simply transferred from the original server) custom
config files to the new config directory (/etc/postfix/).

Postfix started fine this time. Things appear running smoothly until now.

It may have been wrong from my side to simply replace the whole
/etc/postfix/ directory with the one from the original server (as I
initially did). This time I have been more cautious (as I explained above).

Thanks,
Nick
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Peter Ajamian
On 28/07/17 01:51, Nikolaos Milas wrote:
> On 27/7/2017 1:50 μμ, Peter wrote:
>
>>> http://ghettoforge.org/index.php/Packages
>> Right, that one is highly recommended, much better than attempting to
>> install from source.
>
> OK, I followed your advice and I rebuilt the rpm(s) using:
>  
> http://mirror.ghettoforge.org/distributions/gf/el/7Server/plus/SRPMS/postfix3-3.2.2-4.gf.el7.src.rpm

You don't have to actually rebuild the src.rpms, although you certainly
can if you want.  There are binary rpms you can just install as per the
directions at:

http://ghettoforge.org/index.php/Postfix3

> It may have been wrong from my side to simply replace the whole
> /etc/postfix/ directory with the one from the original server (as I
> initially did). This time I have been more cautious (as I explained above).

The main thing to be concerned about here is the possibility of
different versions of the compiled berkley db files.  Simply re-running
postmap on the source files should correct those issues.


Peter
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Nikolaos Milas
On 27/7/2017 10:45 μμ, Peter wrote:

> You don't have to actually rebuild the src.rpms, although you certainly
> can if you want.  There are binary rpms you can just install as per the
> directions at:
>
> http://ghettoforge.org/index.php/Postfix3

Yep, I know; As I've mentioned, I prefer to build against ltb openldap,
which has proved to be well-updated and trustworthy.

[Additionally, I like to maintain my (slight) rpm-build know-how; it has
been very useful in various occasions.]

[I must pay my respect to GhettoForge who are providing reliable updated
packages for numerous software projects.]

Interestingly, I've also noticed that postfix binaries are built against
original mysql, although CentOS 7 now uses mariadb as standard.

I've tried switching the dependency to mariadb instead, and building
using mariadb works fine as well.

Is there a particular reason why mysql is used in the spec file rather
than mariadb (both in the GhettoForge and in the Oostergo versions)?

> The main thing to be concerned about here is the possibility of
> different versions of the compiled berkley db files.  Simply re-running
> postmap on the source files should correct those issues.

I haven't noticed any such issues, but I'll keep an eye for possible
problems.

My concern was that by switching the whole directory I might have missed
some files that may have been needed, although I did not notice any such
files (by comparing the content of the /etc/postfix/ directories on the
two servers) when I tried to resolve the issue.

I am still wondering about the possible cause of the startup problem I
faced.

Cheers,
Nick

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Migrating 2.11 to 3.2

Peter Ajamian
On 28/07/17 08:31, Nikolaos Milas wrote:
> Yep, I know; As I've mentioned, I prefer to build against ltb openldap,
> which has proved to be well-updated and trustworthy.

Ok, I prefer to stick to stock CentOS packages where I can and do so as
a policy to avoid too many 3rd-party deps.

> [I must pay my respect to GhettoForge who are providing reliable updated
> packages for numerous software projects.]

Thank you.

> Interestingly, I've also noticed that postfix binaries are built against
> original mysql, although CentOS 7 now uses mariadb as standard.

They're built against whatever is provided by mysql-devel, in CentOS 6
that's mysql, in CentOS 7 that's MariaDB:

1:mariadb-devel-5.5.52-1.el7.x86_64 : Files for development of
MariaDB/MySQL applications
Repo        : base
Matched from:
Provides    : mysql-devel = 1:5.5.52-1.el7

> I've tried switching the dependency to mariadb instead, and building
> using mariadb works fine as well.

Yes, because you're actually building against MariaDB eitehr way and the
exact same packages.

> Is there a particular reason why mysql is used in the spec file rather
> than mariadb (both in the GhettoForge and in the Oostergo versions)?

Two reasons:  I use the same spec to build for CentOS 6 and CentOS 7,
since mysql-devel pulls in mariadb-devel in CentOS 7 anyways, there is
no reason to special-case it in the spec.

The second reason is that the spec file is historic, in that it was
originally from older Fedora, and then CentOS versions and continually
updated to keep up with what's new.  There is no real reason to change
the requirement at this stage since it works just fine the way it is.
That said, I might change it in 2020 once CentOS 6 goes EOL.

> I am still wondering about the possible cause of the startup problem I
> faced.

I can't say for sure, but it looks to be permissions-related to me.  It
might have to do with the way you built and subsequently installed
postfix, or it might be an selinux issue that simply isn't present in
the GhettoForge packages (assuming you haven't disabled selinux).


Peter
Loading...