Guardian has been upgraded to r1519, and the h1guardian0 machine has been rebooted.

This upgrade includes a couple of minor bug fixes and a new guardian log server/client:

• Guardian nternal channel access server updates at same rate as the main process thread.  This should address the state not registered bug.
• Minor fixes, improvements, and tweaks to some of guardutil functions
  • fixed 'git-clone' function to retrieve the archive
  • improved the 'plot' function to plot node status info around a specified time
  • added 'state-hist' function to print guardian states over a specified time range
• new guardlog client/server
• changes to node logging on h1guardian0 to increase log size, and compress logs on rotation.  This requires the new log server for searching the logs

h1guardian0 reboot

After these changes were applied, all nodes were re-created to get the new changes to the logging, and the h1guardian0 machine was rebooted.  A couple of small issues were encountered during the reboot:

• Some of the manager nodes thought that they had requested states from their subordinates, but the subordinates where in the NONE state (no request).  My guess is that this might be due to some sort of race condition as the nodes are initialized (cas is initialized before the nodes starts processing requests?).   This happened with some of the SEI nodes and the ISC_LOCK.  It was trivially resolved by requesting INIT from the managers.
• BRS nodes have no initial request defined, so they can up with NONE requests.
• SEI_BS is managed by ISC_LOCK, but ISC_LOCK is not initially doing anything.  At some point during initialization SEI_BS stalled, so it just sat there stalled.  Not a big deal, but could maybe be handled cleaner.

New guardctrl log client/server

This version of guardian includes a new and improved log client/server.  The new server running on the h1guardian0 machine:

• has a new RESTful http interface
• is now able to process the now possibly compressed node logs
• handles queries with date range filters, filtering for log files and log lines within the files that correspond to the date/time search parameters
• output log lines with timestamps in UTC, local, or GPS time

See "guardlog -h" for more info.