I just installed xampp on my laptop but I have some issue running apache. It says busy port 80. I have unchecked port 80 on skype and change the apache config to 81.
3:05:11 p.m. [main] Initializing Control Panel
3:05:11 p.m. [main] Windows Version: Windows 7 Home Premium SP1 64-bit
3:05:11 p.m. [main] XAMPP Version: 1.8.2
3:05:11 p.m. [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
3:05:11 p.m. [main] You are not running with administrator rights! This will work for
3:05:11 p.m. [main] most application stuff but whenever you do something with services
3:05:11 p.m. [main] there will be a security dialogue or things will break! So think
3:05:11 p.m. [main] about running this application with administrator rights!
3:05:11 p.m. [main] XAMPP Installation Directory: "c:\users\dean\desktop\m\"
3:05:11 p.m. [main] Checking for prerequisites
3:06:43 p.m. [main] All prerequisites found
3:06:43 p.m. [main] Initializing Modules
3:06:44 p.m. [main] Starting Check-Timer
3:06:44 p.m. [main] Control Panel Ready
3:06:49 p.m. [Apache] Status change detected: running
3:06:50 p.m. [Apache] Status change detected: stopped
3:06:50 p.m. [Apache] Error: Apache shutdown unexpectedly.
3:06:50 p.m. [Apache] This may be due to a blocked port, missing dependencies,
3:06:50 p.m. [Apache] improper privileges, a crash, or a shutdown by another method.
3:06:50 p.m. [Apache] Press the Logs button to view error logs and check
3:06:50 p.m. [Apache] the Windows Event Viewer for more clues
3:06:50 p.m. [Apache] If you need more help, copy and post this
3:06:50 p.m. [Apache] entire log window on the forums
The log says it is not being ran with admin rights. Try right-clicking the xampp_start.exe file and clicking 'Run as Administrator'
Try going into your apache folder inside the xampp folder (xampp\apache) and running the apache_uninstallservice.bat and then apache_installservice.bat. If this doesn't work then hopefully someone else can help cause I'm out of ideas
In windows, disable the already running 'World Wide Web Publishing' service which is running at port 80 ( and is blocking Apache to start). To do so Start >> Run >> services.msc >> lookout for 'World Wide Web Publishing' service >> Stop the service and set the start type to 'Disabled'.
Then try starting the xampp Apache again.
If you done hidden everything (Except or include htdocs) on your xampp folder in C drive (such as C:\xampp) than please un-hidden everything. That may be helpful.
Related
I have been using xampp for some time with no problems. But today, when I try to run it, I get the error Problem detected: Apache Not Found! I have made no changes to any settings/directories that could have caused this error. The only thing that I did was copied a project into the htdocs folder. But deleting it from there makes no difference. Any help would be great!
12:30:24 PM [main] Initializing Control Panel
12:30:24 PM [main] Windows Version: Enterprise 64-bit
12:30:24 PM [main] XAMPP Version: 8.1.6
12:30:24 PM [main] Control Panel Version: 3.3.0 [ Compiled: Apr 6th 2021 ]
12:30:24 PM [main] Running with Administrator rights - good!
12:30:24 PM [main] XAMPP Installation Directory: "d:\xampp\"
12:30:24 PM [main] Checking for prerequisites
12:30:24 PM [main] All prerequisites found
12:30:24 PM [main] Initializing Modules
12:30:24 PM [Apache] Problem detected: Apache Not Found!
12:30:24 PM [Apache] Disabling Apache buttons
12:30:24 PM [Apache] Run this program from your XAMPP root directory!
12:30:24 PM [mysql] XAMPP MySQL is already running on port 3306
12:30:24 PM [main] Starting Check-Timer
12:30:24 PM [main] Control Panel Ready
I installed tomcat 9.0.14 on my system(Windows 10, Windows server 2016 R2)
I've no issue while starting the tomcat service(start in 2-3 sec).
However, it takes 1 minute to stop.
I thought one of my project residing under webapps is taking time so I removed all my project but result is same.
After that I make it empty webapps folder empty to check further still tomcat took 1 min to stop.
I check the log file and their are no errors.Tomcat is idle for 1 minute while stopping.
Common-deamon.log-------
[2019-01-08 16:30:02] [info] [13948] Stopping service...
[2019-01-08 16:30:03] [info] [13948] Service stop thread completed.
[2019-01-08 16:31:03] [info] [ 1940] Run service finished.
[2019-01-08 16:31:03] [info] [ 1940] Commons Daemon procrun finished
catalina.log--------
08-Jan-2019 16:30:02.399 INFO [Thread-6] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-8080"]
08-Jan-2019 16:30:02.431 INFO [Thread-6] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["ajp-nio-8009"]
08-Jan-2019 16:30:02.453 INFO [Thread-6] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
08-Jan-2019 16:30:02.453 INFO [Thread-6] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-8080"]
08-Jan-2019 16:30:02.453 INFO [Thread-6] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["ajp-nio-8009"]
Is their any way I can reduce the sopping time of tomcat 9.
In tomcat 8 stopping time was 3-5 sec
Any help is appreciated.....
I was abel to reproduce this by
Downloading and extracting the apache-tomcat-9.0.14-windows-x64.zip
cd to apache-tomcat/bin
service.bat install
Starting the Service is quick, stopping it delays exactly 60 seconds.
This seemes to be an issue of Tomcat, but current developer snapchot (trunk) changelog suggests it has been already fixed for not yet released Tomcat 9.0.15+ without explicit bug report assigned:
Tomcat 9.0.15 (markt) in development / Catalina:
Correct a bug exposed in 9.0.14 and ensure that the Tomcat terminates in a timely manner when running as a service. (markt)
We had the same problem with Tomcat v9.0.26. Tomcat took exactly 60 seconds to finish once you terminated the server. We tried hard to close and shutdown everything we had in our application and in the end we realized we had a ThreadPoolExecutor that created a newCachedThreadPool() and this cachepool has a "keepAliveTime" of 60 seconds.
So after terminating the tomcat the threadpool was waiting 60 seconds to check if the threads are still needed to be reused. Only after this time it really shut down. So the solution was to shut down the cached thread pool once we shut down the application.
I have installed XAMPP on my windows 7 machine but can't get Apache to work.
After opening the XAMPP panel and installing Apache service: I have tried start it, it always get stuck at "Starting apache service..."
On start I get the following:
7:36:57 [main] Initializing Modules
7:36:57 [main] The MySQL module is disabled
7:36:57 [main] The FileZilla module is disabled
7:36:57 [main] The Mercury module is disabled
7:36:57 [main] Starting Check-Timer
7:36:57 [main] Control Panel Ready
7:37:02 [main] Executing "services.msc"
7:41:50 [Apache] Attempting to start Apache service...
Event Viewer:
The Apache service named
reported the following error: >>>
httpd.exe: Syntax error on line 172 of C:/xampp/apache/conf/httpd.conf: Cannot load modules/mod_ssl.so into server: The specified module could not be found.
I also get an ERROR for the .NET Runtime Optimization Service:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 . Error code = 0x80070002
PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
On the first start i had some .dll problems but i solved them, I do not know if it is related.
I already tried everything in:
"XAMPP - Apache could not start - Attempting to start Apache service"
without improvement.
Any advice on how I could resolve this ?
Thanks
Go to Xampp control panel and click on config->httpd.conf then go to line no 171 and change
ServerName localhost:80
with
ServerName localhost:81
It will work.
I'm installing TeamCity in EC2, starting with the Server then moving on the agents. I'm starting with the Amazon Linux AMI, running on a micro instance. Then I did:
sudo yum update
wget http://download.jetbrains.com/teamcity/TeamCity-7.1.1.tar.gz
tar -xvzf TeamCity-7.1.1.tar.gz
cd TeamCity
bin/teamcity-server.sh start
When I start it using bin/teamcity-server.sh start, things happen. I can connect using a web browser which shows the 'TeamCity is starting' page. The teamcity-server.log shows a bunch of activity, unzipping plugins etc.
But then suddently, the server process just disappears. The port's no longer listened to, ps shows no java process running, and the browser can't connect.
There's no error messages in the catalina or teamcity logs. After much trial and error though, I ran bin/teamcity-server.sh run (instead of start) to get console output, and got the following:
Using CATALINA_BASE: /home/ec2-user/TeamCity
Using CATALINA_HOME: /home/ec2-user/TeamCity
Using CATALINA_TMPDIR: /home/ec2-user/TeamCity/temp
Using JRE_HOME: /usr/lib/jvm/jre
Using CLASSPATH: /home/ec2-user/TeamCity/bin/bootstrap.jar:/home/ec2-user/TeamCity/bin/tomcat-juli.jar
Nov 1, 2012 7:22:25 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Nov 1, 2012 7:22:26 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8111"]
Nov 1, 2012 7:22:26 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2742 ms
Nov 1, 2012 7:22:26 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Nov 1, 2012 7:22:26 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.23
Nov 1, 2012 7:22:26 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /home/ec2-user/TeamCity/webapps/ROOT
Log4J configuration file /home/ec2-user/TeamCity/bin/../conf/teamcity-server-log4j.xml will be monitored with interval 10 seconds.
Nov 1, 2012 7:22:30 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8111"]
Nov 1, 2012 7:22:30 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3786 ms
=======================================================================
TeamCity 7.1.1 (build 24074) initialized, OS: Linux, JRE: 1.6.0_24-b24
TeamCity is running in professional mode
bin/teamcity-server.sh: line 18: 4231 Killed ./catalina.sh $1
I promise that I did not kill the process! I can find my way around in Linux well enough, but I'm not at all sure where to go next to find out why or what killed the process. Can anyone help?
After some further scanning of .sh files to see how TeamCity was starting itself up, I noticed that it was grabbing a fair amount of memory for it's java process (either 512m or 750m depending on which line you use).
The EC2 micro instance only has 613m of RAM total. When I realized this, I tried the whole process again with a larger instance, and things worked fine.
I'm still curious if there's a better way I could've known what was causing catalina to die, so if anyone wants to answer with that information...
When I try to start Apache tomcat 7.0.26 server is not starting. This is first time.
console message as follows :
Mar 7, 2012 12:06:18 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 470 ms
It has been started and the starting process took 470 ms.
That's what the message says.
I have the suspicion that you didn't even bother to check the url of web management to see if Tomcat is up or not.