RT 3.6.1 install question

This is my fourth or fifth time installing RT and I see that the
process continues to improve! I have it just about installed thanks
to some really good Wiki instructions. I’m just about done but have a
final question or two.

RT 3.6.1 on RHEL 4.0

I was confused when it came to setting up the mysql database
stuff. I got error messages because it didn’t like the password but
it seems to have gotten over it. /var/lib/mysql/rt3 has what looks
like everything in it but I cannot log in as root. No matter what I
give it, I get a “username or password incorrect” message.

This is not a huge problem (I don’t think) because I have 3.0.1
running on another LInux box and what I’d really like to do is just
copy over all of the accounts, tickets, settings, etc from that
environment and put them on the new box.

Someone advised me on how to do this a year or so ago and it was very
simple. So simple, that I’ve forgotten what to do. I tried a tar of
everything on the only /var/lib/mysql/rt3 onto the new machine but
then I get text instead of the GUI when I try to bring up RT.

I think if someone can just tell what to copy to the new machine to
make it just like the old RT server, I should be good to go. TIA!

I was confused when it came to setting up the mysql database
stuff. I got error messages because it didn’t like the password but
it seems to have gotten over it. /var/lib/mysql/rt3 has what looks
like everything in it but I cannot log in as root. No matter what I
give it, I get a “username or password incorrect” message.

Check the Apache logs to see what it’s rejecting on. The default username
and password are root/password just in case something’s misplaced on the
wiki. If you can’t log on to a fresh RT install, there may be something
missing.

This is not a huge problem (I don’t think) because I have 3.0.1

running on another LInux box and what I’d really like to do is just
copy over all of the accounts, tickets, settings, etc from that
environment and put them on the new box.

Someone advised me on how to do this a year or so ago and it was very
simple. So simple, that I’ve forgotten what to do. I tried a tar of
everything on the only /var/lib/mysql/rt3 onto the new machine but
then I get text instead of the GUI when I try to bring up RT.

I think if someone can just tell what to copy to the new machine to
make it just like the old RT server, I should be good to go. TIA!

If you have a look at the RT Tarball, there are some upgrade instructions.
Your best bet is to have a look at the INSTALL file. From memory it’s about
point 6 or 7 on there.

There are a few changes from 3.0 to 3.6.1 but they’re relatively easy to
apply. Just a case of running:
% rt-setup-database --datadir /path/to/etc/upgrade/ --dba dbuser
–dba-password dbpass --action insert/act/schema
Sadly you’ve got 6 version updates to do from 3.0, so they’ll be something
like:

% rt-setup-database --datadir /etc/request-tracker3.6/upgrade/3.1.0 --dba
dbuser --dba-password dbpass --action insert
% rt-setup-database --datadir /etc/request-tracker3.6/upgrade/3.1.0 --dba
dbuser --dba-password dbpass --action acl
% rt-setup-database --datadir /etc/request-tracker3.6/upgrade/3.1.0 --dba
dbuser --dba-password dbpass --action schema

for each folder. The instructions in the INSTALL file explain it a bit
better than me.

That’s it :slight_smile:
Obviously, make sure you backup first, but you’ll be doing that anyway if
you’re migrating to a new server.

Good luck,
Regards,

Andrew Nicols

That’s very good information. Thanks very much for the concise
step-by-step Roy.

I do plan to “import” the rt 3.0.? database into this new
installation but I figured it would be better to get the vanilla
3.6.1 install on the new server working first. Did as you suggested
and to no one’s surprise, there is no root account in mysql. The
following “using password: NO” is the same error message I got when I
did a make initialize-database so that’s the smoking gun. Before I
break it again, any ideas on what I did wrong during the install phase?

By starting the installation fresh, do you mean configure, make
install, make initialize-database?

For RT_SiteConfig.pm, understood about rt_user. What should I put in
the DatabasePassword setting? Set($DatabasePassword , ‘rt_pass’);
? That’s the way it is on my original RT server. I built a backup
RT server last year on 3.4.something and that has a null ( ’ ’ )
entry in the Password field. Both RT servers are working fine.

