Jump to content

grave867

Member
  • Posts

    104
  • Joined

  • Last visited

Posts posted by grave867

  1. So far I haven't figured out what is wrong with my server having nothing happen when adding your scripts. However I did notice that in the INI you provided there are missing semicolons for the last three statements.

     

    Also I recommend that you put your adaption to these mods into a github repo so that people can actively submit updates and the like.  

  2. When the download window disappears it means that the installer is downloading the BEC.zip from the official website. It is a slow download as it is, but the download can be slowed by the load on the official BEC server or load on your connection. The zip folder is created as the full file is downloaded as a place holder and it will say the full expected file size as well. The installer isn't finished and it hasn't errored out it is simply taking a while to download the file for one reason or another.  

  3. Hi,

     

    I've got an error when installing. After filling in the details and click "ok" for downloading BEC, about 30 secs later i get this error.

     

     

    Small Private Server & Hive

    Hardware;

    Intel Core i3 @ 3.10ghz

    4gb mem

    Windows Server 2008 R2 Standard 64bit 

     

    Install from directory: C:\Program Files (x86)\Steam\SteamApps\common\Arma 2 Operation Arrowhead

     

    Thanks for any help.

    This caused by your .net framework not working correctly, since the installer itself is programmed in .net. You should look at forums using this as a search "Problem Event Name: CLR20r3" to try and fix the issue. 

  4. take a note that the current work dir of the restart script is where your bec is located.

    so if you want the current workdir for your bat script to be where its located. you need to set it in the bat script.

    from reading the scheduler faq file i saw this,

       4 - Keep in mind that the CWD (Current Work Directory) your bat|cmd script or program will have is the same as your Bec install.

           Let say the path you have your Bec installed is at (C:\Tools\Bec).

           This is and will be the CWD of your script even if its located in C:\Scripts\Myfile.bat or some other place.

           

           Depending on your script and what it does, you might need to set a new work-dir by editing your script with something like:

           ::--------------------

           set NewCWD="C:\Scripts\"

           cd /d %NewCWD%

           

           do stuff

           ::--------------------

    this might be confusing for some people, espesially if they edit the script and mix up rel paths with abs pats and dont know the current workdir.

    this might be a case where it would fail to run the restart script properly i belive.

    You are exactly right, the batch file i provide already has this and the bec is told where to look for the batch. However in the same section of the FAQ is another interest comment, if bec is launched with the --dec argument it won't run external scripts. This may be the cause of the restart now working, I use to tell bec how to launch but was told by the bec creator it was no longer needed. I may re-implement how I use to call bec with specific arguments to see if it fixes the problem. 

     

    Thanks again to everyone trying to help fix this problem as bec is critical to all our servers, I have been busy but will try to at least check this page more often  :D

  5. Cant log in to the bansys web site, setup the account .. added the reporter .. even reset the password.. nada .. zip .. nothing .. whats the dealio ? 

    Does it just take time to fully work , [ Reporter ] = the username and password from the website ? or one from admin list or what ?

    I have no idea how long it takes for the reporter accounts to be setup, I personally haven't set mine up yet so I have no point of reference for you. :(

  6. I think I can more clearly explain for some why the auto-restart function is not working ( I hope I won't need a disclaimer for this). The way the scheduler is setup by default will after whatever pre-defined time you chose shutdown the server and then wait ten seconds before launching the bat file that will re-launch the server.

     

    Now the problem with that is after the server is shutdown, the BEC will only wait just a few seconds before closing down because it does not detect a server. Since the provided schedule waits ten seconds to run "start.bat" BEC will instead close and that portion of the schedule never even gets a chance to run.

     

    To solve the issue simply run the command to launch "start.bat" in the same function as the #shutdown command. I have provided an example here:

     

    <!-- 12:00 AM restart -->
    <job id='12'>
        <day>1,2,3,4,5,6,7</day>
        <start>23:45:00</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>say -1 This server will restart in 15 minutes</cmd>
    </job>
    
    <job id='13'>
        <day>1,2,3,4,5,6,7</day>
        <start>23:55:00</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>say -1 This server will restart in 5 minute, log out now to prevent item loss!</cmd>
    </job>
    
    <job id='14'>
        <day>1,2,3,4,5,6,7</day>
        <start>23:59:00</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>say -1 This server will restart in 1 minute, Log out now!</cmd>
    </job>
    
    <job id='15'>
        <day>1,2,3,4,5,6,7</day>
        <start>00:00:00</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>#shutdown</cmd>
        <cmd>B:\DayZ Server\restart.bat</cmd>
    </job>
    <!-- End 12:00 AM restart -->
    

     

    Please do not use this code as a copy/paste solution as that will not fix your issue, this is simply provided as a means of reference.

     

    I guess that was my disclaimer <_<

     

    Beans to alecwilcox for originally providing the solution for me:

    This could possibly be causing the problem, in older versions of BEC it would wait 30 seconds before terminating the BEC application and that is what i calculated for. However I would advise calling the restart file from a new command block.

  7. Update released version 1.602. Anyone have the change logs?>

     

     

    *** V 1.602 ***
    - Improved: Auto remove starting and ending spaces from the tags in the xml files.
    - Fixed: A typo in the code making WhiteListKickMsg not work unless it was spelled wrong.
    - Added: New setting to [Misc] -> BeCustomBanFiles, define custom banfiles which will do a (loadbans file) if the file(s) gets changed.
    - Added: Logging to BeLog-DATE.log, into about guid verification on player connect when using Bec Reporter. (Status report)
    - Changed: SlotLimit chaned a bit again :\
  8. Can you expand on this a little, possibly with a reference? I have had this working before while not constantly being logged in via RDP but i cannot remember how, and if we have to wait for a new version, what is the ETA on this? 

     

    Many thanks.

    windows will not auto run files that are being executed within an existing running program unless it is a service when logged out, which is why windows event scheduler exists for system admins. However I may have a simple way of turning the restarts into a service fairly easily and will try to have it done sometime this coming weekend at the earliest, lastest hopefully being the following week.

×
×
  • Create New...