Skip to content
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

Node 22 causing FXServer crash #3179

Open
FingerlessGlov3s opened this issue Feb 21, 2025 · 1 comment
Open

Node 22 causing FXServer crash #3179

FingerlessGlov3s opened this issue Feb 21, 2025 · 1 comment
Labels
bug triage Needs a preliminary assessment to determine the urgency and required action

Comments

@FingerlessGlov3s
Copy link

FingerlessGlov3s commented Feb 21, 2025

What happened?

We moved to FXserver b12954 after 12 hours of no problems, we upgraded oxmysql to v2.13.0 and then set our logging resource (Just uses gelf-pro to send logs to Graylog using TCP) to also use node 22, Since applying those resource changes, we've had 5 FXServer crashes. Each of them have the same stack trace far as I can tell, they are little different but most of the trace is the exact same.

There's is some chatter in the Overextended Discord and Linden confirming there's some issues going on with Node 22

We've reverted our logging resource, so when/if it crashes again it'll remove that from the new Node22 to confirm the stack trace is seen with oxmysql and not our logging resource.

Workaround will be to go back a version of oxmysql to revert the node22 change

!analyze -v results

FXServerStacktrace1.txt
FXServerStacktrace2.txt
FXServerStacktrace3.txt

Expected result

No crashing and node 22 to function as usual

Reproduction steps

Use FXserver b12954 and then run oxmysql verison v2.13.0
Leave server running as usual with players, Had roughtly 100~ players while each crash happened.

Importancy

There's a workaround

Area(s)

FXServer

Specific version(s)

FXserver b12954

Additional information

No response

@FingerlessGlov3s FingerlessGlov3s added bug triage Needs a preliminary assessment to determine the urgency and required action labels Feb 21, 2025
@prikolium-cfx
Copy link
Collaborator

Could you send me crashdump in Discord (prikolium) ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triage Needs a preliminary assessment to determine the urgency and required action
Projects
None yet
Development

No branches or pull requests

2 participants