[rt-users] Migration Prep

[Jim Berry]

Similarly at our site:   We observed issues (not just RT) when Apache was started before the Postgres server was ready.   During certain testing, it might be necessary to manually restart Apache.

Jim

-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Thomas Sibley
Sent: Friday, August 09, 2013 3:46 PM
To: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Migration Prep

On 08/09/2013 06:36 AM, Paul O'Rorke wrote:
> When I look at syslog I see the following during startup:
>
>
> Aug  9 08:28:04 rt4 RT: DBI
> connect('dbname=rtdb;host=localhost','rtuser',...) failed: Can't
> connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2) at /usr/local/share/perl/5.14.2/DBIx/SearchBuilder/Handle.pm line 105.
> (/usr/local/share/perl/5.14.2/Carp.pm:102)
> Aug  9 08:28:05 rt4 RT: DBI
> connect('dbname=rtdb;host=localhost','rtuser',...) failed: Can't
> connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2) at /usr/local/share/perl/5.14.2/DBIx/SearchBuilder/Handle.pm line 105.
> (/usr/local/share/perl/5.14.2/Carp.pm:102)
> Aug  9 08:28:08 rt4 mysqld_safe: Starting mysqld daemon with databases
> from /var/lib/mysql

Just by looking at the log timestamps, your system is pretty clearly set to start Apache (or whatever is serving RT) before mysql.  This isn't RT's fault, but simply the wrong startup ordering for your system.  You should change it so Apache/your webserver depends on mysql being started first.  How to do so depends on your distribution.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20130812/c4db32aa/attachment.htm>