vRLI 4.5 (how start Query the Results of In-Production Cluster Checks)

[SebastianGrugel]

According to documentation https://docs.vmware.com/en/vRealize-Log-Insight/4.5/com.vmware.log-insight.administration.doc/GUID-6... this tools can be started by:

"/usr/lib/loginsight/application/sbin/query-check-results.sh"

For me this is not working.

Output:

vrli0:~ # /usr/lib/loginsight/application/sbin/query-check-results.sh

usage: query-check-results.sh {username}

How can we start this tool? that can be useful before upgrade if everything is working fine.

Sebastian

vSebastian.net

[daphnissov]

That syntax is correct. You must supply it a local user name with administrative privileges and then auth (local admin is fine). You'll then get an ugly return of JSON hash that shows the result of the checks. Prettified it looks something like this:

{u'checks': [

  {u'status': u'green', u'finish': 1546434882646, u'name': u'vidm-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434882570, u'result': {u'result': u'Not using VMware Identity Manager for authentication.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434882718, u'name': u'localhost-only-loopback', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434882653, u'result': {u'result': u'localhost correctly placed.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434882776, u'name': u'ntp-config-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434882742, u'result': {u'result': u'NTP is not required in a single node system.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434882786, u'name': u'core-partition-free-space-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434882780, u'result': {u'result': u'There is currently enough free space.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434882857, u'name': u'nfs-deadlock-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434882791, u'result': {u'result': u'There are no NFS mounts'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434882890, u'name': u'active-directory-tcp-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434882862, u'result': {u'result': u'Not using active directory for authentication.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434882910, u'name': u'free-tmp-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434882909, u'result': {u'result': u'There is currently enough free space.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434882968, u'name': u'vidm-tcp-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434882918, u'result': {u'result': u'Not using VMware Identity Manager for authentication.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434883352, u'name': u'vm-ballooning-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434882978, u'result': {u'result': u'No ballooning.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434883361, u'name': u'cluster-tcp-ping-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434883360, u'result': {u'tcp-pings': []

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434883422, u'name': u'smtp-config-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434883368, u'result': {u'result': u'SMTP is configured. The SMTP server localhost: 25 was reachable and TCP connection was successful'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434883439, u'name': u'two-node-cluster-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434883427, u'result': {u'result': u'This is a single node system.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434883456, u'name': u'active-directory-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434883450, u'result': {u'result': u'Not using active directory for authentication.'

  }, u'suggestion': u''

  },

  {u'status': u'green', u'finish': 1546434883587, u'name': u'ntp-sync-check', u'node-token': u'8967126a-86b8-4b13-84e4-7183de86e774', u'start': 1546434883459, u'result': {u'result': u'NTP Server is available and local host is in sync.'

  }, u'suggestion': u''

  }

  ]

}

[SebastianGrugel]

Really ugly

I use root for this command.... and looks that same...

Did you use root account?

[daphnissov]

No, as I said, you need an authorized user to the app...not the appliance. root has no permissions to vRLI the app.

[SebastianGrugel]

Can you advice me which user is authorized for this "app" ?

If we have some default or should we create some separate ?

Sorry im not the best in linux... and this process is not described in documentation...

We have information about root user before use this command....

I tried in different ways without success...

I found some path inside this .sh file...

Some 101 instruction for dump ? eh...

Sebastian

[daphnissov]

As I said previously, the default "admin" account, which is a local user to vRLI (the application) should have rights. If not, use another local account with those permissions.

[SebastianGrugel]

How should looks like syntax in this command ?

/usr/lib/loginsight/application/sbin/query-check-results.sh ?

/usr/lib/loginsight/application/sbin/query-check-results.sh admin ?

Admin is not working for me too.

Other local users should i find in  /etc/passwd or can i create new one ?

Which permission are correct ? and how configure them ?

Sebastian

[daphnissov]

Run the .sh script interactively only passing the script name. Enter admin. Enter your password. Does that work? If not (and if your admin account logs you into the GUI with full administrative permissions), then something is wrong and I'd open an SR.

[sk84]

You need a user who has administrative privileges in the web frontend. Not in the console. So, an user you use to administer Log Insight in the web interface (creating new users or installing content packs, for example).

[daphnissov]

You need a user who has administrative privileges in the web frontend. Not in the console.

I believe I said this twice, right?

[sk84]

I believe I said this twice, right?

Yeah, I know, But since he had tried it with the root user afterwards, I thought I'd explain it even clearly with my words. :smileygrin: