SylenThunder

No, zero logs, which is super annoying. It's like it dies before it can create them. I get one file stdout.log, and it's empty. Did some further poking, and commented out the 64-bit options in /usr/local/lib/7dtd/commands/start.sh. (lines 60, 61, 62) Now it will start in 32-bit without any issues. Log shows 64-bit OS though... 2016-03-27T11:24:56 0.167 INF Version: Alpha 14 (b92) Compatibility Version: Alpha 14, Build: Linux 32 Bit 2016-03-27T11:24:56 0.168 INF System information: 2016-03-27T11:24:56 0.303 INF OS: Linux 3.13 Ubuntu 14.04 64bit I really really don't want to be stuck in 32-bit again, and I have no idea why my server is doing this. I helped a buddy get his up and running with absolutely no issues at all, and it's running 64-bit just fine. Something's got to be missing is the only thing I can think of, but I've installed all the prerequisites, double-checked all the updates, and it simply will not launch.

From my first post on the issue I'm still tinkering, but it's still not making any progress. If it would load enough to create some kind of log, that would be really helpful. >.<

yeah, it's there. ran all of the commands before starting, just to make sure everything was updated. no dice. And no log is generated since it takes maybe 2 seconds to fail.

I am at a complete loss here. I do not understand what has gone wrong at all. I updated everything, I re-created my world. I get... root@7DTD:~# 7dtd.sh start Home Failed! root@7DTD:~# SO I figure it's something in the much tinkering I did with 64-bit or Ubuntu 15 when I was playing with a13.8. I wipe the server completely. Install Ubuntu server 14 LTS. Install the server using Alloc's scripts. Create the instance. Edit the config.xml in /home/sdtd/instances/Home/config.xml to remove the loot and craft timer lines. Start the server. root@7DTD:~# 7dtd.sh start Home Failed! root@7DTD:~# We're as vanilla as it gets here, and I cannot for the life of me get this thing to start. Any ideas?

Sure thing. 32-bit First Run http://pastebin.com/zKc0J3eP Second Run http://pastebin.com/tNqwF0Ar (Removed some of the CBSM queries to shrink the size for pastebin.) 64-bit http://pastebin.com/HRrNMNCW I posted both 32-bit runs because the first one I started, saw in the log it loaded 32-bit, and then shut it down. The second run was after the attempt to run 64-bit and getting the error. It's really strange because no changes were made to any of the xml files at all, and I was successfully running this on 64-bit before I wiped my system.

Ok, this is for Alloc, or anyone else who has some idea of what in the world is going on. Wiped my server. Installed Ubuntu 15.10 Server Installed the Pre-requisites. Installed the server. Ran the updateengine, updatescripts, and updatefixes. Created the instance, started the server. It's peachy. Shut server down, and edit usr/local/lib/7dtd/commands/start.sh to make it run in 64-bit. Start server, it crashes. Gives the following error... 2016-03-17T13:13:27 21.110 INF StartAsServer2016-03-17T13:13:27 21.118 INF createWorld: Navezgane, Navezgane, GameModeSurvivalMP Exception: Block with name 'rockResource02' not found! at WorldBiomes.E (System.String ) [0x00000] in <filename unknown>:0 at WorldBiomes.D (Byte , System.String , System.Xml.XmlElement , Boolean ) [0x00000] in <filename unknown>:0 at WorldBiomes.D (Byte , System.String , System.Xml.XmlElement , Boolean ) [0x00000] in <filename unknown>:0 at WorldBiomes.G (System.Xml.XmlDocument , Boolean ) [0x00000] in <filename unknown>:0 at WorldBiomes..ctor (System.Xml.XmlDocument _genxml, Boolean _instantiateReferences) [0x00000] in <filename unknown>:0 at GameManager.WH (System.String , System.String ) [0x00000] in <filename unknown>:0 at GameManager.ON () [0x00000] in <filename unknown>:0 at GameManager.StartGame () [0x00000] in <filename unknown>:0 at ConnectionManager.Net_ServerInitialized () [0x00000] in <filename unknown>:0 at NetworkCommon.StartServers (System.String _password) [0x00000] in <filename unknown>:0 at MainMenuMono.Start () [0x00000] in <filename unknown>:0 (Filename: Line: -1) Switch it back to 32-bit. Start server, and it runs just peachy. Any clues why I'm getting a blocks.xml error when running 64-bit?

