How to Start a Sky Factory 3 Server on Ubuntu/Linux

[mvdude3]

I'm trying to run all the Sky Factory 3 mods (it's just a bunch of 1.10 mods) on a normal Amazon AWS Ubuntu Linux server. Sky Factory has an option where you can download a server locally that already has all of the mods in, and has it's own .jar file. What I'm trying to do is move all the mods from Sky Factory into my Ubuntu, and run the it with an Amazon AWS server (so I don't give out my ip to people). I'm not sure if I should run the server by moving the Sky Factory .jar file to my main .jar file, and do


"sudo java -Xmx1g -Xms1G -jar FTBserver-1.10.2-12.18.3.2281.jar nogui"


or run all the mods at once using 1.10 Forge:


"sudo java -Xmx1G -Xms1G -jar forge-1.10.2-12.18.3.2185-universal.jar nogui".


Neither of them is working, and they're both creating some strange [STDERR] and "at" errors. If anyone has any ideas about how to fix this, please help me.


To make it simpler, I'm trying to run Sky Factory 3 on my own Amazon AWS Ubuntu/Linux server.


Thanks.

 

[grandrolf]

You should use the provided ServerStart.sh (that will use settings from settings.sh)
(you may need to change attributes on ServerStart.sh to be able to run it)

You should not start Minecraft with sudo.

If i remember right the allocated ram in settings.sh is 3gb - 1gb that you're trying is not going to work, you'll need at least 3gb (perhaps more depending on your player base)

 

[mvdude3]

You should use the provided ServerStart.sh (that will use settings from settings.sh)
(you may need to change attributes on ServerStart.sh to be able to run it)

You should not start Minecraft with sudo.

If i remember right the allocated ram in settings.sh is 3gb - 1gb that you're trying is not going to work, you'll need at least 3gb (perhaps more depending on your player base)

#!/bin/sh
# Fix work directory
# Some GUIs set wrong working directory which breaks relative paths
cd -- "$(dirname "$0")"
# makes things easier if script needs debugging
if [ x${FTB_VERBOSE} = xyes ]; then
set -x
fi
# Read pack related settings from external setting file
. ./settings.sh
# Read settings defined by local server admin
if [ -f settings-local.sh ]; then
. ./settings-local.sh
fi
# cleaner code
eula_false() {
grep -q 'eula=false' eula.txt
return $?
}
# cleaner code 2
start_server() {
"$JAVACMD" -server -Xms${MIN_RAM} -Xmx${MAX_RAM} -XXermSize=${PERMGEN_SIZE} ${JAVA_PARAMETERS} -jar ${FORGEJAR} nogui
}
# run install script if MC server or launchwrapper s missing
if [ ! -f ${JARFILE} -o ! -f libraries/${LAUNCHWRAPPER} ]; then
echo "Missing required jars. Running install script!"
sh ./FTBInstall.sh
fi
# check eula.txt
if [ -f eula.txt ] && eula_false ; then
echo "Make sure to read eula.txt before playing!"
echo "To exit press <enter>"
read ignored
exit
fi
# if eula.txt is missing inform user and start MC to create eula.txt
if [ ! -f eula.txt ]; then
echo "Missing eula.txt. Startup will fail and eula.txt will be created"
echo "Make sure to read eula.txt before playing!"
echo "To continue press <enter>"
read ignored
fi
echo "Starting server"
rm -f autostart.stamp
start_server
while [ -e autostart.stamp ] ; do
rm -f autostart.stamp
echo "If you want to completely stop the server process now, press Ctrl+C before the time is up!"
for i in 5 4 3 2 1; do
echo "Restarting server in $i"
sleep 1
done
echo "Rebooting now!"
start_server
echo "Server process finished"
done


That mouthful is all that's in the ServerStart.sh.
Should I just run that in my own Ubuntu?

 

[grandrolf]

Yes, it's pretty standard.

Every section is commented stating what it's doing.

And don't run this as sudo either.