Since the “drop rt3” command didn’t work, can I just delete the
subdirectory or will that cause additional problems?

Output follows: TIA!

******* This is why I can’t log on to RT *******

[root@patrol etc]# mysql rt3 -p -u root
Enter password:
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 8 to server version: 4.1.7

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the buffer.

mysql> select id,Name,Password from Users where Name like ‘root’;
Empty set (0.00 sec)

mysql> exit
Bye

******** This is similar to the error I got when doing make
database-initialize ***********

[root@patrol etc]# mysqladmin drop rt3
mysqladmin: connect to server at ‘localhost’ failed
error: ‘Access denied for user ‘root’@‘localhost’ (using password: NO)’
[root@patrol etc]#

******** This failed too… files are still in /var/lib/mysql/rt3

[root@patrol mysql]# mysqladmin -u root --password=xxxxxxxx drop rt3
Dropping the database is potentially a very bad thing to do.
Any data stored in the database will be destroyed.

Do you really want to drop the ‘rt3’ database [y/N] y
mysqladmin: DROP DATABASE rt3 failed;
error: ‘Error dropping database (can’t rmdir ‘./rt3’, errno: 39)’

*********** mysql versions currently installed ******************

MYSQL versions installed (just did an apt-get upgrade yesterday so
I’m surprised there is something newer out there. I presume 4.1.7 is
fine though

mysql-devel-4.1.7-4.RHEL4.1
mysql-4.1.7-4.RHEL4.1
mysqlclient10-devel-3.23.58-4.RHEL4.1
mod_auth_mysql-2.6.1-2.1
php-mysql-4.3.11-2.8
mysql-bench-4.1.7-4.RHEL4.1
mysqlclient10-3.23.58-4.RHEL4.1
mysql-server-4.1.7-4.RHEL4.1
freeradius-mysql-1.0.1-2.RHEL4
libdbi-dbd-mysql-0.6.5-10.RHEL4.1

At 09:16 AM 9/7/2006, you wrote:

******** This is similar to the error I got when doing make
database-initialize ***********

[root@patrol etc]# mysqladmin drop rt3
mysqladmin: connect to server at ‘localhost’ failed
error: ‘Access denied for user ‘root’@‘localhost’ (using password: NO)’
[root@patrol etc]#

******** This failed too… files are still in /var/lib/mysql/rt3


This isn’t an RT error as such. The error being reported here is saying that
the mysql database user root has the incorrect password, therefore the
initialize-database script is unable to log into your MySQL database and
create the database structure and initial inserts.
Check your root password for MySQL. Can you log into MySQL?
If you can log into MySQL with the mysql root user, but need to specify a
password to do so, then you need to put this into your RT_SiteConfig.pm and
then re-run the make initialize-database.
I seem to recall you also need to create the initial rt table for MySQL RT
databases, but as I’m not using MySQL I can’t confirm.

Regards,

Andrew Nicols

Frank Saxton wrote:

This is my fourth or fifth time installing RT and I see that the
process continues to improve! I have it just about installed thanks
to some really good Wiki instructions. I’m just about done but have a
final question or two.

RT 3.6.1 on RHEL 4.0

I was confused when it came to setting up the mysql database stuff. I
got error messages because it didn’t like the password but it seems to
have gotten over it. /var/lib/mysql/rt3 has what looks like
everything in it but I cannot log in as root. No matter what I give
it, I get a “username or password incorrect” message.

This is not a huge problem (I don’t think) because I have 3.0.1
running on another LInux box and what I’d really like to do is just
copy over all of the accounts, tickets, settings, etc from that
environment and put them on the new box.

Someone advised me on how to do this a year or so ago and it was very
simple. So simple, that I’ve forgotten what to do. I tried a tar of
everything on the only /var/lib/mysql/rt3 onto the new machine but
then I get text instead of the GUI when I try to bring up RT.

I think if someone can just tell what to copy to the new machine to
make it just like the old RT server, I should be good to go. TIA!


The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

My guess by the error you received is that you aren’t providing a
password when one is needed. Instead of trying to run mysqladmin to
drop the database try

shell>mysql -u root -p
Enter Password: enter either nothing (just hit ‘Enter’) if you never
set up a root password or enter the password you created when you
installed MySQL

mysql> drop database rt3;

See if that works.

Mathew Snyder

Got the vanilla 3.6.1 install going.

Copied the 3.0.1 RT database as follows:
/usr/bin/mysqldump --user=rt_user --password=rt_pass --databases
rt3 > /home/frankie/rt.sql

Copied to the new server

Imported old DB with :
mysql --user=root --password=xxxxx < /home/frankie/rt.sql

Upgraded doing (the 3.0.1 stuff scrolled off the screen but went error free):
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.1.15 --dba root --dba-password xxxxx --action schema
Creating database schema.
Couldn’t find schema file for mysql
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.1.17 --dba dbuser --dba-password dbpass --action insert
Creating ScripActions…16.17.done.
Creating ScripConditions…10.done.
Done setting up database content.
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.1.17 --dba root --dba-password xxxxxx --action acl
Couldn’t find ACLS for mysql in ./etc/upgrade/3.1.17
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.1.17 --dba root --dba-password xxxxxx --action schema
Creating database schema.
Couldn’t find schema file for mysql
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.3.0 --dba dbuser --dba-password dbpass --action insert
Done setting up database content.
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.3.0 --dba root --dba-password xxxx --action acl
Done setting up database ACLs.
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.3.0 --dba root --dba-password xxxxx --action schema
Creating database schema.
Done setting up database schema.
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.3.11 --dba dbuser --dba-password dbpass --action insert
Done setting up database content.
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.3.11 --dba root --dba-password xxxxxx --action acl
Done setting up database ACLs.
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.3.11 --dba root --dba-password xxxxxx --action schema
Creating database schema.
Done setting up database schema.
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.5.1 --dba dbuser --dba-password dbpass --action insert
Creating predefined searches…1.2.3.done.
Done setting up database content.
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.5.1 --dba root --dba-password xxxxxxxx --action acl
Couldn’t find ACLS for mysql in ./etc/upgrade/3.5.1
[root@patrol rt-3.6.1]# /opt/rt3/sbin/rt-setup-database --datadir
./etc/upgrade/3.5.1 --dba root --dba-password xxxxxx --action schema
Creating database schema.
Couldn’t find schema file for mysql

I can log in OK and all of the open tickets are listed. If I click
on any ticket, I get text like the following. I also cannot log out
or do anything from there. I’m gathering that I am missing a
critical step. HELP!

%# BEGIN BPS TAGGED BLOCK {{{ %# %# COPYRIGHT: %# %# This software is
Copyright (c) 1996-2006 Best Practical Solutions, LLC %# %# %#
(Except where explicitly superseded by other copyright notices) %# %#
%# LICENSE: %# %# This work is made available to you under the terms
of Version 2 of %# the GNU General Public License. A copy of that
license should have %# been provided with this software, but in any
event can be snarfed %# from www.gnu.org. %# %# This work is
distributed in the hope that it will be useful, but %# WITHOUT ANY
WARRANTY; without even the implied warranty of %# MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU %# General Public
License for more details. %# %# You should have received a copy of
the GNU General Public License %# along with this program; if not,
write to the Free Software %# Foundation, Inc., 675 Mass Ave,
Cambridge, MA 02139, USA. %# %# %# CONTRIBUTION SUBMISSION POLICY: %#
%# (The following paragraph is not intended to limit the rights
granted %# to you to modify and distribute this software under the
terms of %# the GNU General Public License and is only of importance
to you if %# you choose to contribute your changes and enhancements
to the %# community by submitting them to Best

A little more info about my Apache setup (which worked OK with the
vanilla 3.6.1 install, although I never tried to actually use it)

I’m sure this is a very simple fix to httpd.conf (if I only knew what it was…)

NameVirtualHost *:80
<VirtualHost *:80>
ServerAdmin Frankie@Easyrider.com
ServerName patrol.vigilancemonitoring.com
DocumentRoot /opt/rt3/share/html/
AddDefaultCharset UTF-8
addHandler fastcgi-script .fcgi
#ScriptAlias /rt/ /opt/rt3/bin/mason_handler.fcgi/
<Directory “/opt/rt3/share/html”>
Options FollowSymLinks ExecCGI
AllowOverride None

Alias /NoAuth/images /opt/rt3/share/html/NoAuth/images
ScriptAlias /rt/ /opt/rt3/bin/mason_handler.fcgi/

FastCgiIpcDir /tmp
FastCgiServer /opt/rt3/bin/mason_handler.fcgi -idle-timeout 120 -processes 4

[root@patrol rt-3.6.1]# tail /var/log/httpd/error_log
[Thu Sep 07 17:56:49 2006] [notice] Digest: done
[Thu Sep 07 17:56:49 2006] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Thu Sep 07 17:56:49 2006] [notice] LDAP: SSL support unavailable
[Thu Sep 07 17:56:49 2006] [notice] FastCGI: process manager
initialized (pid 13840)
[Thu Sep 07 17:56:49 2006] [warn] FastCGI: server
“/opt/rt3/bin/mason_handler.fcgi” started (pid 13841)
[Thu Sep 07 17:56:49 2006] [notice] mod_python: Creating 4 session
mutexes based on 256 max processes and 0 max threads.
[Thu Sep 07 17:56:49 2006] [notice] Apache/2.0.53 (Fedora) configured
– resuming normal operations
[Thu Sep 07 17:56:50 2006] [warn] FastCGI: server
“/opt/rt3/bin/mason_handler.fcgi” started (pid 13850)
[Thu Sep 07 17:56:51 2006] [warn] FastCGI: server
“/opt/rt3/bin/mason_handler.fcgi” started (pid 13853)
[Thu Sep 07 17:56:52 2006] [warn] FastCGI: server "/opt/rt3/bin/mason_handler.fc