It's not like you cannot mod it to be a bigger, or infinite map.

Editing startserver.sh always worked before without issues to put it in 64-bit. (Since a12, I've run more stable on the 64-bit than 32.) Tested with editing line 60 in /usr/local/lib/7dtd/commands/start.sh. It does load the 64-bit version. So the real question is, what changed? Because I never had to edit this file to run the 64-bit with Alloc's scripts before.

Yeah, I'm certain something is goofy. Yes it broke the line breaks in the copy. I can't figure out why it's doing this on two different systems though. Sadly, by newly-created test platform crashed the kernel today and I cannot get it back up. Either the hardware is fried, or I dunno. don't feel like messing with it. I think I'll just copy the 64-bit file and rename it to the 32-bit file for now. LOL. Edit: Nope. that didn't work. I start it now, and it says "Failed!". Even tried flipping the comments around in startserver.sh. I've got a real case of weird going on here. Ok, I'm stupid. permissions issue. It's up again, but I can still only get 32-bit for some stupid reason.

OK. I don't get it. I modified startserver.sh to #if [ "$(uname -m)" == "x86_64" ]; then ./7DaysToDieServer.x86_64 -logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt -quit -batchmode -nographics -dedicated $PARAMS #else # ./7DaysToDieServer.x86 -logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt -quit -batchmode -nographics -dedicated $PARAMS fi And yet the log is still showing 32-bit. Going to have to start a fresh box up and test on it I guess. Edit: New box, fresh install, and still I get... 2016-02-22T21:19:41 0.087 INF Version: Alpha 13.8 (b7) Compatibility Version: Alpha 13.8, Build: Linux 32 Bit 2016-02-22T21:19:41 0.087 INF System information: 2016-02-22T21:19:41 0.129 INF OS: Linux 4.2 Ubuntu 15.10 64bit >.<

OK. I don't get it. I modified startserver.sh to #if [ "$(uname -m)" == "x86_64" ]; then ./7DaysToDieServer.x86_64 -logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt -quit -batchmode -nographics -dedicated $PARAMS #else # ./7DaysToDieServer.x86 -logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt -quit -batchmode -nographics -dedicated $PARAMS fi And yet the log is still showing 32-bit.

I can live with it not showing up. LOL. Everyone uses my IP address.

Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-77-generic x86_64) * Documentation: https://help.ubuntu.com/ System information as of Sun Feb 21 16:19:32 EST 2016 System load: 0.01 Processes: 118 Usage of /: 73.6% of 48.72GB Users logged in: 0 Memory usage: 7% IP address for eth0: 192.168.0.143 Swap usage: 0% Graph this data and manage this system at: https://landscape.canonical.com/ 38 packages can be updated. 0 updates are security updates. Last login: Sun Feb 21 16:19:10 2016 from 192.168.0.5 root@7Days2Die:~# uname -m x86_64 root@7Days2Die:~# Which is why I'm confused now. It used to run 64-bit just fine.

Ok dangit. I commented it out to run in 64-bit. So I guess that's not working. Ok, I went and double-checked, and as far as I can see, it should be loading 64-bit. Here's what my startserver.sh looks like. So if that's not working, how do I fix it?

I would keep it under 10. Technically MP only supports 8, but I can do 20 with 16GB RAM on a dedicated Linux blade. Once we get past 15, and a lot are exploring, there is a bit of latency though. (Which truly, could be a result of the very high active zed settings I have, and not the number of players.)

Your server is most likely crashing due to a lack of RAM. I really cannot stress enough that for a dedicated server, you must have 8GB to expect to run it, and 12-16GB if you want it to run well. (32-bit Linux is limited to 4GB of RAM usage, but you must have all 4GB of RAM available and not shared with the system. Even then, I would not recommend that for more than 4 people on a Navezgane map) Are you renting a server, or do you have your own hardware?

Sure thing. It didn't show in the list previously, but sometime after probably 13.5 it has. I restarted the server so you'll have a fresher log. http://pastebin.com/a3EL3qZ9 Here's a shot of the server list. It's the very first one

Odd. Mine does. Although sometimes it doesn't, but I think that was my ISP.

The server used to allow anonymous installs, but they stopped that. Could you just have it call stored data and use that for the authentication like Allocs updateengine script does?

