FXServer exits with SIGSEGV
What happened?
Sometimes, at random times the fxserver crashes with a SIGSEGV and automatically restarts triggered by txadmin. I only noticed this happening when there are many player on the server. I found some other issues about something like that saying its about the recent update to node js 22. I cant really find any errors or problems except for this error by txadmin: [21:02:54][tx:FXProc][5211] FXServer Exited (SIGSEGV). [21:02:54][tx:FXProc][5211] FXServer Closed (SIGSEGV). [21:02:55][tx:FxMonitor] Restarting server: Server process close detected. [21:02:55][tx:FxMonitor] Last HealthCheck error debug data:
{ message: 'connect ECONNREFUSED 127.0.0.1:27000', code: 'ECONNREFUSED', error: 'Response object is undefined.' }
I just updated from 13227 to 13890 on the server artifact in hopes this is already solved, I cant really test this as it just accours randomly. I also noticed this only happens in the evening here -> very probably unrelated Also I already checked for performance issues but all scripts take very low performance
Expected result
Dont exit on a SIGSEGV
Reproduction steps
- Use any artifact after node 22 update
- Have some players on the server
Importancy
Crash
Area(s)
FXServer
Specific version(s)
FiveM 3258, FXServer 13227, linux hosted via pterodactyl
Additional information
No response
I just saw in txadmin that I would be running node js vers v16.9.1, could that be causing this error?
Did you figure this out by any chance? @Kaanhehe
no not yet, I did however find out that our server also crashes if somthing related to money happens like giving money or checking it, idk how that helps
Same
on 13943
I have the same type of error that happens, it's totally random it seems, at first I thought it was related to restarting resources in game, but after spending the evening without restarting any resource my server suddenly restarted 3 times in the space of a few minutes.
tx: v8.0.1 | fx: b13890/Ptero
I have the same type of error that happens, it's totally random it seems, at first I thought it was related to restarting resources in game, but after spending the evening without restarting any resource my server suddenly restarted 3 times in the space of a few minutes.
tx: v8.0.1 | fx: b13890/Ptero
Can you check if this somehow can be related to something being triggered? I noticed on my server that if the anticheat detects someone having to much money and kicks the player from the server it crashes.
I have the same type of error that happens, it's totally random it seems, at first I thought it was related to restarting resources in game, but after spending the evening without restarting any resource my server suddenly restarted 3 times in the space of a few minutes. tx: v8.0.1 | fx: b13890/Ptero
Can you check if this somehow can be related to something being triggered? I noticed on my server that if the anticheat detects someone having to much money and kicks the player from the server it crashes.
I don't have the anticheat active, and I don't really see where it comes from. I need to ask the players what they do when the server crashes.
Same build, same issue, we are rolling back to an older build
Same build, same issue, we are rolling back to an older build
which version did you install?
same on latest build
did u ever find a fix
I'm experiencing these same issues on 16811.
I can give an update on this, I did never find a fix for this, tho its not guaranteed to happen on the newest builds, I am still using the latest builds with multiple servers and this error never appeared again, seems to be a very specific issue with either the system the server is running on, or something triggering this inside a resource.
I have the same type of error that happens, it's totally random it seems, at first I thought it was related to restarting resources in game, but after spending the evening without restarting any resource my server suddenly restarted 3 times in the space of a few minutes.
tx: v8.0.1 | fx: b13890/Ptero
I just saw this comment, when I had this issue I was also using Pterodactyl for running the server, so this could be related, I don’t remember having this issue without pterodactyl