I have the apache 2.2 installed in my RHEL 6.1 and I wanted to try Apache 2.4 before switching to it.
I downloaded the latest version and when I googled around for manual install, I found so many different documents. But I do not know whether my new installation will overwrite my existing apache installation..
I would like to know whether its possible to install Apache on the same maching without disturbing the existing apache service (including no changes to the system configs) ?? If yes, how can I do that?
I would like to install the latest apache with different service (say httpd2) and try it if things are working without any problems (anyway I would stop the other service when I try one).
Any suggestions or help links?
I suggest to look at this: http://developerblog.redhat.com/2014/10/01/using-apache-httpd-2-4-rhel6/
Apache 2.4 is part of Red Hat Software Collections, are Red Hat supported, and are part of the RHEL subscriptions. Look for this in the software collections channel.
Related
I am setting up a CentOS 7 server as the migration target of my old CentOS 6 server.
With the state of system updates being so slow, I was thinking of using a more reactive or up-to-date repository for Apache httpd. This is out of security concerns (https://httpd.apache.org/security/vulnerabilities_24.html).
I came across SCL months ago but despite hours and hours of documentation reading and web browsing, I haven't yet found a way to have httpd24-http from SCL replace the standard httpd package, in the same way that mariadb packages are a drop-in replacement for mysql packages.
Is it possible to do without httpd from the default repository and instead have httpd24-httpd from SCL and how?
The thing that has me asking this question is that some packages (e.g. phpMyAdmin and roundcubemail) seem to not see the package from SCL and pull in httpd, which gets installed as a dependency.
I am still somehow confused as to whether Apache httpd (2.4.39 atm) from the SCL is a replacement or whether it's supposed to be installed alongside httpd (2.4.6 atm), in which case, I am wondering whether there is much use since both programs will try to bind to port 80 and port 443. I'm surely missing a few key points in understanding the SCL ecosystem, specifically concerning httpd or similar daemons.
EDIT
I finally understood that the SCL version is to be installed alongside the standard httpd. Also, the standard http receives security backports, which answers my initial need.
It should be possible to swap httpd from scl with the standard httpd
I've done the same with php versions.
scl enable httpd24 bash
https://www.softwarecollections.org/en/scls/rhscl/httpd24/
I'm asking myself the same question because I'd like to enable TLS 1.3 for centos 7, but besides the httpd, it will also need a manually installed version of openssl to make that possible at the moment.
I need to run Apache 2.4 on MAMP PRO 5.x but the company that makes MAMP issues the following statement:
You can only run the MAMP PRO components with the included Apache 2.2 . We will be upgrading to Apache 2.4 in MAMP PRO 6, which will be available in 2020.
Has anyone figured out a workaround? I need to be using TLS 1.2 and per some other posts I found, i.e. https://apple.stackexchange.com/questions/206901/using-mamp-3-4-how-do-i-upgrade-to-apache-2-4-and-openssl-1-0-2-to-meet-the-ats
They mention:
TLS 1.2 works only with apache 2.4
We are planning on transitioning away from MAMP in favor of homestead or vagrant, but for the current build we would like to figure out a way to use Apache 2.4 (for the sole purposes of using TLS 1.2) without changing our local development environments.
Any help would be appreciated.
Thats just the way it goes when you use a packaged system like MAMP PRO, it is up to them if they want to support Apache 2.4 or not, and it sounds like they will, but just not when it suits you. I also use MAMP 5 and want Apache 2.4, but looks like I will have to suck it up and run my own Apache 2.4 server too.
That said, there might be a way to hack MAMP PRO to work with another local version of Apache, but it would be unlikely you would receive any support from MAMP PRO in trying to get it to work
is it possible to run Solr 6.4.1 on tomcat?
I read that Solr does not support tomcat anymore, is that true, if yes is there any other option without tomcat?
Yes, any version of Solr from 5 and onwards does not support Tomcat as an alternative officially.
The reasoning for this has been documented on the wiki:
Solr is intended to be a server not a Java web application, similar to mysql or the Apache web server. When Solr was first created, designing it as a web application was a convenient choice, to avoid writing a lot of tricky code to build a network layer. These days, this design decision has become a limiting factor.
When you download Solr and install it onto your machine, it should be Solr that gets started. It should not be necessary to install Solr into a third-party application (servlet container) before it will work.
At this time, Solr is still a webapp, but this is an internal implementation detail, not an immutable property. The intention is to make Solr into a completely standalone application. Startup scripts that start the included container are the first step towards that goal. Jetty might still be the technology used once Solr is a standalone application, but if that happens, it will be internally embedded.
At the moment you can still attempt to run Solr in a different container, as the current version bundles jetty and loads Solr inside jetty, but you can run into unexplainable issues where you'll always suspect the container to be the issue .. and if you have a problem, reporting bugs while running under Tomcat won't do any good.
From one of the comments on the old tomcat page on the community wiki:
If you want to go against recommendations and run 5.3 or later in Tomcat, you can likely still do so, but you will need to inform tomcat about an exploded web application (found in server/solr-webapp) instead of the .war file.
The server/solr_webapp/webapp folder is an exploded web application. Tomcat documentation should be able to tell you how to add such an application.
.. but if you're deploying Solr now, you really shouldn't. Use the bundled version of jetty (which might change to a stand alone version later) and the solr command / script.
They have stopped the support for the same.
Other option could be, you can check out the code and see if you can build the solr. I had tried it for earlier version (3.3).
I am not sure of the current version. But that could be the option for you.
I have posted instructions on how to get solr 6.2 running on Tomcat here. However, these instructions no longer work on Solr 6.3 or 6.4.
I have been tasked with moving someone else's site and work from HP-UX to RedHat since our HP-UX system is going away. I have all the components on the RedHat server in place (apache, MySQL, Ruby, passenger) that were on the HP-UX system. I have apache UP on the Redhat system. I have exported the MySQL DB from HP-UX to the RedHat. I have copied all the directories that hold the app from one server to another.
My issue is trying to NOT get the Welcome to Apache screen on my redhat server but my app. I have the site listed in the site-enabled. I have the Include on the httpd.conf file to include all the sites. I have even tried Include /etc/httpd/sites-enabled/* as well as Include /etc/httpd/sites-enabled/. No difference.
I am not sure where else to go to look from old, old HP-UX Apache to the new, just installed RedHat system.
HP-UX 11.31 running Apache 2.2.9
RedHat 7.1 running Apache 2.4.6
What else do you need to know? Where else do I need to look?
Thanks!
Vince
Sorry can't post comment... have you tried to add
Include /etc/httpd/sites-enabled/*.conf
in the httpd.conf?
note the .conf at the end
Apparently there was a lot more required under the hood. One can not just move an older ruby/rails app to a new version. So instead of fighting this battle due to a versioning issue I am just going to close it out for now.
Thanks for all help.
I want to use mod_proxy_wstunnel on my CentOS machine. So, I went through the documentation and it says that, this module is the part of Apache >= 2.4.5 but, I'm not able to use the Module and mod_proxy_wstunnel.so nowhere exists in my server.
I know, there are lots of related questions but those are all for older version of Apache.
Anyway, I'm using
Apache 2.4.18
CentOS 6.7 (Final)
You need to determine where yourour 2.4.18 build came from, because it's not contemporary / part of Centos 6.
Whoever built or packaged it it needs to perform the routine task if including an additional standard module.