Junos
Highlighted
Junos

Commit check warning:statement does not exist

a week ago

Hi everyone,

             I am newbie to Juniper networks and having a problem when I do commit check for new configuration.The user "ktnc" is already deleted from super user group.But warning messages associated with "ktnc" appear while checking commit.I have had done surfing google but nothing solution found out to solve my problem.I really hope you guys could help me in any way.Please check  the following configuration and welcome any suggestions.

 

{primary:node0} [edit]

nlt@xxxx # commit check

[edit system login]

    'user ktnc'

        warning: statement does not exist

[edit system login]

       'user ktnc'

            warning: statement not found: 'uid 2007'

[edit system login]

       'user ktnc'

             warning: statement not found: 'class super-user'

[edit system login user ktnc]

        'authentication'

                warning: statement not found: 'encypted-password xxxxxxxxx'

[edit system login user nlt full-name]

       'full-name "Nay Lin Tun" '

         warning: statement exists but matches patch

 

nlt@xxxx #show system login user ?

Possible completions:

     <user-name>          User name (login)

         PTL                       xxxxxx

        UAK                      xxxxxx

         nlt                         xxxxxx

11 REPLIES 11
Junos

Re: Commit check warning:statement does not exist

a week ago

Hi,

 

That looks strange if already deleted. Possibly some half statement for the user is still in the configuration.

What does the following show when run from configuration mode:-

 

root@Box# show | display set | match ktnc

 

-Rahul

Regards,
Rahul
Junos

Re: Commit check warning:statement does not exist

a week ago

Please get "show system login |display inheritence" and "show configuration |compare rollback 0". Maybe you have not deleted everything associated with that account 


Mengzhe Hu
JNCIE x 3 (SP DC ENT)
Junos

Re: Commit check warning:statement does not exist

a week ago

Hi mhu

            Firstly thanks a lot for your help.For  1st command " show system login | display inheritance", there is no data associated with user "ktnc".But the result of 2nd command "show configuration | compare rollback 0" is just like the followings.

 

nlt@xxxx> show configuration | compare rollback 0

 [edit system login]

            user ktnc {

                     uid 2007;

                     class super-user;

                     authentication {

                                     encrypted-password " xxxxxxxxxxxxxxxxxxxxxx" ; ## SECRET-DATA

                        }

                 }

[edit system login user nlt]

+             fill-name  "Nay Lin Tun" ;

 

 

Could it be cache remains in Juniper or something else I need to delete ?Any suggestion welcome, bro.

Junos

Re: Commit check warning:statement does not exist

a week ago

Thanks for reply,bro.But I don't find out anything associated with user "ktnc" via show | display set | match ktnc .Any other suggestion?

Junos

Re: Commit check warning:statement does not exist

Friday

Hi,

 

This looks incorrect.

"| compare 0" shows that the said commit did not succeed.

 

Do you see any user logged in and trying to edit the config?

show system user

 

** If so, log out all user's apart from yourself using "request system logout terminal __ "

 

Next try to check the configuration for the said user.

 

 

Else try , "clear system commit" to clear any stale commits.

 

_Rahul

Regards,
Rahul
Junos

Re: Commit check warning:statement does not exist

Friday

Hi Nayan,

 

Yes, you are right configuration might not be commited or have you upgrade junos recently?

Please find below kb article, which i think suits for your issue.

 

https://kb.juniper.net/InfoCenter/index?page=content&id=KB25864&cat=ALARMS&actp=LIST





Regards,
NetworkSurfer
Please Mark My Solution Accepted if it Helped, Kudos will be appreciated too!!!
Junos

Re: Commit check warning:statement does not exist

Friday

Hi Rahulverma,  

 

                       I   appreciate your  suggestion and will try that way tonight.And let you know the progress, bro.

Junos

Re: Commit check warning:statement does not exist

Saturday

Hi naylintun3991,

 

Can you 'rollback 0' (rollback any changes you made) and provide the output of 'show system login' please?

 

Cheers

Pooja

 

Junos

Re: Commit check warning:statement does not exist

Sunday

Hey Naylintun3991,

 

Could you please provide me below command outputs?

 

user@host# show | display set | match ktnc

user@host# rollback
user@host# show | compare
user@host# commit check
user@host#run show system users



Thanks,
π00bm@$t€®.
Please, Mark My Solution Accepted if it Helped, Kudos are Appreciated too!!!
Junos

Re: Commit check warning:statement does not exist

Sunday

Finally It was fine.

I alreay tried "show | display set | match ktnc" and found nothing with "ktnc"  in CLI interafce.
After running CLI commands "request system storage cleanup dry-run" and  "request system storage cleanup" , I am able to use Web UI tabs whilst decreasing Node 0 storage capacity.
And hence I find out user "ktnc" still exist in Web UI .So I have deleted "ktnc" and tried to create new user account creation from Web UI.
And I got the following status in Web UI.

"The configuration could not be un-locked.

Error(s):

1)private edits in use.Try 'configure private' or 'configure exclusive'.

2)private edits in use.Try 'configure private' or 'configure exclusive'.

3)private edits in use.Try 'configure private' or 'configure exclusive'.

4)private edits in use.Try 'configure private' or 'configure exclusive'.

A few minutes later,I find out Juniper is working properly.I still cannot figure out which change addressed my problem.For your suggestions, thanks a million guys.

Junos

Re: Commit check warning:statement does not exist

Sunday

Hi,

 

Hence, it was the stuck config from the GUI.

Probably you tried to commit the said user config from WebUI whoch dic not complete and caused the said stuck config.

 

"Dry-run" and "cleanup" would clean up your storage directory and not related to commit.

 

But, I am happy your issue got resolved. Cheers !!

 

-Rahul

Regards,
Rahul