Project

General

Profile

Bug #18118

copyset localapp dpmclient disconnects sometimes don't reconnect automatically.

Added by Dennis Nicklaus almost 3 years ago. Updated almost 2 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
Dennis Nicklaus
Category:
Local App driver
Target version:
dev-app v1.3
Start date:
11/03/2017
Due date:
% Done:

0%

Estimated time:
Duration:

Description

On Nov. 3rd, Elvin called from CMTS to report that the Cryo RF heating compensation wasn't working, and that
the T:CRFPOW device was reading 0. T:CRFPOW should be set by a copyset localapp running on clx58, copying the device T:LPSUMC to T:CRFPOW.

Sometimes, the reading job of copyset dies (many valid reasons). It is supposed to restart automatically. In the clx58 elog, I see:

=INFO REPORT==== 3-Nov-2017::01:06:47 ===
Appserver dpmclient disconnected for copyset:copy_set. Will retry.

=INFO REPORT==== 3-Nov-2017::01:06:50 ===
Appserver reactivated dpmclient for copyset:copy_set.

But apparently the reactivation didn't really work because the above value copy wasn't happening.

The dpmclient readingjob of copyset can be forced to restart by issuing a Reset command to T:CDLPCH, which is what I did to alleviate the immediate problem today.

But Copyset's auto-restart ought to work and it seems it didn't today.

History

#1 Updated by Richard Neswold almost 2 years ago

  • Category set to Local App driver
  • Status changed from New to Assigned
  • Target version set to dev-app v1.3

#2 Updated by Dennis Nicklaus almost 2 years ago

  • Status changed from Assigned to Feedback

dev-app|05e57a33 provides another level of oversight. If no readings have been received for N (default =2) "run" periods (when the runfun is called), then completely destroy and rebuild the dpmclient.

Also available in: Atom PDF