dynmap
dynmap copied to clipboard
SQL ErrorCode: 1064, SQLState=42000.
Issue Description: SQL error 1064 after render
Dynmap Version: 3.4 Beta 5 Server Version: Paper 1.19 build 78 Pastebin of Configuration.txt: https://pastebin.com/KHQPbvv7 Server Host: Selfhosted Pastebin of crashlogs or other relevant logs: https://pastebin.com/WWeZw4ws Other Relevant Data/Screenshots: [08:22:56 ERROR]: [dynmap] SQLException: Tile enum error [08:22:56 ERROR]: [dynmap] ErrorCode: 1064, SQLState=42000 [08:22:56 ERROR]: [dynmap] Message: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'OFFSET 0 LIMIT 100' at line 1 [08:22:56 ERROR]: [dynmap] ConnectionString: jdbc:mysql://localhost:3306/dynmap?allowReconnect=true
Steps to Replicate: /dynamap fullrender world
Please give new SNAPSHOT builds a try - should be fixed (https://dynmap.us/builds/dynmap)
I think is solved thx but have another sql error "timeout"
[11:39:22] [Dynmap Render Thread/ERROR]: [dynmap] SQLException: Standalone file read error [11:39:22] [Dynmap Render Thread/ERROR]: [dynmap] ErrorCode: 0, SQLState=08S01 [11:39:22] [Dynmap Render Thread/ERROR]: [dynmap] Message: The last packet successfully received from the server was 47 959 882 milliseconds ago. The last packet sent successfully to the server was 47 959 914 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. [11:39:22] [Dynmap Render Thread/ERROR]: [dynmap] ConnectionString: jdbc:mysql://localhost:3306/dynmap?allowReconnect=true&autoReconnect=true [11:39:22] [Dynmap Render Thread/ERROR]: [dynmap] CausedBy: The last packet successfully received from the server was 47 959 882 milliseconds ago. The last packet sent successfully to the server was 47 959 914 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. [11:39:22] [Dynmap Render Thread/ERROR]: [dynmap] CausedBy: Connexion ré-initialisée par le correspondant
My storage config: storage: hostname: localhost port: 3306 database: dynmap userid: dynmap password: xxxxx prefix: "" flags: "?allowReconnect=true&autoReconnect=true"
On the third line of that error dynmap states what you can do to midigate this problem, did you do that?
Look my flags !
no need to shout, wait_timeout is not a client setting, it is a mysql server setting. https://mariadb.com/docs/reference/mdb/system-variables/wait_timeout/
The message say. Setting in MySQL server or use flag.
I use flag and plugin don't auto-reconnect.
My MySQL server dont need bigger timeout.
the next beta / release should have a fix, according to the commits from the dev: https://github.com/webbukkit/dynmap/commit/0ab9c9e47b2a1d5ec00c12076459850603b9aa09
Thanks dude, i wait for this !
if you are wanting to try it out, you can download the latest snapshot from the build server: https://dynmap.us/builds/dynmap
I try Snapshot and tell you if it work