0000111: StormAlarm process to idle due to false alarming

Viewing Issue Simple Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0000111

[TMS]

major

always

17-03-09 15:08

14-06-10 07:55

Reporter

Jurjen Sluman

View Status

public

Assigned To

Arno Schoenmakers

Priority

normal

Resolution

fixed

Status

closed

Summary

0000111: StormAlarm process to idle due to false alarming

Description

Sometimes a false alarm is generated by the StormAlarm process.
Due to strange measurement values, reason still unknown, the process generates
a alarm and sends the RT's in the Stormstow (Zenith).

Now we trace the system and try to find the reason of the strage values.
Later the probe might be moved to the other side of the construction, on which it is mounted, to see what the effect is.

Until these test are running no Alarm and Stow command will be generated.
In times of heavy wind or storm we have to take care of the positions of the RT's

Additional Information

email of Arno Schoenmaker 06-Mar-2009:
After today"s incidents I have made some changes to the stormAlarm process on wop33. I added an option "-n" (or "--noalarm") that will run the process without issuing alarm messages, or setting the telescopes in storm position. To remind the operator it is in this state, every 24 hrs a mail or SMS will be send with the text: "Check: stormAlarm will NOT give alarm". The new version is active as of now (minus 10 minutes) The procedure how to handle in case the process creates a false alarm and sends the telescopes to zenith is in the Wiki: http://www.astron.nl/wsrt/wiki/doku.php?id=wsrtinfo:stormalarmdescription#manually_undo_a_storm_alarm [^] * Login as user monitor on wop33 (same password as 'tmsmgr') * Kill the running stormAlarm process running on wop33 (use ps -eaf | grep storm to find process). * Then immediately start it again using the -n option: stormAlarm -n * Make sure only one stormAlarm process is running (use ps -eaf | grep storm to find processes) * Then, log in on wop28 as tmsmgr * com_stow nostorm 0123456789ABCD ¨ releases storm flag * com_status 3 0123456789ABCD ¨ Sets telescopes to computer * com_status 9 5 ¨ Puts Tel. 5 in Test mode. If the problem with the windspeedvalues have been solved, kill the running instance of stormAlarm on wop33. ThestormAlarm process will be started automatically after a while (by SysGuard).

Attached Files

Relationships

There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
17-03-09 15:08	Jurjen Sluman	New Issue
17-03-09 15:09	Jurjen Sluman	Assigned To	=> Arno Schoenmakers
17-03-09 15:09	Jurjen Sluman	Status	new => assigned
29-06-09 07:34	Jurjen Sluman	Status	assigned => resolved
29-06-09 07:34	Jurjen Sluman	Resolution	open => fixed
14-06-10 07:55	Arno Schoenmakers	Status	resolved => closed