Jump to content

  • Log in with Facebook Log in with Twitter Log In with Google Log In with Steam Sign In
  • Create Account
Photo

Callvote shuffle or !shuffle crashes the server

shuffle crash

  • Please log in to reply
7 replies to this topic

#1
OFFLINE   Dzikus

Dzikus

    Member

  • Members
  • PipPip
  • 18 posts
3
A step in the right direction

I have a huge problem on my server. Everytime someone calls a vote for shuffle with no restart and it passes, server crashes and there is a need of doing a server restart. Same thing happens when any of the admins uses !shuffle command (only exception is when it's made at the end of the map). We have temporary fixed this issue by removing shufflenorestart, normal shuffle with restart works fine, also our admins were informed not to do !shuffle while map is running. 

As I mentioned - this is just a temp fix. I've found some info on the internet, that it's possibly fault of the binaries (and their versions) so at this moment I'm considering switching from ET 3.00 to ET Legacy 2.72. 

Any help you can give will be appreciated. Here you can see the actual config:
 

 

set sv_maxRate 50000
set sv_dl_maxRate 42000
set sv_allowDownload 1
set sv_wwwDownload 1
set sv_wwwDlDisconnected 1
set sv_wwwBaseURL "http://172804.node9.pukawka.pl"
set sv_wwwFallbackURL ""
set sv_master1 "etmaster.idsoftware.com"
set sv_master2 "master.gamespy.com:27900"
set sv_master3 "master0.gamespy.com"
set sv_master4 "clanservers.net"
set sv_master5 "master0.etmaster.net"
set sv_pure 1
set sv_minping 0
set sv_maxping 0

// silEnT mod supported cvars
set g_silentac 2
set g_recognition 1
set g_muteRename 1
set g_enableDemolition 1 
set g_antilag 1
set g_antiwarp 1
set g_maxWarp 2
set g_skipCorrection 1
set g_heavyWeaponRestriction 100
set g_altStopwatchMode 0
set g_autofireteams 0
set g_complaintlimit 5
set g_ipcomplaintlimit 3
set g_fastres 0
set g_friendlyFire 0
set g_disableComplaints 32
set g_minGameClients 0
set g_maxlives 0
set g_alliedmaxlives 0
set g_axismaxlives 0
set g_teamforcebalance 1
set g_noTeamSwitching 0
set g_doWarmup 0
set g_warmup 25
set match_latejoin "1"
set match_minplayers 0
set match_mutespecs 0
set match_readypercent 1
set match_warmupDamage 2
set g_dbMaxAliases 20
set g_defaultHitSounds 2
set g_speed 320
set g_gravity 800
set g_knockback 1000
set g_inactivity 240
set g_spectatorInactivity 60
set g_maxConnsPerIP 4
set shoutcastPassword "polubo"
set g_spoofOptions 3
set g_maxNameChanges 5
set g_watermark "pu"
set g_watermarkFadeAfter 0
set g_watermarkFadeTime 0
set g_inactivityOptions 7
set g_ettvFlags 3
set g_doubleJumpHeight 1.4

// Votes
set g_voting 13
set vote_limit 1
set vote_percent 70
set g_noVoteTime 10
set vote_allow_comp 0
set vote_allow_gametype 0
set vote_allow_kick 0
set vote_allow_map 0
set vote_allow_matchreset 0
set vote_allow_mutespecs 0
set vote_allow_nextmap 0
set vote_allow_pub 0
set vote_allow_referee 0
set vote_allow_shuffleteamsxp 1
set vote_allow_swapteams 0
set vote_allow_friendlyfire 0
set vote_allow_timelimit 0
set vote_allow_warmupdamage 0
set vote_allow_antilag 0
set vote_allow_balancedteams 0
set vote_allow_muting 1
set vote_allow_surrender 0
set vote_allow_nextcampaign 0
set vote_allow_restartcampaign 0
set vote_allow_poll 1
set vote_allow_maprestart 1
set vote_allow_shufflenorestart 0
set vote_allow_cointoss 0
set vote_block_nextmap 120
set vote_block_shufflenorestart 60
set vote_block_shuffleteamsxp 60
// Logs
set g_log "server.log"
set g_cheatLog "cheat.log"
set logfile 2
set g_logOptions 16648
set g_logAdmin "admin.log"

// XP Save configuration
set g_XPSave 21
set g_XPSaveMaxAge_xp "6o"
set g_XPSaveMaxAge "6o"
set g_damageXP "1"
set g_damageXPLevel "50"
set g_maxXP "-1"
set g_xpdecay "0"
set g_xpdecayrate "0"
set g_xpdecayfloor "1"
set g_maxXPResetWarn "0"


// Shrubbot and Database
set g_dbDirectory "database"
set g_dbUserMaxAge "90d"
set g_minConnectLevel 0
// see documentation about tyranny enabled commands and flags
set g_tyranny 1
set g_greetingPos 0
set g_warningOptions 25
set g_warningDecay 24
set g_maxWarnings 4
set g_autoTempBan 4
set g_autoTempBanTime 1800
set g_shuffle_rating 3

//
//
g_censor "huj,szmat"

g_censorPenalty 32
g_censorNames 0
g_censorPenalty 0
g_censorNeil 1
g_censorNeilNames 1
g_censorMuteTime 0
g_censorXP 0

//
// Intermission
set g_intermissionTime 35
set g_intermissionReadyPercent 80

//
// Skill points needed for level
set skill_soldier "20 50 90 200"
set skill_medic "20 50 90 200"
set skill_engineer "20 50 90 200"
set skill_fieldops "20 50 90 200"
set skill_covertops "20 50 90 200"
set skill_battlesense "20 50 90 200"
set skill_lightweapons "20 50 90 200"

set g_serverInfo 1
set g_killRating 7
set g_playerRating 3
set g_playerRating_mapPad 50
set g_playerRating_minplayers 8
set g_stats 1


// Custom configs
set g_mapScriptDirectory "mapscripts"
set g_campaignFile "scripts/ubojnia.campaign"
set g_mapConfigs "mapconfigs"
set g_banners "banners.cfg"


// Miscellanous
set g_votedMuteLength 300
set g_skills 1
set g_teamDamageRestriction 0
set g_minHits 6
set g_weapons 13302
set g_mg42 2
set g_goomba 2
set g_goombaFlags 34
set g_spinCorpse 0
set g_teamChangeKills 1
set g_poison 0
set g_poisonFlags 0
set g_slashKill 1
set g_spectator 2
set g_medics 320
set g_medicHealthRegen 4
set g_coverts 1415
set g_truePing 1
set g_dropObj 1
set g_hitsounds 9
set g_playDead 1
set g_shove 75
set g_shoveNoZ 0
set g_dragCorpse 1
set g_classChange 1
set g_classWeapons 63
set g_forceLimboHealth 0
set g_privateMessages 1
set g_packDistance 6
set g_dropHealth 3
set g_dropAmmo 3
set g_dropMsg "^1LAMANIE REGULAMINU LUB BLOKOWANIE SLOTA --> KICK ^22 MINUTY. ^73 WARNY ZA SPAWN KILLING --> ^2BAN 60 MINUT. JESLI DOSTALES BANA STALEGO I CZUJESZ SIE POKRZYWDZONY PISZ NA ^2WWW.UBOJNIA.^2GA DZIAL ^1BANY."
set g_tossDistance 10
set g_fear 2000
set g_misc 1061
set g_obituary 1
set g_throwableKnives 1
set g_maxKnives 5
set g_knifeChargeTime 400
set g_covertopsChargeTime "30000"
set g_engineerChargeTime "30000"
set g_LTChargeTime "40000"
set g_soldierChargeTime "20000"
set g_medicChargeTime "45000" 
set g_constructibleXPSharing 1
set g_asblock 43
set g_panzersVulnerable 0
set g_panzersSpeed 2300
set g_panzersGravity 1
set g_realHead 1
set g_realBody 0
set g_dyno 28
set g_canisterKick 140
set g_canisterKickOwner 0
set g_spreeOptions 2687
set g_multikillTime 2200
set g_medicSelfhealTime 0
set g_maxPanzerSuicides -1
set g_panzerPackDistance 0
set g_maxSelfkills -1
set g_voteResultsMinLevel -1
set g_minCommandWaitTime 0
set g_noSkillUpgrades 0
set g_flushItems 1
set g_headshot 0
set g_instagibDamage 400
set g_staminaRecharge 1.0
set g_mineid 1
set g_tactics 0
set g_landmineNotifyType 1
set g_minAirstrikeTime 60
set g_minArtyTime 45
set g_mode 8
set g_smoothClients 1
set g_spawnInvul 3
set g_spawnInvulFair 1
set g_extraStatistics 0
set g_identOptions 31
set g_min_crazyspeed 250
set g_max_crazyspeed 700
set g_min_crazygravity 100 
set g_max_crazygravity 300
set g_maxMarkers 2
set g_proneDelay 0
set g_realPlayTime 1
set g_teamForceBalance 1
set g_unevenTeamDiff 1 
set g_unevenTeamFreq 60
set g_ammoCabinetTime "3000"
set g_healthCabinetTime "3000"

//
// Weapon damages and radius settings
set g_dmgKnife 25
set g_dmgSten 19
set g_dmgFG42 17
set g_dmgPistol 18
set g_dmgSMG 18
set g_dmgPPSh 17
set g_dmgMG42 20
set g_dmgMG 20
set g_dmgFG42Scope 35
set g_dmgInfRifle 35
set g_dmgSniper 55
set g_dmgFlamer 5
set g_dmgGrenade 250
set g_dmgGrenadeRadius 250
set g_dmgGLauncher 250
set g_dmgGLauncherRadius 250
set g_dmgLandmine 250
set g_dmgLandmineRadius 250
set g_dmgSatchel 250
set g_dmgSatchelRadius 250
set g_dmgPanzer 320
set g_dmgPanzerRadius 320
set g_dmgMortar 400
set g_dmgMortarRadius 400
set g_dmgDynamite 500
set g_dmgDynamiteRadius 500
set g_dmgAir 320
set g_dmgAirRadius 320
set g_dmgArty 320
set g_dmgArtyRadius 320
set g_dmg 0
set g_dmgHeadShotMin 56
set g_dmgHeadShotRatio 2.0
set g_dmgTMine 250
set g_knifeThrowDamage 100
set g_dmgDemolition 400
set g_dmgDemolitionRadius 400
//
// Team restrictions
set team_maxMedics -1
set team_maxEngineers -1
set team_maxFieldOps 2
set team_maxCovertOps 3
set g_maxTeamLandmines 15
set g_maxTeamTripmines 6
set team_maxPanzers 8%-
set team_maxMortars 1
set team_maxFlamers 1
set team_maxMG42s 1
set team_maxGrenLaunchers 21%-

//
// Friendly fire
set g_reflectFriendlyFire 0
set g_reflectFFWeapons 31
set g_friendlyFireOpts 44

//
// Flood protection
set g_floodprotect 1
set g_floodthreshold 1
set g_floodWait 1700
set g_voiceChatsAllowed 2

//
// Map voting
set g_mapVoteFlags 1
set g_maxMapsVotedFor 25
set g_minMapAge 18
set g_resetXPMapCount 0
set g_excludedMaps ":goldrush:"



//
// Omni-bots
set omnibot_enable 1
set omnibot_path "/data/cabanos/172804.et255/omni-bot"
set g_bot_maxXP 1000
set g_bot_minPlayers -1
set omnibot_flags 262212

//
// Fun wars
//set g_sniperwar 0
//set g_panzerwar 0
//set g_riflewar 0

//
// Country flags, You need to have GeoIP database installed to use this.
set g_countryFlags 1

//
// ETPub experimental, not advised to use
set g_fixedphysics 1
set g_fixedphysicsfps 125

//
// Lua API
set lua_modules "autopromo.lua"
set lua_allowedModules ""

exec voting.cfg
set com_watchdog 60
set com_watchdog_cmd "exec voting.cfg"

Edited by Dzikus, 17 January 2015 - 03:36 PM.


#2
OFFLINE   hellreturn

hellreturn

    Management

  • Management
  • PipPipPipPip
  • 2693 posts
158
On the road to fame

Can you please do this:

 

Upload console logs somewhere and submit the link using contact us? 

 

http://mygamingtalk....ction=form&id=1

 

Possible to give your server access to silencer? He can easily debug it for you once he is free.

 

I am not able to re-create your issue. Just did !shuffle on my server and it didn't crash at all.



#3
OFFLINE   TheSilencerPL

TheSilencerPL

    Advanced Member

  • Management
  • PipPipPipPip
  • 3099 posts
216
On the road to fame
  • LocationPoland

I would rather consider this as an ET 3.00 issue.

 

 

I am not able to re-create your issue. Just did !shuffle on my server and it didn't crash at all.

@Hellreturn, what are you running on that server, I guess not ET 3.00?



#4
OFFLINE   Dzikus

Dzikus

    Member

  • Members
  • PipPip
  • 18 posts
3
A step in the right direction


Can you please do this:

 

Upload console logs somewhere and submit the link using contact us? 

 

http://mygamingtalk....ction=form&id=1

 

Possible to give your server access to silencer? He can easily debug it for you once he is free.

 

I am not able to re-create your issue. Just did !shuffle on my server and it didn't crash at all.


I admire your nobel idea but our server is too popular to make such a security risk.
Don't get me wrong of course... imho this is a way too far request. It would be easier to share most of the configs to recreate the scenario.
Changing subject to logs - I'll upload them soon. There is nothing special in them, trust me, I've already checked.

I would rather consider this as an ET 3.00 issue.


I think the same. Found some old thread about identical issue and changing binaries fixed this problem.
If it's really because of ET 3.00 I need a suggestion about binaries replacement.

First of all - our server is pretty old and we don't wanna lose players by a mistake. At this time like I've mentioned before, the server runs on ET 3.00 which makes possible to connect players with ET 2.55 and 2.60 (not only 2.60b).
Practically if I upgrade to ET:Legacy 2.72 or ET 2.60b it will probably fix the issue but many of our veteran players will be kicked because of different version, and trust me - many of them will have a problem with upgrading ET version, even when It's so simple that even a monkey can do it...

The question is: Which version of ET binaries will be optimal for me (not buggy 3.00 but also giving possibility for players with older versions like 2.55/2.60 to connect without a problem) ? Any ideas?

#5
OFFLINE   hellreturn

hellreturn

    Management

  • Management
  • PipPipPipPip
  • 2693 posts
158
On the road to fame

I would rather consider this as an ET 3.00 issue.

 

@Hellreturn, what are you running on that server, I guess not ET 3.00?

 

It has ET 3.00. Majority of clan run ET 3.0. If !shuffle was an issue then we would have seen reports by now.

 

I admire your nobel idea but our server is too popular to make such a security risk.
Don't get me wrong of course... imho this is a way too far request. It would be easier to share most of the configs to recreate the scenario.

 

Don't get me wrong but your scenario is not reproducible with configs only. You already had posted the config which you use and even with that config while using ET 3.00 my server doesn't crash.

 

For update: Just ask your regulars to remove old installation and install this one:

 

http://mygamingtalk....ersion-windows/

 

It's directly on 2.6b.  No need for patches. Now if they can install 2.55 then can install 2.6b directly. 



#6
OFFLINE   Dzikus

Dzikus

    Member

  • Members
  • PipPip
  • 18 posts
3
A step in the right direction

 

It has ET 3.00. Majority of clan run ET 3.0. If !shuffle was an issue then we would have seen reports by now.

 

 

Don't get me wrong but your scenario is not reproducible with configs only. You already had posted the config which you use and even with that config while using ET 3.00 my server doesn't crash.

 

For update: Just ask your regulars to remove old installation and install this one:

 

http://mygamingtalk....ersion-windows/

 

It's directly on 2.6b.  No need for patches. Now if they can install 2.55 then can install 2.6b directly. 

 

Well, I see your point. However there is another solution for this - a test server based on exact configs I use on the main server.

Let's face the facts.... some of our regulars were never seen to use chat or voicechat, colored nicks etc. so it will be a major problem to force them to update to 2.60b.... In my opinion we'll lose them while making such a changes.

Is there any way to make it more simple? Some kind of way around like ingame download. I'd like to make a change which fixes the problem and is also unnoticable by players.


Edited by Dzikus, 18 January 2015 - 02:49 AM.


#7
OFFLINE   Dragonji

Dragonji

    Advanced Member

  • Members
  • PipPipPipPip
  • 514 posts
142
On the road to fame
  • LocationPoland
I wouldn't recommend ET: Legacy just now because it still has a critical unresolved bug: http://dev.etlegacy.com/issues/746

BTW, it shouldn't be difficult to make ET:L 2.55+ compatible, just need to remove a few lines in the code and recompile.

Edited by Dragonji, 18 January 2015 - 12:19 PM.


#8
OFFLINE   Dragonji

Dragonji

    Advanced Member

  • Members
  • PipPipPipPip
  • 514 posts
142
On the road to fame
  • LocationPoland
The issue of ET:L has been fixed a few days ago. I personally run it on my own server with no problems now. It is way better than ET 3.00, just have a look here. It doesn't accept 2.55 clients by default but it is not a big problem to make it support multiprotocol as it is an open source project.

I used ET 3.00 for a while too, but it was causing inexplicable crashes. ET:L is surely free of bugs ET 3.00 has.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users