OK! I’m making some progress here! I have RT 3.6.1 working just
fine, as near as I can tell with all of my 3.0.1 “stuff” imported
over. Whew! I really like the new GUI!!! Much nicer looking

Only problem now is that the RT URL is http://192.168.0.3/ instead of
http://192.168.0.3/rt like I have it everywhere else. Again, I’m
guessing this is a small config setting change somewhere. But where?

In /opt/rt3/etc/RT_SiteConfig.pm I see:

#Set($WebPath , “/rt”); # Added after I built everything
Set($WebPath , “”);

Changing the comments on both made no difference. Please tell me I
don’t need to do the whole database thing over again if I change
something in this file!

For reference, here is the latest httpd.conf:

Alias /rt/ “/opt/rt3/share/html/”
Alias /rt “/opt/rt3/share/html/”
FastCgiIpcDir /tmp
FastCgiServer /opt/rt3/bin/mason_handler.fcgi -idle-timeout 120 -processes 4

NameVirtualHost *:80
<VirtualHost *:80>
ServerAdmin Frankie@Easyrider.com
ServerName patrol.vigilancemonitoring.com
DocumentRoot /opt/rt3/share/html/
AddDefaultCharset UTF-8
AddHandler fastcgi-script .fcgi
ScriptAlias / /opt/rt3/bin/mason_handler.fcgi/
Alias /NoAuth/images /opt/rt3/share/html/NoAuth/images

