No relevant devices found in WebUI

Usage and Config WebUI
1

Good day, I have recently set-up WebUI on 9.2.6 and there is a strange behaviour that I have no idea what’s going on.

I could login (with MO), navigate properly but whenever I try to deploy a patch (definitely relevant to some of the computer), it shows “No relevant devices found”. However I could target dynamically on a specific computer group (and shows the number of relevant devices).

I have tried deleting the entire WebUI folder’s content and regenerate it and the issue still persist, anyone could advise me on this please? Much appreciated.

2

Can you check for, and disclose any errors in your /Bigfix Server/WebUI/Logs/etl.log.

It could be helpful to check the other logs as well for errors.

3

Hi kevin_friedheim,

Thanks for your advice but i do not see any errors in the etl.log. moreover it causes severe lag in the server that I had to remove it today. I will attempt another installation again and update here.

4

This is definitely suspicious. Does what the WebUI report match with what you see in the thick console with the same user?

ALSO, what do you define as a patch? From what site is it? If it’s from one of the WebUI supported patch sites (Patches for Windows, patches for mac os x, patches for RHEL, patches for CentOS, updates for windows applications (notice that we expanded it!?) ) then we’ve got a problem. Sorry, that was a horrible sentence.

Maybe list out what patch sites you have subscribed on your deployment?

5

Maybe just point your favorite browser to: https://SERVER:52311/api/webui-sites and give us that output - along with the patch/fixlet ID that is being stubborn about becoming relevant.

6

webui-sites will help because that lists all the WebUI sites you have subscribed.

I think if you tell us the output of https://SERVER:52315/api/etl/sites it will help more because that gives the actual list of content sites subscribed to the deployment.

If you get a chance sending us the output of both would help us out a lot here.

7

I will do a new setup shortly and update you guys when I have the information. Thanks for the help.

8

Hi @wonkt any updates?

9

Hi and sorry for the late reply. Been busy with other stuff and just manage to enable WebUI again today.

Below are the output from https://BFServer:52315/api/webui-sites and the ETL.log. I have yet to login as the webui.db is creating. I will update further once it is ready to login.

[{“id”:12047,“name”:“WebUI Common Beta”,“version”:24,“url”:"\u002fwebui-sites\u002f12047"},{“id”:12048,“name”:“WebUI Patch Beta”,“version”:23,“url”:"\u002fwebui-sites\u002f12048"},{“id”:12049,“name”:“WebUI Common”,“version”:26,“url”:"\u002fwebui-sites\u002f12049"},{“id”:12203,“name”:“WebUI Custom Beta”,“version”:21,“url”:"\u002fwebui-sites\u002f12203"},{“id”:12204,“name”:“WebUI Software Distribution Beta”,“version”:22,“url”:"\u002fwebui-sites\u002f12204"}]

