ryvix

How will this work with 8.7? Do we have to do anything differently?

I would think there is room for improvement in the future since this is just alpha. I have never used it on wine, at least I don't think, just what this script does now. All I can compare it to is a Minecraft server and it's probably at least 5-10 times more CPU intensive than Minecraft at this point. Not sure about the RAM usage but I have 32 gigs of RAM and it only takes up about 1.3 gigs so I'm not really worried about that. I set max players to 10. I've had about 5 on at a time at the very most and haven't noticed any lag or anything but it was using a lot of CPU. Though I'm not sure if I would really be able to tell the difference between lag and a buggy game at this point. The server is running Ubuntu 14.04 and has 32 gigs of RAM, SSD drives and Intel Xeon E3 1245v2 4 core/8 thread processor.

I sent a PM with this info. True, only if the machine is completely dedicated to this game and I know exactly what's going on would I get the machine to restart during a game restart if necessary and plus I can easily write a script to do this. That is definitely a possibility if people were to turn such an option on. Perhaps it could just give notifications that there is an update of some sort. If it could give a notification or an email saying there is an update ready and to click here to apply. I guess to click though you would have to have some sort of web interface control panel thing but that would be another project or layer to this. Doing things manually isn't so bad yet I suppose. Oh nice! That should be perfect. Thanks!

Hey there, I had an idea. I think the server gets slightly wonky eventually for whatever reason, but it's alpha so I guess that's to be expected. I don't really know what all exactly but just little things feel different after a restart. So is there some way to do an announcement for auto restarts? I was hoping to setup auto restarts every 6 hours or something so that it gives a series of warnings saying it's about to restart. For example: The server is restarting in 5 minutes. The server is restarting in 1 minute. The server is restarting in 30 seconds. The server is restarting in 10 seconds. The server is restarting in 5 seconds. 3 2 1 The server is restarting now! Then it waits for a small period of time. Then it restarts. When the server is down it could even optionally do a backup before starting up again or restart the system (if there were kernel updates installed or something) or optionally update things automatically in the future or at least check for updates and optionally send an email if there is an update for this script or for 7dtd or whatever else there happens to be to check for updates for. This could help to automate things a little but give us a chance to manually update if we wanted to so things don't break. I saw this but it doesn't seem to work quite right for me: http://7daystodie.com/forums/showthread.php?7246-Simple-Status-Script Anyway, just an idea.

Ah yes, maybe tar is the culprit. That would make sense. Maybe the user is being created the same as what's in the tar file somehow instead of ignoring the user permissions. Thanks for the other info too. Pretty neat stuff! Can't wait to see what the future holds. Oh I noticed another thing, in the players.xml file in the instance if the nick has a space in it then it gets cut off at the first space. Not sure if that's intended or what but thought I should mention it anyway. Thanks again =) Edit: I noticed it also in the players.log file.

I had an issue with file permissions. Seems it has used user 1000 which is a different user than sdtd on my system and it has seemingly chowned a lot of things to that user for some reason and messed a bunch of things up until I chowned them back to root. I think these included the /home, /usr, /var and /etc folders as well as the folders used or created by the bootstrap script where it installed files. For example /usr, /usr/local, /usr/local/bin, /usr/local/lib, /usr/local/lib/7dtd were all owned by user 1000. So was the /etc, /etc/cron.d, and the /etc/cron.d/7dtd-backup file and whatever else there was. It's very odd considering that not only is this not the right user but it shouldn't be touching those folders in the first place. I realize everything probably shouldn't run as root but it seems this script requires it. Luckily I don't really have anything else on this server other then some inactive stuff I was testing before. If it ever ends up not running as root then there are some things in /home/sdtd that are owned by root which may cause issues too but I'm sure that would get sorted out. So anyway, once I fixed that I created a cronjob to remove old backups. I simply modified the 7dtd-backup cron file that was added and added another cron to it. 5 * * * * root nice -n 19 find /home/sdtd/backup/* -maxdepth 0 -type d -mmin +1440 -exec rm -rf {} \; > /dev/null 2>&1 Make sure to leave a blank line at the end of the cron file. It removes any backups that are older than 24 hours. Change the number -mmin +1440 to remove files older than that number of minutes. You just have to make sure to download them before they get deleted in case you ever need them. I changed the times because I don't like running things exactly at the top of the hour since other cronjobs will often run then and potentially cause some lag. I also added nice to everything to help prevent lag as well. It might be good to just rsync them off to another server but it might be nice if it compressed them first to save bandwidth and disk space. I tried to add a cron to do this but something in the backup script is conflicting with it. Probably the way you copy the folder and then rsync it. So if it was going to compress it then it would have to be compressed in there somehow which would probably be better anyway. I'm not sure exactly what it's doing there with the rsync parameters but I know the backups work because I used one.

Thank you very much for your help! I got it to work by deleting everything and starting over. I deleted those folders you mentioned and the stuff in /tmp that I found. Woohoo! =)

Hi there, By installing I just meant when running the boostrap.sh file. I just created a brand new instance just to test and it has the exact same problem with not showing on the public servers list. I just tested and I can still connect to it. So maybe it's something messed with the files like you say but I don't know what. I know I had some issues with Steamguard at the start and had to disable it so I could even get the updateengine part to login to Steam. Maybe that somehow messed it up? Here is the output.log from after I started the instance: http://pastebin.com/9KKxHm6D I have now allowed port 80 and it makes no difference so I don't think that's it. If I could somehow uninstall and start over that would be ok if that's what has to happen for it to work. I had it do backups. I'm just not 100% sure which files to remove and whatnot because I'm pretty sure it has put some in other places on the server. Also, if you have a donation button somewhere for Paypal I would send you a donation =) Thanks!

Thank you very much! I have tried to setup a dedicated server with this on Ubuntu 14.04 and it works for the most part. I had to install some of the deps but thats ok. There is also a couple issues I am having which I was wondering if you could help with. 1. When I do 7dtd.sh updateengine I get some things that look like errors. This is the output: http://pastebin.com/PUWxQwbw What's odd is that there is no /home/buildbot on my machine so I'm not sure why it shows that. 2. In the instance log I get this line a bunch: Fallback handler could not load library /home/sdtd/engine/7DaysToDie_Data/Mono/x86/SteamworksNative I get some others as well that say they are harmless but this one doesn't say it's harmless. Plus when installing it said something about SteamworksNative.dll not being found. 3. I cannot get the server to show up in the public servers list even though I have set it as public. I can however connect to it if I add it manually to favourites. I couldn't find anywhere which ports I should open. I researched and found that only ports 25000-25002 UDP are required. I ran this command: ufw allow 25000:25003/udp I can connect with that but I still don't see it in the server list. I have tried doing: ufw allow 25000:25003/tcp But that still doesn't work. I have also tried: ufw allow 35000:35003/udp and ufw allow 35000:35003/tcp But that still doesn't work. When the server starts it shows using another port that randomly changes and port 27036 which never changes and I have tried allowing that through tcp and udp but it still doesn't work. So maybe you could give some straight up iptables rules to setup the server from scratch or something that makes it show up in the server list? That's about all I have noticed so far. The only other thing I'm wondering is if this will be lower performance than a straight up windows server or maybe better. The server is running Ubuntu 14.04 and has 32 gigs of RAM, SSD drives and Intel Xeon E3 1245v2 4 core/8 thread processor. Do you have any recommended player limit to set for such a server? Thanks again!