I'm using FireDaemon to restart two instances of Arma 3 epoch, in separate directories, with separate BEC instances as well. Everything works great, except for admin tools on my 2nd instance. No matter how I configure it, even with getting proper publicvariables.txt to show being rewritten by what I assume is watchdog plugin on both instances, the 2nd server will kick for restriction #0 if I try to use the admin tools.
I've been able to get the 2nd instance to NOT kick, by deleting BEserver.cfg, making a brand new one, and reverting to the .original publicvariables.txt. This will work fine for the 4 hours it's up, but then restart happens using #shutdown in BEC scheduler, and I get kicked again once it comes back up by FireDaemon. This only happens when using admin tools, and I've confirmed my steam id, and guid are in place, and all of my configs point correctly to 2nd instance directory. Proof being that I can get it working between restarts.
My first instance, restarts without issue, and allows me to use admin tools without kick every time.
I'm really at a loss as to why this happens. I noticed in the FAQ page in this forum there is mention of an unconfirmed bug with txt filters not replacing:
Perhaps this is what I'm dealing with? Do I really have to separate my arma 3 instances onto two separate servers?
Question
nimh
I'm using FireDaemon to restart two instances of Arma 3 epoch, in separate directories, with separate BEC instances as well. Everything works great, except for admin tools on my 2nd instance. No matter how I configure it, even with getting proper publicvariables.txt to show being rewritten by what I assume is watchdog plugin on both instances, the 2nd server will kick for restriction #0 if I try to use the admin tools.
I've been able to get the 2nd instance to NOT kick, by deleting BEserver.cfg, making a brand new one, and reverting to the .original publicvariables.txt. This will work fine for the 4 hours it's up, but then restart happens using #shutdown in BEC scheduler, and I get kicked again once it comes back up by FireDaemon. This only happens when using admin tools, and I've confirmed my steam id, and guid are in place, and all of my configs point correctly to 2nd instance directory. Proof being that I can get it working between restarts.
My first instance, restarts without issue, and allows me to use admin tools without kick every time.
I'm really at a loss as to why this happens. I noticed in the FAQ page in this forum there is mention of an unconfirmed bug with txt filters not replacing:
Perhaps this is what I'm dealing with? Do I really have to separate my arma 3 instances onto two separate servers?
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now