Re: Apache woes after upgrade - seg fault
On Fri, Jan 16, 2004 at 04:45:58PM +1030, David Purton wrote: Hi, I'm having all sorts of trouble since upgrading Apache to the latest in testing, yesterday. Using the default settings, it works. As soon as I try and add some VirtualHost directives and start apache, very occasionally it works, but mostly it just fails silently. On further investigation, if I run apache -X, it seg faults almost immediately :( -- David Purton [EMAIL PROTECTED] For the eyes of the LORD range throughout the earth to strengthen those whose hearts are fully committed to him. 2 Chronicles 16:9a signature.asc Description: Digital signature
Re: Apache woes after upgrade - seg fault
On Fri, Jan 16, 2004 at 07:26:57PM +1030, David Purton wrote: On Fri, Jan 16, 2004 at 04:45:58PM +1030, David Purton wrote: Hi, I'm having all sorts of trouble since upgrading Apache to the latest in testing, yesterday. Using the default settings, it works. As soon as I try and add some VirtualHost directives and start apache, very occasionally it works, but mostly it just fails silently. On further investigation, if I run apache -X, it seg faults almost immediately :( OK more info - If I take out the php4 module it works. I want php, so leaving it out is not a good solution dc -- David Purton [EMAIL PROTECTED] For the eyes of the LORD range throughout the earth to strengthen those whose hearts are fully committed to him. 2 Chronicles 16:9a signature.asc Description: Digital signature
Re: Apache woes after upgrade [SOLVED]
On Fri, Jan 16, 2004 at 11:21:48PM +1030, David Purton wrote: OK more info - If I take out the php4 module it works. I want php, so leaving it out is not a good solution Ha! Great support on this mailing list :) My problem is solved - commenting out extension=imap.so from /etc/php4/apache/php.ini fixed things. I somebody else can reproduce this I'll file a bug report (though I'm not sure against which package?): Debian mostly sarge on i386 +++-==-==-= ii apache 1.3.29.0.1-3 Versatile, high-performance HTTP ii php4 4.3.3-4A server-side, HTML-embedded ii php4-imap 4.3.3-4IMAP module for php4 Vith at least one virtual host setup in an otherwise default httpd.conf cheers dc -- David Purton [EMAIL PROTECTED] For the eyes of the LORD range throughout the earth to strengthen those whose hearts are fully committed to him. 2 Chronicles 16:9a signature.asc Description: Digital signature
Re: Apache woes after upgrade [SOLVED]
Hello David! On Fri, Jan 16, 2004 at 11:44:38PM +1030, David Purton wrote: My problem is solved - commenting out extension=imap.so from /etc/php4/apache/php.ini fixed things. I somebody else can reproduce this I'll file a bug report (though I'm not sure against which package?): Some people had the same problem and already filed some reports. Please see http://bugs.debian.org/php4-imap maybe you can add something useful... Cheers, Flo signature.asc Description: Digital signature
Apache woes after upgrade
Hi, I'm having all sorts of trouble since upgrading Apache to the latest in testing, yesterday. Using the default settings, it works. As soon as I try and add some VirtualHost directives and start apache, very occasionally it works, but mostly it just fails silently. Which log file will this sort thing appear in? apache -t says that the syntax of the file is ok Any ideas, I've been trying to fix it for last couple of hours :( dc -- David Purton [EMAIL PROTECTED] For the eyes of the LORD range throughout the earth to strengthen those whose hearts are fully committed to him. 2 Chronicles 16:9a signature.asc Description: Digital signature
Re: apache woes.
Subject: apache woes. Date: Tue, Dec 05, 2000 at 04:37:32PM -0500 In reply to:Jim Lynch Quoting Jim Lynch([EMAIL PROTECTED]): I looked at the bugs on www.debian.org and didn't see mine described, so I thought I bounce it off of this group. I installed potato. That was my first mistake. I haven't been able to get samba working nor will apache work. Nothing seems wrong with the install, but I can't get pages to display right. There is an index.html file in the /var/www directory but apache isn't looking for it there. Sorry about the wasted bandwidth. Somehow I sent the message before I finished. Can anyone tell me how to get apache working again? Thanks, Jim. Jim I am also having a problem with Apache on a box I installed from the CD's. I have it working on a Slink upgraded to Potato box so I have a working example to compare things with. I have been working on this problem box, off and on, for over a week now and just now found what was wrong. I will 'try' to explain how I fixed it. Ok, the main problem was 404 and 403 errors. I could run some of the index.html files but not all of them. I was unable to run any files, dww and dhelp, from the index.html located in /var/www. I just added/changed entries the the packaged /var/www/index.html file. Solutions: I found that in the /var/log/apache/error.log an error message was logged each time I force-reload(ed) apache [crit] (98)Address already in use: make_sock: could not bind to port 80 I stopped everything I could think but still got the message unitl I noticed that httpd was still running even if I had stopped Apache. I then killed httpd and restarted Apache (force-reload) and the error messages stopped, apache started normally. The error messages then pointed me to an unknown server 'host.mtntop.home'. I grepped the conf files on both systems. On the bad box it had /etc/apache/httpd.conf:DocumentRoot /var/www/host.mtntop.home and the good box /mnt/etc/apache/srm.conf:DocumentRoot /var/www I commented out the DocumentRoot /var/www/host.mtntop.home line, made sure that srm.conf was correct, restarted apache (force-reload) and now most everything works. I had added a bunch of earlier hints given to help fix Apache problems but they (of course) didn't help. My conf files were fsck badly. Hope that this might be of use to you. Wayne -- Keyboard : Instrument used to enter errors into computer. ___
Re: Debian apache woes
Erin, Without thinking too hard about what's going on since I don't admin apache, I'm wondering if your problem could not just be that '/etc/.profile' should really be called '/etc/profile' . I believe the convention is that these types of files are dotfiles in users' directories (so they won't have to see them without ls -a) but do not have dot prefix in /etc/ directory where they apply systemwide. However, maybe you just mistyped below and it really is correctly named on your system. HTH, Daniel Date: Tue, 5 Dec 2000 00:14:59 -0500 From: Eireann Lewy [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Debian apache woes Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Okay. I am completely and utterly at a loss here. I feel as if someone has stolen my brain because I should not be this stupid. I am, however, a relative linux fledgling (I have been windows-free for about a year and a half on the outside, and that's if I take out various pitfalls but anyway...). I'm having the following problems: 1) The worst: Despite having umask 022 in /etc/.profile and everyone's personal .profiles, newly created directories are randomly getting bad perms. This is bad because most of my users don't know what the hell permissions are, having none (except in very limited cases) in windows. I just taught my two main cronies about chmod 755 and 644 (for regular web files), but this shit can't keep happening. (For FTPed files, I set up a umask in the wu-ftpd ftpaccess file to set things at 644 which seemed to work.)
Re: Debian apache woes
On Tue, Dec 05, 2000 at 01:16:37PM -0500, Daniel Freedman wrote: Erin, Without thinking too hard about what's going on since I don't admin apache, I'm wondering if your problem could not just be that '/etc/.profile' should really be called '/etc/profile' . I believe it is called so the convention is that these types of files are dotfiles in users' directories (so they won't have to see them without ls -a) but do not have dot prefix in /etc/ directory where they apply systemwide. However, maybe you just mistyped below and it really is correctly named on your system. HTH, Daniel Date: Tue, 5 Dec 2000 00:14:59 -0500 From: Eireann Lewy [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Debian apache woes Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Okay. I am completely and utterly at a loss here. I feel as if someone has stolen my brain because I should not be this stupid. I am, however, a relative linux fledgling (I have been windows-free for about a year and a half on the outside, and that's if I take out various pitfalls but anyway...). I'm having the following problems: 1) The worst: Despite having umask 022 in /etc/.profile and everyone's personal .profiles, newly created directories are randomly getting bad perms. This is bad because most of my users don't know what the hell permissions are, having none (except in very limited cases) in windows. I just taught my two main cronies about chmod 755 and 644 (for regular web files), but this shit can't keep happening. (For FTPed files, I set up a umask in the wu-ftpd ftpaccess file to set things at 644 which seemed to work.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- ,---. Name: Alson van der Meulen Personal: [EMAIL PROTECTED] School: [EMAIL PROTECTED] `---' dd if=/dev/null of=/vmunix -
apache woes.
I looked at the bugs on www.debian.org and didn't see mine described, so I thought I bounce it off of this group. I installed potato. That was my first mistake. I haven't been able to get samba working nor will apache work. Nothing seems wrong with the install, but I can't get pages to display right. There is an index.html file in the /var/www directory but apache isn't looking for it there. Sorry about the wasted bandwidth. Somehow I sent the message before I finished. Can anyone tell me how to get apache working again? Thanks, Jim. It seems to be looking in /usr/htdocs. However I get the message, The requested URL / was not found on this server. When I look at the error log I see: [Tue Dec 5 16:17:27 2000] [error] [client 169.238.221.206] File does not exist : /usr/htdocs/ [Tue Dec 5 16:17:49 2000] [error] [client 169.238.221.206] File does not exist : /usr/htdocs/ There is an index.html file in /usr/htdocs, see: chinaberry:/usr/htdocs# ls -ld drwxr-xr-x2 root root 1024 Dec 5 16:28 . chinaberry:/usr/htdocs# ls -l total 4 -rw-r--r--1 root root 4094 Dec 5 14:44 index.html chinaberry:/usr/htdocs# ls -ld /usr drwxr-xr-x 17 root root 1024 Dec 5 14:42 /usr chinaberry:/usr/htdocs# It does display it as if it were a text file if I specifically address it (http://chinaberry.peachtree.sgi.com/index.html). Here is the text of the removal of the old stuff and the installation of the new: chinaberry:/usr/htdocs# apt-get remove apache-common Reading Package Lists... Done Building Dependency Tree... Done The following packages will be REMOVED: apache apache-common 0 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 2402kB will be freed. Do you want to continue? [Y/n] Y (Reading database ... 38069 files and directories currently installed.) Removing apache ... Stopping web server: apache. /usr/sbin/apachectl stop: httpd (no pid file) not running dpkg - warning: while removing apache, directory `/var/log/apache' not empty so not removed. dpkg - warning: while removing apache, directory `/etc/apache' not empty so not removed. Removing apache-common ... chinaberry:/usr/htdocs# rm -r /var/log/apache chinaberry:/usr/htdocs# rm -r /etc/apache chinaberry:/usr/htdocs# rm -r /var/www chinaberry:/usr/htdocs# apt-get remove apache.doc Reading Package Lists... Done Building Dependency Tree... Done The following packages will be REMOVED: apache-doc 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 1690kB will be freed. Do you want to continue? [Y/n] y (Reading database ... 37798 files and directories currently installed.) Removing apache-doc ... chinaberry:/usr/htdocs# apt-get install apache Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: apache-common The following NEW packages will be installed: apache apache-common 0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/1076kB of archives. After unpacking 2402kB will be used. Do you want to continue? [Y/n] y Media Change: Please insert the disc labeled 'Debian GNU/Linux 2.2 r0 _Potato_ - Official i386 Binary-1 (2814)' in the drive '/cdrom/' and press enter Selecting previously deselected package apache-common. (Reading database ... 37655 files and directories currently installed.) Unpacking apache-common (from .../apache-common_1.3.9-13.1.deb) ... Selecting previously deselected package apache. Unpacking apache (from .../web/apache_1.3.9-13.1.deb) ... Setting up apache-common (1.3.9-13.1) ... Setting up apache (1.3.9-13.1) ... Installing new configuration file /etc/apache/httpd.conf ... Installing new configuration file /etc/apache/cron.conf ... An Apache configuration exists, but needs some tweaking. Your config files will not be modified until you select Y at save changes. The ServerAdmin is set to [EMAIL PROTECTED] The Apache server will serve documents from a directory called the document root or server root. You must specify such a directory for the server to work: /var/www is recommended. What should the DocumentRoot be? [/var/www] Created directory /var/www. Fixing: owner of /var/www retained as root.root Installing your new homepage in /var/www. Finding DSO mods.found. # LoadModule vhost_alias_module /usr/lib/apache/1.3/mod_vhost_alias.so # LoadModule env_module /usr/lib/apache/1.3/mod_env.so LoadModule config_log_module /usr/lib/apache/1.3/mod_log_config.so # LoadModule mime_magic_module /usr/lib/apache/1.3/mod_mime_magic.so # LoadModule mime_module /usr/lib/apache/1.3/mod_mime.so # LoadModule negotiation_module /usr/lib/apache/1.3/mod_negotiation.so LoadModule status_module /usr/lib/apache/1.3/mod_status.so # LoadModule info_module /usr/lib/apache/1.3/mod_info.so # LoadModule includes_module
Re: Debian apache woes
Except I suck at it. I'm running debian potato (I run woody at home but I wouldn't trust it on a server till it's distributed officially) and apache 1.3.9. (I know, it is old, but it's the latest version in potato as far as I can see.) Keep trying. It really does get better. I'm having the following problems: 1) The worst: Despite having umask 022 in /etc/.profile and everyone's personal .profiles, newly created directories are randomly getting bad perms. This is bad because most of my users don't know what the hell permissions are, having none (except in very limited cases) in windows. I just taught my two main cronies about chmod 755 and 644 (for regular web files), but this shit can't keep happening. (For FTPed files, I set up a umask in the wu-ftpd ftpaccess file to set things at 644 which seemed to work.) Randomly getting bad perms? That sounds strange. Is there a pattern to the permissions? Do the users who get the bad perms always get the same ones? Do whatever you can to reproduce the problem so that you can see it happening and not just rely on the users' input. Eliminate as many variables as you can and often the solution will present itself. Make sure the file in /etc is named profile, not .profile. Woud it be possible to consider changing ftp servers? I have used proftpd and have seen that the configuration process is much easier than wu-ftp. 2) Periodically and randomly people alert me I can't FTP. This seems to occassionally clear up or people just tell me I'm not having a problem anymore. Since I can FTP fine, and can test the files I put there via FTP, I really can't see what the problem is for these people. Are they being stupid? I don't know, because it's now happened to two different people. Does the machine have more than one network interface? If so, do an nslookup and see what your DNS reports back. Check to see if you always get the same IP address first (assuming more than one) or it reports them in a different order with each lookup. If the ftp server listens to a particular IP address, ftp to the IP address and see what haapens. 3) After having CGI scripts forbidden for a while I finally found the umpteenth place where I had to put an ExecCGI in the apache config files and now every CGI script on the page (one for using finger to return e-mail addresses of people put into the search thing via a second page frame, and one for a message board) is run and returns internal errors. The error in /etc/logs/apache/error.log is that there is a premature ending of headers. Check the script to make sure that before it sends any output back to the client that it sends a header first. In Perl, the statement looks like so: print Content-type: text/html\n\n; The two newlines are essential. I am not usually this stupid. Honestly. I run my own machine virtually error-free. Apache is simply the bane of my fucking existance. Please give me ANY input you can. I'm going away for a semester and my co-admin thought this would be fine until everything simultaneously decided to break this week. :P Don't let the pressure get to you. Try to give yourself some space. Remember that computers are relentlessly logical, even if it's a logic not obvious at the time. A patient, disciplined approach of assessing what you know about a problem, reducing it to the simplest possible form and then proceeding to ask questions and try out different hypotheses will often lead to the answer. And when it doesn't, then you have valuable input to post a question to the list. Murphy's law will never be repealed. Ernest Johanson Web Systems Administrator Fuller Theological Seminary
Debian apache woes
Okay. I am completely and utterly at a loss here. I feel as if someone has stolen my brain because I should not be this stupid. I am, however, a relative linux fledgling (I have been windows-free for about a year and a half on the outside, and that's if I take out various pitfalls but anyway...). So I'm going to this tiny liberal arts college where I am one of four people I know who run linux on campus. I shit you not. Most people don't want to have to learn computers. So I am a small fish in a tiny pond, making me one of the most knowledgable people here and this is how I was selected to admin this student-run webserver which runs Linux. My co-admin is very slowly learning small commands while she does most of the HTML and I just, well, geek. Except I suck at it. I'm running debian potato (I run woody at home but I wouldn't trust it on a server till it's distributed officially) and apache 1.3.9. (I know, it is old, but it's the latest version in potato as far as I can see.) I'm having the following problems: 1) The worst: Despite having umask 022 in /etc/.profile and everyone's personal .profiles, newly created directories are randomly getting bad perms. This is bad because most of my users don't know what the hell permissions are, having none (except in very limited cases) in windows. I just taught my two main cronies about chmod 755 and 644 (for regular web files), but this shit can't keep happening. (For FTPed files, I set up a umask in the wu-ftpd ftpaccess file to set things at 644 which seemed to work.) 2) Periodically and randomly people alert me I can't FTP. This seems to occassionally clear up or people just tell me I'm not having a problem anymore. Since I can FTP fine, and can test the files I put there via FTP, I really can't see what the problem is for these people. Are they being stupid? I don't know, because it's now happened to two different people. 3) After having CGI scripts forbidden for a while I finally found the umpteenth place where I had to put an ExecCGI in the apache config files and now every CGI script on the page (one for using finger to return e-mail addresses of people put into the search thing via a second page frame, and one for a message board) is run and returns internal errors. The error in /etc/logs/apache/error.log is that there is a premature ending of headers. I am not usually this stupid. Honestly. I run my own machine virtually error-free. Apache is simply the bane of my fucking existance. Please give me ANY input you can. I'm going away for a semester and my co-admin thought this would be fine until everything simultaneously decided to break this week. :P Erin
