Is there a hardstop on number of managed clients for WebUI limits?

SLB · February 16, 2016, 11:26am

We’ve recently upgraded our server that manages 100k endpoints to patch 6. Though the WebUI documentation states that 60k managed endpoints is an upper use limit, we are really keen to explore WebUI in our production environment and as there isn’t anything saying WebUI wont work on more than 60k endpoints and we are happy to risk the performance impacts, we enabled WebUI after the patch 6 update. Having left the BESRootServer service to do its thang and spawn the WebUI processes, after 48 hours we are still faced with the “The WebUI is initializing” message on the login portal. Checking the ETL, there is a 18Gb DB (the BFEnterprise DB is around 35GB used space). There are no errors in the etl.log. The service-app.log (attached) is showing some errors some 12 hrs after the process first initialized.

Mon, 15 Feb 2016 02:24:14 GMT bf:appmonitor:debug GET https://localhost:52315/api/webui-sites
URIError: Failed to decode param '/%NETHOOD%/'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
Mon, 15 Feb 2016 02:25:24 GMT bf:appmonitor:debug GET https://localhost:52315/api/webui-sites
TypeError: Cannot read property 'toLowerCase' of undefined
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:399:24
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:131:13)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
Mon, 15 Feb 2016 02:26:34 GMT bf:appmonitor:debug GET https://localhost:52315/api/webui-sites
URIError: Failed to decode param '/%80../%80../%80../%80../%80../%80../windows/win.ini'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
URIError: Failed to decode param '/%80../%80../%80../%80../%80../%80../winnt/win.ini'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
URIError: Failed to decode param '/%c0.%c0./%c0.%c0./%c0.%c0./%c0.%c0./%c0.%c0./windows/win.ini'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
URIError: Failed to decode param '/%c0.%c0./%c0.%c0./%c0.%c0./%c0.%c0./%c0.%c0./winnt/win.ini'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
URIError: Failed to decode param '/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/windows/win.ini'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
URIError: Failed to decode param '/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/winnt/win.ini'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
URIError: Failed to decode param '/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/windows/win.ini'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
URIError: Failed to decode param '/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/winnt/win.ini'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
URIError: Failed to decode param '/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/etc/passwd'
    at decodeURIComponent (native)
    at decode_param (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:167:12)
    at Layer.match (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:143:15)
    at matchLayer (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:557:18)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:216:15)
    at updateLastRequestTime (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:116:3)
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:312:13)
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\index.js:330:12)
Mon, 15 Feb 2016 02:27:44 GMT bf:appmonitor:debug GET https://localhost:52315/api/webui-sites
TypeError: Cannot read property 'toLowerCase' of undefined
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:399:24
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:131:13)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
Mon, 15 Feb 2016 02:28:54 GMT bf:appmonitor:debug GET https://localhost:52315/api/webui-sites
TypeError: Cannot read property 'toLowerCase' of undefined
    at E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\lib\bfproxy.js:399:24
    at Layer.handle [as handle_request] (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\layer.js:95:5)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:131:13)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
    at next (E:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\service-app\node_modules\bfappmonitor\node_modules\bfproxy\node_modules\express\lib\router\route.js:125:14)
Mon, 15 Feb 2016 02:30:04 GMT bf:appmonitor:debug GET https://localhost:52315/api/webui-sites

Could we be exceeding the limits of what WebUI can cope with? (would be a shame as we are really keen to use WebUI)

Thanks & Regards
Rob

SLB · February 17, 2016, 5:00pm

So things have started working, just over 72 hrs after starting BESRootServer.
Guessing the ETL runs in a non-intrusive manner so on our larger deployment base it just needed a lot longer than was anticipated.

Regs
Rob

jgstew · March 2, 2016, 6:19am

I’d be really curious how the WebUI goes for you with that many endpoints.

If you don’t have a lot of operators and you have a pretty beefy root server, then it might work great.

I’m waiting on the WebUI to run on a separate server from the root.

I believe right now the WebUI uses a SQLite DB which does put some limitations on it’s scalability, but this doesn’t mean you will have any issues.

How many operators do you have? How many do you have that are in the console+WebUI at the same time?

CC: @dexdexdex

SLB · March 2, 2016, 12:37pm

We haven’t started using WebUI much yet but I’ll be happy to give feedback on how we find it in our environment. We are looking to use it to delegate certain roles so limited numbers of WebUI users can issue actions without the need to use the fat console.

Certainly the initial ETL is time consuming and as you rightly say, its is building a SQLite copy of the main DB (not sure how much of the actual live DB is copied during the ETL). There is also a long wait for WebUI to become usable after any stop|start of the main root service, 2 maybe 3 hours before you can get the login for WebUI. Our live DB is 35GB, the SQLite copy is 27GB. We’re running the app and DB on the same physical server which is an 8 core Xeon @ 2.2GHz with 64GB RAM. Main DB is on LUN made up of server certified SAS SSD in a RAID5, DB logs are on a RAID5 LUN of 15k SAS HDD, the app is installed on a RAID10 LUN of 15k SAS HDD (so this is also where the SQLite DB exists). We have only 2 master ops so there are no more than 2 console sessions in use and, so far, no more than 2 WebUI session in use at any one time.

I completely agree that having WebUI where it can be hosted on a separate server would be great…similar to how you can with Web reports.

dexdexdex · March 2, 2016, 7:11pm

We’re working on that bit! Feed us more pizzas and coffee.

While simultaneous operators hitting the WebUI have performance impacts for high numbers of concurrent users, I’m guessing the thing that defines how long ETL takes is a function of the number of endpoints and actions and the amount of content that you have.

@sbl: The really long initialization time with ETL is something I’ve heard before. I’d love to hear about anything else that you have in terms of feedback as you play around with it.

jgstew · March 2, 2016, 7:17pm

I agree. I wasn’t suggesting the number of simultaneous operators would affect the ETL process, because it shouldn’t, though the total number of operators defined might have some impact on it.

I was asking this question just to gauge potential scaling issues of the WebUI in this case.

it_cat · December 12, 2016, 11:24am

@SLB - How are you finding the WebUI in your 100k endpoint environment… any scaling concerns?

SLB · December 12, 2016, 11:51am

We had to disable it. Following the patch 7 update we were seeing ETL take so long it overlapped with the daily DB defragmentation and re-organization and killed the application server. We have tried re-enabling it a couple of times after the WebUI updates that were announced but ETL never completed and it times out while trying to process the COMPUTER_FIXLETS table.

We haven’t yet updated to 9.5 to try running the WebUI on seperate hardware, but for us its not hardware resurces that are the issue.