+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Discussion (https://forum.cuberite.org/forum-5.html)
+--- Thread: Deadlock detected, aborting the server (build id: #396) (/thread-2396.html)
Pages:
1
2
Deadlock detected, aborting the server (build id: #396) - TheSnowman - 03-04-2016
Hi@all,
and sorry, if my problem maybe exists within another / older post, but I didn't find anything regarding my problem.
May be I've did something wrong or not in the right way, but I'm not a regulary Linux User, so please forgive me ;-)
I've installed some weeks ago on my Pi 2 a current raspbian version and some days ago the current version of Cuberite - the server starts fine, in my point of view ;-)
Code:
Linux MC-RASPI 4.1.7-v7+ #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Mar 3 14:56:18 2016 from nbook-02-moritz.local
pi@MC-RASPI ~ $ byobu
Attaching: [tmux____0]
enable HTTPS support
[15:56:24] Loaded 449 crafting recipes
[15:56:24] Loaded 20 furnace recipes and 56 fuels
[15:56:24] Loaded 88 brewing recipes
[15:56:24] -- Loading Plugins --
[15:56:24] Initialized ChatLog v.3
[15:56:24] Initialised Core v.15
[15:56:24] Initialized TransAPI v.1
[15:56:24] -- Loaded 3 Plugins --
[15:57:04] Preparing spawn (world): 22.50% (90/400; 89.46 chunks / sec)
[15:57:05] Preparing spawn (world): 57.25% (229/400; 138.72 chunks / sec)
[15:57:06] Preparing spawn (world): 92.25% (369/400; 139.44 chunks / sec)
[15:57:08] Preparing spawn (world_end): 25.00% (100/400; 93.90 chunks / sec)
[15:57:09] Preparing spawn (world_end): 60.25% (241/400; 128.30 chunks / sec)
[15:57:10] Preparing spawn (world_end): 94.75% (379/400; 128.61 chunks / sec)
[15:57:11] Preparing spawn (world_nether): 17.75% (71/400; 70.23 chunks / sec)
[15:57:12] Preparing spawn (world_nether): 44.00% (176/400; 104.48 chunks / sec)
[15:57:13] Preparing spawn (world_nether): 71.25% (285/400; 107.71 chunks / sec)
[15:57:14] Preparing spawn (world_nether): 95.25% (381/400; 95.90 chunks / sec)
[15:57:14] Startup complete, took 63908ms!My son and his friend are playing a little bit in the Cuberite-created world and after some undefined actions / minutes the server crashes and writes the following messages:
Code:
[16:57:16] Deadlock detected, aborting the server
[16:57:32] D: | Cuberite has encountered an error and needs to close
[16:57:32] Cuberite Jenkins gcc armhf Release (master) build id: #396
1 Mar 12:47:02 CET 2016
./Cuberite[0x1ebc1c]
/lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer_v2+0x0)[0x76c6f160]
pi@MC-RASPI ~/Server $ [16:57:16] Deadlock detected, aborting the server
needs to close
[16:57:32] Cuberite Jenkins gcc armhf Release (master) build id: #396
[16:57:32] from commit id: 48532d86cf3a4d549e9f7e6697d821946d7fa341 built at: Tue 1 Mar 12:47:02 CET 2016
./Cuberite[0x1ebc1c]After starting the server again, the last view minutes of playing are not saved.
And this kind of Deadlock happens very often, so gaming with that situation is not funny...
What could I do? Did I do something wrong?
Should I change the configuration?
What else information you need to make an analyse?
Thank you in advance.
RE: Deadlock detected, aborting the server (build id: #396) - Rekuen - 03-04-2016
Could you post your Deadlock settings?
You can find them in the settings.ini file.
(edit by xoft: removed the needless quote)
RE: Deadlock detected, aborting the server (build id: #396) - Seadragon91 - 03-04-2016
If you are exploring the world much and quick (visiting not generated chunks), can overload the chunk generator and cause a deadlock.
Another possible is that a combination of actions, could run into a deadlock.
RE: Deadlock detected, aborting the server (build id: #396) - NiLSPACE - 03-04-2016
Probably the latter. You'll have to generate allot of chunks to overload the chunk generator. Were you doing anything that made the server stop responding?
RE: Deadlock detected, aborting the server (build id: #396) - Schwertspize - 03-04-2016
Maybe this is related to my crash some time ago. I executed /regen too often i think (power tool.....)
RE: Deadlock detected, aborting the server (build id: #396) - xoft - 03-04-2016
Hello, and welcome to the forum.
A deadlock could be caused by a multitude of factors, most of them point at some issues at the program itself. We need more information in order to be able to identify the problem.
The server should produce a "core" file when it stops with a deadlock, have a look in the server's folder if there is such a file; if so, please post it somewhere online for us to analyse. If the file is not there, you should do a "ulimit -c unlimited" just before launching the server, this will tell the OS to allow creation of such files.
Thanks.
RE: Deadlock detected, aborting the server (build id: #396) - TheSnowman - 03-04-2016
Hello @ all and thanks for your multiple reply!
I will try to answer all your questions as fast as I can:
Deadlock-Settings within the settings.ini:
I didn't even know, that there are Deadlock Settings!
Here are the (standard) entry of my settings.ini:
Code:
[DeadlockDetect]
Enabled=1
IntervalSec=20About the "core" file: has this file to be directly into the Server folder or in any kind if subfolder?
Within the subfolder there isn't such a file with that name...
I've just executed your command "ulimited..." and started the Cuberite Server.
Now waiting for my son, comming back from school and testing the server.
As soon as we have the next Deadlock, I will have a look, if this had produced a core-File and will make that File available for you...
Is it possible to attach it here?
Just a hint, because I've forgot to tell in my first post and maybe it's part of the problem...
To run Minecraft, I start it within byobu, because screen didn't work on my raspbian / Pi 2...
I don't know, if this is important for your analyze...
Thank you so much for your help
RE: Deadlock detected, aborting the server (build id: #396) - TheSnowman - 03-04-2016
OK, we had another Deadlock and the Server wrote a Core File - i hope you can download it from my Google Drive:
https://drive.google.com/folderview?id=0BzEt4qR9JqzZQXlkVTVNeVEzZmM&usp=sharing
I compressed it with 7-zip Version 9.20 without any password: core.7z
RE: Deadlock detected, aborting the server (build id: #396) - xoft - 03-04-2016
It would be great if you could add the server log corresponding to that core file. The logs are in the "logs/" subfolder.
Okay, linux guys, anyone up for the analysis?
RE: Deadlock detected, aborting the server (build id: #396) - TheSnowman - 03-04-2016
I've added the Server Logs to the 7-zip-File "Cuberite-Server-Logs.7z" and uploaded it into the same Google-Drive folder as the Core File (see post before)