SRX

last person joined: yesterday 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.
Expand all | Collapse all

Web Management crashes

  • 1.  Web Management crashes

    Posted 01-29-2012 18:38

    I am trying to get the web management to start, but it refuses.

    /var/log/messages:

     

    Jan 30 10:23:58  srx240b init: web-management (PID 6092) terminated by signal number 11. Core dumped!
    Jan 30 10:23:58  srx240b init: web-management (PID 6144) started

     

    /var/log/httpd.log

     

    httpd: 2: Activating module (Builtin) fileHandler
    httpd: 2: Add handler "fileHandler" for "html htm gif jpeg png pdf js gz css jpg xml swf xml exe cab cli jar"
    httpd: 1: Started at Mon Jan 30 10:24:20 2012 UTC
    httpd: 1: Starting host named: "srx240b"
    httpd: 1: Starting host named: "srx240b"
    httpd: 1: Starting host named: "srx240b"
    httpd: Error: Can't open a socket on , port 443
    httpd: Error: Can't listen for HTTP on :443
    httpd: Error: Can't start HTTP service, exiting.
     1: HTTP services are ready with max 5 worker threads

     

     

     services {
            ssh;
            web-management {
                https {
                    system-generated-certificate;
                    interface [ vlan.1 vlan.0 ge-0/0/13.0 ];
                }
            }
        }

     

    I tried upgrading firmware, but no luck. I don't understand why it can't allocate 443. I tried just plain http (80) and I pretty much get the same error.

     

    Thanks in Advance!



  • 2.  RE: Web Management crashes

    Posted 01-29-2012 22:08
    signal 11 httpd crashes are due to hardware (memory / cpu)

    check

    1. whether free memory available (show sys storage)
    2. view cpu usage
    3. did you tried it with different web-browsers with different client machines

    regards


  • 3.  RE: Web Management crashes

    Posted 01-30-2012 09:50

    I tried in different browsers and the SRX looks in good shape in terms of available resources:

     

    run show chassis routing-engine

     

    Routing Engine status:
        Temperature                 41 degrees C / 105 degrees F
        CPU temperature             40 degrees C / 104 degrees F
        Total memory              1024 MB Max   809 MB used ( 79 percent)
          Control plane memory     560 MB Max   476 MB used ( 85 percent)
          Data plane memory        464 MB Max   334 MB used ( 72 percent)
        CPU utilization:
          User                       5 percent
          Background                 0 percent
          Kernel                     2 percent
          Interrupt                  0 percent
          Idle                      94 percent
        Model                          RE-SRX240H
        .

        .
        Load averages:                 1 minute   5 minute  15 minute
                                           0.06       0.05       0.01

     

     

    run show system storage
    Filesystem              Size       Used      Avail  Capacity   Mounted on
    /dev/da0s1a             292M       148M       121M       55%  /
    devfs                   1.0K       1.0K         0B      100%  /dev
    /dev/md0                404M       404M         0B      100%  /junos
    /cf                     292M       148M       121M       55%  /junos/cf
    devfs                   1.0K       1.0K         0B      100%  /junos/dev/
    procfs                  4.0K       4.0K         0B      100%  /proc
    /dev/bo0s3e              24M        48K        22M        0%  /config
    /dev/bo0s3f             342M       262M        53M       83%  /cf/var
    /dev/md1                168M        17M       137M       11%  /mfs
    /cf/var/jail            342M       262M        53M       83%  /jail/var
    /cf/var/log             342M       262M        53M       83%  /jail/var/log
    devfs                   1.0K       1.0K         0B      100%  /jail/dev
    /dev/md2                 39M       4.0K        36M        0%  /mfs/var/run/utm
    /dev/md3                1.8M       4.0K       1.7M        0%  /jail/mfs



  • 4.  RE: Web Management crashes

    Posted 01-30-2012 15:22

    Hi ,

     

    You can try rebooting the device or restart the http process using command > restart web-management and check httpd.log to confirm if it is able to open the socket for port 443. You can also try to change the port for https using command

     

    #set system services web-management https port 8080

    #commit

     

    Hope this helps.


    Regards,

    Visitor

    --------------------------------------------------​--------------------------------------------------​---

    If this post was helpful, please mark this post as an "Accepted Solution".Kudos are always appreciated!



  • 5.  RE: Web Management crashes

    Posted 07-15-2013 00:27

    Dear all,

     

    I am having that kind of log as well and I have verified everything already, (System Services, memory Space).

    httpd: Error: Can't open a socket on , port 443
    httpd: Error: Can't listen for HTTP on :443
    httpd: Error: Can't start HTTP service, exiting.
     1: HTTP services are ready with max 5 worker threads

    And it was working fine when I were made a change services https to port 8080.

    But I have still have problem when I am trying to access dynamic vpn.

     

    Could you please post up any idea with this issue, 🙂

    Regards,
    Kriss..


    @Visitor wrote:

    Hi ,

     

    You can try rebooting the device or restart the http process using command > restart web-management and check httpd.log to confirm if it is able to open the socket for port 443. You can also try to change the port for https using command

     

    #set system services web-management https port 8080

    #commit

     

    Hope this helps.


    Regards,

    Visitor

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

    If this post was helpful, please mark this post as an "Accepted Solution".Kudos are always appreciated!


     



  • 6.  RE: Web Management crashes

    Posted 10-24-2013 06:49

    we ever had the same problem.

     

    this is how we have solved it:

    1. enable http.

          set system services web-management http interface "your lan IF".

    don't forget to commit.

    2. surf to http://your firewall ip. and check if this works.

    if http works it means your HTTPS certificate on your firewall is not good.

     

    3. try a self-signed certificate

    - while you are on your http web-interface, goto configure - system properties - management access.

    - click on the edit button on the top right

    - in the edit management access window, select system-generated-certificate noted next to HTTPs certificate:

    then press ok.

     

    commit again en retry https.

     

    we had this problem when we upgraded the junos on our firewall. the upgrade deleted the certificate, so we where unable to access it through https and we also got the error: cannot bind to port 443.

     

    good luck

     



  • 7.  RE: Web Management crashes

    Posted 10-24-2013 07:01

    oh, and also: check the system-services on your lan IF or zone. if you not have configured the "all" system-services for host-inbound-traffic on your trusted zone, make sure that you have at least allowed http and https on it.

     

    also take a note that you can't enable system-services on both the interface and the zone. As soon as you configure system-services on a interface that is member of the specified zone, al the system-services configured on that zone do not work any more. You al need to move them to the interface.

     

    an example:

     

        zones {
            security-zone trust {

                host-inbound-traffic {
                    system-services {
                        all;
                    }
                    protocols {
                        all;
                    }
                }
                interfaces {
                    vlan0.0;
                }

     

    there are some system-services that only work on the  interface, like DHCP and if i am not wrong also ike. at least, that is my experience with system-services,

     

    sincerely.



  • 8.  RE: Web Management crashes

    Posted 01-30-2012 22:26

    Looks like there is httpd core

    1. Check:

    show system core-dumps

    2. you can de-activate web-management config and check if there is any httpd (kill if any)

    show system processes | match httpd

    Activate the config and check the process again.



  • 9.  RE: Web Management crashes

    Posted 01-31-2012 10:17

    I tried the above suggestions and rebooting. Looks like there is something intrinsically wrong with the device, or I could be wrong. This is what I saw in the messages log:

     

    Feb  1 02:05:10  srx240b snmpd[1145]: SNMPD_TRAP_COLD_START: trap_generate_cold: SNMP trap: cold start
    Feb  1 02:05:18  srx240b init: web-management (PID 1171) terminated by signal number 11. Core dumped!
    Feb  1 02:05:18  srx240b init: web-management (PID 1190) started
    Feb  1 02:05:25  srx240b init: web-management (PID 1190) terminated by signal number 11. Core dumped!
    Feb  1 02:05:25  srx240b init: web-management (PID 1202) started
    Feb  1 02:05:26  srx240b init: l2cpd-service (PID 1160) exited with status=0 Normal Exit
    Feb  1 02:05:26  srx240b init: l2cpd-service (PID 1208) started
    Feb  1 02:05:32  srx240b init: l2cpd-service (PID 1208) exited with status=0 Normal Exit
    Feb  1 02:05:32  srx240b init: l2cpd-service (PID 1241) started
    Feb  1 02:05:32  srx240b init: web-management (PID 1202) terminated by signal number 11. Core dumped!
    Feb  1 02:05:32  srx240b init: web-management (PID 1243) started
    Feb  1 02:05:39  srx240b init: l2cpd-service (PID 1241) exited with status=0 Normal Exit
    Feb  1 02:05:39  srx240b init: l2cpd-service (PID 1273) started
    Feb  1 02:05:40  srx240b init: web-management (PID 1243) terminated by signal number 11. Core dumped!
    Feb  1 02:05:40  srx240b init: web-management is thrashing, not restarted
    Feb  1 02:05:44  srx240b init: l2cpd-service (PID 1273) exited with status=0 Normal Exit
    Feb  1 02:05:44  srx240b init: l2cpd-service is thrashing, not restarted
    Feb  1 02:05:46  srx240b alarmd[1142]: syslog: unknown facility/priority: ff04
    Feb  1 02:05:55  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:05:58  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:05:58  srx240b init: l2cpd-service (PID 1368) started
    Feb  1 02:05:58  srx240b init: can not access /usr/sbin/hostname-cached: No such file or directory
    Feb  1 02:05:58  srx240b init: hostname-caching-process (PID 0) started
    Feb  1 02:05:58  srx240b init: web-management (PID 1370) started
    Feb  1 02:05:58  srx240b init: can not access /usr/sbin/ipmid: No such file or directory
    Feb  1 02:05:58  srx240b init: ipmi (PID 0) started
    Feb  1 02:06:00  srx240b /kernel: GENCFG: op 2 (USP Blob) failed; err 7 (Doesn't Exist)
    Feb  1 02:06:00  srx240b /kernel: GENCFG: op 2 (USP Blob) failed; err 7 (Doesn't Exist)
    Feb  1 02:06:03  srx240b init: l2cpd-service (PID 1368) exited with status=0 Normal Exit
    Feb  1 02:06:03  srx240b init: l2cpd-service is thrashing, not restarted
    Feb  1 02:06:04  srx240b init: web-management (PID 1370) terminated by signal number 11. Core dumped!
    Feb  1 02:06:04  srx240b init: web-management is thrashing, not restarted
    Feb  1 02:06:09  srx240b /kernel: GENCFG: op 2 (USP Blob) failed; err 7 (Doesn't Exist)
    Feb  1 02:06:35  srx240b srx240b SCHED: Thread 40 (FWDD CM) ran for 1677 ms without yielding
    Feb  1 02:06:35  srx240b srx240b Scheduler Oinker
    Feb  1 02:06:35  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:36  srx240b last message repeated 2 times
    Feb  1 02:06:36  srx240b srx240b Frame 00: sp = 0x508da5a8, pc = 0x08028cd0
    Feb  1 02:06:37  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:37  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:37  srx240b srx240b Frame 01: sp = 0x508da650, pc = 0x080139d0
    Feb  1 02:06:37  srx240b srx240b Frame 02: sp = 0x508da6c0, pc = 0x080151a4
    Feb  1 02:06:37  srx240b srx240b Frame 03: sp = 0x508da6e0, pc = 0x081c3be4
    Feb  1 02:06:37  srx240b srx240b Frame 04: sp = 0x508da700, pc = 0x081c4080
    Feb  1 02:06:37  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:37  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:38  srx240b srx240b Frame 05: sp = 0x508da750, pc = 0x08028528
    Feb  1 02:06:38  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:38  srx240b srx240b Frame 06: sp = 0x508da778, pc = 0x00014000
    Feb  1 02:06:38  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:39  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:39  srx240b srx240b SCHED: Thread 74 (PFE Manager) ran for 3128 ms without yielding
    Feb  1 02:06:39  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:40  srx240b srx240b Scheduler Oinker
    Feb  1 02:06:40  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:40  srx240b srx240b Frame 00: sp = 0x50b07798, pc = 0x08028cd0
    Feb  1 02:06:40  srx240b /kernel: STP: STP IPC op 1 (ForwardingState) failed, err 1 (Unknown)
    Feb  1 02:06:40  srx240b last message repeated 2 times
    Feb  1 02:06:41  srx240b srx240b Frame 01: sp = 0x50b07840, pc = 0x080139d0
    Feb  1 02:06:41  srx240b srx240b Frame 02: sp = 0x50b078b0, pc = 0x080196d0
    Feb  1 02:06:41  srx240b srx240b Frame 03: sp = 0x50b078e8, pc = 0x080107a0
    Feb  1 02:06:41  srx240b srx240b Frame 04: sp = 0x50b07918, pc = 0x08e65ba0
    Feb  1 02:06:41  srx240b srx240b Frame 05: sp = 0x50b07950, pc = 0x08e4d5b8
    Feb  1 02:06:41  srx240b srx240b Frame 06: sp = 0x50b07a00, pc = 0x08e4d9d0
    Feb  1 02:06:41  srx240b srx240b Frame 07: sp = 0x50b07a40, pc = 0x08e4db18
    Feb  1 02:06:41  srx240b srx240b Frame 08: sp = 0x50b07a60, pc = 0x08b9dd60



  • 10.  RE: Web Management crashes

    Posted 01-31-2012 10:34

    Hi

     

    Your device is constantly core dumping for http . Can you provide with the following outputs :

     

    #show | match trace | display set  (This will tell if there are unwanted traceoptioms active.This can cause http cores)
    > show system processes extensive | no-more (Daemon usage)
    > show system users (Management users connected)
    > show version (Current Version)

     

    I would also suggest you to open a case with JTAC to have those core-dump analysis so that
    they can provide you with the root cause of http core dumps.

     

    Hope this helps.


    Regards,

    Visitor

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

    If this post was helpful, please mark this post as an "Accepted Solution".Kudos are always appreciated!



  • 11.  RE: Web Management crashes

    Posted 01-31-2012 10:38
    which junos you are using, why not upgrade to some recommended release

    try commit full

    and finally its better you contact JTAC to resolve these internal errors 🙂

    regards



  • 12.  RE: Web Management crashes

    Posted 02-14-2012 05:15

    Please provide your configuration, especially for the security part.

     

    Most of time, HTTPD coredump is caused by other modules, such as Dynamic VPN.