Server hang on startup
AndrielChaoti opened this issue · 15 comments
After Precious Stones reaches "MySQL connection successful", it hangs the entire server during startup for a full 60 seconds, but not if it's manually reloaded using an external plugin like PlugMan
The plugin reports it's version 9.6.6 in game with /ver
We are having the same issue right now here is the log output on initial startup:
28.07 23:11:55 [Server] INFO Enabling PreciousStones v10.5.3 28.07 23:11:55 [Server] INFO Version 10.5.3 loaded 28.07 23:11:55 [Server] INFO MySQL Connection successful 28.07 23:11:55 [Server] INFO Creating table: pstone_cuboids 28.07 23:11:55 [Server] INFO Creating table: pstone_fields 28.07 23:11:55 [Server] INFO Creating table: pstone_unbreakables 28.07 23:11:55 [Server] INFO Creating table: pstone_grief_undo 28.07 23:11:55 [Server] INFO Creating table: pstone_translocations 28.07 23:11:55 [Server] INFO Creating table: pstone_storedblocks 28.07 23:11:55 [Server] INFO Creating table: pstone_players 28.07 23:11:55 [Server] INFO Creating table: pstone_snitches 28.07 23:11:56 [Server] INFO Added new indexes to database 28.07 23:11:56 [Server] INFO Creating table: pstone_purchase_payments 28.07 23:11:56 [Server] ERROR Error at SQL Query: Duplicate key name 'key_grief_locs' 28.07 23:11:56 [Server] ERROR Error at SQL Query: Duplicate key name 'indx_field_owner' 28.07 23:11:56 [Server] ERROR Error at SQL Query: Duplicate key name 'unq_uuid' 28.07 23:11:56 [Server] ERROR Error at SQL Query: Duplicate key name 'inx_player_name' 28.07 23:11:56 [Server] ERROR Error at SQL Query: Duplicate key name 'indx_cuboids_owner' 28.07 23:11:56 [Server] ERROR Error at SQL Query: Duplicate key name 'indx_cuboids_parent' 28.07 23:11:56 [Server] ERROR Error at SQL Query: Duplicate key name 'indx_unbreakables_owner' 28.07 23:11:56 [Server] ERROR Error at SQL Query: Duplicate key name 'indx_storedblocks_1' 28.07 23:11:56 [Server] ERROR Error at SQL Query: Duplicate key name 'indx_storedblocks_2' 28.07 23:11:56 [Server] INFO Added new indexes to database
and it hangs there until server process is killed
the same issue happens too when using sqlite
when reloading the server you get this output
28.07 23:14:42 [Server] INFO Preparing start region for level 2 (Seed: 7826167578441289788) 28.07 23:14:43 [Server] INFO Enabling PreciousStones v10.5.3 28.07 23:14:43 [Server] INFO Version 10.5.3 loaded 28.07 23:14:44 [Server] INFO MySQL Connection successful
running version 10.5.3 on spigot 1.12
Quick Question here: I don't always see it happening, do any of you experiencing this issue also use the Parkour plugin?
i have noticed this at times and its random for me but i have 70plugs so yea....
I ruled out the "Parkour" plugin on a testing server, leading it to be a preciousstones problem.
when i take preciousstones out of the directory, it fixes it
it always happens right after it successfully connects to the database, doesn't matter if its mysql or the light one
Sorry for taking so long to respond. Have been away due to personal probs. Ok so PS pulls the list of all fields from db to memory on first connect. The hanging experienced is this process taking its time, which gets longer with the more fields you have. It you wait it will eventually finish. Gonna find some time this week to see what I can do to optimize this.
i don't think its getting the first fields
sometimes its instantaneous. other (most) times its not
maybe if you can just add some more debugging indicators about what its
doing around there we can help you narrow it down
because even with a brand new install with zero fields it still took a
minute to get past that part
seems to take a pretty consistently long amount of time if it hangs at all
On Sun, May 11, 2014 at 12:05 AM, phaed420 [email protected] wrote:
Sorry for taking so long to respond. Have been away due to personal probs.
Ok so PS pulls the list of all fields from db to memory on first connect.
The hanging experienced is this process taking its time, which gets longer
with the more fields you have. Gonna find some time this week to see what I
can do to fix this issue.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/742#issuecomment-42762329
.