Switching

 View Only
  • 1.  EX2300-48P Commit fails in CLI editor but works fine EVERYWHERE else!

    Posted 03-13-2026 01:31

    This is really annoying me. I have tried several versions of firmware including the Juniper recommended version in an EX2300-48P and keep experiencing the same problem. When I run a "commit check" from a SSH command in configure mode, it returns a "configuration check succeeds" response so all shoulld be good.. but isn't. If my colleague (or myself) logs into Jweb, we can make a change ANYWHERE within Jweb's pages and after changing whatever which brings up the Commit Pending prompt, we can click the Commit button up top and it thinks about it then responds with "Configuration Delivery status : Success" and exits back to Jweb.

    However, if we try to make any change within Jweb's CLI Editor, when clicking the Commit button, it thinks about it for 20 seconds or so then returns  " Validating Configuration status : Failed     |    Click on 'Details' for more information   |    The configuration could not be un-locked.
    Error(s): 
    1) syntax error
    Warning(s): 
    1) -

    and bombs out reverting any changes that were made. 

    I cannot find any locked files, doing reboots does not fix it. Weird is that it is only the CLI Editor that throws this error, yet every other place in Jweb you can edit something, the commit works fine, and a SSH CLI command returns that the configuration is fine... what the? 



    ------------------------------
    STEPHEN MCBRIDE
    ------------------------------


  • 2.  RE: EX2300-48P Commit fails in CLI editor but works fine EVERYWHERE else!

    Posted 10 days ago

    This is a classic J-Web "phantom" error that has haunted the EX2300 series for a bit, Because your SSH commit check passes, you've already proven that the Junos configuration database is healthy. The issue isn't your config; it's the translation layer between the J-Web CLI Editor and the actual Junos management process (mgd)

    There are ways to fix it, but since you are confident to CLI, stick to CLI for config changes and use J-Web for management and monitoring

    -------------------------------------------



  • 3.  RE: EX2300-48P Commit fails in CLI editor but works fine EVERYWHERE else!

    Posted 5 hours ago

    Please share what the ways of fixing it are. I have a senior colleague who only uses the JWeb CLI editor as he is not confident in using the SSH CLI editor. 



    ------------------------------
    STEPHEN MCBRIDE
    ------------------------------