Junos OS

Expand all | Collapse all

Jweb install fails on MX240

  • 1.  Jweb install fails on MX240

    Posted 01-28-2018 14:08

    I've tried several versions of JUNOS, and even did a complete wipe and reinstall to version 15.1R3.6 None of them will install the jweb package, They all get the following error.

     

    THIS IS A SIGNED PACKAGE
    ERROR: /usr/libexec/ui/downgrade: a legacy Junos installation package is required...

    I've looked thru all the logs, I can't find what package it is looking for and not finding.... any ideas?



  • 2.  RE: Jweb install fails on MX240

     
    Posted 01-28-2018 18:33

    Hi,

     

    Starting 15.1 JUNOS we start supporting freebsd kernel 10.1 version and we call these images junos-install.
    We continue to call pre kernel 10.1 images as jinstall files.

    For junos-install packages, the jweb package is built-in and it's optional, so we have to add it when required.

    Use below command to enable J-Web in "junos-install" packages for MX.

    > request system software add optional://jweb

    This change for MX is from 15.1 release on-wards.

     

    TEST> request system software add optional://jweb
    Verified jweb signed by PackageDevelopmentEc_2018 method ECDSA256+SHA256

     

    Regards,

    Rahul N



  • 3.  RE: Jweb install fails on MX240

    Posted 01-28-2018 19:05

    Thank you, At least it didn't error... Is there updated documentation hidden somewhere? every pdf etc I have read did not show your method...

    Verified jweb signed by PackageProductionEc_2016
    Verified jail-runtime signed by PackageProductionEc_2016

     

    Are their any tricks to getting it to listen?  I enabled SSH and can see the port open, I enabled web-mangement and 80 doesn't show as open.



  • 4.  RE: Jweb install fails on MX240

    Posted 01-28-2018 19:07

    run restart web-management got it to listen... thanks again.



  • 5.  RE: Jweb install fails on MX240

     
    Posted 01-28-2018 19:18

    Glad to know issue is resolved. I'll file documentation PR.

     

    Regards,

    Rahul



  • 6.  RE: Jweb install fails on MX240

    Posted 02-10-2018 03:12

    Well it stopped working again today, I was using jweb to capture some packets and the browser just acted like it got dropped.  My ssh session and console sessions were fine.

     

    I've rebooted it
    ran the request storage cleanup commands
    ran the web restart command
    I even changed the admin url to /admin to see if that would make a difference...

    When I login via the browser I see this in the syslog
    Feb 10 04:36:21 MX240 mgd[4674]: UI_JUNOSCRIPT_CMD: User 'aaron' used JUNOScript client to run command 'get-software-information'
    Feb 10 04:36:21 MX240 mgd[4674]: UI_CHILD_START: Starting child '/usr/libexec/ui/package-info'
    Feb 10 04:36:21 MX240 mgd[4674]: UI_CHILD_STATUS: Cleanup child '/usr/libexec/ui/package-info', PID 4695, status 0
    Feb 10 04:36:21 MX240 mgd[4674]: UI_JUNOSCRIPT_CMD: User 'aaron' used JUNOScript client to run command 'get-software-information'
    Feb 10 04:36:21 MX240 mgd[4674]: UI_CHILD_START: Starting child '/usr/libexec/ui/package-info'
    Feb 10 04:36:21 MX240 mgd[4674]: UI_CHILD_STATUS: Cleanup child '/usr/libexec/ui/package-info', PID 4800, status 0
    Feb 10 04:36:22 MX240 mgd[4674]: UI_LOGOUT_EVENT: User 'aaron' logout

    ^I did not logout, and I've tried 2 or 3 different machines and browsers from my office and the office where the juniper is installed. with the same result.

    if I tail -f  the httpd log on the juniper while I"m logging in via browser i can see my session.
    httpd: 0: Interface allowed for jweb URL. Transparent redirect to /login
    httpd: 2: POST /login HTTP/1.1
    httpd: 2: POST /login HTTP/1.1
    httpd: 2: GET /stylesheet/juniper.css HTTP/1.1
    httpd: 2: GET /javascript/global.js HTTP/1.1
    httpd: 2: GET /extjs/resources/css/ext-all.css HTTP/1.1
    httpd: 2: GET /images/newlogin.png HTTP/1.1
    httpd: 2: GET /images/browser-notify.png HTTP/1.1
    httpd: 2: GET /extjs/resources/ext-theme-jweb/ext-theme-classic-all.css HTTP/1.1
    httpd: 2: GET /extjs/resources/ext-theme-jweb/ext-theme-jweb-all.css HTTP/1.1
    httpd: 2: GET /extjs/ext-all.js?ver=15.1R6.7 HTTP/1.1
    httpd: 2: POST /login HTTP/1.1
    httpd: 2: POST /login HTTP/1.1
    httpd: 2: GET /stylesheet/juniper.css HTTP/1.1
    httpd: 2: GET /javascript/global.js HTTP/1.1
    httpd: 2: GET /images/newlogin.png HTTP/1.1
    httpd: 2: GET /images/browser-notify.png HTTP/1.1
    httpd: 2: GET /extjs/resources/css/ext-all.css HTTP/1.1
    httpd: 2: GET /extjs/resources/ext-theme-jweb/ext-theme-classic-all.css HTTP/1.1
    httpd: 2: GET /extjs/resources/ext-theme-jweb/ext-theme-jweb-all.css HTTP/1.1
    httpd: 2: GET /extjs/ext-all.js?ver=15.1R6.7 HTTP/1.1

    The only other thing I've found is in the /var/log/messages file.  It can't read /etc/login.conf?

    Feb 10 10:36:21  MX240 checklogin[4675]: _secure_path: /etc/login.conf is not a regular file
    Feb 10 10:36:21  MX240 checklogin[4675]: login_getclass: unknown class 'j-super-user'
    Feb 10 10:36:21  MX240 checklogin[4675]: failed to open /var/db/login-attempts for reading and writing: Read-only file system
    Feb 10 10:36:21  MX240 checklogin[4675]: _secure_path: /etc/login.conf is not a regular file
    Feb 10 10:36:21  MX240 checklogin[4675]: login_getclass: unknown class 'junos-login-defaults'
    Feb 10 10:36:21  MX240 checklogin[4675]: _secure_path: /etc/login.conf is not a regular file
    Feb 10 10:36:21  MX240 checklogin[4675]: login_getclass: unknown class 'j-super-user'
    Feb 10 04:36:21  MX240 checklogin[4675]: WEB_AUTH_SUCCESS: Authenticated httpd client (username aaron)
    Feb 10 10:36:21  MX240 checklogin[4675]: _secure_path: /etc/login.conf is not a regular file
    Feb 10 10:36:21  MX240 checklogin[4675]: login_getclass: unknown class 'j-super-user'

    Any ideas? why would it be read-only?  or other logs I could look at?