Valentin Vidić

You can check if it works correctly with the `sources.json` included in the repo. If that is working than it has some problems reading from the provided sources. To debug...

Sure, here is a [test.zip](https://github.com/ClusterLabs/crmsh/files/615892/test.zip) example created on a test Debian/unstable cluster with: ``` /usr/share/crmsh/hb_report/hb_report -f 09:00 test ``` Some resources were moved and node put into standby but still...

Yes, the problem with log detection seems to be the grep exits with 2 probably due to subdirs. ``` # grep -l -e Mark:HB_REPORT:1480335149 /var/log/*; echo $? grep: /var/log/apache2: Is...

Another problem seems to be that the logger is called after the HA logs are checked: ``` # /usr/share/crmsh/hb_report/hb_report -v -f 09:00 test2 crm2: DEBUG: setting CRM_DAEMON_DIR to /usr/lib/pacemaker crm2:...

Adding more verbosity fails if ``dash`` is used as ``/bin/sh``: ``` # /usr/share/crmsh/hb_report/hb_report -v -v -f 09:00 test2 crm2: INFO: high debug level, please read debug.out /usr/share/crmsh/hb_report/hb_report: 1285: /usr/share/crmsh/hb_report/hb_report: Bad...

Seems that changing the condition from ``is_node`` to ``is_collector`` in ``hb_report`` helps with logfile detection: ``` # # part 4: find the logs and cut out the segment for the...

Changing to bash does not seem to make a difference. It seems to me ``logger`` is only run for ``__slave`` calls but log detection is run before that in the...

Thanks for checking the report I sent. Here is what I get by default from ``crm -d history``: ``` crm(live)history# events DEBUG: setting source to live DEBUG: setting report times:...

Yep, until there is a more general solution I patched the Debian package to prefer ``pacemaker.log`` and ``syslog`` as can be seen here: https://anonscm.debian.org/cgit/debian-ha/crmsh.git/tree/debian/patches/0012-Fix-crm-history.patch Using multiple log files would be...

Maybe it would be easier if you used some command line TWAMP server/client rather than a graphical one?