Bug 3965 - MySQL module doesnt seem to work with MySQL 5.1.30
MySQL module doesnt seem to work with MySQL 5.1.30
Status: RESOLVED INCOMPLETE
Product: AMX Mod X
Classification: Unclassified
Component: Module: MySQL
trunk
PC Linux
: P3 major
Assigned To: amxmodx-bugs@alliedmods.net
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-24 14:47 PDT by richardritter09
Modified: 2013-06-25 08:41 PDT (History)
4 users (show)

See Also:


Attachments

Description richardritter09 2009-08-24 14:47:38 PDT
Hey,

I recently switched my website provider. Im running amxbans and several other SQL plugins which are custom made. It used to work on MySQL 4.4.xx . As soon as I switched over to the new provider(cpanel), the server wont retrieve data from that server. They moved everything for me including db users and databases. I also re-dumped the database. I also made sure the users and passwords are correct. Me and my new provider already tried to troubleshot but we did not find any solution. All Settings are perfect and it does connect. As soon as its trying to retrieve/update/delete database information, the server will crash. I also made a test plugin with nextra to test which MySQL functions work and which do not. We were only able to connect to the server. Anything further will crash the server.
Comment 1 David Anderson [:dvander] 2009-08-27 20:21:24 PDT
Please post a test case, and ideally, a backtrace or core dump.
Comment 2 richardritter09 2009-08-28 16:18:41 PDT
I would provide an test environment but I already switched back to the old one with MySQL 4.4.x . So I cannot do anymore tests. The only thing I can find that is caused by the MySQL Module is this:

L 08/23/2009 - 02:32:56: [MySQL] Thread worker was unable to start.
L 08/23/2009 - 02:32:56: [AMXX] Run time error 10 (plugin "amxbans.amxx") (native "SQL_ThreadQuery") - debug not enabled!

L 08/23/2009 - 13:47:50: [MySQL] Thread worker was unable to start.
L 08/23/2009 - 13:47:50: [AMXX] Run time error 10 (plugin "amxbans.amxx") (native "SQL_ThreadQuery") - debug not enabled!


That's the only logs I have left after one of my admins cleared the error log. Im unable to test this further currently since Im leaving for a meeting on Tuesday for a couple of days. After that I can make the exact same environment on my computer and give you further information if needed...
Comment 3 devicenull 2010-07-09 13:59:19 PDT
I'm also seeing issues with a similar setup.  Server worked fine with MySQL 4.4.x, now that we went to MySQL 5.1.x we are seeing the server die with SIGALRM when queries are performed.

I'd suggest upgrading the MySQL client library that the build server is using, based on the build server logs it seems to be using a 5.0.x one, which is old.

If you know a way to get linux/gdb to write core dumps on SIGALRM, I can provide them.

This is happening in 1.4 build 3073.
Comment 4 devicenull 2010-07-09 13:59:40 PDT
bah, amxmodx != sourcemod, nevermind.

Note You need to log in before you can comment on or make changes to this bug.