[j-nsp] Configuration database stuck with mgd crashing
luis at luisbalbinot.com
Mon Sep 3 06:48:33 EDT 2018
Mini heart attacks :-)
Now seriously, I’ve seen none so far.
On Mon, 3 Sep 2018 at 07:40 Sebastian Wiesinger <sebastian at karotte.org>
> * Phil Shafer <phil at juniper.net> [2018-09-01 20:28]:
> > "commit full" helps when daemons miss config changes (which they
> > shouldn't) or if you just want to say "because I said so", but it
> > needs a functioning database, provided by MGD. In this case, MGD
> > has corrupted the database (due to a software bug) and the assert
> > means that it's unable to do anything useful with the database since
> > it's corrupted and cannot be trusted. "mgd -I" is the "nuke the
> > entire site from orbit" option. It rebuilds the schema and the
> > database from scratch and reloads the entire contents. It's the
> > only way to be sure.
> What operational impact does mgd -I have?
> GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE)
> 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE
> -- Terry Pratchett, The Fifth Elephant
> juniper-nsp mailing list juniper-nsp at puck.nether.net
More information about the juniper-nsp