make sure mysql-async is started before the other resources, maybe by adding a dependency.
@ChrisKylee they might not help at all, but it is the server.cfg where they should be. also you need to fill out username, password, etc in the string above.
make sure mysql-async is started before the other resources, maybe by adding a dependency.
@ChrisKylee they might not help at all, but it is the server.cfg where they should be. also you need to fill out username, password, etc in the string above.
@zr0iq it start before other resources I have no idea what to do now but in the other case when I use command /admin the console return something like that
I get this after updating… all I did is drag and drop the 3.0.11 to the same folder with the correct name and cleared cache and update the artifices!

@Keanan_Kruse is your server the latest version?
set mysql_keep_alive_seconds 60 as a convar to send a query every 60s.I personally share the idea of the mysqljs author, that there has to be something wrong within your network or computer, maybe a firewall issue, if you are experiencing it; as I fail to replicate these issues no matter how hard I try.
yeah latest server from fivem.net artifacts, do I Just paste mysql_keep_alive_seconds to the server config file?
you do not need that.
also your issue is not mysql related. I just downloaded the last copy and it works fine on my pc.
maybe you got a wrong server version? a revoked one maybe.
will try and go to a old version and report back… only thing i did is update to your 12 version and the artifacts
ok well… went back a few days and put the old mysql-async back and still crashes (facepalm) so dont think its to do with your resource… but I have not changed anything else!!
Ok so I went back to a older artifact from 6 days ago to get it to work but now im getting this with your latest version?
you have added
set mysql_debug 1
somewhere in your server.cfg
ahh yes!!! I do see that lol! ok cool so its just printing stuff but working OK I guess? never seen all that before on 3.0.0.8
Still doesn’t work for me on Linux (keep crashing after first query, version 3.0.12):
All I did is install mysql through npm install -g mysql
mysql Ver 14.14 Distrib 5.5.62, for debian-linux-gnu (x86_64) using readline 6.3
Unhandled Exception:
System.NullReferenceException: Object reference not set to an instance of an object
GlobalError: Unhandled exception in Mono script environment: System.NullReferenceException: Object reference not set to an instance of an object
(null)
Unhandled exception in Mono script environment: System.NullReferenceException: Object reference not set to an instance of an object
(null)
What kind of info do you need to resolve this problem?
I think the mysql-async git clone should be enough to run it, you do not need any modules installed.
I am not certain why there is a mono exception, since it is purely in node.
mysql.js is tested also against 5.5 so there shouldn’t be any issues. If you would feel better about it, I could make me a custom dockerfile to test for your linux version + mysql 5.5, instead of the alpine I am using.
Alright, for some reason I changed userid parameter to uid and problem has gone.
Are you planning to add MySQL.transaction support for 3.x version?
I am currently not planning to add the transaction code anytime soon, just because I do not feel like testing it extensively and debugging it with the time I have available.
But there is a development build for 3.1 in the development branch, that has some new features. Most notably the F8 -> mysql command, which allows you to get some profiled data.
Which versioun should we use for Linux servers_
Any of the newer ones? They all looked stable on in my dockers.
since updating to the latest my scoreboard does not show the players… it counts them as you can see and sees what job they have but it doesnt show their names ping etc…?
mysql command. Follow this link for an old demonstration on how it looks and behaves.