Hi,
Having issues with my Root Server and it connecting to its MSSQL DB (various DB connection issues in the BESRelay.log file. Need to turn on DEBUG logging for support. Not sure how to do this. Can I use the “BES Client Setting: Enable Debug Logging” fixlet?
Is there a manual procedure? I found this: https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Installation/c_logfiles.html But I am not 100% clear what needs to be done.
Thanks,
Doug
I think the steps described at https://hclpnpsupport.service-now.com/csm?id=kb_article&sysparm_article=KB0023389 would produce the most useful log info.
Thank you Jason!!! Saved that for future reference (not sure why I couldn’t find it)
Glad to help. I knew the terms I was looking for 
If you can post a snippet of your log here I’d be happy to have a look. Do you have a support case open yet?
I do have a case open: (Case CS0104242)
Have a lot of weird errors with data base connection issues…Masthead issues, etc. Something went haywire on Friday night bring things to a halt. All my actions disappeared from the console…just really weird.
Here’s some of the non DEBUG logging as I turned it off last night.
Sun, 29 Mar 2020 11:22:12 -0400 - /data/actions (4528) - A problem occurred with the action having id = 428398 Database Error: A database query unexpectedly failed to return any results.
Sun, 29 Mar 2020 11:22:12 -0400 - /data/actions (4528) - Database Error: A database query unexpectedly failed to return any results.
Sun, 29 Mar 2020 11:22:12 -0400 - /masthead (2528) - Unable to find site id for URL: http://BFServer:52311/cgi-bin/bfgather.exe/actionsite
Sun, 29 Mar 2020 11:22:12 -0400 - /masthead (2528) - MastheadPlugin Error: class NoSiteIDMatchesURL
Sun, 29 Mar 2020 11:22:12 -0400 - /masthead (9904) - Unable to find site id for URL: http://BFServer:52311/cgi-bin/bfgather.exe/actionsite
Sun, 29 Mar 2020 11:22:12 -0400 - /masthead (9904) - MastheadPlugin Error: class NoSiteIDMatchesURL
Sun, 29 Mar 2020 11:22:14 -0400 - /data/actions (4928) - A problem occurred with the action having id = 428398 Database Error: A database query unexpectedly failed to return any results.
Sun, 29 Mar 2020 11:22:14 -0400 - /data/actions (4928) - Database Error: A database query unexpectedly failed to return any results.
Sun, 29 Mar 2020 11:22:15 -0400 - /masthead (9396) - Unable to find site id for URL: http://BFServer:52311/cgi-bin/bfgather.exe/actionsite
Sun, 29 Mar 2020 11:22:15 -0400 - /masthead (9396) - MastheadPlugin Error: class NoSiteIDMatchesURL
Sun, 29 Mar 2020 11:22:16 -0400 - /masthead (6536) - Unable to find site id for URL: http://BFServer:52311/cgi-bin/bfgather.exe/actionsite
Sun, 29 Mar 2020 11:22:16 -0400 - /masthead (6536) - MastheadPlugin Error: class NoSiteIDMatchesURL
Sun, 29 Mar 2020 11:22:17 -0400 - /data/actions (4532) - A problem occurred with the action having id = 428398 Database Error: A database query unexpectedly failed to return any results.
Sun, 29 Mar 2020 11:22:17 -0400 - /data/actions (4532) - Database Error: A database query unexpectedly failed to return any results.
Sun, 29 Mar 2020 11:22:19 -0400 - /data/actions (4140) - A problem occurred with the action having id = 428398 Database Error: A database query unexpectedly failed to return any results.
Sun, 29 Mar 2020 11:22:19 -0400 - /data/actions (4140) - Database Error: A database query unexpectedly failed to return any results.
It’s good you have a case open. Did anything unusual occur Friday night? Can you see when action 428398 was issued and check the Windows Event Logs for errors around that time?
Some of those messages look familiar. I had a case about a year ago where the RAID volume hosting the SQL database went offline and left a corrupt action, causing subsequent site gathers to fail. The Support team should be able to help.
In my case we went in to the SQL database and deleted the affected action manually, then created another action as Master Operator to increment the version of actionsite.
No idea what happened on Friday. I know no changes have been made to the BF server since February (Windows patches) and the system was working fine up until EOD when I logged off. heh.
Can’t see any actions in my console, unfortunately …Probably need to figure out how to fish around in the SQL DB…as I suspect (from the start) if we delete that "rogue’ action 428398, might help things out, if not resolve this issue…as it has been repeating over and over again.
I agree, I think that’s the case.
When I ask if anything happened Friday, I mean something along the lines of a power outage, unexpected reboot, or hard drive going offline; a corrupt action isn’t something you can make happen if you tried, I’d be looking for something like a hardware problem.
You might try using the REST API to check this from a browser.
First navigate to https://your-bes-server:52311/api/action/428398
You’ll get prompted for your console credentials. I’m curious whether it’ll even retrieve the details of the action (it probably won’t).
You might also try using iem.exe, the REST API client that comes with the BigFix Server installation.
iem LOGIN --server <bigfix_server> --user <operator_name> --password <operator_password>
Then try stopping the action via
iem POST https://bigfix-server-name:52311/api/action/428398/stop
and try deleting it via
iem DELETE https://bigfix-server-name:52311/api/action/428398
Reference:
https://developer.bigfix.com/rest-api/iem_cli/iem_requests.html
If none of these clears it up, then you’re down to surgery at the SQL level, which you should do only with the help of the Support team. Let me know if this helps first though.
Hi Jason,
Got it. Support sent a few SQL’s to ID the action and delete it. Looks like a similar issue to what you mentioned earlier. Thanks for that, helped tremendously.
Doug