XAMPP 5.6.11-0 on Mac OS X 10.7.5 Apache Web Server won't run - macos

In the XAMPP Application Manager both the "MySQL Database" and "ProFTPD" apps have a status of "Running". The "Apache Web Server" app has a status of "Stopped".
If you click on the Applications Log in XAMPP Applications Manager, it says:
Starting Apache Web Srver… /Applications/XAMPP/xamppfiles/apache2/scripts/ctl.sh : httpd started
I did a config test in the Terminal using "sudo apachectl configtest". The Terminal came back with the following:
httpd: Could not reliably determine the server's fully qualified domain name, using Jennifers-iMac-2.local for ServerName
Syntax OK
Web Sharing is turned on in System Preferences. Web Sharing also has its own folder in the System Library.
There is a "Sites" folder under my User's directory in which I have placed some WordPress plugins folders. I will be attempting to utilize these once Apache gets running. I'm not sure they are in the correct folder, as I added them there prior to installing XAMPP.
The XAMPP Application Manager has Apache Web Server at Port 80.
XAMPP is installed in the Applications folder.
I am not a developer, so I am not real comfortable with messing with the Terminal. But if I have to, I will.
Any suggestions on how I can get Apache to run? I've been trying to set up a localhost server for 3 days now with zero success….

Related

How do I change the path for the Apache Service in XAMPP?

After I have changed the ports for my Apache server, and I try and run it, it comes up with this error message:
Apache Service detected with wrong path
Change XAMPP Apache and Control Panel settings or
Uninstall/disable the other service manually first
Found Path: "C:\apache24\bin\httpd.exe" -k runservice
Expected Path: "c:\xampp\apache\bin\httpd.exe" -k runservice
I think this might be because I tried to download Apache separately from XAMPP, and I stored the httpd in that file location. However, I have deleted that file and that area, and I think XAMPP is trying to access that file when it doesn't exist. So how do I change XAMPP apache and control panel settings to the desired field?

How to find WebSphere 8.5 Admin console URL in Linux

I installed WebSphere 8.5 on Redhat Linux using the below steps.
1. Unzip the installation kit (WAS_V8.5_1_OF_3.zip, WAS_V8.5_2_OF_3.zip & WAS_V8.5_3_OF_3.zip)
2. Login as normal user
3. Navigate to the folder WLP/wlp-8500.jar
4. Install thru Running: 'java -jar wlp-8500.jar'
5. Follow the steps and complete installation (all comand line)
6. Move to wlp folder
7. Create server instance thru Moving to bin folder and Run 'server create <serverName>'
7. Start server thru Running 'server start <serverName>'
8. Check the server status thru Running 'server status <serverName>'
After this setup I created and started the server. It is up and running.
I dont know how to login to Admin console. I tried different URLs and ports nothing is working.
http://localhost:9060/ibm/console
http://localhost:9080/ibm/console
How to find the Admin Console URL or Port no?
You have installed WebSphere Liberty Profile (wlp) not the full (aka classic) WebSphere Application Server. WebSphere Liberty doesn't have full administrative console like classic one. You have only simplified adminCenter feature, which must be installed separately.
The Admin Center is a web user interface that runs on Liberty profile V8.5.5.2 and later servers, since you have 8.5.0.0 version looking at your log, you will have to install later version to see it.
See also:
AdminCenter feature
Settig up AdminCenter in Liberty
AdminCenter on youtube - Overview, New features (03/2015)
If you want full administrative console, you have to use Installation Manager and install WebSphere Application Server, not the Liberty profile.
I can only tell you the default ports you may have changed them:
http : 9060
https: 9043
To find the exact port:
Open WC_profiledir/logs/AboutThisProfile.txt
Look for lines similar to the following:
Administrative console port: 9102
Administrative console secure port: 9104

How do I upgrade Apache Tomcat from 6.0.20 to 6.0.24?

