Ubuntu 16.04 Server Crash

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
J

Jaysalina

Guest
Title Ubuntu 16.04 Server Crash

Launcher Type Server

Modpack FTB Infinity Evolved

Modpack version 2.6.0

Have you modified the pack? No

Link to log file http://imgur.com/mPSkEIE

Details of the issue So I was able to recreate my server on a Ubuntu 16.04 computer. The server was on a Windows 10 computer to start but I merely made the server on the new computer and added my world and plugins through google drive.

Everything was running smoothly minus my spawn not showing up and homes gone. Other than that everything worked fine. My friend and I copied and pasted a schematic at the same time and the server of course crash. Neither of us knowing that we were pasting the same spawn which is huge. That being said... Server crashed.

I tried to type stop in the terminal but it wouldn't work the only thing I could do was exit the terminal. When I tried to restart the server it gave me this error.

Link: http://imgur.com/mPSkEIE

So far I cannot for the life of me figure out what to do. Any help would be greatly appreciated. I am completely new to all of this!

(Also tried finding the PID to kill process in terminal.)
 

compwiz91

Active Member
Nov 19, 2012
14
0
26
Somersworth, New Hampshire
Hello,
The server appears to be failing to append a log file and create a new one when it starts.
The account running the server doesn't have appropriate permissions on one of the log files,
upload_2017-6-7_10-33-39.png

This could happen if the Server is still running and you try starting a second instance while one is already running and using the file.
If your sure the server is not currently running you could try renaming the log file so it creates a new one. Be sure to check that the user account running the server has the appropriate permissions for the log folder.