Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
Date: 2014-12-29 14:47:25 UTC We've isolated and blocked the flow in question and adapted the workaround to take into account the new settings.
Date: 2014-12-29 12:28:23 UTC There's a new issue. The workaround implemented this weekend isn't enough. We're going to try to identify the flow causing the issue.
Date: 2014-12-28 10:36:01 UTC We set up a workaround
We must decide wether we update the vRack infrastructur
with some interruptions in the service or we wait until
the end of March to have the switch on the vRack 3.0 without
any interruption in the service. We are going to discuss
with our customers.
Date: 2014-12-28 10:34:20 UTC RP/0/RSP0/CPU0:Dec 27 15:19:45 UTC: packet[77]: %PKT_INFRA-PAKWATCH-6-INFO_HEAD : PROCESS NAME PID COUNT
RP/0/RSP0/CPU0:Dec 27 15:19:45 UTC: packet[77]: %PKT_INFRA-PAKWATCH-6-INFO_BODY : pkg/bin/udp 775307466 9044
RP/0/RSP0/CPU0:Dec 27 15:19:45 UTC: packet[77]: %PKT_INFRA-PAKWATCH-6-USER_INFO2 : Only 1 users found using PAK FSV.
RP/0/RSP0/CPU0:Dec 27 15:20:45 UTC: packet[77]: %PKT_INFRA-PAKWATCH-3-DEPLETION_CRITICAL : Depletion level 90 percent for resource PAK FSV
RP/0/RSP0/CPU0:Dec 27 15:20:45 UTC: packet[77]: %PKT_INFRA-PAKWATCH-6-USER_INFO : Top 5 users of PAK FSV:
RP/0/RSP0/CPU0:Dec 27 15:20:45 UTC: packet[77]: %PKT_INFRA-PAKWATCH-6-INFO_HEAD : PROCESS NAME PID COUNT
RP/0/RSP0/CPU0:Dec 27 15:20:45 UTC: packet[77]: %PKT_INFRA-PAKWATCH-6-INFO_BODY : pkg/bin/udp 775307466 9044
RP/0/RSP0/CPU0:Dec 27 15:20:45 UTC: packet[77]: %PKT_INFRA-PAKWATCH-6-USER_INFO2 : Only 1 users found using PAK FSV.
We have restarted the UDP process on rbx-g5-a9 too.