Some how, I've messed things up and my web-server is not listening on port 80 for my virtual web site. I am able to connect to the GUI via port 81, but port 80 is not accepting connections, even if I just try to telnet to the IP address port 80. Can someone point me in the right direction as to what I may have messed up?
ISPConfig installs it's own webserver, so ports 80 and 81 are completely unrelated in that port 81 is the ISPConfig server, and port 80 the virtual hosts main web server. Check the web server logs for errors, and try starting it from a command line/terminal window. /etc/init.d/apache2 start or whatever it is on the system you are using
I tried that I didn't receive any erros on the screen or in the syslog file. So I then attempted a restart of apache2 and received the follow error: Forcing reload of web server: Apache2 ... no pidfile found! not running?vweb1:
That would be because the Apache2 logs are in the /var/log/apache2 folder not the syslog file.(at least they are in debian and ubuntu)
I was finally able to generate an error but I'm not sure what's is saying. This is from the error.log file within the /var/log/apache2 directory: [Mon Oct 15 15:01:50 2007] [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock Configuration Failed I realize it's saying that "something" is out of space but when I look at the ISP Server Status, here's what I see: Filesystem Size Used Avail Use% Mounted /dev/sda3 9.2G 754M 8.0G 9% / tmpfs 126M 0 126M 0% /dev/shm /dev/sda1 89M 11M 73M 13% /boot /dev/sda4 68G 891M 64G 2% /var
I'd have to say thats a new one on me! Translation mod_rewrite can't write an entry to it's log file. Any particular reason you're using logging on mod_rewrite? If not try a RewriteLogLevel 0. I'd say also do a df from a terminal window/command line just to make sure there isn't a full file system somewhere, or it could be a permissions thing on the log file, or simply that the file doesn't exist, and mod_rewrite thinks it should.
I've found a few articles specifying it may have something to do with ipcs but all the "fixes" are not fixing my issue. I'm at a complete loss...
Please check with the command: repquat -avug if you set a quta limit for your apache user and if the quota is full. Another possibility might be that you changed the permissions of the log file directory so that apache is not able to write to the file.
I'll give that a shot and let you know if it works. In the mean time, I just brought up an identical appliance and moved the web site over (since I only have 1 so far). One evening, I'll shutdown the production appliance and bring up the one giving me issues and attempt this command to see if it works. Now that you mention quota's, I did have an issues a few weeks ago in that even though I gave 250MB to this client and they had only uploaded abuot 200MB, they were unable to upload any additional files. Any ideas? Currently, they only have around 125MB with a 500MB limit.