Yeah, no change is required for 13.7. With some upgrades, you may need to re-install the mod afterwards. I know my Linux dedi is like this.

It works. Or at least last I checked it did. It spawns the horde at a completely random location.

NOTE: If you have a PC Bug Report, or are a Console player, you are in the wrong section! Howdy folks, If you're reading this, you're probably thinking about starting a thread for help with an issue. This post is intended for you to understand what we need in order to assist you properly, and how you can give it to us. Threads created without the information outlined in this post are not likely to get you a good resolution. (Most likely you will simply be re-directed to this thread to get instruction on posting the information we need to help you.) Also note, some of this posts content is blatantly copied from Alloc's sticky in the Bug Report forum. Generic Stuff First of all if you are having a problem running the game on Windows make sure to try out the "Launch without AntiCheat" (EAC) option and see if that fixes your problem. If it does still continue with the reporting process but indicate that your problem seems to be related to running the game with the AntiCheat. Also make sure to get answers to the following question before posting if the problem is related to an in-game aspect: Did you start a new game and re-create the issue? Have you validated your files through Steam? After validation, did you re-try with a brand new game? Basic Rules for Posts Use the search first! (I know, the engine sucks. Try wording it a couple of different ways.) One issue per thread please. Short thread title giving a quick info on what the issue is. Try to select the thread Prefix that is fitting most to your system/issue. (Mac, Windows, Dediated, Linux, EAC) Be as concise as possible, e.g. what happened / is the problem, how did you get to that point. Please provide full information on the game type. SP, MP local, MP dedi. If MP, are you hosting it, or is someone else? Please state if you, (or the hosted server), are using any mods. Also state what they are. Provide the log file of the game (see below) Provide the log file of the server (if applicable) If it is about a performance, compatibility issue or anything like that provide system stats (Speccy is an excellent tool to publish system information.) Log Files Depending on where you were experiencing a problem, please provide either the log from the client, the server, or both. If you were playing single-player, hosting a multiplayer game with the game or were playing a multiplayer game but do not have any way to get a copy of the server's log: provide your client's log If you were playing multiplayer on a server that you can get the log of: Provide both your client's and the server's log There is an error hosting a server: Provide the server's log The logs typically reside in these locations: Windows client C:\Users\yourname\AppData\Roaming\7DaysToDie\logs a.k.a. %userdata%\7DaysToDie\logs Before A20.4 the logs were in the client folder. <gamefolder>/7DaysToDie_Data/output_log.txt Windows client as dedicated started through startdedicated.bat <gamefolder>/7DaysToDie_Data/output_log__<DATETIME>.txt Windows dedicated server <gamefolder>/7DaysToDieServer_Data/output_log.txt Windows dedicated server started through startdedicated.bat <gamefolder>/7DaysToDieServer_Data/output_log__<DATETIME>.txt MacOS <homefolder>/Library/Logs/Unity/Player.log Linux client calling the executable manually <homefolder>/.config/unity3d/The Fun Pimps/7 Days To Die/Player.log Linux client using the default start scripts (or through Steam) <gamefolder>/7DaysToDie_Data/output_log__<DATETIME>.txt Linux dedicated server calling the executable manually <homefolder>/.config/unity3d/The Fun Pimps/7 Days To Die - Dedicated/Player.log Linux dedicated server using the default start scripts (or through Steam) <gamefolder>/7DaysToDieServer_Data/output_log__<DATETIME>.txt Linux dedicated server with management scripts /home/sdtd/instances/<instancename>/logs/output_log__<DATETIME>.txt Please find the appropriate file, open it, copy everything. Then go to http://pastebin.com, paste all the text in there, click Submit and then post the link in the thread itself. If the log content is too big to be pasted on pastebin.com, try https://justpaste.it/ or attach the log file to the thread. Please, make sure you read the stuff above and provide as much information as possible in your thread. This makes life easier for everyone, and makes it much more likely for you to get the help you need. Regards, SylenThunder

Re-install the mods folder. I had this happen once and apparently I had messed up the files in the 13.6 patch somehow. Killing the server, copying over the Mods folder again and restarting resolved it. Don't forget to check the console when you start it to make sure Allocs mods load correctly.

The map is console port +2. So if your console was on 25002, then the map would be on 25004. Check the console port in the server config for your current setup.

It's working just fine for me.