1 (edited by nicola.braccia 2015-12-14 22:01:06)

Topic: [SOLVED] Problem to update iredapd 1.6 to 1.7

==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version: Debian Jessie
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Yes
- Related log if you're reporting an issue:
====

I upgraded iredadp with this guide http://www.iredmail.org/docs/upgrade.iredapd.html
but i have a fatal error with user iredapd

# bash upgrade_iredapd.sh
* Detected Linux/BSD distribution: DEBIAN
* Found iRedAPD directory: /opt/iredapd, symbol link of iRedAPD-1.6.0
* Found iRedAPD config file: /opt/iredapd/settings.py
CREATE ROLE
CREATE DATABASE
ALTER DATABASE
psql: FATAL:  Peer authentication failed for user "iredapd"
* Checking dependent Python modules:
  + [required] python-sqlalchemy
* Create directory /opt/iRedAPD-1.7.0.
* Copying new version to /opt/iRedAPD-1.7.0
* Removing old symbol link /opt/iredapd
* Creating symbol link /opt/iredapd to /opt/iRedAPD-1.7.0
* Copy new SysV init script.
* Add missing parameters or rename old parameter names.
* Remove deprecated plugins.
* Create directory to store log files: /var/log/iredapd.
* Restarting iRedAPD service.
* Upgrade completed.
<<< NOTE >>> If iRedAPD doesn't work as expected, please post your issue in
<<< NOTE >>> our online support forum: [url]http://www.iredmail.org/forum/[/url]
<<< NOTE >>> iRedAPD log file is /var/log/iredapd.log.

I check /opt/iredadp/settings.py and it seems to be all right.
Thank you in advance

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: [SOLVED] Problem to update iredapd 1.6 to 1.7

It didn't import required SQL tables (/opt/iRedAPD-1.7.0/SQL/iredapd.pgsql, /opt/iRedAPD-1.7.0/SQL/greylisting_whitelists.sql). iRedAPD will keep running but two plugins are not working: greylisting, throttle. Although they're not working, but it doesn't block incoming/outgoing emails.

*) Do you have parameters which start with 'iredapd_db_' in /opt/iredapd/settings.py?
*) Do you have one line for 'iredapd' user in file "~postgres/.pgpass"?
*) Could you please show me all settings in pg_hba.conf?

I will give you solution to fix it manually after i got your reply. Sorry about this trouble.

3 (edited by nicola.braccia 2015-12-14 21:16:24)

Re: [SOLVED] Problem to update iredapd 1.6 to 1.7

1) in settings.py i have:

iredapd_db_server = '127.0.0.1'
iredapd_db_port = '5432'
iredapd_db_name = 'iredapd'
iredapd_db_user = 'iredapd'
iredapd_db_password = 'xxx'

2)
yes -> localhost:*:*:iredapd:xxx

3)

# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the PostgreSQL
# documentation for a complete description of this file.  A short
# synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access.  Records take one of these forms:
#
# local      DATABASE  USER  METHOD  [OPTIONS]
# host       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
# hostssl    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
# hostnossl  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain
# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
# plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", "replication", a
# database name, or a comma-separated list thereof. The "all"
# keyword does not match "replication". Access to replication
# must be enabled in a separate record (see example below).
#
# USER can be "all", a user name, a group name prefixed with "+", or a
# comma-separated list thereof.  In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names
# from a separate file.
#
# ADDRESS specifies the set of hosts the record matches.  It can be a
# host name, or it is made up of an IP address and a CIDR mask that is
# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
# specifies the number of significant bits in the mask.  A host name
# that starts with a dot (.) matches a suffix of the actual host name.
# Alternatively, you can write an IP address and netmask in separate
# columns to specify the set of hosts.  Instead of a CIDR-address, you
# can write "samehost" to match any of the server's own IP addresses,
# or "samenet" to match any address in any subnet that the server is
# directly connected to.
#
# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
# "krb5", "ident", "peer", "pam", "ldap", "radius" or "cert".  Note that
# "password" sends passwords in clear text; "md5" is preferred since
# it sends encrypted passwords.
#
# OPTIONS are a set of options for the authentication in the format
# NAME=VALUE.  The available options depend on the different
# authentication methods -- refer to the "Client Authentication"
# section in the documentation for a list of which options are
# available for which authentication methods.
#
# Database and user names containing spaces, commas, quotes and other
# special characters must be quoted.  Quoting one of the keywords
# "all", "sameuser", "samerole" or "replication" makes the name lose
# its special character, and just match a database or username with
# that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal.  If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect.  You can
# use "pg_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
# "host" records.  In that case you will also need to make PostgreSQL
# listen on a non-local interface via the listen_addresses
# configuration parameter, or via the -i or -h command line switches.




# DO NOT DISABLE!
# If you change this first entry you will need to make sure that the
# database superuser can access the database using some other method.
# Noninteractive access to all databases is required during automatic
# maintenance (custom daily cronjobs, replication, and similar tasks).
#
# Database administrative login by Unix domain socket
local   all             postgres                                peer

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                peer
#host    replication     postgres        127.0.0.1/32            md5
#host    replication     postgres        ::1/128                 md5

many thanks

4

Re: [SOLVED] Problem to update iredapd 1.6 to 1.7

In pg_hba.conf, please change all "local ... peer" to "local ... md5", then restart PostgreSQL service.

This is the cause of this failure.

I may need to update tools/upgrade_iredadmin.sh to fix this setting in pg_hba.conf and restart postgresql service, then import sql tables.

5

Re: [SOLVED] Problem to update iredapd 1.6 to 1.7

Steps to fix your issue:

*) In pg_hba.conf, please change all "local ... peer" to "local ... md5", then restart PostgreSQL service.
*) Copy sample SQL templates to /tmp:

# cp /opt/iredapd/SQL/{iredapd.pgsql,greylisting_whitelists.sql} /tmp/
# chmod 0755 /opt/iredapd/SQL/{iredapd.pgsql,greylisting_whitelists.sql}

*) Login to PostgreSQL database as "iredapd" user like below:

# psql -U iredapd -d iredapd

It will ask for password, you can find it in /opt/iredapd/settings.py (parameter "iredapd_db_password").

*) In SQL command line, import the sql templates:

sql> \i /tmp/iredapd.pgsql;
sql> \i /tmp/greylisting_whitelists.sql;

That's all.

6

Re: [SOLVED] Problem to update iredapd 1.6 to 1.7

Thank you Zhang, i really appreciate your professionalism.

7

Re: [SOLVED] Problem to update iredapd 1.6 to 1.7

UPDATE:

1: I fixed this issue in iRedAPD-1.7.0 and repacked it.
2: I repacked iRedMail-0.9.3 with this repacked iRedAPD-1.7.0.