rt.log shows:
[Sun Mar 6 21:34:14 2005] [error]: FAILED LOGIN for root from
10.10.0.12 (/usr/local/rt3/share/html/autohandler:191)
I’ve reset root’s password in mysql so I’m sure it’s correct.
I also have
Mail loops will generate a critical log message.
Set($LogToSyslog , ‘debug’);
Set($LogToScreen , ‘debug’);
Set($LogToFile , ‘debug’);
Set($LogDir, ‘/usr/local/rt3/var/log’);
Set($LogToFileNamed , “rt.log”); #log to rt.log
in RT_Siteconfig.pm. rt.log doesn’t really have any more information
that what I’ve listed above.
RT 3.4.1 under freebsd 4.8, perl 5.8.5, apache 1.3.31 / mod_perl 1.2.9
I’ve applied the database patches in the 3.3.0/ and 3.3.11 dirs, with no
errors.
Any ideas?
Thanks,
Graham
Sorry if this shows up twice.
Following up with more info:
Graham Dunn wrote:
rt.log shows:
[Sun Mar 6 21:34:14 2005] [error]: FAILED LOGIN for root from
10.10.0.12 (/usr/local/rt3/share/html/autohandler:191)
[snip]
RT 3.4.1 under freebsd 4.8, perl 5.8.5, apache 1.3.31 / mod_perl 1.2.9
DBIx::SearchBuilder 1.15
mysql Ver 12.22 Distrib 4.0.21, for portbld-freebsd4.8 (i386)
Inserting
if (!$session{‘CurrentUser’}->IsPassword($pass)) {
$RT::Logger->error(“pass $pass was bad:$!”);
}
into autohandler
prints
[Sun Mar 6 23:41:45 2005] [error]: pass password was bad:
(/usr/local/rt3/share/html/autohandler:191)
in the logs. Again, this is using root/password, the hash in Users
matches the value given in the wiki, so there’s something going wrong in
IsPassword.
Not sure where to go from here.
Graham
in the logs. Again, this is using root/password, the hash in Users
matches the value given in the wiki, so there’s something going wrong in
IsPassword.
It really sounds like you’re not even connecting to the database
Jesse Vincent wrote:
in the logs. Again, this is using root/password, the hash in Users
matches the value given in the wiki, so there’s something going wrong in
IsPassword.
It really sounds like you’re not even connecting to the database
If I stop mysql, I get an error in http-error.log
DBI connect(‘dbname=rt3’,‘rt_user’,…) failed: Can’t connect to local
MySQL server through socket ‘/tmp/mysql.sock’ (2) at
/usr/local/lib/perl5/site_perl/5.8.5/DBIx/SearchBuilder/Handle.pm line 96
[Sun Mar 6 18:56:01 2005] [error] Connect Failed Can’t connect to local
MySQL server through socket ‘/tmp/mysql.sock’ (2)\n at
/usr/local/rt3/lib/RT.pm line 168\n
So the connection is being made … can I get more debugging output from
IsPassword?
Graham
So the connection is being made … can I get more debugging output from
IsPassword?
Did you upgrade mySQL, as well? I vaguely recall something in the mySQL
documentation about the format of the passwords changing in later
versions. To allow the old behavior, you have to include something like
old_password or old_password_format in the configuration file.
Russell Mosemann, Ph.D. * Computing Services * Concordia University, Nebraska
“Everyone generalizes!”
Russell Mosemann wrote:>On Sun, 6 Mar 2005, Graham Dunn wrote:
So the connection is being made … can I get more debugging output from
IsPassword?
Did you upgrade mySQL, as well? I vaguely recall something in the mySQL
documentation about the format of the passwords changing in later
versions. To allow the old behavior, you have to include something like
old_password or old_password_format in the configuration file.
No, MySQL remained at 4.0.1
Graham
Jesse Vincent wrote:
in the logs. Again, this is using root/password, the hash in Users
matches the value given in the wiki, so there’s something going wrong in
IsPassword.
It really sounds like you’re not even connecting to the database
The MySQL log for the failed login:
DO RELEASE_LOCK(“Apache-Session-5abd9d5e70ec23ebf24361149da4842c”);
at 1378
#050306 20:15:23 server id 1 log_pos 1378 Query thread_id=3
exec_tim
e=0 error_code=0
SET TIMESTAMP=1110158123;
UPDATE sessions SET a_session =
‘^E^F^C\0\0\0^D^D^Q^ORT::CurrentUser^C\0\0\0^D^D
^Q^LRT::I18N::en^C\0\0\0\0\0\0\0\nLangHandle\n^EUsers\0\0\0^Etable^D^C\0\0\0\0\0
\0\0^Fvalues^D^C\0\0\0\0\0\0\0^Gfetched\0\0\0^KCurrentUser^D^B\0\0\0\0\0\0\0^Pcr
eate_in_queues\n
5abd9d5e70ec23ebf24361149da4842c\0\0\0^K_session_id^D^C\0\0^X
0\0^A<9E>' <A
HREF="/Ticket/Display.html?id=id">id/TITLE
:#',\n'<A
HREF="/Ticket/Display.html?id=id">Subject/TITLE
:Subject',\n'Status',\n'QueueName',\n'OwnerName',\n'Priori
ty',\n'NEWLINE',\n'',\n'Requestors',\n'_
CreatedRelative_',\n'ToldRelative',\n'__
LastUpdatedRelative__',\n'TimeLeft'\0\0\0^FForma
\0\0\0^KRowsPerPage\n^CASC\0\0\0^EOrder\n^Cnew\0\0\SearchId\n\0\0\0\0^EQuery
^E\0\0\0^FObject^E\0\0\0^KDescription\n^Bid\0\0\0^GOrderBy\0\0\0^QCurrentSearchH
ash’ WHERE id = ‘5abd9d5e70ec23ebf24361149da4842c’;
at 2377
#050306 20:15:23 server id 1 log_pos 2377 Query thread_id=3
exec_tim
e=0 error_code=0
SET TIMESTAMP=1110158123;
DO RELEASE_LOCK(“Apache-Session-5abd9d5e70ec23ebf24361149da4842c”);
There’s an associated in sessions with the id from the query…
Graham