+- 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: Server stopping after left idle? (/thread-2939.html)
Server stopping after left idle? - tikitofu - 04-11-2017
Hi. I'm not sure how long it takes for this to happen, but when I leave my pi3 idle, it seems to stop the server. I have to ssh in and manually start it up again.
I've been running ./Cuberite in /home/pi/Server.
Am I missing any settings/steps? THANKS!
RE: Server stopping after left idle? - yoboykai - 04-11-2017
Do you get an error message when this happens?
RE: Server stopping after left idle? - xoft - 04-11-2017
Have a look at the log files that the server generates in the "logs" subfolder, is there any error message at the end of the file that would indicate a problem?
RE: Server stopping after left idle? - tikitofu - 04-12-2017
Here is the latest log. Great program by the way!
[11:55:51] --- Started Log --- [11:55:51] Cuberite Jenkins gcc armhf Release (master) build id: #698 [11:55:51] from commit id: 7960d142ca3e28e0e4550faf131398899dca90dc built at: Fri 7 Ap$ [11:55:51] Creating new server instance... [11:55:51] Reading server config... [11:55:51] Starting server... Info [11:55:51] Compatible clients: 1.8.x, 1.9.x, 1.10.x, 1.11.x Info [11:55:51] Compatible protocol versions 47, 107, 108, 109, 110, 210, 315, 316 Warn [11:55:51] WebServer: The server will run in unsecured HTTP mode. Info [11:55:51] Put a valid HTTPS certificate in file 'webadmin/httpscert.crt' and its corre$ [11:55:51] Loaded 726 crafting recipes [11:55:51] Loaded 52 furnace recipes and 66 fuels [11:55:51] Loaded 88 brewing recipes [11:55:51] -- Loading Plugins -- [11:55:51] Initialised Core v.15 [11:55:51] Initialized ChatLog v.3 [11:55:51] -- Loaded 2 Plugins -- [11:55:52] Preparing spawn (world): 11.25% (45/400; 44.69 chunks / sec) [11:55:53] Preparing spawn (world): 31.00% (124/400; 78.14 chunks / sec) [11:55:54] Preparing spawn (world): 55.25% (221/400; 95.85 chunks / sec) [11:55:55] Preparing spawn (world): 79.75% (319/400; 96.84 chunks / sec) [11:55:57] Preparing spawn (world_nether): 17.75% (71/400; 70.37 chunks / sec) [11:55:58] Preparing spawn (world_nether): 47.50% (190/400; 117.71 chunks / sec) [11:55:59] Preparing spawn (world_nether): 77.25% (309/400; 117.82 chunks / sec) [11:56:01] Preparing spawn (world_the_end): 17.00% (68/400; 67.06 chunks / sec) [11:56:02] Preparing spawn (world_the_end): 46.25% (185/400; 115.50 chunks / sec) [11:56:03] Preparing spawn (world_the_end): 76.50% (306/400; 120.64 chunks / sec) Warn [11:56:04] Did not find an acceptable spawnpoint. Generated a random spawnpoint positio$ Warn [11:56:04] Cannot listen on port 25565: 98 (Cannot bind IPv6 socket to port 25565: 98 ($ Err [11:56:04] Couldn't open any ports. Aborting the server [11:56:04] Unloading worlds... [11:56:05] Disabled Core! [11:56:05] Cleaning up... [11:56:05] Shutdown successful! [11:56:05] --- Stopped Log ---
So I believe this happens when I try to log in at work - which is likely the cause:
Code:
Warn [11:56:04] Cannot listen on port 25565: 98 (Cannot bind IPv6 socket to port 25565: 98 ($RE: Server stopping after left idle? - xoft - 04-12-2017
That message means that something is already listening on the port, or there was some other obscure error. Do you have another Minecraft server running on that machine? If you change the port number in settings.ini (with the server not running, of course), does the message appear after starting the server? If you do a "netstat -nlat" while Cuberite is not running, do you see the port 25565 as used?
RE: Server stopping after left idle? - tikitofu - 04-13-2017
I do not have another server. However, I haven't yet tested trying another port. Here are the results from netstat:
Code:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 320 192.168.1.202:22 192.168.1.108:52571 ESTABLISHED
tcp6 0 0 :::445 :::* LISTEN
tcp6 0 0 :::139 :::* LISTEN
tcp6 0 0 :::22 :::* LISTENafter starting the server
Code:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 192.168.1.202:22 192.168.1.108:52571 ESTABLISHED
tcp 0 256 192.168.1.202:22 192.168.1.108:52767 ESTABLISHED
tcp6 0 0 :::25565 :::* LISTEN
tcp6 0 0 :::445 :::* LISTEN
tcp6 0 0 :::8070 :::* LISTEN
tcp6 0 0 :::139 :::* LISTEN
tcp6 0 0 :::22 :::* LISTENRE: Server stopping after left idle? - tikitofu - 04-13-2017
I found that when I close the putty terminal, ending the session, the server becomes unreachable. Should I not be using ssh to start it?
RE: Server stopping after left idle? - Mathias - 04-13-2017
I recommend using Cuberite together with screen or tmux. This ensures that the server keeps running when you exit putty, and you can access the console later.
These are the commands I use for my server:
To start the server:
Code:
screen -dmS server sh -c 'while true; do sleep 1; cd $HOME/Server; ./Cuberite && break; done'To access the console, use
Code:
screen -r serverTo exit the console, hold CTRL and A, release them, and press D.