For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

fajari_200811's avatar
fajari_200811
Icon for Nimbostratus rankNimbostratus
May 06, 2015

Problem : Can not login to Admin (LTM)

Hi,

 

I have problem with one of my F5. I can not login. Error page on log is :

 

May 5 16:23:13 LTM-01 err httpd[26217]: [error] ajp_read_header: ajp_ilink_receive failed May 5 16:23:13 LTM-01 err httpd[26217]: [error] (120006)APR does not understand this error code: proxy: read response failed from (null) () May 5 16:23:14 LTM-01 err httpd[26205]: [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 () failed May 5 16:23:14 LTM-01 err httpd[26205]: [error] proxy: AJP: failed to make connection to backend: localhost May 5 16:23:17 LTM-01 err httpd[26207]: [error] (111)Connection refused: proxy: AJP: attempt to connect to 127.0.0.1:8009 (*) failed

 

What should I Do ?

 

7 Replies

  • you may try to restart httpd and tomcat to see if it helps.

     bigstart restart httpd  
     bigstart restart tomcat
    

    you may also generate qkview (before restarting httpd and tomcat) and open a support case.

  • Hi,

     

    after restart httpd and tomcat, it able to login, but some menu not available (Statistic, iAPP, local traffic, device management, network and system)

     

     

  • I already use different browser and get the same result.

     

    Is it ok to restart F5 ?

     

    • nitass's avatar
      nitass
      Icon for Employee rankEmployee
      yes, you can but you may not be able to find a root cause because unit reboots. you may open a support case before reboot. so, support engineer can gather whatever data they want before.
    • MOHIT_125417's avatar
      MOHIT_125417
      Icon for Altostratus rankAltostratus
      Hi Fajari, What are the results post opening the support case
  • HP1's avatar
    HP1
    Icon for Nimbostratus rankNimbostratus

    Check the disk space, I've experienced this once before, and the /shared storage was at 99 percent capacity.