whats the difference between restarting/stopping apache using 'service httpd restart/stop' and apachectl restart/stop. I know that using 'service httpd restart' is actually a script in /etc/init.d/httpd but what about apachectl?
When I do " ps aux | grep apache " I can see that apache2 is running. But when I do the same thing for http or httpd there is nothing. I looked for this question in the forums but couldn't find it. I probably don't know just what to look for.I'm using the new Debian Squeeze, and was fooling around heavily with new software installations and modifications, and just noticed all of a sudden that I couldn't get on the internet - so I know I did something but don't know what.I can plug in a thumb drive with a bitnami joomla stack on it and run, " ~/tmp/joomla-1.6.0-0/./ctlscript.sh start "and that gets things going for the joomla stuff (apache, http, mysql, php), but that stuff is pretty self contained and does not effect the browser's attempt to reach the web.
I have just installed Fedora 11 on a "fresh machine" and everything works ok, except for Apache httpd the message seen in the error_log is the following: Name or service not known: mod_unique_id: unable to find IPv4 address of "myserver"
Code: #!/bin/bash #count lines that show apache2 but not the fgrep itself let i=`ps aux | fgrep apache2 | fgrep -v grep | wc -l` if [ "$i" -gt 0 ] then #log something
[Code]...
It has all been working fine until recently when Apache is becoming unresponsive. I manually ran ps to check and there were 3 processes. However when I ran apache2ctl graceful I got the message 'httpd not running, trying to start' Is there a better way to check if a daemon is up?
I installed LAMPP a couple of weeks ago and was working fine. Today when I try to start lampp, it will only start MySql and ProFTPD. It says "XAMPP: Another web server daemon is already running." How can I find out where this other server is located and stop it?
I have installed fedora 13 in my system. httpd server is also installed. when I tried to start the service of httpd, following error message displayed: Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80
When creating sub-domains, and creating log files for each domain, do I need to ensure that apache owns the log files, so that it can write to it? As I notice they are owned by root, obviously whom I used to make the file...
I'm running Ubuntu 10.04 LTS and I have installed openssh.I need to find a way to configure it so that it never start up when I boot into my computer. The reason is: I haven't had the time yet to learn how to set it up and configure it correctly. Until that time comes I don't want it to run at all.Every single time I boot into the system and I have to do that first before I can even do what I really need to on the computer. It's annoying.Does anyone know the best and least complicated way to just make it not run at all until I'm ready to set it up properly?Also how to check what is running on my system after I boot up so I can double check, after making the changes, that it worked right.
I have one previously compiled apache server from source. I would like to know is there any option to get previous configuration file from /etc/httpd/.
Running CentOS 5 x64 And today my httpd is running very slow and I can't find a fix. Looked all over different forums
When starting httpd I get the message: /var/lock/subsys/httpd': No space left on device I checked that directory above and there is no file called httpd tried rebooting server
Can't do updates too: [root@u15438957 ~]# yum update Loaded plugins: fastestmirror, priorities rpmdb: unable to join the environment
I have a big database, which should "build up" before receiving requests, so i need httpd to start about 3 minutes after mysql start, so it prevents the visitors to start querys to the database, and making server load high. How can i do this.
Im having problems getting the httpd service to start. Instead of clearing my log files in var/log i accidently did a force remove command on all the log files within the log directory. I'm not unable to start my httpd service and of course unable to check my log files to see whats what.
I configured httpd.conf. With ip, port 80 and specified the document path correctly. But service httpd restart shows httpd stop fail, httpd start fail.
I have centos 5.3 installed, while restarting httpd service I get error starting http:/bin/bash line 1 9941 segmentation fault /usr/sbin/httpd. If I stop httpd service and start it will start but if make service httpd restart it give above error.
We have apache installed at a directory other than the default location. There are two httpd.conf files on the server, one at the apache installation directory, and the other one is the default one at /etc/httpd/conf. The apache ran very well with the customized httpd.conf before, but after I installed php 5, the server seems taking the default httpd.conf and doesn't display the html pages which are installed at our apache directory. How to let the server know not to use the default httpd.conf and use the customized one instead?
I just did a clean install of FC12 x86_64 and want to configure tomcat to run behind apache httpd. What is the easiest way to accomplish this? I'm a newbie at server configuration so detailed instructions would be nice
I have Apache Server working online under Fedora Core 6. But before I installed and configured everything, I've been testing in Fedora 12. The problem surges here, when I start the httpd service, every supuse 404 action on a web browser, takes me to localhost. I mean, if I enter google.com, no error, just goes to localhost, http://asdasd, no error, gives back localhost. I used to ignore the problem 'cause I thought it was a problem on my apache, but when I installed the Server on the Fedora Core 6 machine, I found that I have the same problem there. Of course, it only occurs when I am browsing through the same machine that has httpd started. Does anyone know how to change that??
I am trying to setup Fedira 12 Linux Apache in my home network. I am able to access the hosted website from inside my home network without any problem. I am facing the problem to access it from outside. At the moment i have connected the Apache directly to DSL modem for testing purpose. I was reading "The ISP may have blocked the HTTP port 80. So check it by connecting the Apache directly to DSL modem." The temporary network connections for testing purpose are as follows..
DSL modem (SIEMENS Speed Stream 4200)-->Fedora 12/Linux Apache Server
I am even unable to PING the real ip (IP for DSL modem).(Firefox gave me error message "Connection Timed out) I have tried to ping it from the internet.I can PING the DSL from Apache without any problem.
1. Why i am even unable to PING the real IP of DSL modem at my home.?
2. Is it possible to run/setup Apache by using this type of DSL modem?
3. DSL modem has real IP. DSL MODEM assigns private IP (192.168.x.x) to Apache. So when a http request form the internet came to DSL modem on port 80, will it forward to Apache automatically.? or i have to made any changes.(I can not see anything in DSL modem to change/modify), OR do I have to use another DSL MODEM/Equipment (router)? This setup is just temporary. The actual design is as follows
DSL MODEM(Speed Stream 4200)-->Fedora 12 Linux ROUTER--->Internal network with DNS/Apache Server
I have both apache and tomcat services running, both in their standard doors (tomcat 8080, httpd 80). I need to setup tomcat to run on door 80 instead of httpd. I changed httpd door with success to 8180. Now I want to change tomcat6 door to 80, and I did that by editing server.xml config file of tomcat. After restarting tomcat, the system tells me it's ok, but I can see that it's not running on 80, nor at any other door. A simple nmap search confirm that. What should I do to have tomcat running in door 80?
I am unable to examine Apache httpd error log from YaST2 because the lines are too long; the browser just truncates them and thus it does not show any description. The only option is to save it. However, when I chose that option, YaST2 encourages me to save it in /tmp, and as soon as I do that, the log becomes accessible to every user!