aLIGO LHO Logbook

H1 GRD

jameson.rollins@LIGO.ORG - posted 11:51, Friday 06 May 2016 - last comment - 12:01, Wednesday 11 May 2016(27046)

minor guardian update to fix minor log viewing issue

I just pushed a minor upgrade to guardian to fix a small issue with the guardlog client when following node logs. The new version is r1542.

The client was overly buffering stream data from the server, which was causing data from the stream to not be output in a timely manner. This issue should be fixed in the version I just pushed.

As always make sure you have a fresh session to get the new version:

jameson.rollins@operator1:~ 0$ which guardlog
/ligo/apps/linux-x86_64/guardian-1542/bin/guardlog
jameson.rollins@operator1:~ 0$

Comments related to this report

sheila.dwyer@LIGO.ORG - 17:02, Tuesday 10 May 2016 (27099)

Link

sheila.dwyer@operator1:~/StripTools$ lockloss select

usage: guardlog [-h] [-a TIME] [-b TIME] [-c TIME] [-d S] [-o H] [-t] [-n]

[-u | -l | -g | -r | -p] [-x]

NODE [NODE ...]

guardlog: error: unrecognized arguments: --dump

Traceback (most recent call last):

File "/ligo/cds/userscripts/lockloss", line 408, in

args.func(args)

File "/ligo/cds/userscripts/lockloss", line 259, in cmd_select

selected = select_lockloss_time(index=args.index, tz=args.tz)

File "/ligo/cds/userscripts/lockloss", line 140, in select_lockloss_time

times = list(get_guard_lockloss_events())[::-1]

File "/ligo/cds/userscripts/lockloss", line 107, in get_guard_lockloss_events

output = subprocess.check_output(cmd, shell=True)

File "/usr/lib/python2.7/subprocess.py", line 544, in check_output

raise CalledProcessError(retcode, cmd, output=output)

subprocess.CalledProcessError: Command 'guardlog --dump --today ISC_LOCK' returned non-zero exit status 2

sheila.dwyer@operator1:~/StripTools$ which guardlog

/ligo/apps/linux-x86_64/guardian-1542/bin/guardlog

sheila.dwyer@operator1:~/StripTools$

It seems like there is a problem accessing the guardian logs again, I wonder if its related to this update or not. I don't know if anyone had tried to look at locklosses since the update.

sheila.dwyer@operator1:~/StripTools$ lockloss select

usage: guardlog [-h] [-a TIME] [-b TIME] [-c TIME] [-d S] [-o H] [-t] [-n]

[-u | -l | -g | -r | -p] [-x]

NODE [NODE ...]

guardlog: error: unrecognized arguments: --dump

Traceback (most recent call last):

File "/ligo/cds/userscripts/lockloss", line 408, in

args.func(args)

File "/ligo/cds/userscripts/lockloss", line 259, in cmd_select

selected = select_lockloss_time(index=args.index, tz=args.tz)

File "/ligo/cds/userscripts/lockloss", line 140, in select_lockloss_time

times = list(get_guard_lockloss_events())[::-1]

File "/ligo/cds/userscripts/lockloss", line 107, in get_guard_lockloss_events

output = subprocess.check_output(cmd, shell=True)

File "/usr/lib/python2.7/subprocess.py", line 544, in check_output

raise CalledProcessError(retcode, cmd, output=output)

subprocess.CalledProcessError: Command 'guardlog --dump --today ISC_LOCK' returned non-zero exit status 2

sheila.dwyer@operator1:~/StripTools$ which guardlog

/ligo/apps/linux-x86_64/guardian-1542/bin/guardlog

sheila.dwyer@operator1:~/StripTools$

jameson.rollins@LIGO.ORG - 07:25, Wednesday 11 May 2016 (27110)

Link

Sorry, Sheila. This issue has been fixed now. Just needed to tweak the lockloss script to account for some updated guardlog arguments.

sheila.dwyer@LIGO.ORG - 12:01, Wednesday 11 May 2016 (27117)

Link

Yes, its working, thank you Jamie.