[deathcurse]

I use a few SM plugins that connect to MySQL databases on a different server and the last day or two I've had trouble with this server, meaning the MySQL databases were sometimes unavailable.

Now what I've noticed is when the databases aren't reachable, when the game server goes to change level they usually timeout/crash. Is this normal behavior or is it a badly designed plugin?

Using MMS 1.10 and SM 1.5

The plugins that use MySQL that I have installed are:

- Sourcebans
- Ads mysql
- Client prefs

Anyone know of any related problems?

[asherkin]

Originally Posted by deathcurse Now what I've noticed is when the databases aren't reachable, when the game server goes to change level they usually timeout/crash. Is this normal behavior or is it a badly designed plugin?

It's a bug, but a known one that's being worked on.

[minimoney1]

Originally Posted by deathcurse I use a few SM plugins that connect to MySQL databases on a different server and the last day or two I've had trouble with this server, meaning the MySQL databases were sometimes unavailable. Now what I've noticed is when the databases aren't reachable, when the game server goes to change level they usually timeout/crash. Is this normal behavior or is it a badly designed plugin? Using MMS 1.10 and SM 1.5 The plugins that use MySQL that I have installed are: - Sourcebans - Ads mysql - Client prefs Anyone know of any related problems?

This issue, from what I know, happens with non-threaded approaches, and out of the three that you have listed, ClientPrefs is the only one that I'd imagine it causing this. I would just switch ClientPrefs to SQLite database as it makes little difference (and it would be more convenient for me as a user to be able to set different client options across multiple servers).

[deathcurse]

I'll try changing clientprefs to sqlite then.

asherkin, can you give any info on if clientprefs is the cause?

Thanks for the replies.

[asherkin]

It's a root problem in the database API, anything using threaded queries can cause it, I'm on my phone at the moment but can provide a technical explanation later if you want it.

Your time would be better spent fixing your MySQL server to not be unavailable.

[deathcurse]

Ah right, I see.

Yea everything is pretty much sorted with our MySQL server so shouldn't be an issue again.

[hkkelvin1995]

using MM 1.9 would be more stable than using 1.10
It is still a development build:-)

[deathcurse]

Originally Posted by asherkin It's a root problem in the database API, anything using threaded queries can cause it, I'm on my phone at the moment but can provide a technical explanation later if you want it. Your time would be better spent fixing your MySQL server to not be unavailable.

I don't suppose you know when this is likely to be fixed?

[asherkin]

When one of the 2 of us have time to basically re-write the MySQL extension (and probably more).