WebUI broken after update?

IanDM · July 13, 2024, 8:12pm

Hi All,

BigFix on RHEL8 OS with no changes to the environment in several months. I noticed Patch policies did not start as expected and then found I can’t log in to WebUI. When I checked on WebUI logs I find the below.

(Note: “FQDN” for brevity and redaction)

Sat, 13 Jul 2024 20:01:37 GMT bf:appmonitor:debug Requesting APP_KEY and APP_CERT from the platform.
Sat, 13 Jul 2024 20:01:37 GMT bf:appmonitor:debug POST https://bigfixuat.FQDN:52315/api/webui-app-credentials
Sat, 13 Jul 2024 20:01:37 GMT bf:appmonitor:debug Requesting WEB_KEY and WEB_CERT from the platform.
Sat, 13 Jul 2024 20:01:37 GMT bf:appmonitor:debug GET https://bigfixuat.FQDN:52315/api/webui-web-credentials
Sat, 13 Jul 2024 20:01:37 GMT bf:bfquery:debug GET https://bigfixuat.FQDN:52315/api/serverinfo
Sat, 13 Jul 2024 20:01:37 GMT bf:appmonitor:debug Unable to retrieve Platform server information, defaulting to SQLite
/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:155
                throw e;
                ^

Error: OS not supported
    at n (/var/opt/BESWebUI/WebUI/service-app/node_modules/bfappmonitor/lib/env.js:7:2914)
    at _fulfilled (/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:854:54)
    at /var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:883:30
    at Promise.promise.promiseDispatch (/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:816:13)
    at /var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:624:44
    at runSingle (/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:137:13)
    at flush (/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:125:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

I am guessing updates have caused incompatibility issues as somehow after being active for years node or some WebUI component is now reporting “Error: OS not supported”.

From action logs, it seems the patching did not run last month either but the app logs are rolling over several times a day so when it started is not available. Anyone experience this? Is this a known issue?

Thanks,
Ian

orbiton · July 13, 2024, 9:08pm

Please look into the following line:

Sat, 13 Jul 2024 20:01:37 GMT bf:bfquery:debug GET https://bigfixuat.FQDN:52315/api/serverinfo
Sat, 13 Jul 2024 20:01:37 GMT bf:appmonitor:debug Unable to retrieve Platform server information, defaulting to SQLite

Looks like it was unable to complete the API call.

Have you checked if the port 52315 is open on the Remote WebUI server by the WebUI process?

DanieleColi · July 15, 2024, 7:32am

@orbiton is right. You may also want to try to run the fixlet “Rotate WebUI Certificates”: it won’t affect custom HTTPs certificate presented to end users, but it will renew internal certificate used for secure communications between WebUI and Root Server.

IanDM · July 15, 2024, 6:15pm

I can confirm, actually reconfirmed the port is open. WebUI is installed on the master so firewalls etc are not an issue.

I tried rotating certificates and that did not make any difference.

Since it’s just a lab environment, I removed and reinstalled fresh (using fixlets) and the issue was recreated. I have another Linux machine in lab environment to test on to see if the issue happens there as well, maybe I’ll try using the installer ISO, but this is starting to look like a case for a case.

# tail -f service-wrapper.log WebUI/logs/service-app.log
==> service-wrapper.log <==
Mon, 15 Jul 2024 12:49:44 -0400 -- [WebUI] process started

==> WebUI/logs/service-app.log <==
Mon, 15 Jul 2024 16:49:44 GMT bf:appmonitor:debug Requesting APP_KEY and APP_CERT from the platform.
Mon, 15 Jul 2024 16:49:44 GMT bf:appmonitor:debug POST https://bigfixuat.FQDN:52315/api/webui-app-credentials
Mon, 15 Jul 2024 16:49:44 GMT bf:appmonitor:debug Requesting WEB_KEY and WEB_CERT from the platform.
Mon, 15 Jul 2024 16:49:44 GMT bf:appmonitor:debug GET https://bigfixuat.FQDN:52315/api/webui-web-credentials
Mon, 15 Jul 2024 16:49:44 GMT bf:bfquery:debug GET https://bigfixuat.FQDN:52315/api/serverinfo

==> service-wrapper.log <==
Mon, 15 Jul 2024 12:49:44 -0400 -- [WebUI] process exited with code 1 signal 0

==> WebUI/logs/service-app.log <==
Mon, 15 Jul 2024 16:49:44 GMT bf:appmonitor:debug Unable to retrieve Platform server information, defaulting to SQLite
/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:155
                throw e;
                ^

Error: OS not supported
    at n (/var/opt/BESWebUI/WebUI/service-app/node_modules/bfappmonitor/lib/env.js:7:2914)
    at _fulfilled (/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:854:54)
    at /var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:883:30
    at Promise.promise.promiseDispatch (/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:816:13)
    at /var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:624:44
    at runSingle (/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:137:13)
    at flush (/var/opt/BESWebUI/WebUI/service-app/node_modules/q/q.js:125:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

Node.js v18.20.2

orbiton · July 15, 2024, 7:06pm

Just to make sure if you stop the webui service
Port 52315 is not listened by another process?

And it is not listened by another process , when the WebII is started which results returned by the :
https://bigfixuat.FQDN:52315/api/serverinfo

I had an issue that another application took this number Port because it’s on the range of high ports

IanDM · July 17, 2024, 4:57am

The issue it turns out was at the DB2 level. After checking the /api/serverinfo I noted it was showing the following DB2 error:

After consulting with one of our DBA he suggested the following which resolved the issue.

# ./db2iupdt -u db2fenc1 db2inst1

Have not been able to determine what caused the issue to start but at this point, just happy the lab environment WebUI is functional again

orbiton · July 17, 2024, 5:41am

Amazing! Thanks for sharing!