A bit of info about the env:
RHEL4.6_i386
RT version 3.6.6
Apache 2.0.52-38
MySQL-standard 5.0.24a-0
After a bit of stracing the running httpd processes, I found some
information leading up to the segfault.
munmap(0xb7f6d000, 4096) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 1
fcntl64(1, F_GETFL) = 0x2 (flags O_RDWR)
connect(1, {sa_family=AF_FILE, path="/var/lib/mysql/mysql.sock"}, 110) =
0
setsockopt(1, SOL_IP, IP_TOS, [8], 4) = -1 EOPNOTSUPP (Operation not
supported)
setsockopt(1, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
read(1, ">\0\0\0", 4) = 4
read(1, "\n5.0.24a-standard\0\304\224\0\0-gCVdwJK\0,"..., 62) = 62
open("/usr/share/mysql/charsets/Index", O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
write(1, "\24\0\0\1\217 \0\0\0rt\XXXXXXX\0rt3", 24) = 24
read(1, "\5\0\0\2", 4) = 4
read(1, "\0\0\0\2\0", 5) = 5
fcntl64(1, F_SETFL, O_RDWR|O_NONBLOCK) = 0
read(1, 0xc0977b8, 8192) = -1 EAGAIN (Resource
temporarily unavailable)
fcntl64(1, F_SETFL, O_RDWR) = 0
write(1, "\21\0\0\0\3set autocommit=1", 21) = 21
read(1, "\5\0\0\1", 4) = 4
read(1, "\0\0\0\2\0", 5) = 5
time(NULL) = 1206447319
time(NULL) = 1206447319
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
chdir("/etc/httpd") = 0
rt_sigaction(SIGSEGV, {SIG_DFL}, {SIG_DFL}, 8) = 0
kill(5043, SIGSEGV) = 0
sigreturn() = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 5043 detached
There is no /usr/share/mysql/charsets/Index file, but copying an old
version from a 3.0 mysql server gives
open("/usr/share/mysql/charsets/Index", O_RDONLY|O_LARGEFILE) = 36
fstat64(36, {st_mode=S_IFREG|0755, st_size=549, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7e63000
read(36, "# sql/share/charsets/Index\n#\n# T"..., 4096) = 549
read(36, "", 4096) = 0
close(36) = 0
munmap(0xb7e63000, 4096) = 0
The data and segfault there after are pretty much the same
I have tried installing shared-compat libs for mysql as we were using
shared-standard, but this did not change anything either.
Anyone able to make more sense out of this than I or perhaps point me in
the right direction. It would be much appreciated.
Cheers,
------------------------------------------------------------------------
-------
> 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.
> peter.musolino at dbzco dot 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.
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
