29
/
en
AIzaSyAYiBZKx7MnpbEhh9jyipgxe19OcubqV5w
April 1, 2024
Create
Public Timelines
Library
FAQ
For education
Cabinet
For educational institutions
For teachers
For students/pupils
Download
Export
Duplicate
Embed
Edit
532 views
0
0
New timeline
Created by
vinothkumar b
⟶ Updated 2 Aug 2017 ⟶
List of edits
Comments
Events
6th July 17:49 : FE0VM1636 Virtual Memory reached 99% Server stopped responding
6th July 20:49 : FE0VM1392 & FE0VM1391 Virtual Memory reached >99% Server stopped responding.
7th July 09:49 : FE0VM1635 back on production. Was out of pool since 24th May
7th July 15:39 : FE0VM1635 Virtual Memory reached 99% Server stopped responding
7th July 17:03 : FE0VM1391 Rebooted
7th July 17:23 : FE0VM1392 Rebooted
7th July 16:48: SI0VM2209 Virtual Memory reached 99% Server stopped responding
7th July 16:15: SI0VM2210 Virtual Memory reached 99% Server stopped responding
9AM Germany
7AM Germany
7th July 09:00 : Hendy noted abnormal session count. Asked wengfatt to check
7th July 16:44 : INC000012164682 was created by CI-Hotline but priority set to low
7th July 12:05 : WengFatt Send email to CI-Hotline. "Please help to log a ticket to the CI/OSB server operations team to restart 2 servers that are hang. Please set the priority to HIGH. This is important as the users are starting to login to the servers. Thank you very much. FE0VM1391.DE.BOSCH.COM FE0VM1392.DE.BOSCH.COM"
6th July 01 15 : INC000012150232 User reported performance issue.
5th July 6pm Germany
INC000012150232 investigation When all server was checked for the performance. Only three server shown in graph for Virtual Memory usage was dangerously high. but when checked up on previous date trend it is same and servers were back to normal state. Ticket was kept open for further investigation.
Periods
3 out of 5 servers were down
3 out of 6 servers were down
5 out of 6 servers down
FE0VM 1391 Maintena nce WengFatt
Grouping
Group of some events