[j-nsp] EX-4200 VC, unable to lock config on fpc

[Cord MacLeod]

Did they explain which versions of code this affects, or is it  
specific to your code train of 9.3S1.6?

I'm also curious why you went with 9.3S1.6 as opposed to 9.3R3, which  
JTAC tells me is the release they recommend.


On Jun 25, 2009, at 12:17 PM, Ross Vandegrift wrote:

> On Thu, Jun 25, 2009 at 07:51:03PM +0100, Firth,MJC,Michael,DMJ R  
> wrote:
>> Could you keep us updated with the progress of this?
>>
>> In particular a PR number if you get one, and whether the issue only
>> affects VCed EXes, or if it can also cause issues on standalone
>> units.
>
> I just finished a secure meeting with ATAC and Juniper engineering.
> It definitely only affects virtual chassis EX-4200s, as it requires a
> backup RE.  No idea if it affects EX-8200s.
>
> dcd on the backup RE is leaking one file descriptor per physical
> interface in the virtual chassis.  When the number of leaked
> descriptors exceeds 2000 (the kern.maxfiles limit), any commit causes
> mgd to corrupt the configuration database on the backup RE.
>
> A PR is being filed on the issue (don't have a number yet).  You can
> clear the condition by killing dcd on the backup, blowing away the
> config database on the backup, restarting mgd, and HUPing init.
>
> -- 
> Ross Vandegrift
> ross at kallisti.us
>
> "If the fight gets hot, the songs get hotter.  If the going gets  
> tough,
> the songs get tougher."
> 	--Woody Guthrie
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp