Hi,
Is there any information for Bigfix Server connecting which SQL or version?
If customer wants to provide that the Bigfix Server exactly connect to the right DB. How do I know which DB is bigfix server connect now?
Thanks.
For Windows/SQL, you can check the DSN sources in odbcad32.exe.
Thanks for reply.
But how to prove that the Bigfix Server is connecting. It seems there is no information on Bigfix tool or GUI could check about it.
How do you mean?
In my experience when the root server is failing to connect to the databse, I can’t open the console. When that’s occurred I’ve found related data in the server’s relay log (it’s either besrelay.log or relay.log or something like that in the BES Server directory).
Hi,
Customer wants to know the information on Bigfix Server like the following :
Connect DB:
10.xx.xx.xx or hostname
SQL 2016
To prove that the Bigfix is using this SQL.
Thanks.
Yes, - to get information like that will require a bit of searching.
From the BESRelay.log file mentioned earlier there is this:
Thu, 24 May 2018 21:50:30 +0200 - Main Thread (4146681984) - Soft Limit for Max Open Files: 1024.
Thu, 24 May 2018 21:50:30 +0200 - Main Thread (4146681984) - OpenSSL Initialized (Non-FIPS Mode)
Thu, 24 May 2018 21:50:30 +0200 - Main Thread (4146681984) - Using OpenSSL crypto library libBEScrypto - OpenSSL 1.0.2j-fips 26 Sep 2016
Thu, 24 May 2018 21:50:30 +0200 - Main Thread (4146681984) - Successfully connected to database
Thu, 24 May 2018 21:50:31 +0200 - Main Thread (4146681984) - Signature Algorithms: sha256, sha1
Thu, 24 May 2018 21:50:31 +0200 - Main Thread (4146681984) - Download Algorithms: sha256, sha1
Thu, 24 May 2018 21:50:31 +0200 - Main Thread (4146681984) - Successfully read server signing key
Thu, 24 May 2018 21:50:32 +0200 - Main Thread (4146681984) - Successfully read client CA key
And - maybe this helps - I am not a db2 specialist - so I am just adding a suggestion. Maybe someone else has a better idea (and this says nothing about connection with Windows/SQL).
db2 => LIST APPLICATIONS
Auth Id Application Appl. Application Id DB # of
Name Handle Name Agents
-------- -------------- ---------- -------------------------------------------------------------- -------- -----
DB2INST1 BESRootServer 111 *LOCAL.db2inst1.180524200933 BFENT 1
DB2INST1 BESFillDB 110 *LOCAL.db2inst1.180524200934 BFENT 1
DB2INST1 BESRootServer 77 *LOCAL.db2inst1.180524200900 BFENT 1
DB2INST1 BESRootServer 123 *LOCAL.db2inst1.180524200946 BFENT 1
DB2INST1 BESRootServer 287 *LOCAL.db2inst1.180524202628 BFENT 1
DB2INST1 BESRootServer 7458 *LOCAL.db2inst1.180525085146 BFENT 1
DB2INST1 BESRootServer 96 *LOCAL.db2inst1.180524200919 BFENT 1
DB2INST1 BESFillDB 109 *LOCAL.db2inst1.180524200932 BFENT 1
DB2INST1 BESRootServer 115 *LOCAL.db2inst1.180524200938 BFENT 1
DB2INST1 BESFillDB 114 *LOCAL.db2inst1.180524200937 BFENT 1
DB2INST1 BESRootServer 7456 *LOCAL.db2inst1.180525085144 BFENT 1
DB2INST1 BESRootServer 7442 *LOCAL.db2inst1.180525085013 BFENT 1
DB2INST1 BESFillDB 113 *LOCAL.db2inst1.180524200936 BFENT 1
DB2INST1 BESFillDB 112 *LOCAL.db2inst1.180524200935 BFENT 1
DB2INST1 BESWebReportsS 98 *LOCAL.db2inst1.180524200921 BESREPOR 1
DB2INST1 BESWebReportsS 2354 *LOCAL.db2inst1.180524234828 BESREPOR 1
And I am thinking that there may also be something to show the configuration using BESAdmin.sh - but that is just a guess.
Hope this helps!