1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

upgrading to apache 2.0.54

Discussion in 'Plesk for Linux - 8.x and Older' started by k.satirli, Jun 27, 2005.

  1. k.satirli

    k.satirli Guest

    0
     
    I've been searching these forums but havent yet found a definitive answer outlining what I need to mind when I update to .54

    .51 doesnt cut it with the application I'm using and I would prefer to still have a working apache after updaing ;)

    I'm guessing I can do it with yum, however I'd like to know if I need to remove something first, need to mind something special etc.

    current setup:

    Fedora Core 2
    Plesk 7.5.3
    Apache 2.0.51
    no ASP, no Frontpage.

    any thoughts?

    I'd prefer ART rpms if possible - anyone got a real good walkthru ?

    [EDIT]

    SW-Soft says it shouldnt be a problem. so your help would be most greatly appreciated :)
     
  2. hardweb

    hardweb Guest

    0
     
    You have to compile a RPM from with the new apache source. You will not find 2.0.54 on FC2 repository.
     
  3. k.satirli

    k.satirli Guest

    0
     
    okay thank you. I'll have a go at that then
     
  4. k.satirli

    k.satirli Guest

    0
     
    hm ok - I guess this just wont work for me.

    Sure, downloading apache and MAKEing it and installing it should be no problem, but where should I install it?

    I'm coming from a cPanel background and it was all so easy there lol

    If you were missing apache - you'd install it one dir up where conf was.

    Here, the conf is in /etc/ yet the apache is not

    What's the latest RPM available?

    [EDIT]

    When I execute
    rpm --install -ivh httpd-2.0.54-10.i386.rpm
    I get a list of failed dependencies:

    libcrypto.so.5 is needed by httpd-2.0.54-10
    libdb-4.3.so is needed by httpd-2.0.54-10
    liblber-2.2.so.7 is needed by httpd-2.0.54-10
    libldap-2.2.so.7 is needed by httpd-2.0.54-10
    libssl.so.5 is needed by httpd-2.0.54-10

    So I guess as soon as I solve those, I should be good to go
     
  5. hardweb

    hardweb Guest

    0
     
    You try to install a RPM package compiled for another OS, with other libraries. You must compile your own on your server from source. This is not related to Plesk or any control panel.
     
  6. k.satirli

    k.satirli Guest

    0
     
    you're correct.

    I had a go at the FedoraCore 4 RPM.

    When I complained about cPanel being easier, I meant that it was easier to see where the httpd was actually installed.
     
  7. jamesyeeoc

    jamesyeeoc Guest

    0
     
    On RH type servers, httpd is usually in /usr/sbin/ and the config files are in /etc/httpd/conf/
     
  8. k.satirli

    k.satirli Guest

    0
     
    the software I used was initially written for apache 1, I was hoping that the update to the latest 2.x version would solve the problems I had with it, however I found it easier to install apache 1 and just run it on port 81.

    this saved me the headache of compiling and probably breaking the apache 2 installation.

    now I just got to find out if its possible to have apache 2 listen on IP x.x.x.x on port 80 and apache 1 listen on IP y.y.y.y on port 80 with both installations on the same machine.
     
  9. jamesyeeoc

    jamesyeeoc Guest

    0
     
    In the httpd.conf file you can specify the 'Listen' command with an IP:port combination. The conf file is well commented, you should see it with no problem. The default will show:

    Listen 80

    Just change it to:

    Listen x.x.x.x:80 or Listen x.x.x.x:81

    or whatever you need. Just don't try to have them both listening on the same IP and same port.

    As long as you tell each apache a different IP I don't think you'll have any problem.
     
  10. k.satirli

    k.satirli Guest

    0
     
    THANK YOU james,

    you just made me a happy plesk customer :)
     
  11. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Glad to hear it, but that's actually an apache feature, not specific to Plesk (in any case).
     
Loading...