What will help us debug this one is people send us everything they see in BigFix Enterprise\BES Server\WebUI\logs. Feel free to PM directly and I can look and help forward to the right people.
I expect to see everyone’s ETL still making progress if they’re still in the initialization state, but if there are fires or locking issues or error messages that’s super interesting and we’ll look closer. WebUI should come back up online on it’s own given time.
Root Cause: There was a recent schema update that caused this issue. Usually WebUI recovers naturally as it rebuilds webui.db over time. The time this takes depends on your deployment size, how many content items you have, and your specific hardware configuration. 90% of the time updates in WebUI aren’t schema updates but this one was.
We’re actively working on a feature that will let folks control when WebUI updates happen more granularly so that these situations are a little bit more controlled. We also have some client settings that exist today that delay updating for a while and only have updates happen during a specific time and day of week.
You can also kind of implement a freeze on your currently gathered WebUI sites but that’s a little bit tricky and has some caveats. If folks are interested in that maybe PM me. I was putting together a guide on it based on popular request.
@swiars: your case seems odd. bigfix-webui-etl.exe is the process that grabs data from bfEnterprise and loads it into webui.db. Do you see any logs (BESRelay.log) or anything in the WebUI\logs that indicate things have crashed? I’d maybe try a restart of the root server service to see if it comes back.