New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Callbacks not firing? #19
Comments
I also tried using a
But in this case, the clients timed out and the server seems to have stopped running completely. Edit: It seems like I was able to mitigate this and get a longer-running program by adding |
this might help resolve brouznouf/fivem-mysql-async#19
Looks like this was solved on the FiveM side, beginning with artifact 298 and later. This issue can be closed. |
Awesome repro by the way, will leave it open to see if no other people have callback issue, i have currently more time to look at this. |
Should be good, did not have this issue anymore |
I'm getting a very similar error same as this. https://forum.fivem.net/t/fxserver-random-error-s/37333
It seems to be related to using MySQL.
Trying to terminate the TCP connection to MySQL at runtime does not seem to cause this error (using tcpkill, iptables, etc).
We do not necessarily get the following error, but we have had it before:
This error sometimes happens ONCE during the course of server operation, and the server continues to function...
We have also gotten a variant:
(note in this case there is no "
Error during Tick
")But when this begins happening...
as quickly as the server can output the messages, the game continues to run (and scripts generally seem to execute) but all database queries do not fire.
We've had
Error during Tick: System.NullReferenceException
occur after aSELECT COUNT(*)
(fetchScalar),SELECT
(fetchScalar), andUPDATE
(execute). It does not seem to happen when usingfetchAll()
during testing, but it may exist.I have found no correlation of query type (
SELECT
,UPDATE
) or single statement which causes this.The error seems to happen after several minutes of server uptime, and is fairly reproducible using code similar to the following:
This has occurred with artifacts 284 and 294 (and likely others) of FiveM proot on Linux.
https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/294-b2423af33c0033b34d47f1d6ec42a49d12127efa/
We have tried using the stock clone of this repository's master (1a98024), and we have also tried by building MySqlConnector v0.23.0 (
mysql-net/MySqlConnector
) on Linux using mono. After that, we have also tried replacing the .dll's that come with mysql-async with .dll's from the runtime:/usr/share/dotnet/shared/Microsoft.NETCore.App/1.1.2/System.Runtime.InteropServices.RuntimeInformation.dll
/usr/share/dotnet/shared/Microsoft.NETCore.App/1.1.2/System.Threading.Tasks.Extensions.dll
/usr/share/dotnet/shared/Microsoft.NETCore.App/1.1.2/System.Buffers.dll
After copying the .dll's from the runtime it seems to run a little longer, but it still ultimately enters the "
Error on Tick
" loop which prevents any queries from completing.The text was updated successfully, but these errors were encountered: