I have a fresh BigFix deployment on Windows 2016, (deployed specifically for ILMT purposes). I have installed the WebUI component, assigned our SSL certificate, and can access the homepage of the WebUI, but see only “The WebUI is initialising. the login screen will appear shortly”. It has been like this for 18hours. I see in datasync.log as the last entry “Successfully completed initialization at…”, so looking for any advice where to go next.
Thanks, Paul A
Without seeing the logs, I cannot say for certain. I have seen this where there’s a database discrepancy with credentials. Also, check to make sure the port for the DB is correct, by default it is 1433 but I have seen DBAs get fancy and change this from the standard.
Yes, we use non-standard ports for databases in my organisation. I have configured the logon details using the BigFix task called “Deploy/Update WebUI Database Configuration”, using windows authentication (user which has sa permissions to the database instance). We also have two database instances on this SQLServer Express install, this one called “BES”. In the database config form I have specified port number instead of instance name, which is an alternative option. I am going through logs and can see the following in login.log (all other logs show no errors):
2019-10-31T10:07:21.349Z bf:login:error Error: write EPROTO 6420:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:252:
at WriteWrap.afterWrite [as oncomplete] (net.js:779:14)
Note, the path specified in the error does not exist on my server.
I should advise that I also applied a replacement SSL certificate issued by our own organisation’s CA. Browsing to the WebUI site in Firefox I can see this company SSL cert being used correctly, so the config for this looks to be correct I.e,. not related to the issue in the log above.
Edit: I have spotted additional database connection errors in pps.log. I am investigating.
I have tried several different logon/instance/port/hostname combinations in the connect string and am now of the belief that its not a logon issue - it may have been earlier, but not with the current configuration. I now see the following in these logs (not sure if its maybe a licensing issue - I have only a free ILMT license - am I allowed to use WebUI on this license?) Anyway here’s the log details:
appadmin.log:
Thu, 31 Oct 2019 11:05:04 GMT hsts deprecated The "includeSubdomains" parameter is deprecated. Use "includeSubDomains" (with a capital D) instead. at node_modules\bfapp\lib\bfapp.js:8:3810
2019-10-31T11:05:04.588Z bf:bfapp:debug appAdmin 0.2.1 listening on port 5010 in production mode
datasync.log:
Thu, 31 Oct 2019 11:05:02 GMT hsts deprecated The "includeSubdomains" parameter is deprecated. Use "includeSubDomains" (with a capital D) instead. at node_modules\bfapp\lib\bfapp.js:8:3810
2019-10-31T11:05:02.118Z bf:bfapp:debug datasync 1.0.0 listening on port 5003 in production mode
Thu, 31 Oct 2019 11:05:02 GMT bf:datasync:initialize:debug Beginning initialization at 2019-10-31T11:05:02+00:00
Thu, 31 Oct 2019 11:05:02 GMT bf:datasync:initialize:debug Initiating Cache Refresh with TTL : 600 sec
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug Reset completed, Check if need to reset sequence
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug sequence check completed, initializing custom app tables at 2019-10-31T11:05:03+00:00
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug Creating tables!
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug Custom app table initialization completed at 2019-10-31T11:05:03+00:00
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug Table definitions have not changed, skipping initialization
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug Functions definitions have not changed, skipping initialization
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug View definitions have not changed, skipping initialization
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug Initializing stored procedures at: 2019-10-31T11:05:03+00:00
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug Removing any existing stored procedures.
Thu, 31 Oct 2019 11:05:03 GMT bf:datasync:initialize:debug Finished removing any existing stored procedures.
Thu, 31 Oct 2019 11:05:04 GMT bf:datasync:initialize:debug Stored procedure initialization completed at 2019-10-31T11:05:04+00:00
Thu, 31 Oct 2019 11:05:04 GMT bf:datasync:initialize:debug Index definitions have not changed, skipping initialization
Thu, 31 Oct 2019 11:05:04 GMT bf:datasync:initialize:debug Updating schema version at 2019-10-31T11:05:04+00:00
Thu, 31 Oct 2019 11:05:04 GMT bf:datasync:initialize:debug Schema version update completed at 2019-10-31T11:05:04+00:00
Thu, 31 Oct 2019 11:05:04 GMT bf:datasync:initialize:debug Successfully completed initialization at 2019-10-31T11:05:04+00:00
login.log:
2019-10-31T11:23:42.950Z bf:login:error Error: write EPROTO 7144:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:252:
at WriteWrap.afterWrite [as oncomplete] (net.js:779:14)
pps.log:
Thu, 31 Oct 2019 11:05:03 GMT hsts deprecated The "includeSubdomains" parameter is deprecated. Use "includeSubDomains" (with a capital D) instead. at node_modules\bfapp\lib\bfapp.js:8:3810
2019-10-31T11:05:04.775Z bf:bfapp:debug pps 1.0.0 listening on port 5006 in production mode
workflow.log:
Thu, 31 Oct 2019 11:05:03 GMT hsts deprecated The "includeSubdomains" parameter is deprecated. Use "includeSubDomains" (with a capital D) instead. at node_modules\bfapp\lib\bfapp.js:8:3810
(node:776) [DEP0025] DeprecationWarning: sys is deprecated. Use util instead.
2019-10-31T11:05:03.135Z bf:bfapp:debug workflow 1.0.0 listening on port 5004 in production mode
a lot of these logs mentioning “includeSubdomains” parameter. Not sure if that has any relevence.
Can anyone provide info/advice on this please?