I have an ec2 instance with ubuntu 12.04 installed. I am trying to upload a running server application on this instance. The application requires JBoss 4.0.4 and apache 2.2.3 to run. The application is old, therefore I can not use the latest JBoss and Apache 2. I installed JBoss 4.0.4 and apache 2 but ran into difficulty configuring it. So I uninstalled Apache 2, downloaded apache 2.2.3 and installed it...now when i try to run the command "/etc/apache2/bin/apachectl start" (old version of apache is installed in apache2) to start apache i get this error "httpd.conf: module auth_basic_module is built-in and can't be loaded" apache ubuntu on ec2 instance".
Sounds like Apache was built by including modules in the code its self rather than having them loaded during startup.
Comment out the line in httpd.confwhere it is trying load this module(s)
You might try httpd -M to see a list of already compiled in modules.
Related
I have installed XAMPP 7.2.10 on my Win 10 and other services like Apache and MySQL are working fine.
But the Tomcat service is not starting and is throwing an error as:
"Tomcat Started/Stopped with errors, return code: 1,
Make sure you have Java JDK or JRE installed and the required ports are free,
Check the "/xampp/tomcat/logs" folder for more information"
XAMPP Tomcat error image
I have installed Java JDK in "C:\Program Files\Java" and have set the environment variables path.
I have set the "JAVA_HOME" variable path as "C:\Program Files\Java\jdk-10.0.2"
Also, no other program is using the required ports.
When I run the "catalina_start.bat", I get error as:
"ERROR: The system was unable to find the specified registry key or value.
. [XAMPP]: Cannot find current JDK installation!
. [XAMPP]: Cannot set JAVA_HOME. Aborting ..."
What mistakes have I made here?
I had the same problem (XAMPP 7.3.0 / Windows Server 2016 / Java 11). I first checked the environment variables, the java installation - all seemed to be fine.
Sadly the XAMPP error message is not very meaningful, so i looked inside of tomcat installation. To my surprise XAMPP 7.3.0 uses a very old version of Apache Tomcat (7.0.56 from 2014!), that don’t work well with Java 9+. The reason is Tomcat 7.0.56 uses the "-Djava.endorsed.dirs" option, that is no longer supported in Java 9+. Up-to-date Tomcat versions have no problem with java 9+. To solve this you can just stay with Java 8 (if possible for you) or try to fix this on your own by modify Tomcat start-up: Go to your \xampp\tomcat\ folder and see this fix in Tomcat 7.0.73 doesn't work with java 9.
But i would recommend you to install a up-to-date version of tomcat and don’t use the XAMPP one (what i finally did) - at least until XAMPP updates there tomcat version .
I have XAMPP installed on Windows 7 virtual machine. My old PHP version was 7.0.9 with Apache 2.4
I needed to upgrade the PHP version to 7.1.x and I set out reading about how to best to this. In end, I settled with the simple plan:
Stop Apache service
Downloaded new PHP version from official php website. For PHP 7 the 7.1.17 version was listed. I downloaded the thread safe version, as my Apache has thread safety enabled.
I extracted the contents of the downloaded archive to a folder.
I copied and replaced all files in the appropriate folders from C:/Server/php with the new php version files from the extracted archive.
I attempted to start Apache from the XAMPP control panel and the server will not start.
The message "Attempting to start Apache service..." just hangs and nothing happens.
The last entry in the error.log file in C:\Server\apache\logs shows the event when the server was stopped and that's it.
When I check the php version from CLI with the command php -v, the console returns installed php version 7.1.17
I tried different suggestions I read from similar questions, like changing ServerName localhost:80 to ServerName localhost:8080 and copying php7apache2.dll to apache/bin ( as suggested here: Upgrading PHP in XAMPP for Windows? ), alas the issue is not fixed and Apache does not start.
Of course, I also restarted the virtual machine, all the same.
At this point, I'm dumbfounded. Don't know what to do.
I need to get Apache running with php 7.1, as it is required by Magento 2.2.4. I do not want to reinstall XAMPP, as this will be a lenghty process with a lot of risk for more things to go wrong.
Any help is much appreciated!
Alright, so after checking Windows Logs > Application in Event Viewer I saw the error ".. the Apache service named is not a valid win32 application". I downloaded the x86 version of PHP from official website PHP for Windows
Then copied and replaced files as described above, and Apache started successfully.
To see if your Apache version is x64 or x86 open command prompt and cd to your Apache bin directory, in my case C:/Server/apache/bin , then run:
file httpd
I am installing OpenCPU on a production RedHat 7 Server and it turned out that the path to their Apache server is not
/etc/httpd
but something else.
Apparently, OpenCPU was still referring to /etc/httpd and therefore did not work.
I am wondering if there is a way to specify custom path to Apache server for OpenCPU installation (as a parameter for installation, or somewhere in the code, or after installation)?
OpenCPU version is 2.0.7, RedHat version is 7.3, Apache server version is 2.4
Where is your Apache2 located then? Did you compile it from source?
OpenCPU depends on httpd via rapache (which has mod_R). The rApache manual has some docs about how to compile rapache from source against a custom version of R or Apache.
Once this works you can try to build OpenCPU. The default opencpu-server rpm spec is copies opencpu.conf into /etc/httpd because that is the path of the httpd package in Fedora or Enterprise Linux. I guess you could modify that if you run a non-standard version of httpd.
I am getting the apache error:
Cannot load C:/ms4w/Apache/modules/mod_wsgi.so into server: The specified module could not be found
I searched on the web already, and found this link and I think I tried most of what is described in here, and my installation is still not working, so I think I need a bit of help.
I run windows XP 32bit pro SP3, freshly installed on a VM
I am running python 2.6 which I downloaded here
I am trying to install mod_wsgi 3.3 for python 2.6, which I downloaded here
Python is installed for all users
I run apache 2.2.22, as part of ms4w package
My file name is correct ( mod_wsgi.so )
My LoadModule entry is: LoadModule wsgi_module modules/mod_wsgi.so
If I comment my LoadModule line apache is running great. Python is working too.
However, I am not sure how to verify that apache's user is able to read the module on windows XP.
I don't know what else to try, thanks in advance to anyone who helps.
hope you might have got your issue resolved. if not there's a very easy tutorial I'd like to suggest, however this is using wampserver.
some points that needs to be considered:
download mod_wsgi version compatible to the wampserver's apache & python version
I've installed the latest wamp with apache 2.4 & python 2.7 32 bit so I got the mod_wsgi from here.
hope it helps.
I am installing Glassfish 3.1.2 on a vps server running Ubuntu 12.04 LTS and a I am not being able to start glassfish.
As X are not installed and I am connecting via ssh I am using the manual unzip method to install Glassfish.
Inside Glassfish bin directory with the glassfish user I do ./asadmin start-domain and nothing happens. It seems to hang. I cannot even stop it with ctrl+c. I need to kill the java process from another console.
The server.log file in the domain does not show any error. Last two lines are:
mar 23, 2013 1:12:03 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Se ha iniciado correctamente en 7 mseg.
Thank you very much for your help.
I had the same problem when I was installing glassfish. I fixed this problem by running Glassfish on an old version of jre. I was trying to install with version 1.8 and ended up using an old installation of jre6. Server started fine after I installed Glassfish using version 1.6.
It looks like a bug with the log levels. GFFileHandler logging level might be set to "OFF".
Try this:
asadmin start-domain
asadmin set-log-levels com.sun.enterprise.server.logging.GFFileHandler=ALL
asadmin restart-domain