Jump to content
Welcome to our new Citrix community!
  • 0

How to read logs and track actvity of pool operator?


Question

I recently found that one of the poll hosts (not master) has been rebooted. I see plenty of message just before reboot.

 

xapi: [ info|msqh43|9614012 |Async.VM.clean_shutdown R:2f56ea77c6f2|dispatcher] spawning a new thread to handle the current task (trackid=9210b59112762c9ce2397da14c45e9a7)
xapi: [debug|msqh43|9614012 |Async.VM.clean_shutdown R:2f56ea77c6f2|audit] VM.clean_shutdown: VM = 'd44a19c0-54b3-6ed3-b7a3-47c2497ae15a (vpn1 vpn2)'
xapi: [ info|msqh43|9614012 |Async.VM.clean_shutdown R:2f56ea77c6f2|xapi] Session.create trackid=83fafba5520f388d22ef2742bd9f8e6f pool=true uname= originator=xapi is_local_superuser=true auth_user_sid= parent=trackid=9210b59112762c9ce2397da14c45e9a7
xapi: [debug|msqh43|9614012 |Async.VM.clean_shutdown R:2f56ea77c6f2|mscgen] xapi=>xapi [label="pool.get_all"];
xapi: [ info|msqh43|9614014 |Async.VM.clean_shutdown R:d2417aee323b|dispatcher] spawning a new thread to handle the current task (trackid=9210b59112762c9ce2397da14c45e9a7)
xapi: [debug|msqh43|9614014 |Async.VM.clean_shutdown R:d2417aee323b|audit] VM.clean_shutdown: VM = '6c349a21-fca2-e17d-5bca-df13de65adcc (ELK Server)'
xapi: [debug|msqh43|9614013 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:pool.get_all D:4e2107056753 created by task R:2f56ea77c6f2
xapi: [ info|msqh43|9614014 |Async.VM.clean_shutdown R:d2417aee323b|xapi] Session.create trackid=158142cda7e3ab3b4d153ea416d164cd pool=true uname= originator=xapi is_local_superuser=true auth_user_sid= parent=trackid=9210b59112762c9ce2397da14c45e9a7

 

So I guess it is just a human mistake and not hardware issue. We are using Active Directory group for access to pool and some engineers have root passwords as well.

How can I track the situation down to the AD login name or (and even better) source IP address of the connection?

 

Thank you.

Link to comment

2 answers to this question

Recommended Posts

  • 0

Thank you Tibias!


I already checked last and now reading raw logs like audit and xensource.log.

I just don't have an information about Xenservre internals, especially in pool environment. There are lot of information in that logs and I wonder how to start tracking managing connection from the stunnel to particular thread which executing task.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...