[rt-users] [phish?] RE: No outbound email after upgrade

Tue Aug 25 17:06:54 EDT 2015

On Tue, Aug 25, 2015 at 3:39 PM, Ditri, Chris <Cditri at experi-metal.com> wrote:
>
> ________________________________________
> From: Matt Zagrabelny <mzagrabe at d.umn.edu>
> Sent: Tuesday, August 25, 2015 2:55 PM
> To: Ditri, Chris
> Cc: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] No outbound email after upgrade
>
> On Tue, Aug 25, 2015 at 1:43 PM, Ditri, Chris <Cditri at experi-metal.com> wrote:
>> Hi Matt,
>>
>> There is absolutely nothing in ObjectScrips, and everything is set to NULL in Scrips (in the database).
>>
>> Are you implying that I need to make custom scrips to send routine emails regarding tickets?
>> Something is different then... I definitely didn't have to do that before... must be new between 4.0.7 and 4.2.8 (4.0.7 shipped with Wheezy, and 4.2.8 with Jessie).  Was it normal to lose that functionality in the upgrade?
>
> Certainly not normal.
>
> You do need to run some upgrade commands (DB scripts) when upgrading
> though. The (upstream) upgrade will normally prompt you for what
> version of RT you are upgrading from and which one you are upgrading
> to. Do you remember seeing that?
>
> For the RT 3.8 Debian package, there was a directory,
> /etc/request-tracker3.8/etc/upgrade. Do you have something similar for
> RT 4(.2) ?
>
> 3.8 was the last time I used the deb package for RT, and I don't
> remember what the upgrades were like - I'd imagine it also varies
> depending on if you use db-config or not. We use Debian for the OS,
> but use upstream tarballs for the RT installation. There is a make
> target that handles applying the DB upgrade scripts.
>
> Cheers,
>
> -m
>
>
> Now that you mention it, Matt, there was an issue with dbconfig-common.  It didn't want to take the root password for the the database.  Eventually I got it to go through, but there were some errors.  I found a log for dbconfig-common... but I honestly don't know why it goofed up, and how tor re-run dbconfig common for rt.

I don't know anything about dbconfig-common. I generally stay away
from it, but perhaps it is useful in certain circumstances.

You could always file a Debian bug against the package if it broke
during upgrades. Dom is a very good maintainer.

> Here is the log I found in /var/log/dbconfig-common:
>
> RROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2).
> unable to connect to mysql server.
> ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2).
> unable to connect to mysql server.
> granting access to database rtdb for rtuser at localhost: success.
> verifying access for rtuser at localhost: success.
> creating database rtdb: success.
> verifying database rtdb exists: success.
> populating database via scriptfile...  done.
> dbconfig-common: dumping mysql database rtdb to /var/tmp/request-tracker4.rtdb.2013-12-16-14.45.mysql.q3wmxz.
> dbconfig-common: dropping mysql database rtdb.
> dropping database rtdb: success.
> verifying database rtdb was dropped: success.
> dbconfig-common: revoking privileges for user rtuser on rtdb.
> revoking access to database rtdb from rtuser at localhost: success.
> granting access to database rtdb for rtuser at localhost: success.
> verifying access for rtuser at localhost: success.
> creating database rtdb: success.
> verifying database rtdb exists: success.
> populating database via scriptfile...  done.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES).
> unable to connect to mysql server.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES).
> unable to connect to mysql server.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES).
> unable to connect to mysql server.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES).
> unable to connect to mysql server.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES).
> unable to connect to mysql server.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.10.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12-2.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.19.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.3.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.4.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.6.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.7.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.10.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12-2.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.19.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.3.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.10.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12-2.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.19.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.3.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.10.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12-2.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.19.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.3.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.10.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12-2.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.19.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.3.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES).
> unable to connect to mysql server.
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u3.mysql.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.10.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12-2.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.19.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.3.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.4.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.6.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.7.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.10.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12-2.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.19.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.3.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.4.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.6.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.7.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.4.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.6.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.7.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.4.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.6.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.7.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.4.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.6.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.7.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.4.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.6.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.7.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.10.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12-2.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.19.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.3.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.4.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.6.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.7.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.10.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.12-2.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.0.19.
> applying upgrade script for 4.0.7-5+deb7u3 -> 4.2.3.
>
> It was nonsense that it wouldn't take the password...I've had problems like that with dbconfig-common before...  But ultimately, it looked like it worked for rt, and it seems to work just fine in all other respects.
>
> Is there a way to repair the damage?

Depends on how much you've customized. You can re-import stock scrips.
Or if you've customized, you can dump/restore the data and attempt the
upgrade DB scripts again.

Perhaps re-import the scrips and see if that is close enough. Take a look at:

sbin/rt-setup-database

and

(from the source tarball) etc/initialdata

Also, grepping the mailing list archives might help with examples or
syntax. I just did "grep rt-setup-database full_archives.txt | wc -l"
and got 2672 hits.

  I'm not sure where scrips live even... in the db?  on the filesystem?

Scrips live in the DB.

-m