[j-nsp] Configuration database lock problem

[Keegan.Holley at sungard.com]

I don't usually use the commit at option, but I have had the same problem 
with users going into edit/configure exclusive and then being forcefully 
logged out for some reason.  You should be able to go into normal 
configure/edit mode and do a commit or a rollback 0. 





Jonas Frey <jf at probe-networks.de> 
Sent by: juniper-nsp-bounces at puck.nether.net
04/04/08 08:21 AM

To
juniper-nsp at puck.nether.net
cc

Subject
[j-nsp] Configuration database lock problem






Hello,

i've got a problem after doing a "commit at". The user that executed
this is no longer logged in but junos thinks its still logged in.
Due to this i cannot change the configuration anymore:

 error: configuration database locked by:  root terminal  (pid 26710) on
since 2008-04-04 03:22:20 CEST, idle 09:47:29      commit at

This pid is not running, the user is not logged in (show system users)
and "clear system commit" doesnt help either. I have no idea howto
unlock the db again. I tried restarting serveral processes but without
success. 


Regards,
Jonas Frey

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp