Re: apache 1.3.28-4 on unstable
Sorry. I subscribed here at work and didn't read work email all weekend. I did a little searching around the net after sending my email to the list and thought it might be a problem w/ /etc/apache/modules.conf . I looked at that file and an old httpd.conf and all seemed to be in order. However, I ran /usr/sbin/modules-config apache again anyway. This command was in the comments in the header of modules.conf. This isn't a production machine so it wasn't urgent. This morning I restarted apache and all is good. BTW, was someone suggesting that I should read the bug reports for every package before going ahead with an ``apt-get -u dist-upgrade''. I suppose if I were really cautious I would, but then I wouldn't be running unstable would I ;-) Thanks for the help. Charles H. Baker Unix/Linux Systems Administrator chbaker at ps dot rockwell dot com work: 864.281.2409 fax: 864.281.2487 cell: 864.363.5302 If you do what you have always done, you will get what you have always gotten. --Paul J. Meyer Jeff Elkins [EMAIL PROTECTED]To: [EMAIL PROTECTED] link.netcc: Subject: Re: apache 1.3.28-4 on unstable 10/25/2003 11:20 PM Please respond to jeffelkins On Saturday 25 October 2003 10:05 pm, W. Paul Mills wrote: Well, it is a known bug in the apache package, you should have checked. The basic problem is that the modules are inserted into modules.conf in reverse order. Ouch, this just bit me too. Editing modules.conf didn't seem to work What's a fix? For some reason I never saw this message from ??. Perhaps edited /etc/apache/modules.conf, but are running apache-perl and need to edit /etc/apache-perl/modules.conf? An easy mistake to make, as you can have both installed. Fixed on my system. I re-created modules.conf by stripping out the loadmodules statements from an older httpd.conf modules.conf Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apache 1.3.28-4 on unstable
On Mon, 27 Oct 2003 14:05:29 +, chbaker wrote: BTW, was someone suggesting that I should read the bug reports for every package before going ahead with an ``apt-get -u dist-upgrade''. I suppose if I were really cautious I would, but then I wouldn't be running unstable would I ;-) Thanks for the help. Depends on your situation. But bug reports was the first place I went when I had the same problem. Had everything working again in about 5 minutes from initial discovery. I was using apt-listbugs, but it is broken now. Paul -- /** Running Debian Linux * For God so loved the world that He gave his only begotten Son,* * that whoever believes in Him should not perish...John 3:16* * W. Paul Mills * mailto:[EMAIL PROTECTED] * http://Mills-USA.com/ * * GnuPGPrint = 09BB FDEA 69E5 0E55 3843 B063 BB8B 518A B293 3D8C * / -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apache 1.3.28-4 on unstable
On Friday 24 October 2003 9:55 pm, W. Paul Mills wrote: On Fri, 24 Oct 2003 20:45:46 +, chbaker wrote: Ever since upgrading to apache 1.3.28-4 on unstable some strange things have happened. Index pages, whether html, shtml, or cgi are no longer working unless the page is explicitly listed. Example ``http://servername/'' yeilds a 403 Forbidden, but ``http://servername/index.html'' works. Also, I can no longer log into my installation of nagios-mysql. Does anyone have a clue? Is anyone experiencing anything similar? My quick scan of this months postings didn't turn up anything. I must also admit that I didn't do a thorough search of the bug db either. Well, it is a known bug in the apache package, you should have checked. The basic problem is that the modules are inserted into modules.conf in reverse order. Ouch, this just bit me too. Editing modules.conf didn't seem to work What's a fix? Luckily, the fix was easy. Replacing modules.conf with a backup copy worked, as did extracting the loadmodule statements from an httpd.conf into modules.conf Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apache 1.3.28-4 on unstable
Well, it is a known bug in the apache package, you should have checked. The basic problem is that the modules are inserted into modules.conf in reverse order. Ouch, this just bit me too. Editing modules.conf didn't seem to work What's a fix? For some reason I never saw this message from ??. Perhaps edited /etc/apache/modules.conf, but are running apache-perl and need to edit /etc/apache-perl/modules.conf? An easy mistake to make, as you can have both installed. Paul -- /** Running Debian Linux * For God so loved the world that He gave his only begotten Son,* * that whoever believes in Him should not perish...John 3:16* * W. Paul Mills * mailto:[EMAIL PROTECTED] * http://Mills-USA.com/ * * GnuPGPrint = 09BB FDEA 69E5 0E55 3843 B063 BB8B 518A B293 3D8C * / -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apache 1.3.28-4 on unstable
On Saturday 25 October 2003 10:05 pm, W. Paul Mills wrote: Well, it is a known bug in the apache package, you should have checked. The basic problem is that the modules are inserted into modules.conf in reverse order. Ouch, this just bit me too. Editing modules.conf didn't seem to work What's a fix? For some reason I never saw this message from ??. Perhaps edited /etc/apache/modules.conf, but are running apache-perl and need to edit /etc/apache-perl/modules.conf? An easy mistake to make, as you can have both installed. Fixed on my system. I re-created modules.conf by stripping out the loadmodules statements from an older httpd.conf modules.conf Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
apache 1.3.28-4 on unstable
Ever since upgrading to apache 1.3.28-4 on unstable some strange things have happened. Index pages, whether html, shtml, or cgi are no longer working unless the page is explicitly listed. Example ``http://servername/'' yeilds a 403 Forbidden, but ``http://servername/index.html'' works. Also, I can no longer log into my installation of nagios-mysql. Does anyone have a clue? Is anyone experiencing anything similar? My quick scan of this months postings didn't turn up anything. I must also admit that I didn't do a thorough search of the bug db either. Charles H. Baker Unix/Linux Systems Administrator chbaker at ps dot rockwell dot com work: 864.281.2409 fax: 864.281.2487 cell: 864.363.5302 If you do what you have always done, you will get what you have always gotten. --Paul J. Meyer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apache 1.3.28-4 on unstable
On Fri, 24 Oct 2003 20:45:46 +, chbaker wrote: Ever since upgrading to apache 1.3.28-4 on unstable some strange things have happened. Index pages, whether html, shtml, or cgi are no longer working unless the page is explicitly listed. Example ``http://servername/'' yeilds a 403 Forbidden, but ``http://servername/index.html'' works. Also, I can no longer log into my installation of nagios-mysql. Does anyone have a clue? Is anyone experiencing anything similar? My quick scan of this months postings didn't turn up anything. I must also admit that I didn't do a thorough search of the bug db either. Well, it is a known bug in the apache package, you should have checked. The basic problem is that the modules are inserted into modules.conf in reverse order. Paul (Just a dumb hobby administrator!) -- /** Running Debian Linux * For God so loved the world that He gave his only begotten Son,* * that whoever believes in Him should not perish...John 3:16* * W. Paul Mills * mailto:[EMAIL PROTECTED] * http://Mills-USA.com/ * * GnuPGPrint = 09BB FDEA 69E5 0E55 3843 B063 BB8B 518A B293 3D8C * / -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apache 1.3.28-4 on unstable
On Friday 24 October 2003 9:55 pm, W. Paul Mills wrote: On Fri, 24 Oct 2003 20:45:46 +, chbaker wrote: Ever since upgrading to apache 1.3.28-4 on unstable some strange things have happened. Index pages, whether html, shtml, or cgi are no longer working unless the page is explicitly listed. Example ``http://servername/'' yeilds a 403 Forbidden, but ``http://servername/index.html'' works. Also, I can no longer log into my installation of nagios-mysql. Does anyone have a clue? Is anyone experiencing anything similar? My quick scan of this months postings didn't turn up anything. I must also admit that I didn't do a thorough search of the bug db either. Well, it is a known bug in the apache package, you should have checked. The basic problem is that the modules are inserted into modules.conf in reverse order. Ouch, this just bit me too. Editing modules.conf didn't seem to work What's a fix? Jeff Elkins -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
