-
Content count
9 -
Donations
0.00 EUR -
Joined
-
Last visited
Community Reputation
1 NeutralAbout Jaeger
-
Rank
Bambi
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
One key difference between your host OS and Docker container may be the libraries it's linking to. Otherwise, hard to know why. Nobody wants to look at your core file, dude If I were you, I'd just keep it running happily in a Docker container. You get free restarts if it does crash, and it's more portable, too!
-
I run A3XAI and DMS and have not had any crashes. Not sure why you'd say A3XAI is dodgy - seems like well-written script that performs as advertised. When we were demo'ing VEMF we had a few crashes. To be fair, I didn't do any further troubleshooting, we just went with DMS + custom missions. I guess the advice stands, though - remove each mod until it no longer crashes!
-
Nein
-
I also have Infistar shutdown enabled. crontab just ensures the scheduled restarts happen (always at 2, 6, and 10). I have no start script, per se, just the exile.conf file that defines my start/stop behaviour for Upstart, which handles the rest using the start, stop, restart commands.
-
I found that issue with no PID file being written, which normally I rely on for writing my start/stop scripts. I ended up using Debian's Upstart to handle restarts (and recovery) and it works beautifully. Please see this post for my Upstart script.
-
If you're using Upstart, add the file /etc/init/exile.conf with the following contents: description "ArmA 3 Exile" author "Jaegerhaus" start on filesystem or runlevel [2345] stop on shutdown respawn nice -19 kill signal SIGINT kill timeout 60 chdir /opt/arma/arma3 exec ./arma3server -filePatching -autoInit -loadMissionToMemory -cfg=basic.cfg -config=exile-esseker.cfg -profiles=/opt/arma/arma3/profiles -servermod='@exileserver;@infistar_exile;@asr_ai3;@a3xai;@a3_dms' -mod='@exile;@esseker;@ryanzombies;@cba_a3;@cup_units;@cup_weapons;@cup_vehicles;@cup_terrains_core;@tryk;@hlc_core;@hlc_ak;@hlc_ar;@hlc_mp5;@hlc_fal;@hlc_springfield;@jonzie;@the_birds_and_the_bees' Then you can run start, stop, and restart, like so: arma@arma:~# restart exile Or even add a line to your crontab (with crontab -e): 0 2,6,10,14,18,22 * * * /sbin/restart exile Hope that helps!
-
Server shutting down shortly after start up, new server install
Jaeger replied to bored's topic in Linux
No, that's not true. I've been running ArmA 2 and 3 servers on Linux for a long time. It may be more of a challenge but you'll always get better performance. Check out Jaegerhaus.org - we have zombies! Unfortunately, segfaults are difficult to troubleshoot (Windows has them, too!) but I would recommend (as you did) starting with vanilla Exile and adding in each piece until you figure out which is causing it. From there, you can talk to the devs, even look at the code, or just move stuff around in your init and mission file until it works! -
This is a dedicated Linux server running in NY. It runs the amazing ASR AI mod so you'll never be sure if it's roaming AI or players - they're smart, and vicious! Also watch out for wandering zombie hoards. All you need is Exile and these mods. Tons of vics and guns. Good luck, convicts!