The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Problems Building Apache with easyapache.

Discussion in 'EasyApache' started by bet0x, Dec 15, 2008.

  1. bet0x

    bet0x Member

    Joined:
    Oct 3, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Im compiling Apache with the cpanel tool, php4 and php5 dso and apache 1.3 always failing with the same problem:

    Code:
    Apache Restart Output:
    /etc/init.d/httpd: line 83: 28394 Segmentation fault      (core dumped) $HTTPD -DSSL
    /etc/init.d/httpd start: httpd could not be started
    Log:
    [Mon Dec 15 08:30:22 2008] [notice] caught SIGTERM, shutting down
    [Mon Dec 15 08:30:27 2008] [notice] Apache/1.3.41 (Unix) PHP/4.4.9 mod_log_bytes/1.2 mod_bwlimited/1.4 mod_auth_passthrough/1.8 FrontPage/5.0.2.2635 mod_ssl/2.8.31 OpenSSL/0.9.8b configured -- resuming normal operations
    [Mon Dec 15 08:30:27 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Mon Dec 15 08:30:27 2008] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Mon Dec 15 08:33:56 2008] [error] [client 190.246.174.140] File does not exist: /usr/local/apache/htdocs/test.php
    [Mon Dec 15 08:33:56 2008] [error] [client 190.246.174.140] File does not exist: /usr/local/apache/htdocs/404.shtml
    [Mon Dec 15 08:35:02 2008] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/htdocs/whm-server-status
    [Mon Dec 15 08:40:01 2008] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/htdocs/whm-server-status
    [Mon Dec 15 08:45:01 2008] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/htdocs/whm-server-status
    [Mon Dec 15 08:50:01 2008] [error] [client 127.0.0.1] File does not exist: /usr/local/apache/htdocs/whm-server-status
    [Mon Dec 15 08:53:19 2008] [notice] caught SIGTERM, shutting down !!
    !! '/usr/sbin/lsof -n -iTCP:443 -iTCP:443' failed with exit code '256' !!
    !!
    Ouput from '/bin/netstat -a -n --tcp | grep LISTEN':
    tcp        0      0 0.0.0.0:993                 0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:1                   0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:2082                0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:995                 0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:2083                0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:2086                0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:2087                0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:110                 0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:143                 0.0.0.0:*                   LISTEN     
    tcp        0      0 127.0.0.1:783               0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:2095                0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:2096                0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:465                 0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:21                  0.0.0.0:*                   LISTEN     
    tcp        0      0 72.233.93.65:53             0.0.0.0:*                   LISTEN     
    tcp        0      0 72.233.93.64:53             0.0.0.0:*                   LISTEN     
    tcp        0      0 10.17.10.1:53               0.0.0.0:*                   LISTEN     
    tcp        0      0 72.233.93.63:53             0.0.0.0:*                   LISTEN     
    tcp        0      0 72.233.93.62:53             0.0.0.0:*                   LISTEN     
    tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN     
    tcp        0      0 127.0.0.1:5432              0.0.0.0:*                   LISTEN     
    tcp        0      0 127.0.0.1:63000             0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN     
    tcp        0      0 127.0.0.1:953               0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:2077                0.0.0.0:*                   LISTEN     
    tcp        0      0 0.0.0.0:2078                0.0.0.0:*                   LISTEN     
    tcp        0      0 :::21                       :::*                        LISTEN     
    tcp        0      0 :::22                       :::*                        LISTEN     
    !!
    !! Archiving successful build so it can be restored via --restore-archive once the httpd.conf are resolved !!
    !! '/usr/local/apache/conf/httpd.conf.1229338393' does not exist, using '/usr/local/apache/conf/httpd.conf' instead !!
    !! Done Archiving successful build !!
    !! Restoring original working apache !!
    !! Executing '/scripts/initsslhttpd' !!
    !! Restarting 'httpd' ... !!
    !! 'httpd' restart complete. !!
    !! Executing '/scripts/initfpsuexec' !!
    !! Executing '/scripts/initsslhttpd' !!
    Compiling report...
    Sending report (1995 bytes)...
    !! If you want to create a support ticket with cPanel regarding this please reference 'BuildAP Report Id': '1455849' !!
    Report processed.
    !! Verbose logfile is at '/usr/local/cpanel/logs/easy/apache/build.1229337143' !!
    
    I attached the full LOG on a ZIP file.
     

    Attached Files:

  2. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    You may wish to let our technical analysts take a look at this for you.
     
  3. bet0x

    bet0x Member

    Joined:
    Oct 3, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Why, if its a issue with CPANEL you cant support me on YOUR OWN product with a SOLUTION?.
     
  4. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    14,450
    Likes Received:
    195
    Trophy Points:
    63
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
    I'm sure they will, after they've had a look for you.

    Note the message in the footer of every page:



    Notice: These forums are not an official means of support. We have technical support analysts standing by 24x7x365 to provide official support.
     
  5. bet0x

    bet0x Member

    Joined:
    Oct 3, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Then i wait.
     
  6. bet0x

    bet0x Member

    Joined:
    Oct 3, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    I still waiting....
     
  7. sirotex

    sirotex Well-Known Member

    Joined:
    Jul 10, 2008
    Messages:
    121
    Likes Received:
    0
    Trophy Points:
    16
    You're very arrogant arn't you? HIRE A SYSTEM ADMIN if you cannot fix solutions without asking cPanel to hold your hand. Being arrogant will just make you wait even longer.

    '!! If you want to create a support ticket with cPanel regarding this please reference 'BuildAP Report Id': '1455849' !!'

    This means DON'T use the forums, make a SUPPORT ticket.
     
    #7 sirotex, Dec 21, 2008
    Last edited: Dec 21, 2008
  8. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    14,450
    Likes Received:
    195
    Trophy Points:
    63
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
Loading...

Share This Page