View Issue Details

IDProjectCategoryView StatusLast Update
0000108Volume 2Featurepublic2019-05-30 02:55
ReporterChetAssigned Tomichaeldcullen 
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Product Version 
Target VersionIssue 2Fixed in Version 
Summary0000108: Update DBServer/MapServer Initialization
DescriptionThe loadbalancer is unfortunately designed to require separate launchers (and therefore separate physical machines due to a lack of port range) to load LogServer, StatServer, ArenaServer, and RaidServer as independent roles.

For most server deployments this is unnecessary, as typically they will be running on the same machine as DBserver. This PR essentially removes them from the required list of auto-start launcher roles (if they are not manually specified in servers.cfg) and allows for them to be started as part of a standard loadbalance config.

Additionally, a -silent switch should be added for MapServer, which can be specified in Launcher to hide the (potentially hundreds) of console windows generated as new MapServer processes spin up. Based on management of a live server, this is a logistical NIGHTMARE when actually trying to do anything over RDP.

Feature provided by CoC team.
TagsNo tags attached.
subsystem

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-05-18 19:17 Chet New Issue
2019-05-18 19:17 Chet Assigned To => michaeldcullen
2019-05-18 19:18 Chet Status new => assigned
2019-05-30 02:55 Chet Target Version Issue 1 => Issue 2