Upgrade to 3.1 went badly (log content)

Discussion in 'General' started by Gern Blanston, Oct 11, 2016.

  1. Gern Blanston

    Gern Blanston New Member

    Thanks for any pointers. I'm getting the forum complaining to me about "links" in my messages so a little sanitizing was attempted in there.

    Gern

    ------

    I'm getting a gaggle of messages, here are a few:


    Oct 11 19:52:28 www postfix/proxymap[8021]: warning: connect to mysql server 127.0.0.1: Access denied for user 'ispconfig'@'localhost' (using password: YES)


    Oct 11 19:52:28 www postfix/cleanup[11034]: warning: proxy:mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf lookup error for "[email protected]"


    Oct 11 19:52:28 www postfix/cleanup[11034]: warning: B5E3E601C2: sender_bcc_maps map lookup problem -- message not accepted, try again later


    Earlier:


    Oct 11 19:48:35 www postfix/smtpd[5053]: connect from localhost[127.0.0.1]


    Oct 11 19:48:35 www postfix/smtpd[5053]: D961E60084: client=localhost[127.0.0.1]


    Oct 11 19:48:35 www postfix/cleanup[11034]: warning: proxy:mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf lookup error for "ping.domenico-kaper=[email protected]"


    Oct 11 19:48:35 www postfix/cleanup[11034]: warning: D961E60084: sender_bcc_maps map lookup problem -- message not accepted, try again later


    Oct 11 19:48:35 www postfix/cleanup[11034]: DA45260084: message-id=<[email protected]>


    Oct 11 19:48:35 www amavis[10205]: (10205-06) Negative SMTP response to data-dot (<[email protected]>): 451 4.3.0 Error: queue file write error, dt: 0.1 ms


    Oct 11 19:48:35 www amavis[10205]: (10205-06) (!)4o8JxqF1z2Bp FWD from <ping.domenico-kaper=[email protected]> -> <[email protected]>, BODY=7BIT 451 4.3.0 from MTA(smtp:[127.0.0.1]:10025): 451 4.3.0 Error: queue file write error


    Oct 11 19:48:35 www postfix/qmgr[1365]: DA45260084: from=<[email protected]>, size=1112, nrcpt=1 (queue active)


    Oct 11 19:48:35 www postfix/smtpd[5053]: disconnect from localhost[127.0.0.1]


    Oct 11 19:48:35 www amavis[10205]: (10205-06) Blocked MTA-BLOCKED {TempFailedInbound}, [89.163.251.183]:59770 [89.163.251.183] <ping.domenico-kaper=[email protected]> -> <[email protected]>, Queue-ID: 619C260080, Message-ID: <[email protected]>, mail_id: 4o8JxqF1z2Bp, Hits: 12.833, size: 17516, dkim_sd=dkim:iphoneprofphotos.com, 945 ms


    Oct 11 19:48:35 www postfix/smtp[8739]: 619C260080: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.5, delays=0.56/0/0/0.95, dsn=4.3.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.3.0 id=10205-06 - Temporary MTA failure on relaying, from MTA(smtp:[127.0.0.1]:10025): 451 4.3.0 Error: queue file write error (in reply to end of DATA command))


    Oct 11 19:48:35 www postfix/pipe[7356]: DA45260084: to=<[email protected]>, orig_to=<postmaster>, relay=dovecot, delay=0.02, delays=0/0/0/0.02, dsn=5.1.1, status=bounced (user unknown)


    Oct 11 19:48:35 www postfix/bounce[10202]: warning: DA45260084: undeliverable postmaster notification discarded


    Oct 11 19:48:35 www postfix/qmgr[1365]: DA45260084: removed
     
  2. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    Looks like postfix isn't configured to talk to the database correctly. Try running the ispconfig update script and answer yes to reconfigure services.
     
  3. Gern Blanston

    Gern Blanston New Member

    Still getting errors, like this:

    Oct 12 00:06:23 www postfix/proxymap[16387]: warning: connect to mysql server 127.0.0.1: Access denied for user 'ispconfig'@'localhost' (using password: YES)
     
  4. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    Postfix is still not able to log in to mysql -- you did tell it to reconfigure services when updating? That is what configures the mysql connection info in all the /etc/postfix/mysql-*.cf files.
     
  5. Gern Blanston

    Gern Blanston New Member

    Yes I did reconfigure services. At this point it's time to restore from backup. I looked in the manual but the procedure there to restore the MySQL database dbispconfig seems incomplete. I did a drop database dbispconfig; and then tried to use mysql -h to restore from the .sql file I found in /var/backups/ and now I am getting an error:

    # mysql -h localhost -u root -pthepass dbispconfig < ispconfig_db_backup.sql
    ERROR 1146 (42S02) at line 22: Table 'dbispconfig.aps_instances' doesn't exist

    What creates the tables for dbispconfig?
     
  6. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

  7. Gern Blanston

    Gern Blanston New Member

    Well, the backup of MySQL and /etc/ that I have is prior to the update (the update seems to have failed). So if I restore the 3.0 database backup and the /etc files then I will have 3.0 databse and /etc files but a 3.1 update for everything else. Not sure what to do, am I looking at rebuilding from scratch?
     
  8. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    If you want to go back to 3.0, restore the needed old config files to /etc, load the 3.0 schema and import the database dump, and replace /usr/local/ispconfig from ispconfig_software.tar.gz. You sure shouldn't have to rebuild from scratch, and probably don't even need to go back to 3.0 to fix the problem with postfix logging in to mysql.

    For the latter (postfix/mysql problem), open one of the /etc/postfix/mysql-*cf files and test the username/password there to see if you can login to mysql. You probably can't, but fixing that issue should get postfix working, or at least move on to the next issue if there is one.

    On related info, does the ispconfig 3.1 web interface work? Is this a single server or multi-server install? What all user/host combos do you have in the mysql.user table?
     
  9. Gern Blanston

    Gern Blanston New Member

    Tried resetting the password first after looking in the *.cf file using:
    # mysql -u root -p
    Password:
    mysql> use mysql;

    Reading table information for completion of table and column names
    You can turn off this feature to get a quicker startup with -A
    Database changed

    mysql> update user set password=PASSWORD("mycooliopassword") where User='ispconfig';

    Query OK, 0 rows affected (0.00 sec)
    Rows matched: 1 Changed: 0 Warnings: 0

    mysql> flush privileges;
    But still doesn't connect (log message errors).
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    empty the browser cache and delete cookies in the browser.
     

Share This Page