This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
lbaops:cacorhints [2008/06/06 11:59] guest |
lbaops:cacorhints [2015/12/18 16:38] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== CACOR Freezes\\ ==== | + | ==== CACOR Freezes ==== |
- | \\ | + | |
- | Assistance complains of "no recent data, check caobs & cacor" | + | Assistance complains of "no recent data, check caobs & cacor" |
- | \\ | + | |
- | In cacor area the cacor display and its starting term should have been ticking over every 10 sec. In this fault they are frozen!\\ | + | In cacor area the cacor display and its starting term should have been ticking over every 10 sec. In this fault they are frozen! |
- | \\ | + | |
- | Only known fix is to either use ^C in the xterm to kill cacor OR if that does not work, login to caccc as corr from another xterm and do an explicit kill.\ | + | Only known fix is to either use ^C in the xterm to kill cacor OR, if that does not work, login to caccc as corr from another xterm and do an explicit kill on the cacor process. |
- | \ | + | |
- | Then restart cacor.\\ | + | Then restart cacor. |
- | \ | + | (If cacor does not restart there may be residual processes running on caccc that need killing. Most likely a tk or sync process.) |
- | If caobs does not pick it up exit and restart caobs. You ned to do start/stop on the scan at least twice to get the system working properly.\ | + | |
- | \ | + | If caobs does not pick it up exit and restart caobs. You need to do start/stop on the scan at least twice to get the system working properly. |
Tasso 6/6/08 | Tasso 6/6/08 | ||