Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

URGENT APACHE/EASYAPACHE problem

Discussion in 'EasyApache' started by tris, Dec 31, 2004.

  1. tris

    tris Active Member

    Joined:
    Apr 11, 2003
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    156
    i did get a maketree error but i fixed that and now i get

    #-> service httpd start
    Processing config directory: /etc/httpd/conf.d/*.conf
    Processing config file: /etc/httpd/conf.d/authz_ldap.conf
    Processing config file: /etc/httpd/conf.d/php.conf
    Processing config file: /etc/httpd/conf.d/python.conf
    Syntax error on line 6 of /etc/httpd/conf.d/python.conf:
    Cannot load /etc/httpd/modules/mod_python.so into server: /etc/httpd/modules/mod_python.so: undefined symbol: apr_bucket_type_flush
    /etc/init.d/httpd start: httpd could not be started


    whatever i do it just gets worse and worse... any help is appreciated
     
  2. tris

    tris Active Member

    Joined:
    Apr 11, 2003
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    156
    fixed lass problem. Now I have.......

    root@server1 [/usr/local/apache/conf]# service httpd start
    [Fri Dec 31 18:55:30 2004] [error] VirtualHost 70.84.120.2:0 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
    [Fri Dec 31 18:55:30 2004] [error] VirtualHost 70.84.120.2:0 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
    [Fri Dec 31 18:55:30 2004] [error] VirtualHost 70.84.120.2:0 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
    [Fri Dec 31 18:55:30 2004] [error] VirtualHost 70.84.120.2:0 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
    /etc/init.d/httpd start: httpd started
     
  3. tris

    tris Active Member

    Joined:
    Apr 11, 2003
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    156
    fixed that by adding port 80.

    Then no errors were given but i looked in the error log and found some.

    I fixed them and now it starts fine... no errors in error log but when trying to stop it says no pid file.

    quick browse to /etc/httpd/run and i see a httpd.pid file.

    so... whats wrong?
     
  4. AndyReed

    AndyReed Well-Known Member
    PartnerNOC

    Joined:
    May 29, 2004
    Messages:
    2,222
    Likes Received:
    4
    Trophy Points:
    193
    Location:
    Minneapolis, MN
    I am not sure what you did to get these errors, but your httpd.conf is messed up.
    Need to do more polishing.

    Good luck!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. brentp

    brentp Well-Known Member

    Joined:
    Mar 11, 2004
    Messages:
    324
    Likes Received:
    0
    Trophy Points:
    166
    Location:
    Ayr, North Queensland, Australia
    use the following scripts to fix your httpd.conf :

    /scripts/rebuildhttpdconffromproftpd (doesnt matter if you use proftpd or not)
    /scripts/rebuildhttpdconf

    chances are they wont screw it up, but still theres that tiny chance. Make a backup before you you execute them..

    Regards,
    Brent
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice