-
Notifications
You must be signed in to change notification settings - Fork 9
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
Segmentation fault #29
Comments
A stupid solution is for you to start another node project, such as nest.js, to do the interaction between api and the database, and to call the api interface of another node project for the samp-node server, such as through http ajax. |
@Revalto this is a problem that occurs when you are running 32bit systems and trying to access 64bit programs, or a 32bit program trying to load a 64bit library. it's possible one of npm packages depends on a 64bit library, figure out which one and maybe you can find a 32bit version or find a workaround. |
A quick search suggests you can get npm to install 32bit versions of packages: npm by default will download the precompiled versions of modules for your system which is likely 64bit while SAMP is 32bit and as a result samp-node is. |
Hello. Maybe someone has encountered this problem and knows how to fix it. The server crashes with the error "Segmentation fault" often, rarely, in absolutely different cases. It is displayed directly in the console of the NodeJS part.
I have a frequent and not a little data exchange between PAWN and NodeJS, at some point, an error can pop up, and can work without incident for several days.
I already wanted to try to watch everything through the package - "segfault-handler", but at startup I get an error - "wrong ELF class: ELFCLASS64".
Installed plugins:
crashdetect.so samp-node.so FCNPC.so sscanf.so filemanager.so streamer.so mysql_static.so gvar.so env.so
Packages used:
The text was updated successfully, but these errors were encountered: