Internal Errigal Collaboration Wiki

User Tools

Site Tools

Trace: • res-w9202 • res-w9103 • res-w9105 • res-w9231 • res-w9901 • res-w9802 • res-w8401 • res-w9403 • res-w9502 • res-w9601
resolution_area:watchdog_resolutions:res-w8603

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
resolution_area:watchdog_resolutions:res-w8603 [2021/06/25 10:09] – external edit 127.0.0.1resolution_area:watchdog_resolutions:res-w8603 [2021/07/05 16:55] (current) – wflaherty
Line 1: Line 1:
 =====FiberImportMissingFor48hrs===== =====FiberImportMissingFor48hrs=====
  
-**Level:** Major+**Level:** Major 
  
  
 **Purpose:** **Purpose:**
 +
 +This is to ensure that the Fiber tool is working and updated regularly.
 +
 +Fiber is only used for ExteNet.
  
 **Scenario:** **Scenario:**
 +Watchdog: 
 +[name: 'checkLog', type: 'EQUAL', value: ['Stale import check - no automated imports found for past 48 hours'], level: ['MAJOR'], alarmId: 'FiberImportMissingFor48hrs']
 +
 +This watchdog looks back about 4 hours in the logs for the line in the value field above. If there hasn't been a successful import in 48 hours, this will be printed to the logs. 
 +
 +Further details on the specifics are here 
 +https://docs.google.com/document/d/1zO4FdZSOijXBcqedM8afvp3xKOgzIVuHEOi_UdQMREo/edit#
  
 **Resolution:** **Resolution:**
 +
  
 **Manual Action Steps:** **Manual Action Steps:**
 +Probably have to restart the Fiber application
 +
 +Ensure you have the latest of the env-config repo and the deployments-playbook repo from bitbucket.
 +Assuming you have both repositories in the same folder then run 
 +<code>
 +cd /your/env-config/location
 +git checkout master && git pull && cd ../deployment-playbooks && git checkout master && git pull
 +</code>
 +
 +Restart the application with
 +<code>
 +ansible-playbook -i ../env-configuration/ServerName/hosts.ini fiber.yml --vault-id @prompt -e"actions='stop,start'" 
 +</code>
 +NOTE: Change ServerName and AppName for the actual server and application name 
 +
  
 **Auto Clear:** **Auto Clear:**
 +It will autoclear once the watchdog doesn't see the log line 4 hours back. So it may take 4 hours to auto clear even if it recovered. However, this is unlikely to automatically clear on its own since the line wouldn't have printed if there was a sucess in the last 48 hours.
  
resolution_area/watchdog_resolutions/res-w8603.1624612196.txt.gz · Last modified: 2021/06/25 10:09 by 127.0.0.1

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki