[Arkshine]

I'm confused, why did you renamed "metamod.so" from 1.21-am package to "metamod12137_i386.so"?
The error seems like a missing lstdc++ dependency, but the 1.21-am doesn't have that, so I'm sure to understand and I'm wondering if you really upload the right binary.

About the metamod debug log, make sure to have meta_debug 9 in your server.cfg.

About Mysql not loading, having some metamod information would be welcomed, meanwhile, I guess it's CentOS x64? Did you properly installed the 32bits libs like (ia32-libs, lib32z1 lib32z1-dev, libc6-dev-i386 libc6-i386)? Do you have some security enabled like SELinux or similar?

[Arkshine]

Originally Posted by claudiuhks These logs are because meta_debug CVar is still 3. Set it to zero.

If you set to 0, you won't get log.

Actaully to get in verbose mode, you shouild set a higher value. Metamod uses some "level" value and it seems to go up to 9.

[fysiks]

Why are you trying to skip a stable version directly to an unstable version? Try 1.8.2 first. There were changes in 1.8.2 to deal with Valve updates so you probably have to be sync'd between versions.

But, in the end, you know the drill, if you don't have the version of the engine for which the current version of AMX Mod X was designed, we can't really help you (and certainly not very effectively).

[aron9forever]

so 3 or 9?
I changed it to 3 while I was on 1.8.3 and the logs that I've posted on the last page are what showed up
none of these funky hook calls are printed there

then I just deleted amxmodx , uploaded 1.8.1 base and cstrike , my plugins, enabled mysql and started it and now the debugs show

@arkshine renamed metamod because that's what it was written like in plugins.ini and I was too lazy to change the directory
the error you're talking about came up with the metamod I downloaded from http://www.amxmodx.org/dl.php?filena...od-1.21-am.zip TX USA

centos is x64 but all libs are installed fine since the servers are running fine and have been for a while
don't know about SELinux but I'm 90% sure we don't have that

it's a dedicated server, not a hosting provider

@fyskis
because 1.8.2 doesn't have the function I updated for, menu_addblank2
also when 1.8.2 was released, it was written in bold everywhere DONT USE THIS UNLESS YOU HAVE 6XXX


I will reinstall 1.8.3 on another server and try again to fish for logs
ATM I have a deadline I've missed with launching these servers so I'm looking for the fastest solution, not the best one.

[JusTGo]

aron9forever
1.8.3 will never work on 6xxx< servers you will get seg faults and bugs so the only solution is to update your hlds if you want to use amx 1.8.3.

[Arkshine]

Mysql crashing is likely unrelated to old or new HLDS build.

@aron, can you do that https://forums.alliedmods.net/showpo...postcount=1350 with the mysql binary, it will give directly the error if .so can't be loaded.

[fysiks]

Originally Posted by aron9forever @fyskiswhen 1.8.2 was released, it was written in bold everywhere DONT USE THIS UNLESS YOU HAVE 6XXX

So . . . Since 1.8.3-dev is entirely based on 1.8.2, logic dictates that the same restriction applies to 1.8.3.

The suggestion of upgrading to 1.8.2 (a very stable release) first is a logical step to verify whether or not the change from 1.8.1 to 1.8.2 was where the issue was created instead of going directly to an unstable dev version. Debugging 101.

[Arkshine]

Originally Posted by Arkshine Mysql crashing is likely unrelated to old or new HLDS build. @aron, can you do that https://forums.alliedmods.net/showpo...postcount=1350 with the mysql binary, it will give directly the error if .so can't be loaded.

so ?