We have RT installed on two systems (1 production and 1 development) and
things have been running great for nearly a year. We are at 3.6.3 on both
systems as well. There were some Perl updates made on our DEV environment
and I believe this included MySQL portions. We started getting 500 Error
Message from Apache when trying to hit the dev site.
I looked at the HTTPD/error_log and found the following:
[Wed May 23 09:47:11 2007] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)
[Wed May 23 09:47:11 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
DBI connect(‘dbname=rt3;host=localhost;port=3306’,‘rt_user’,…) failed:
Client does not support authentication protocol requested by server;
consider upgrading MySQL client at
/usr/lib/perl5/site_perl/5.8.3/DBIx/SearchBuilder/Handle.pm line 106
[Wed May 23 09:49:21 2007] [error] Connect Failed Client does not support
authentication protocol requested by server; consider upgrading MySQL
client\n at /opt/rt3/lib/RT.pm line 205\n
I’ve gone into MySQL and did the whole “OLD_PASSWORD” thing for the RT_USER
account but we still get the same thing. I’m checked to make sure the the
Perl modules are all up to date and they are. I’m not sure what else I
should look at so any help would be appreciated.
Thanks,
CR
/usr/lib/perl5/site_perl/5.8.3/DBIx/SearchBuilder/Handle.pm line 106
[Wed May 23 09:49:21 2007] [error] Connect Failed Client does not support
authentication protocol requested by server; consider upgrading MySQL
client\n at /opt/rt3/lib/RT.pm line 205\n
Second question: 5.8.3 is a fairly old version of Perl. Did you check to ensure
that Perl isn’t somehow grabbing an older version of DBI instead of a newer
one? Maybe you have DBI installed two different places under /usr/lib/perl5/*.
Just a thought.
Scott
Scott Courtney | “I don’t mind Microsoft making money. I mind them
scott@4th.com | having a bad operating system.” – Linus Torvalds
http://4th.com/ | (“The Rebel Code,” NY Times, 21 February 1999)
| PGP Public Key at http://4th.com/keys/scott.pubkey
I enabled the old password support in my.cnf and then re-started both apache
and mysql. When I try to hit the site in the web browser I get a blank
page, absolutely nothing with no errors.
In the httpd/error_log I get:
[Wed May 23 11:08:23 2007] [notice] child pid 28611 exit signal Segmentation
fault (11)
In the httpd/access_log I get:
<> - - [23/May/2007:09:45:17 -0500] “Get /rt3 HTTP/1.1” 500 662
There is nothing in the rt.log.
CROn 5/23/07, Scott Courtney scott@4th.com wrote:
On Wednesday 23 May 2007 10:58, Carlos Randolph wrote:
I’ve gone into MySQL and did the whole “OLD_PASSWORD” thing for the
RT_USER
account but we still get the same thing. I’m checked to make sure the
the
Perl modules are all up to date and they are. I’m not sure what else I
should look at so any help would be appreciated.
Did you enable old password support in your my.cnf (or equivalent) config
file? I believe you can’t do it on an account-by-account basis unless it’s
also enabled at the global level in the server config.
Kind regards,
Scott
–
Scott Courtney | “I don’t mind Microsoft making money. I mind them
scott@4th.com | having a bad operating system.” – Linus
Torvalds
http://4th.com/ | (“The Rebel Code,” NY Times, 21 February 1999)
| PGP Public Key at
http://4th.com/keys/scott.pubkey
I’ve gone into MySQL and did the whole “OLD_PASSWORD” thing for the RT_USER
account but we still get the same thing. I’m checked to make sure the the
Perl modules are all up to date and they are. I’m not sure what else I
should look at so any help would be appreciated.
Did you enable old password support in your my.cnf (or equivalent) config
file? I believe you can’t do it on an account-by-account basis unless it’s
also enabled at the global level in the server config.
Kind regards,
Scott
Scott Courtney | “I don’t mind Microsoft making money. I mind them
scott@4th.com | having a bad operating system.” – Linus Torvalds
http://4th.com/ | (“The Rebel Code,” NY Times, 21 February 1999)
| PGP Public Key at http://4th.com/keys/scott.pubkey
Did anyone ever figure this out? I am having the same problem. At
first I had the regular password style:
DBI connect(‘dbname=rt3;host=localhost’,‘rt’,…) failed: Client does
not support authentication protocol requested by server; consider
upgrading MySQL client at
/usr/lib/perl5/site_perl/5.8.5/DBIx/SearchBuilder/Handle.pm line 106
[Wed Mar 19 14:06:33 2008] [error] [client 10.20.1.102] Connect Failed
Client does not support authentication protocol requested by server;
consider upgrading MySQL client\n at /opt/rt3/lib/RT.pm line 220\n
Changing the password to use the old_password function gave me:
[Wed Mar 19 14:07:37 2008] [notice] child pid 6190 exit signal
Segmentation fault (11)
Thanks in advance,
Peter Musolino
D.B. Zwirn (UK) Ltd.
52 Conduit Street
London, W1S 2YZ
Phone: +44 (0) 20 7220 2322
Mobile: +44 (0) 79 0953 0687
peter.musolino at dbzco dot com
I enabled the old password support in my.cnf and then re-started both
apache
and mysql. When I try to hit the site in the web browser I get a
blank
page, absolutely nothing with no errors.
In the httpd/error_log I get:
[Wed May 23 11:08:23 2007] [notice] child pid 28611 exit signal
Segmentation
fault (11)
In the httpd/access_log I get:
<> - - [23/May/2007:09:45:17 -0500] “Get /rt3 HTTP/1.1”
500 662
There is nothing in the rt.log.
CR
I’ve gone into MySQL and did the whole “OLD_PASSWORD” thing for the
RT_USER
account but we still get the same thing. I’m checked to make sure
the
the
Perl modules are all up to date and they are. I’m not sure what
else I
should look at so any help would be appreciated.
Did you enable old password support in your my.cnf (or equivalent)
config
file? I believe you can’t do it on an account-by-account basis unless
it’s
also enabled at the global level in the server config.
Kind regards,
Scott
–
Peter Musolino
D.B. Zwirn (UK) Ltd.
52 Conduit Street
London, W1S 2YZ
Phone: +44 (0) 20 7220 2322
Mobile: +44 (0) 79 0953 0687
peter.musolino@dbzco.com
This e-mail message is intended only for the named recipient(s) above. It may contain confidential information. If you are not the intended recipient, you are hereby noti
fied that any use, dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. D.B. Zwirn & Co., L.P. reserves the right to archive
and monitor all e-mail communications through its networks. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and
delete the message and any attachment(s) from your system. Thank you.