Fri, 29 Apr 2016 07:11:20 GMT bf:bfapp:debug ETL 1.0.2 listening on port 5001 in production mode
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Re-creating database tables
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Re-creating database indexes
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Successfully initialized database schema
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Spawning D:\Program Files (x86)\BigFix Enterprise\BES Server\WebUI\sites\WebUI Common Beta_12047_24\etl-app\node_modules\bfetl\lib\bin\win32\bigfix-webui-etl.exe
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Sending request for 66 tables
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Starting bigfix-webui-etl version 1.0.12
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded COMPUTED_FIXLET_COUNTS 0 rows in 0.016 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded COMPUTED_BASELINE_COUNTS 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded COMPUTED_DEVICE_COUNTS 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded USERS 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded ROLES 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded USER_ROLES 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded COMPUTERS 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded COMPUTER_USERS 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded COMPUTER_ROLES 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded SITES 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded SITE_USERS 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded SITE_ROLES 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded CUSTOM_BASELINES 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded COMPUTER_BASELINES 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded CUSTOM_FIXLETS 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded EXTERNAL_FIXLETS 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded COMPUTER_FIXLETS 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded COMPUTER_SITES 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded CONTENT_VISIBILITY 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded CONTENT_VISIBILITY_USER 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed all fixlets in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded patches 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Loaded critical patches 0 rows in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed globally readable sites in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed operator permissions in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed visible sites for non-master operators in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed visible fixlets for all users in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed fixlet applicability in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed baseline applicability in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed devices for master operators in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed devices for non-master operators in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed fixlet counts for non-master operators in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Computed baseline counts for non-master operators in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Updated COMPUTED_FIXLET_COUNTS: no rows modified in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Updated COMPUTED_BASELINE_COUNTS: no rows modified in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Updated COMPUTED_DEVICE_COUNTS: no rows modified in 0.000 seconds
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Waiting for request
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug Received request for 66 tables
Fri, 29 Apr 2016 07:11:20 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/actions
Fri, 29 Apr 2016 07:11:45 GMT bf:bfetl:debug Updated ACTIONS 1473 rows in 24.772 seconds (59 rows per second)
Fri, 29 Apr 2016 07:11:45 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/action-fields
Fri, 29 Apr 2016 07:11:46 GMT bf:bfetl:debug Updated ACTION_FIELDS 0 rows in 1.404 seconds
Fri, 29 Apr 2016 07:11:47 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/action-parameters
Fri, 29 Apr 2016 07:11:48 GMT bf:bfetl:debug Updated ACTION_PARAMETERS 15 rows in 1.451 seconds (10 rows per second)
Fri, 29 Apr 2016 07:11:48 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/action-target-names
Fri, 29 Apr 2016 07:11:49 GMT bf:bfetl:debug Updated ACTION_TARGET_NAMES 0 rows in 1.435 seconds
Fri, 29 Apr 2016 07:11:49 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/action-target-static
Fri, 29 Apr 2016 07:11:51 GMT bf:bfetl:debug Updated ACTION_TARGET_STATIC 15777 rows in 1.778 seconds (8873 rows per second)
Fri, 29 Apr 2016 07:11:51 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/action-user-groups
Fri, 29 Apr 2016 07:11:53 GMT bf:bfetl:debug Updated ACTION_USER_GROUPS 0 rows in 1.451 seconds
Fri, 29 Apr 2016 07:11:53 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/analysis-activations
Fri, 29 Apr 2016 07:11:54 GMT bf:bfetl:debug Updated ANALYSIS_ACTIVATIONS 77 rows in 0.858 seconds (89 rows per second)
Fri, 29 Apr 2016 07:11:54 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/computer-actions
Fri, 29 Apr 2016 07:12:09 GMT bf:bfetl:debug Updated COMPUTER_ACTIONS 200301 rows in 15.802 seconds (12675 rows per second)
Fri, 29 Apr 2016 07:12:10 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/computer-analyses
Fri, 29 Apr 2016 07:12:36 GMT bf:bfetl:debug Updated COMPUTER_ANALYSES 398643 rows in 26.458 seconds (15067 rows per second)
Fri, 29 Apr 2016 07:12:37 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/computer-groups
Fri, 29 Apr 2016 07:12:41 GMT bf:bfetl:debug Updated COMPUTER_GROUPS 42784 rows in 4.634 seconds (9232 rows per second)
Fri, 29 Apr 2016 07:12:41 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/computer-property-info
Fri, 29 Apr 2016 07:14:39 GMT bf:bfetl:debug Updated COMPUTER_PROPERTY_INFO 2897505 rows in 117.515 seconds (24656 rows per second)
Fri, 29 Apr 2016 07:14:39 GMT bf:bfetl:debug GET https://localhost:52315/api/etl/computer-property-text

10

Alright the database is loaded, however it displays the same issue as before.

For all the patches I have tried to deploy (definitely applicable as shown at the right side of the fixlet and shown XXX vulnerable devices reported when i click into it), it will show “No relevant devices found” once I click on “Deploy patch”. Even by clicking the check box “Show non-relevant”, no endpoints will be displayed. However if I select by group, it will show the correct number of relevant devices at the right pane.

Is there any way to completely purge the WebUI installation and start afresh? My management is very interested in this tool as we have remote offices that could make use of it for some basic administration. Any help will be much appreciated, thank you.

11

Thanks for the reply. We are looking into this. In the meantime, the way to purge would be to simply delete your existing webui.db file.

Also, which patch specifically have your tried that demonstrated this issue (ID and Name and if you know it, what site the patch belongs to e.g. Patches for RHEL or Patches for Mac OSX.

Can you poke around in your patch.log (same location as etl.log). Anything interesting in there (errors? warnings?)

1 Like
12

Actually, what’s really weird about the logs that I see is that apparently you’re still on the WebUI Beta sites (which we basically haven’t updated since close to release 1.0 of the WebUI way back in November of 2015. Since then, we’ve updated a huge amount of things in the WebUI.

In order to get the latest production stuff, simply delete stuff in your WebUI \ mastheads directory and restart the root server service. I think you’ll also need to clear everything in the WEBUI_SITES table in BFEnterprise (there’s not really a great way to go back and forth from dev sites to production sites).

Let us know if that works for you!

1 Like
13

Alright guys, thanks for your input, I will try and update as soon as I could.

Edited. I have cleared the rows in WEBUI_SITES table and now it looks like this. Looking good I guess and will update again later.

[{“id”:12049,“name”:“WebUI Common”,“version”:26,“url”:"\u002fwebui-sites\u002f12049"},
{“id”:12050,“name”:“WebUI Patch”,“version”:10,“url”:"\u002fwebui-sites\u002f12050"},
{“id”:12090,“name”:“WebUI Software Distribution”,“version”:8,“url”:"\u002fwebui-sites\u002f12090"},
{“id”:12124,“name”:“WebUI Custom”,“version”:7,“url”:"\u002fwebui-sites\u002f12124"}]

14

Great, removing the WEBUI_SITES in the database and resetting WebUI has resolved the issue. Now i am able to deploy any fixlets to a specific relevant endpoint. Thank you guys for your great assistance.

15

Yeah, this is kind of a crappy way of dealing with this particular problem. We’re kind of okay with it for now because most people don’t switch between non production versions of sites and production versions of sites in the WebUI.