<Directory “/opt/rt3/share/html”>
Options FollowSymLinks ExecCGI
AllowOverride None

Correct. If I had given the mysqladmin root password when asked for
a password after invoking make initialize-database, I would have been
fine. Hitting return, as the prompt advised me to do) hose me
good. There is no recovery from that point except to manually blow
away the ./mysql/rt3 subdirectory per the procedure I described earlier.

This “RT root” business is very confusing. By default, RT wants to
run from the root URL http://localhost. I guess that’s fine if the
only thing apache does on the server is server up RT
connections. But the way it’s set up now, fastcgi screws up all of
the other web stuff on the server. Apparently, some change was made
in RT 3.5 or 3.6 that makes simple aliasing NOT a viable option. I
attached a copy of the pertinent httpd.conf entries
yesterday. Basically, what I want to do is run RT from
http://localhost/rt not http://localhost

It looks like RT_SiteConfig: Set($WebPath , “/rt”);
would do that but apparently I need to do something to get the chance
to take. If I have to rebuild everything just to make this small
change, I am going to be very upset.

If I change ScriptAlias in httpd.conf to point to “/rt” instead of
“/” it breaks RT (but fixes all of the other web sites on the server)

I guess what I’m asking is what do I need to do to alias RT from /
where it is now to /rt where I want it and get everything to work?

