On some of the instances running in us-east-1b, there are below errors in system log:-
********
Initialising Xen virtual ethernet driver. microcode: CPU0 sig=0x206d7, pf=0x1, revision=0x70a platform microcode: firmware: requesting intel-ucode/06-2d-07 microcode: CPU1 sig=0x206d7, pf=0x1, revision=0x70a platform microcode: firmware: requesting intel-ucode/06-2d-07 Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed NET: Registered protocol family 10 lo: Disabled Privacy Extensions
********
Amazon had mentioned about the problems in a single zone in the status dashboard:-
http://status.aws.amazon.com/
Later today evening, AWS Support informed that interruption has been resolved:-
*************
8:59 PM PDT Between 3:22PM -- 8:40PM PDT we experienced elevated API error rates and latencies launching and stopping instances, and attaching and detaching EBS volumes in a single Availability Zone in the US-EAST-1 Region. Running instances and volumes were not affected. The issue has been resolved and the service is operating normally.
************
********
Initialising Xen virtual ethernet driver. microcode: CPU0 sig=0x206d7, pf=0x1, revision=0x70a platform microcode: firmware: requesting intel-ucode/06-2d-07 microcode: CPU1 sig=0x206d7, pf=0x1, revision=0x70a platform microcode: firmware: requesting intel-ucode/06-2d-07 Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed microcode: CPU0 update to revision 0x710 failed microcode: CPU1 update to revision 0x710 failed NET: Registered protocol family 10 lo: Disabled Privacy Extensions
********
Amazon had mentioned about the problems in a single zone in the status dashboard:-
http://status.aws.amazon.com/
Later today evening, AWS Support informed that interruption has been resolved:-
*************
8:59 PM PDT Between 3:22PM -- 8:40PM PDT we experienced elevated API error rates and latencies launching and stopping instances, and attaching and detaching EBS volumes in a single Availability Zone in the US-EAST-1 Region. Running instances and volumes were not affected. The issue has been resolved and the service is operating normally.
************
No comments:
Post a Comment