Bug#419771: Segfaults with mod_auth_dbd and "DBDriver pgsql"
This could also be a problem in apache2. If you are using unstable, you could try again with apache 2.2.6-1, which had quite a few mod_dbd fixes. Cheers, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301155: marked as done (ssl.conf won't run)
Your message dated Sat, 8 Sep 2007 11:51:46 +0200 with message-id <[EMAIL PROTECTED]> and subject line Apache2 SSL service stopped working since upgrade to 2.2.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- package: apache2-doc version: 2.0.53-5 The file /usr/share/doc/apache2/examples/ssl.conf encloses the virtual host definition in . However there's no simple way to define SSL since in Debian apache2 is started with apache2ctl. The user might assume SSL is defined by apache2 if mod_ssl is loaded, but this is not the case. If SSL is not defined manually the configuration file doesn't load and no error message is produced. The problem may be difficult for the user to track down. I suggest the IfDefine line be simply deleted. The ssl configuration file can always be unlinked from the hosts-enabled directory if it is not wanted. Daniel Woodard [EMAIL PROTECTED] --- End Message --- --- Begin Message --- Version: 2.2.3-4+etch2 A warning has been added to NEWS.Debian in 2.2.3-4+etch2, which will be in etch 4.0r2. --- End Message ---
Bug#395936: marked as done (Apache2 SSL service stopped working since upgrade to 2.2.3-2)
Your message dated Sat, 8 Sep 2007 11:51:46 +0200 with message-id <[EMAIL PROTECTED]> and subject line Apache2 SSL service stopped working since upgrade to 2.2.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: Apache2 Version: 2.2.3-2 Apache2 server has been running fine for years with SSL enabled. However since this I upgraded Apache2 I can't connect to the https:// service anymore, although the http:// service runs fine. Firefox complains: has sent an incorrent or unexpected message. Error Code: -12263. Apache2 error.log shows: [client ] Invalid method in request \x16\x03\x01 --- Debian testing/unstable, kernel 2.6.18 i686 GNU/Linux libc6 2.3.6.ds1-4 --- End Message --- --- Begin Message --- Version: 2.2.3-4+etch2 A warning has been added to NEWS.Debian in 2.2.3-4+etch2, which will be in etch 4.0r2. --- End Message ---
Bug#397338: marked as done (apache2.2-common: 2.0->2.2 upgrade fails with custom jk module)
Your message dated Sat, 8 Sep 2007 11:49:02 +0200 with message-id <[EMAIL PROTECTED]> and subject line apache2.2-common: 2.0->2.2 upgrade fails with custom jk module has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: apache2.2-common Severity: normal My problem appears to be similar to #391864 and #392352 -- but not a duplicate as far as I can tell. I have a machine running apache2 with jboss and jk. I built jk as a module using "./configure --with-apxs=/usr/bin/apxs2" under Apache 2.0 (sarge) and then later upgraded the machine to etch. Today I attempted to upgrade to apache 2.2 in etch. It failed, horribly. I didn't understand what was going on, and so I had to roll back to 2.0. That was miserable. Alas, my terminals don't have the tens of thousands of lines of scrollback that would be required to give a FULL report of what happened. I can only give an approximation. If there is a fundamental incompatibility between apache 2.0 and apache 2.2 which causes custom modules (like jk) to become unusable upon update, then there should be a huge red blinking warning sign on this update, and a chance to abort. Here's my feeble attempt to describe what happened. 538 apt-get install apache2 539 apt-get install apache2 libapache2-mod-php4 At this point, Apache was updated, and failed to start. It complained about the jk module. So my first instinct was to rebuild it from the source directory. 540 apt-cache search -- apache -dev 541 dpkg -l | grep apache 542 apt-get install apache2-prefork-dev (In the other window:) 515 cd /var/tmp 516 ls 517 cd jakarta-tomcat-connectors-1.2.15-src 518 ls 519 cd jk/ 520 ls 521 less BUILD.txt 522 cd native 523 cat ../BUILD.txt 524 ./configure --with-apxs=/usr/bin/apxs2 525 make clean 526 ./configure --with-apxs=/usr/bin/apxs2 This is where ./configure decided that it couldn't figure out how big an "int" or a "long" was, and threw up its hands in despair. 527 gcc -v 528 cd /usr/bin 529 ls -l gcc 530 ln -sf gcc-3.3 gcc 531 cd - 532 ./configure --with-apxs=/usr/bin/apxs2 533 make That one got farther, but still died. It was using libtool inside apr-1.0 which, I noticed, was part of the updated stuff from the original apt-get. The failures appeared to be connected to that. I did NOT want to start poking around inside a non-default libtool. I just wanted Apache to run! So I started trying to downgrade back to the older packages. Those of you who've read #391864 can guess how smoothly *that* went. 544 cd /var/cache/apt/archives/ 545 ls 546 ls apache* 547 dpkg -i apache2-mpm-prefork_2.0.55-4.1_i386.deb apache2_2.0.55-4.1_i386.deb apache2-threaded-dev_2.0.55-4.1_i386.deb apache2-utils_2.0.55-4.1_i386.deb 548 dpkg --remove apache2-prefork-dev 549 dpkg -i apache2-mpm-prefork_2.0.55-4.1_i386.deb apache2_2.0.55-4.1_i386.deb apache2-threaded-dev_2.0.55-4.1_i386.deb apache2-utils_2.0.55-4.1_i386.deb 550 dpkg -i apache2-mpm-prefork_2.0.55-4.1_i386.deb apache2_2.0.55-4.1_i386.deb apache2-threaded-dev_2.0.55-4.1_i386.deb apache2-utils_2.0.55-4.1_i386.deb apache2-common_2.0.55-4.1_i386.deb 551 dpkg --remove apache2.2-common 552 apt-get --remove apache2.2-common 553 apt-get remove apache2.2-common 554 apt-get -f install 555 dpkg -i apache2-mpm-prefork_2.0.55-4.1_i386.deb apache2_2.0.55-4.1_i386.deb apache2-threaded-dev_2.0.55-4.1_i386.deb apache2-utils_2.0.55-4.1_i386.deb apache2-common_2.0.55-4.1_i386.deb 556 apt-get remove libapache2-mod-php4 557 apt-get remove libapache2-mod-php4 apache2-threaded-dev apache2-mpm-prefork 558 apt-get -f install 559 apt-get remove apache2 560 dpkg -i apache2-mpm-prefork_2.0.55-4.1_i386.deb apache2_2.0.55-4.1_i386.deb apache2-threaded-dev_2.0.55-4.1_i386.deb apache2-utils_2.0.55-4.1_i386.deb apache2-common_2.0.55-4.1_i386.deb 561 apt-get remove libapache2-mod-php4 562 dpkg -l | grep apache 563 apt-get remove apache-common apache2 apache2-common apache2-doc apache2-mpm-prefork apache2-threaded-dev apache2-utils apache2.2-common libapache-mod-php4 libapache2-mod-php4 564 dpkg -i apache2-mpm-prefork_2.0.55-4.1_i386.deb apache2_2.0.55-4.1_i386.deb apache2-threaded-dev_2.0.55-4.1_i386.deb apache2-utils_2.0.55-4.1_i386.deb apache2-common_2.0.55-4.1_i386.deb 565 dpkg --configure -a 566 apt-get -f install 567 dpkg --configure -a 568 ls libapr* 569 dpkg -i libapr0_2.0.55-4.1_i386.deb libapr0-dev_2.0.55-4.1_i3
Processed: fixed 397338 in 2.2.3-5
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.7 > fixed 397338 2.2.3-5 Bug#397338: apache2.2-common: 2.0->2.2 upgrade fails with custom jk module Bug marked as fixed in version 2.2.3-5. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397338: apache2.2-common: 2.0->2.2 upgrade fails with custom jk module
Version: 2.2.3-4+etch2 A warning is in the etch release notes and has now been added in 2.2.3-4+etch2 which will be in the next etch point release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342141: apache2: Apache2 weird forks (owned by root)
On Saturday 08 September 2007, Josip Rodin wrote: > On Fri, Sep 07, 2007 at 10:11:57PM +0200, Stefan Fritsch wrote: > > Has somebody seen this with 2.2.x? If not, I will close this bug > > report. > > I'm hoping to upgrade the machine experiencing it to etch soon, and > then I can say for sure. > > We actually experienced the problem again this morning (with 2.0). Possible ways to debug this would be stracing the root owned processes to see where they hang, or restarting under strace until the problem appears again. BUT this bug is not going to be fixed in sarge (being oldstable now). It is unfortunate that this has not been investigated earlier, but I think now it makes more sense to spend time on 2.2.x. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342141: apache2: Apache2 weird forks (owned by root)
On Fri, Sep 07, 2007 at 10:11:57PM +0200, Stefan Fritsch wrote: > Has somebody seen this with 2.2.x? If not, I will close this bug > report. I'm hoping to upgrade the machine experiencing it to etch soon, and then I can say for sure. We actually experienced the problem again this morning (with 2.0). -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
