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

2018-12-19 Thread Martin T
On Mon, Sep 3, 2018 at 1:49 PM Luis Balbinot wrote: > > Mini heart attacks :-) > > Now seriously, I’ve seen none so far. > > On Mon, 3 Sep 2018 at 07:40 Sebastian Wiesinger > wrote: > > > * Phil Shafer [2018-09-01 20:28]: > > > "commit full" helps when daemons miss config changes (which they >

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

2018-09-03 Thread Sebastian Wiesinger
* Phil Shafer [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

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

2018-09-01 Thread 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

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

2018-09-01 Thread 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

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

2018-08-31 Thread Aaron Gould
ct: [j-nsp] Configuration database stuck with mgd crashing One of my routers (a MX240 running 16.1R6-S2.3) have gotten stuck in a state where it believes the configuration database has been modified, and if I try to configure it anyway, mgd crashes and is respawned: tore@router> configure exc

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

2018-08-31 Thread Luis Balbinot
As root you can “mgd -I” to fix that. We also had the same issue and it’s been fixed on 16.1R7. We never opened a JTAC case for that because we knew the answer would be software upgrade since 16.1R7 was already out. The cause was Netconf and it randomly occurred. Strangely this was caused by the

[j-nsp] Configuration database stuck with mgd crashing

2018-08-31 Thread Tore Anderson
One of my routers (a MX240 running 16.1R6-S2.3) have gotten stuck in a state where it believes the configuration database has been modified, and if I try to configure it anyway, mgd crashes and is respawned: tore@router> configure exclusive error: configuration database modified tore@router>