Our security team has scanned our production server and identified vulnerabilities with Apache Tomcat server v 6.0.20.
They have recommended that Apache be upgraded to 6.0.24. Reading through the forums, I believe this is the process to do so
Take a backup of httpd.conf file
Using add remove programs, uninstall version 6.0.20
Install 6.0.24
But, I have some questions depending on a quick test I did to install 6.0.20 and upgrade it to 6.0.24
Where do I get Tomcat administrator login information?
Is it enough just to backup the HTTPD.CONF file? I was thinking to back up everything in the Apache folder instead.
Is it possible not to upgrade 6.0.20 to 6.0.24 by running the MSI installer over the same Apache folder? Is it due to the HTTP/1.1 Connector Port being busy/used that doesn't allow an update of Tomcat on the same port?
Is a restart of the server required after upgrade?
Last but not the least, I am using these executables to test the upgrade. 6.0.20 gets installed fine but when I run 6.0.24, it prompts me for the JRE path and directing it to 6.0.20 JVM Path gives me a message that "JVM is not found". The JVM info on the Apache manager is in this directory
What am I missing here?
I need your thoughts and advice to make this as easy as possible since this is a production server.

XAMPP - Apache could not start - Attempting to start Apache service

While trying to start Apache using XAMPP, I was receiving - "Attempting to start Apache service..." message in XAMPP UI. No further details were available.
Where can I see the logs (I was running XAMPP as Admin) ?
IF PORT 80 IS NOT THE ISSUE!
Check to see if the port 80 is in use first as this can be an issue.
You can do this by typing "netstat -an" into cmd. The look for 0.0.0.0:80 under Local Address, if you find this is in use then follow the solution from #Karthik. However, I had a similar issue but my port 80 was not in use.
My XAMPP had wrong paths locations, steps to fix this:
1.Find out the Apache version you are using, you can find this by looking in Services (Control panel, Admin Tools, Services) and finding Apache in my case it was listed as Apache2.4
2.Close XAMPP.
3.Run cmd as admin.
4.execute 'sc delete "Apache2.4"' (put your version in place of mine and without the surrounding ' ', but with the " " around Apache).
5.execute 'sc delete "mySQL"', again remove the '' when you type it.
6.reopen XAMPP and try starting Apache
If you are having trouble with FileZill, Mercury, or Tomcat you could try it here too, but I have not tested that myself.
Hope this helps!
I realized it was a port issue since I was running IIS and other web servers in my machine. But I was more interested to see a detailed error message with the port number in the UI.
Seems like it was not logged in the UI or log file (at least in my case), but in the Event viewer (Control panel -> View Event Logs). Under the Even viewer -> Windows Logs -> Application
I could see a permission error something like the below one:
An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address 0.0.0.0:443
To fix this permission issue for SSL port, Please change the below line in httpd-ssl.conf (C:\xampp\apache\conf\extra)
# When we also provide SSL we have to listen to the
standard HTTP port (see above) and to the HTTPS port
Listen xxx
Replace XXX with any valid port number that is open in your machine
If you are having issues with Port 80, then change the httpd.conf file (C:\xampp\apache\conf)
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 127.0.0.1:8000
I have also summarized other solutions that I came across:
Most often Skype blocks the Apache port. So terminate it and try again.
Find the process id (PID) that is using the Blocked port ( netstat -ano) and kill the corresponding process in Windows Task Manager.
For those who have accidentally (or not) changed one of the .conf files and apache does not run even after trying all the above solutions.
One easy way to track where the issue is located, is to run Apache via command prompt:
(On windows) : open command prompt as admin then navigate inside the bin folder of Apache , next run
httpd in order to run apache
C:\xampp\apache\bin\httpd
For my case it was :
someone had added a virtual host in the specific file that caused the problem . I commented the lines and Apache ran fine.
start xampp (as administrator),
(1) right click C:\xampp\xampp-control.exe, and run as administrator.
(2) unistall service module and then install service module.
(3) now try start the apache and mysql.
Check your DocumentRoot path (in httpd.conf); a typo there can cause this problem.
Had the same issue while updating to PHP7.2
Problem:
First I closed skype and then checked whether port 80 is not an issue. How you can check that? See #AlexT comment above.
In my case, port 80 wasn't an issue. So now I had to figure out what was wrong. So I checked Error Logs Control Panel > Even viewer > Windows Logs > Application and found following error against Apache2.4
httpd.exe: Syntax error on line 520 of C:/xampp/apache/conf/httpd.conf: Syntax error on line 18 of C:/xampp/apache/conf/extra/httpd-xampp.conf: Cannot load C:/xampp/php/php7ts.dll into server: The Apache service named is not a valid Win32 application.
Which means I had installed wrong PHP version. Actually I downloaded win64 version while the required version was Win32 for me.
So I downloaded correct version from: Download PHP 7.2.0 extracted it in C:/xampp/php folder, restarted the apache and it worked :)
I had the same issue, executing "setup_xampp.bat" in xampp folder solved my issue.
I had the same problem but it was because I had a previous version of xampp already installed and I tried to install a newer version. I had installed the newer version in another file directory (I had named the file directory xampp2). I solved the problem by uninstalling the newer version, renaming the old one (I renamed it xamppold) and I installed xampp again.
I guess if you haven't installed xampp in another file directory , it should be enough to reinstall xampp. If you are worried about your files , you always can make a backup before reinstalling xampp.
I solved the problem after watching the xampp activity log (the list of the bottom) and realizing xampp was trying to open the custom file path but I had another route path. If the first option didn't work, at least you can scroll up in the activity log and see what's error you get while starting as admin and trying to re install the Apache module or trying to start the module.
You may wander why I didn't just simply uninstall the whole thing from the beginning , and the answer would be because I had to tweak a couple of things in xampp for some different projects (from changing the ports , to add .dll to run mongo.db in Apache), and I was just too lazy to re-do everything again :b
I hope my answer can be helpful for anyone since this is my first time writing in stackoverflow :)
Cheers
In my case, with the same problem and Xampp window, I had copied \apache\conf\extra\httpd-vhosts.conf entries from an old Xampp version to a newly installed one so I could continue to open local projects in browsers. One of the vhosts paths was wrong. After deleting that entry Apache started without problem.
The reference by #Karthik to "in the Event viewer (Control panel -> View Event Logs" saved me time. It's all too easy to presume Xampp logs will point to the problem. It doesn't.
Also check if your xampp is installed in the main directory like C or D or E and not in or within a folder of that directory? i.e. ( "D:/Xampp" or is it "D:/something/Xampp") if its not in the main path of the directory, it will show this error.
copy your xampp directory from "D:\Something\Xampp" to "D:"
So it becomes like this "D:\Xampp"
and the issue will be resolved.
Starting Xampp as a console application (simply by doubleclicking xampp_start.exe in the Xampp root folder) was the only thing that worked for me on Windows 10 (no Skype, no Word Wide Web Publishing Service). WampServer and UwAmp also didn't work.
I had a hard-coded IP in httpd.conf and my local IP had changed which was causing my issue, changed IP over and all worked again
My scenario was different after I tested all the possible options. If you have changed the ports and still get the same problem, well here's something you can try out. This was done in Windows 7.
Step 1: Confirm the cause of the error by going to Control Panel -> System and Security -> Administrative Tools -> Event Viewer -> Windows Logs -> Application -> Error. Mine said "The Apache service named reported the following error:
httpd.exe: Syntax error on line 424 of C:/xampp/apache/conf/httpd.conf: Cannot load c:\xampp\php\php5apache.dll into server: The specified module could not be found." So I needed to change \php5apache.dll to the version of my php and apache version installed which was php7apache2_4.dll
Step 2: To get the correct name for your .dll php and apache file, got to C:\xampp\php. You will see something like php7apache2_4.dll with other files in the folder.
Step 3: Go to C:/xampp/apache/conf/httpd.conf and edit the configuration file and change "c:\xampp\php\php5apache.dll" to "c:\xampp\php\php7apache2_4.dll" in my case. Make sure you open the file as administrator save changes made.
Step 4: Run the xampp server and everything should work fine. Do not forget to shut down the xampp server before doing the changes to the apache configuration file.
Hope this helps. Cheers! :)
Try to install x86 version of XAMPP. The default XAMPP version on their website is x64 (maybe because I'm using x64 Windows 7).
download link here
I had this issue when I installed under Program Files, which they do not recommend due to write issues. This might only be a problem if you are not logged in as an admin and use a password to install. I just uninstalled and installed in a directory that did not need admin privileges.
Make sure Apache didn't get Disabled in Services (Control panel, Admin Tools, Services). If it's Disabled then Set it to Manual and it should run. That was my case, I found Apache Disabled.
Solution for my particular scenario (It had been working a couple days before getting borked):
Port 80 was not the problem, but something I had done while messing around with Services and Startup.
Type msconfig on Windows' Start menu
Click System Configuration
Screenshot for System Configuration
In the Services tab, search for Apache24 (Click "Hide all Microsoft services" in the checkbox at the bottom of the window to make it easier to find)
If its checkbox isn't checked, check it
If it was already checked, then this guide isn't going to help. However if it is:
Click OK, your PC will have to restart
Try once again! In my case Apache was already running once I opened Xampp
I had the same issue.Just click on services button.Then find apache and right cick > properties > set startup type as Automatic/ Manual. Now close apache and try again.It will work!
For me it wasn't a port or service issue; I had to re-run the XAMPP setup script. Although this didn't directly fix the issue for me, the script was much more verbose than the XAMPP log, pointing me in the right direction to actually solve the problem.
From the XAMPP GUI, click on Shell, type set, press Tab to autocomplete to the setup_xampp.bat file, and then press Enter to run it.
In my case I got the following output:
[ERROR]: Test php.exe failed !!!
[ERROR]: Perhaps the Microsoft C++ 2008 runtime package is not installed.
[ERROR]: Please try to install the MS VC++ 2008 Redistributable Package from the Mircrosoft page first
[ERROR]: http://www.microsoft.com/en-us/download/details.aspx?id=5582
This particular error is misleading. Although it specifies the Visual C++ 2008 Redistributable Package, PHP 7.4.x requires the Visual C++ 2019 Redistributable Package.
After installing that and following the prompt to restart, sure enough I'm now able to start Apache as normal.
make sure no space in front of the port number if you ever edited it.
From Xampp control panel, click on config (next to Apache), then choose Apache(httpd.config), search for listen 80 and change the port to another port.
If nothing works with you, I would suggest you download MAMP and use it instead.
It does the same thing, if not better.
Comment this lines from httpd.conf:
# Virtual hosts
#Include etc/extra/httpd-vhosts.conf
In the case you're using them it may solve.
when i run xampp control panel normal:
I had been run
I can’t start apache
So, I will run it with administrator:
I can run apache

asp.net not running on Apache 2 on OSX Lion - Getting a Forbidden 403 response

As of the current time of writing (2012-03-05) I'm running the following components:
OSX Lion
Default Apache installation (Apache2)
SSLEngine on Apache is "on" (doing some dev, but not trying to access .net through ssl yet)
Mono 2.10.8
xsp 2.10.2
mod_mono 2.10
I'm an Win/IIS guy so this is all new to me, but trying to get the xsp test ASP.NET app running on my mac (the app is in the xsp folder and is referenced in the mod_mono install guide).
I've run through the INSTALL guide for xsp and mod_mono.
As far as I can tell everything is running. Appache seems to have loaded the mono module, as it's ok with the mono configuration elements in it's httpd.cong file.
However, when I try to browse to an ASP.NET page, for example, the xsp test one (http://127.0.0.1/demo/index.aspx), I get:
Forbidden
You don't have permission to access /demo/index.aspx on this server.
Apache/2.2.20 (Unix) mod_ssl/2.2.20 OpenSSL/0.9.8r DAV/2 mod_mono/2.10 Server at 127.0.0.1 Port 80
The mono_mod troubleshooting guides say this might happen if Apache doesn't have read acess, but read access on the xsp test folder is set to:
everyone: Read & Write
I'm thinking it's not a directory permissions issue?
I wonder if the mono mod isn't running properly so actually Apache is trying to do a directory listing, which would give a 403?
What could be causing this? And is there any way to diagnose if all the mono mod stuff is installed and running correctly with Apache?
thanks
A script might also require execute permission, try from the command line:
chmod +x /path/to/script.aspx
This let's OS X (and other unixes) know that the file can be run.

Resources