Native Linux server (with management scripts)

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.

 
Fully upgraded debian, full https://7dtd.illy.bz/ rewipe, fresh new instance cannot start."ERR Error parsing configfile property 'CraftTimer': Could not parse config value '1'"

(this is generated by server management script)

log output

HOTFIX: remove nodes with CraftTimer & LootTimer variables from config.xml
From my first post on the issue :)

...Edit the config.xml in /home/sdtd/instances/Home/config.xml to remove the loot and craft timer lines.

...
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. >.<

 
Bwahah.. ok, iam deleting my post :)

Try to call runtime manually:

/home/sdtd/engine/7DaysToDieServer.x86_64 -logfile /home/sdtd/instances/$instancename/logs/2016-03-27_16-21-08_output_log.txt -configfile=/home/sdtd/instances/$instancename/config.xml

 
This would start the server again yes, but the "dead" instance would still be running as it always does when i look at the processes. I always had to manually kill the old process as it still consumes memory, before i restart.
Hm, never had that happen with OOMs. Other causes my obviously leave a process running but unusable. Some people wrote nice little scripts for detecting this though.

Code:
root@7DTD:~# 7dtd.sh start Home
Failed!
root@7DTD:~#
Logs? stdout.log, output_log ... anything?

 
Hm, never had that happen with OOMs. Other causes my obviously leave a process running but unusable. Some people wrote nice little scripts for detecting this though.
Logs? stdout.log, output_log ... anything?
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...

Code:
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.

 
have you doublechecked requirements libs in prerequisities?

It could be related to your issues.. Do you have exactly the same libraries packages?

 
Last edited by a moderator:
Try to run the process manually as palmic pointed out.
That give me "Illegal instruction (core dumped)

no new logs

- - - Updated - - -

have you doublechecked requirements libs in prerequisities?It could be related to your issues.. Do you have exactly the same libraries packages?
Yes, triple-checked. All are installed and updated.

 
That give me "Illegal instruction (core dumped)
Well, you kinda got your culprit there ... seems to be a deeper issue with your system / Unity. It doesn't even get *close* to the game code itself.

What CPU do you run? If VM both host as well as the virtualize CPU type.

 
Server Specs

Operating System

Ubuntu 14.04.1 LTS 64-bit

CPU

2x Dual Core AMD Opteron Processor 275 @ 2.20GHz

RAM

16.0GB DDR1/333 SDRAM

Motherboard

SunFire V20z system board

Graphics

N/A

Storage

Two 73GB Ultra320 SCSI disk drives in RAID1

It's really weird that it started having issues with the 64-bit reading blocks.xml in a13.8, and now just crashes when starting 64-bit in a14. It runs one Navezgane map fine in 32-bit, but I know if I'm going to use RWG for a number of players, I'll want to use 64-bit. Not certain that I can (or would want to) run Windows on this old web server. Last time I tried to install Server 2008, it didn't end well. I was wondering if installing an old 512MB PCI video card would help at all LOL. I think I have one laying around on my desk somewhere.

 
CPU2x Dual Core AMD Opteron Processor 275 @ 2.20GHz
Yeah, almost looks like that's the issue. I assume Unity requires some newer CPU instruction set extensions on the 64 bit builds, like SSE4 or AVX. Same problem for another old AMD processor is described on this Unity thread. I suppose you're out of luck there with the 64 bit build :(

 
Hi,

got a little Question about the different Ubuntu releases, maybe its related to SylenThunder´s

Problem as well.

Ubuntu 14.04 LTS uses Init.d als the Init/deamon System and Ubuntu 15.10 uses System.d,

therefor your Bootstrap.sh will only work on Ubuntu Versions below 15.10?

The Release of Ubuntu 16.04 LTS is only a few Days/Weeks away and System.d will become

the standard Init System, do you intend to update your bootstrap.sh to System.d?

Mostly all major Distributions use System.d now

Thx and Greetings

Jason

P.S. Sorry still learning English

 
Good point ... didn't really catch my attention as my game VM is still running a rather old Debian which does use init.d ;)

Of course this has to be updated at some point, just gotta figure out what exactly needs to be done for that. (Btw, the bootstrapper shouldn't be affected a lot by this ... of course it won't be able to create a start script but everything else should be fine)

 
Hey man. Just installed the bootstrap on a fresh server. when I go to make an instances I get this back.

/usr/local/lib/7dtd/serverconfig.sh: line 963: /usr/bin/xmlstarlet: No such file or directory

/usr/local/lib/7dtd/serverconfig.sh: line 964: /usr/bin/xmlstarlet: No such file or directory

 
Hey man. Just installed the bootstrap on a fresh server. when I go to make an instances I get this back.
/usr/local/lib/7dtd/serverconfig.sh: line 963: /usr/bin/xmlstarlet: No such file or directory
As it says: You're missing xmlstarlet (as pointed out in the prerequisites page) ;)

 
Back
Top