Re: [j-nsp] Configuration database stuck with mgd crashing

[Phil Shafer]

Aaron Gould writes:
>Maybe "commit full"

"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.

Thanks,
 Phil
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Configuration database stuck with mgd crashing

[Tore Anderson]

* Aaron Gould

> Maybe "commit full"

Thank you for the suggestion! I was however unable to get into configure
mode in the first place, so I couldn't issue any kind of "commit". 

Luis's suggestion of «mgd -I» from a root shell did the trick, though.

Tore
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp