anc 0 Posted September 13, 2007 Hi, sorry i don't know where exatly to post this, if i'm posting in the wrogn forum please move it to the right one. Well, last week we did host a dedicater server, but if someone enters the server using the mod xam, some few minutes later the server crashes. We didn't install the xam in the server yet, but i guess that there are some servers out there withou the xam, but they accept it. Yesterday the server crashed again, but we didn't know if someone was using the xam. I'll post here the cfg that we are using. // // server.cfg // // comments are written with "//" in front of them. password = ""; passwordAdmin = "***"; maxplayers = 12; hostname="***"; logFile = "server_console.log"; motd[]= { "BEM-VINDO AO *** ", "*** ", "Team Speak Obrigatorio: *** ", "Respeite as regras " }; motdInterval=15; voteMissionPlayers=3; voteThreshold=0.33; reportingIP=""; checkFiles[]={}; kickDuplicate=1; equalModRequired=0; persistent=1; disableVoN=1; class Missions { class MPCOOP { template = EvolutionV31+.Sara; cadetMode = 1; }; checkfiles[]= { "dta\bin.pbo", "Addons\wheeled3.pbo", "Addons\weapons3.pbo", "Addons\A10.pbo", "Addons\weapons\config.cpp", "Addons\weapons\config.bin", "Addons\wheeled\config.cpp", "Addons\wheeled\config.bin", "Addons\tracked\config.cpp", "Addons\tracked\config.bin", "Addons\sara\config.cpp", "Addons\sara\config.bin", "Addons\air\config.cpp", "Addons\air\config.bin", "Addons\miscUS\config.cpp", "Addons\miscUS\config.bin" }; verifySignatures=0; onHackedData = "ban (_this select 0)"; onUnsignedData = "kick (_this select 0)"; Share this post Link to post Share on other sites
ArMoGaDoN 0 Posted September 14, 2007 Also seen weird client-CTDs and server CTD shortly afterwards when folks join with XAM. XAM has bugs where servers and other clients don't use XAM... Share this post Link to post Share on other sites
Rambo-16AAB 0 Posted September 14, 2007 Ive also seen this when users with XAM hjoin a non Xam server. Share this post Link to post Share on other sites
.kju 3245 Posted September 14, 2007 Hard way would be <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE"> equalModRequired=1; that disallows any modfolder.. The admin could check people joining for XAM and tell em to return with XAM disabled for example. Share this post Link to post Share on other sites
poweruser 10 Posted September 14, 2007 there's an error in the config file: ( a }; is missing) Quote[/b] ]class Missions { Â class MPCOOP Â Â { Â Â Â template = EvolutionV31+.Sara; Â Â Â cadetMode = 1; Â }; change it to <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">class Missions { Â class MPCOOP Â Â { Â Â Â template = EvolutionV31+.Sara; Â Â Â cadetMode = 1; Â Â }; }; Share this post Link to post Share on other sites
anc 0 Posted September 14, 2007 Thanks. I think that we found out what was the problem. We guess that the problem was with a CTF mission, we deleted it. And we will keep testing, to see if this was the problem. Once again thx for the help =) Share this post Link to post Share on other sites
anc 0 Posted September 15, 2007 After deleting all the missions and left only the original missions, the server still crashed. Now we think that the problem is related to the server that we rent. Share this post Link to post Share on other sites
anc 0 Posted September 19, 2007 We deleted more missions and the serve is stable now. But we do have another problem, the server it's public, and there are some ppl entering our server. And they are trying to ruin our server, but they do not enter when one of our Admins are online. We hade the IDs of some of them. Is there a way to ban them with the ids that we have, without them being online on the server? Regards Share this post Link to post Share on other sites
russin 0 Posted September 19, 2007 ya you need Desktop Access to the server and have -netlog i think in the server config Share this post Link to post Share on other sites
jasono 0 Posted September 19, 2007 XAM has had a bug in it for a while where some data sent to the server would 'confuse' it and therefore make it crash. The server won't crash if you have XAM mod running on it, however some clients who don't have it probably will. I don't know if they are going to fix this soon (of even if they already have) but for now I wouldn't recommend allowing single players with this running on the server. My clan's server has done this and people who want to play return a minute later with it switched off, since they know why we ask. No crash ever since we investigated the problem. Share this post Link to post Share on other sites
killswitch 19 Posted September 23, 2007 Is there a way to ban them with the ids that we have, without them being online on the server? 1) Close the ArmA server. 2) Edit the file "ban.txt" and add the ID numbers to it. 3) Start the ArmA server again. Share this post Link to post Share on other sites
Junker 0 Posted September 23, 2007 Is there a way to ban them with the ids that we have, without them being online on the server? 1) Close the ArmA server. 2) Edit the file "ban.txt" and add the ID numbers to it. 3) Start the ArmA server again. You dont have to close the server to add to the ban list, all u have to do is add the ID, next time they try to connect they DONT Share this post Link to post Share on other sites
anc 0 Posted September 23, 2007 Thanks for the replys =) The server is still crashing, but now it's more stable. We changed some stuffs in the server cfg. And we are still testing. If it isn't ask to much. Is there any code to kick people if their ping its to high? Regards Share this post Link to post Share on other sites
poweruser 10 Posted September 23, 2007 http://community.bistudio.com/wiki....ommands the one you are looking for is (you have to be logged in as admin): <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">#kick (name or ID) Share this post Link to post Share on other sites
anc 0 Posted September 23, 2007 No, i mean the server to kick people with ping higher than 300. Is there any commando to put in the server cfg? Share this post Link to post Share on other sites
anc 0 Posted September 23, 2007 I see. Thanks for the replys. Share this post Link to post Share on other sites
.kju 3245 Posted October 22, 2007 Well bad news (I guess...). A crack for ArmA 1.08 is crashing the server upon connecting, if the windows dedicated server is newer than the one from 1.08.. arma_server.exe 9,50 MB (9.969.664 Bytes) Version: 1.8.0.5163 If the server is newer than this, it should crash if someone with the crack is trying to join.. pretty bad bug and behavior.. from the arma.rpt <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 12 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 20 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 24 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 28 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 32 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 36 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 40 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 44 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 48 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 56 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 128 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 224 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 416 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 448 w:\c\Poseidon\lib\memTable.cpp(922) : SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 480 and <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 12 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 16 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 20 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 24 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 28 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 32 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 36 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 40 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 44 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 48 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 128 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 224 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 416 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 448 SmallMemAlloc not free when destructed - SmallMemAlloc::ReleaseAll skipped. Elem. size 480 Crash files and crack sent to BI.. Share this post Link to post Share on other sites