[Critical] [PBAS] HTTPD "Address already in use: make_sock: could not bind to address 0.0.0.0:443"

Discussion in 'Troubleshooting' started by AaronMcH, Sep 26, 2014.

  1. AaronMcH

    AaronMcH Mega Poster

    Messages:
    130
    Hi

    So we have a problem where HTTPD won't start because something else is using port 443.

    Code:
    [root@mn2 logs]# sudo service httpd start
    Starting httpd: [Fri Sep 26 14:17:45 2014] [warn] module ssl_module is already loaded, skipping
    [Fri Sep 26 14:17:45 2014] [warn] module ssl_module is already loaded, skipping
    WARNING: MaxClients of 100 exceeds ServerLimit value of 10 servers,
    lowering MaxClients to 10.  To increase, please see the ServerLimit
    directive.
    (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
    no listening sockets available, shutting down
    Unable to open logs
      [FAILED]
    
    and it seems that it is trying to bind twice

    Code:
    [pid  2626] bind(3, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("0.0.0.0")}, 16) = 0
    [pid  2626] bind(4, {sa_family=AF_INET, sin_port=htons(4443), sin_addr=inet_addr("127.0.0.1")}, 16) = 0
    [pid  2626] bind(5, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("0.0.0.0")}, 16) = 0
    [pid  2626] bind(6, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EADDRINUSE (Address already in use)
    [pid  2626] write(2, "(98)Address already in use: make"..., 77(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
    
    This only happened after we updated open-ssl today, we also have an issue with yum where when trying to update pages it throws errors which seem to be connected: http://pastebin.com/SnaJHgHG; The only way I was able to update open-ssl and bash was by using "yum update openssl", "yum update bash", and "yum update --skip-broken".

    Any help would be great
    Thank you
    Aaron
     
  2. AaronMcH

    AaronMcH Mega Poster

    Messages:
    130
    To provide an update and for anyone who might have a similar issue, I opened a support ticket and it seems that the issue can be resolved by following this article when performing updates http://kb.odin.com/en/8993
     

Share This Page