Details
-
Type:
Bug
-
Status:
Need More Info
(View Workflow)
-
Priority:
Normal
-
Resolution: Not Fixed
-
Component/s: NEP
-
Labels:None Labels
-
Customer:Azerconnect
Description
RB not Running on PROD
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 2 hours
-
checking server logs + adding more logs
-
- Time Spent:
- 1 hour
-
automated xml import run and log monitoring, the import params values are getting assigned the correct value now.
-
- Time Spent:
- 3 hours
-
Apply the requested patch and restart the application over the weekend.
-
- Time Spent:
- 1 hour
-
Shared required server log.
-
- Time Spent:
- 2 hours
-
After checked the status of application cascade the error to next label for fix this issue.
-
- Time Spent:
- 5 hours
-
Analyze the logs and checked the application status, also followup with L3 and discuss with them to show them the status.
-
- Time Spent:
- 3 hours
-
Analyze the log for check changes status in XML and forward to L3 about status over the weekend.
-
- Time Spent:
- 6 hours
-
Applied patch of which released to fix this issue and generate XML manual then followup with L3.
-
- Time Spent:
- 6 hours
-
Followup with L3 to fix the issue then update config file shared by L3 then manual generate XML and share feedback to them. Also join call with cyber mack for patch deployment.
-
- Time Spent:
- 2 hours
-
Restart AZRC test server.
-
- Time Spent:
- 1 hour
-
Check Import status and share logs with Khaled.
-
- Time Spent:
- 30 minutes
-
Given XML files uploaded on AZRC test server .
-
- Time Spent:
- 2 hours
-
Download and share requested dumps with Khaled
-
- Time Spent:
- 3 hours
-
Reachability status of all the provided IPs has been thoroughly checked. All the reachable IPs have been successfully added to the IP.list
-
- Time Spent:
- 2 hours
-
Build 3.7.71.80.432 patch has been deployed for AZRC test server and 2024-08-08-05.23.24_Azerbaijan.xml copied from prod to test server.
-
- Time Spent:
- 1 day, 4 hours
-
I have added the monitoring logs on the lambda rout saver to trouble shoot the cause of the delay.