Timeline
05/07/13:
- 00:22 Ticket #26 (NCL-2001 thermal derate flapping under load (Tyne Bridge gantry)) updated by
- It's a thermistor on a wire, Pike. There is no DNS involved in a …
05/06/13:
- 00:11 Ticket #26 (NCL-2001 thermal derate flapping under load (Tyne Bridge gantry)) updated by
- Could the derate flag be a bad reading coming back over DN—
- 00:00 Ticket #26 (NCL-2001 thermal derate flapping under load (Tyne Bridge gantry)) created by
- NCL-2001 (ANPR gantry, Tyne Bridge southbound) intermittently asserts …
05/05/13:
- 00:33 Ticket #25 (SENTRIS actuation web service (.asmx) returning wrong/stale results ...) updated by
- Confirmed against the CMS: GetNodeStatus on GAT-4471 returns …
05/04/13:
- 00:22 Ticket #25 (SENTRIS actuation web service (.asmx) returning wrong/stale results ...) updated by
- Not DNS this time, Pike. The .asmx worker came back on stale cached …
05/03/13:
- 00:11 Ticket #25 (SENTRIS actuation web service (.asmx) returning wrong/stale results ...) updated by
- First guess, and don't all groan at once: is it DNS? The service …
- 00:00 Ticket #25 (SENTRIS actuation web service (.asmx) returning wrong/stale results ...) created by
- After the overnight Server 2008 R2 hiccup on the SENTRIS host, the …
05/02/13:
- 00:22 Ticket #24 (IIS worker process recycling under load; escalated to Microsoft support) updated by
- While we wait — could the health-check be failing a lookup and …
04/30/13:
- 00:11 Ticket #24 (IIS worker process recycling under load; escalated to Microsoft support) updated by
- Crash dumps point at a native ISAPI filter, not our code. Beyond what …
- 00:00 Ticket #24 (IIS worker process recycling under load; escalated to Microsoft support) created by
- The IIS application pool fronting the internal actuation service …
04/29/13:
- 00:33 Ticket #23 (Telensa CMS intermittently cannot resolve node-registry hostname) updated by
- Pinned it to the primary resolver, bumped the TTL, killed the flapping …
04/24/13:
- 00:22 Ticket #23 (Telensa CMS intermittently cannot resolve node-registry hostname) updated by
- It's DNS. The CMS caches the registry A-record on a 60-second TTL …
- 00:11 Ticket #23 (Telensa CMS intermittently cannot resolve node-registry hostname) updated by
- Estate 'down' for two minutes then back. Nodes never dropped …
- 00:00 Ticket #23 (Telensa CMS intermittently cannot resolve node-registry hostname) created by
- The CMS periodically fails to reach the node registry and reports the …
Note:
See TracTimeline
for information about the timeline view.
