Buffalo Posted April 29, 2012 Posted April 29, 2012 Every time player joins the server it freezes with current registry.db : http://www.mediafire.com/?raf7v0z4ttgz2x9 Is it too big ? There is important data stats and etc.
-ffs-Sniper Posted April 29, 2012 Posted April 29, 2012 (edited) I was able to open your registry.db without any problem using a standalone SQLite browser. The problem is probably caused by your script. Therefore I recommend you to post parts of your stats system showing what is being executed when a player joins. Edited April 29, 2012 by Guest
Jaysds1 Posted April 29, 2012 Posted April 29, 2012 Actually, it's not suppose to freeze when a player joins the server, unless people are logging in at the same time. It has to be your script.
Buffalo Posted April 29, 2012 Author Posted April 29, 2012 Well i have disabled stats system and every resource that could use sqlite db commands. Now it freezes for 10seconds after this simple test function: addCommandHandler('test',function(player) local serial = getPlayerSerial(player) executeSQLSelect ( "AdminInfo", "adminlvl","serial = '" .. serial .. "'") end) It worked all fine back some time. Also works fine if registry.db is deleted. Backtrace (by this guide https://wiki.multitheftauto.com/wiki/Bui ... er_freezes) gives this: #0 0xb74e2f0f in ?? () from /usr/lib/libsqlite3.so.0 #1 0xb74e7090 in ?? () from /usr/lib/libsqlite3.so.0 #2 0xb7506cae in ?? () from /usr/lib/libsqlite3.so.0 #3 0xb7556685 in ?? () from /usr/lib/libsqlite3.so.0 #4 0xb753c670 in sqlite3_step () from /usr/lib/libsqlite3.so.0 #5 0xb7735ba2 in CRegistry::QueryInternal(char const*, CRegistryResult*) () from /root/race/mods/deathmatch/deathmatch.so #6 0xb77381a1 in CRegistry::Select(std::string const&, std::string const&, std::string const&, unsigned int, CRegistryResult*) () from /root/race/mods/deathmatch/deathmatch.so #7 0xb777b823 in CStaticFunctionDefinitions::ExecuteSQLSelect(std::string const&, std::string const&, std::string const&, unsigned int, CRegistryResult*) () from /root/race/mods/deathmatch/deathmatch.so #8 0xb77e1ca5 in CLuaFunctionDefinitions::ExecuteSQLSelect(lua_State*) () from /root/race/mods/deathmatch/deathmatch.so #9 0xb7877571 in luaD_precall () from /root/race/mods/deathmatch/deathmatch.so #10 0xb78829d0 in luaV_execute () from /root/race/mods/deathmatch/deathmatch.so #11 0xb7877a58 in luaD_call () from /root/race/mods/deathmatch/deathmatch.so #12 0xb7872781 in f_call () from /root/race/mods/deathmatch/deathmatch.so #13 0xb7876fb3 in luaD_rawrunprotected () from /root/race/mods/deathmatch/deathmatch.so #14 0xb7877018 in luaD_pcall () from /root/race/mods/deathmatch/deathmatch.so #15 0xb7872598 in lua_pcall () from /root/race/mods/deathmatch/deathmatch.so ---Type <return> to continue, or q <return> to quit---
Castillo Posted May 1, 2012 Posted May 1, 2012 Topic moved to "Support for MTA:SA 1.x > Linux-Server".
Phat Looser Posted May 1, 2012 Posted May 1, 2012 There has been a server I hosted with exactly the same problem. The databases became too big and suddenly the server froze. It wasn't a script problem. Deleting the databases solved the issue.... Its happening on Linux Debian 64 bit.
Buffalo Posted May 1, 2012 Author Posted May 1, 2012 Yes it's on Debian 64-bit. But well, i've just tested it on Debian 32-bit and Windows and it freezes too.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now