If anyone wants to view the problem, on a plain vanilla RT 3.6.1
server, try to view http://localhost/server-status and you’ll see what I mean.

TIA!

At 09:23 AM 9/8/2006, you wrote:>On 9/8/06, Frank Saxton <mailto:frankie@easyrider.comfrankie@easyrider.com> wrote:

Imported old DB with :
mysql --user=root --password=xxxxx < /home/frankie/rt.sql

Just for reference now (seeing as you’ve got it all working), the
initialize-database script was failing before because you hadn’t
given it the MySQL root password - the one that you’ve specified in
the line I’ve quoted above.
I can’t remember completely, but I seem to recall that the make
initialize-database command asks you for the root password, but you
can initialize-the database with the rt-setup-database command
giving it the action ‘init’.
Anyway, you’ve got it all working now so it’s neither here nor there!

As far as I know, changing the WebPath shouldn’t affect RT in any
way, but if RT used to be at /rt and people using it have it
bookmarked, it might just be worth putting a 302 redirect to the new location.

Good luck and best wishes,


Regards,

Andrew Nicols
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.12.2/441 - Release Date: 9/7/2006

“It looks like RT_SiteConfig: Set($WebPath , “/rt”);
would do that but apparently I need to do something to get the chance to
take. If I have to rebuild everything just to make this small change, I
am going to be very upset.”

service httpd stop
rm -rf /rt_dir/var/mason_data/obj*
service httpd start

This is all over the mailing list archives and the wiki.

Drew,

I apologize for squandering your valuable time.

That made the improvement I was looking for but it’s still slightly
broken now that it’s moved.

Everything seems to work OK except if I click a ticket from the home
screen “ticket at a glance”. I get text like there is a problem with
fastcgi. If I click on the same ticket from the ticket screen, it
displays correctly

Ticket from Home/glance which doesn’t work (displays text)
http://192.168.0.3/Ticket/Display.html?id=688

Ticket from Tickets/display (which does work):
http://192.168.0.3/rt/Ticket/Display.html?id=688

For some reason, this link (http://192.168.0.3/Ticket/*) hasn’t
picked up the /rt change. As near as I can tell, everything else did.

The only change made to RT_SiteConfig.pm:
Set($WebPath , “/rt”);
#Set($WebPath , “”);

httpd.conf:
FastCgiIpcDir /tmp
FastCgiServer /opt/rt3/bin/mason_handler.fcgi -idle-timeout 120 -processes 4

NameVirtualHost *:80
<VirtualHost *:80>
ServerAdmin Frankie@Easyrider.com
ServerName patrol.vigilancemonitoring.com
DocumentRoot /opt/rt3/share/html/
AddDefaultCharset UTF-8
AddHandler fastcgi-script .fcgi

ScriptAlias /rt /opt/rt3/bin/mason_handler.fcgi/

 ScriptAlias /rt/ /opt/rt3/bin/mason_handler.fcgi/
 Alias /NoAuth/images /opt/rt3/share/html/NoAuth/images
Options FollowSymLinks ExecCGI AllowOverride None

At 10:14 AM 9/8/2006, Drew Barnes wrote: