AlliedModders - [MySQL] New SQL files -> Server crash!

AlliedModders (https://forums.alliedmods.net/index.php)

- (OLD) Bug Reports (https://forums.alliedmods.net/forumdisplay.php?f=24)

- - [MySQL] New SQL files -> Server crash! (https://forums.alliedmods.net/showthread.php?t=13182)

[MySQL] New SQL files -> Server crash!

Hello,

I have MySQL 4.1.11 installed on my server.

The current AMXmodX versions doesn't support this version. That's why I downloaded the SQL Modules (1.01 SQL Modules).

When I run my server, I get this error:

Quote:

./hlds_run: line 423: 27717 Segmentation fault (core dumped) $HL_CMD

With -debug:

Quote:

./hlds_run: line 423: 27717 Segmentation fault (core dumped) $HL_CMD
Cannot access memory at address 0x55004000
debug.cmds:1: Error in sourced command file:
Cannot access memory at address 0xfeffede4
email debug.log to [email protected]

If i remove the MySQL modules, my server works fine!

Will there be support for MySQL 4.1.11? Or should I have to downgrade :( .

Greetz,
GDX^

Use the regular AMXX Mysql files then do this:

http://forums.alliedmods.net/showthread.php?t=8235

Go to the second to last post and do what Viper says on there.

If you need help, go to the Mysql manuals on www.mysql.com

I'm running Mysql 4.1 right now just fine doing that.

You only need the new MySQL modules for 4.1.8 or greater.

Quote:

Originally Posted by BAILOPAN

You only need the new MySQL modules for 4.1.8 or greater.

Regular Mysql Module works with 4.1.8 or greater also by setting the old password setting, I'm running 4.1.8 right now with it set :)

Those new modules seems to not work though when I tried it before, it just crashes like what GDX^ said, Linux and Windows.

Want me to try it out again and tell you how it works Bail?

Nope, it doesn't work...

I added old-password=1 under [mysqld].
my.cfg (only [mysqld]):

Quote:

# The MySQL server
[mysqld]
port = 3306
socket = <<<<<<removed>>>>>>
skip-locking
set-variable = key_buffer=16M
set-variable = max_allowed_packet=1M
set-variable = table_cache=64
set-variable = sort_buffer=512K
set-variable = net_buffer_length=8K
set-variable = myisam_sort_buffer_size=8M

old-password=1

Error with the standard modules:

Quote:

L 05/11/2005 - 14:21:41: [MYSQL] DB Connection failed(1251): Client does not support authentication protocol requested by server; consider upgrading MySQL client
[AMXX] SQL error: can't connect: 'Client does not support authentication protocol requested by server; consider upgrading MySQL client'

Error with the new modules (amxmodx-SQLmodules-1.01.zip):

Quote:

./hlds_run: line 423: 25858 Segmentation fault $HL_CMD
Add "-debug" to the ./hlds_run command line to generate a debug.log to help with solving this problem
Wed May 11 14:25:36 CEST 2005: Server restart in 10 seconds

-debug:

Quote:

./hlds_run: line 423: 25876 Segmentation fault (core dumped) $HL_CMD
Cannot access memory at address 0x55004000
debug.cmds:1: Error in sourced command file:
Cannot access memory at address 0xfeffee44
email debug.log to [email protected]

I wonna run it with AMXBans so I really need MySQL..

I hope someone can help me!

When u do that, you need to redo all of your usernames so they use the old-password method, look here:

http://dev.mysql.com/doc/mysql/en/old-client.html

Trust me, I got mine working following those steps. Going from 4.0.xx to 4.1.xx, they updated the password hashing algorithm so any clients (AMXX) that doesn't support that will give you that message, it won't happen when you get it setup properly.

I gonna try this one :)

EDIT:
Doesnt works :(

Quote:

bash: syntax error near unexpected token `('

@Developers: Will there be another release for the new MySQL versions?

Try reinstalling, I've installed this successfully on both Linux and Windows Boxes with no problems. I don't see a reason for it to not work. Which one do you have?

Problem is this, you have to use the old password method with the username you are using to logon with on AMXX, if it's not using that older method then that error pops up. Somehow you didn't do it right so delete your databases and try installing it again.

If you don't want to, just install 4.0.xx version, there really isn't a reason to use 4.1.xxx unless you use other services that use the new features 4.1.xxx has or if you run multiple Mysql servers on one machine because it will give you performance increases if that is the case and doing one task like AMXX won't stress Mysql enough for an upgrade to be neccessary.

Well, I think that my my.cnf-file isn't correct configured...

What did u add to it? Witch binary did u use to make it an old password?

Greetz,
GDX^