-
Notifications
You must be signed in to change notification settings - Fork 30
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
Server crashes on mission load. #35
Comments
Make sure you have used the tolower file and that every file is lower-case and make sure you installed both the 32 libs and 64 libs as that is a cause for the error. |
Everything is lowercase and all the libs are installed. I have to admit, on debian 7 it's a bit of a hack job to get the server to run but for the sake of this issue everything is in place. It is also not a file permission issue and I would be surprised if that could cause a memory error. So sadly the problem still persists. |
Was there ever a fix for this? |
Can't say that I remember - was quite a while ago now and I'm pretty sure the 1.7 update broke things more but I started working on DayZ Standalone stuff so I never updated my version of these files. I'm on a business trip for the next few days so I can have a look when I return is it the same error your getting? |
You could possibly follow this to generate a stacktrace when the segmentation fault happens. https://stackoverflow.com/questions/77005/how-to-automatically-generate-a-stacktrace-when-my-program-crashes/77336#77336 this might give you more info as to why it happens |
Are you having mission folder/files? |
Disclaimer: I don't know if this is still maintained. Also I noted that there's already an issue open about this, however the poster fixed his problem.
Issue: When I start the server and join the server will crash while the client shows "Receiving Mission file: 01kb/XXkb"
Now I used to play on Panthera and the server would actually start every few restarts without crashing but now that I switched to Lingor it doesn't work anymore. I did a full fresh install and tried debugging everything but no luck.
Starting the server without screen (so you can see crash messages) yields:
And that's that.
The text was updated successfully, but these errors were encountered: