Problem with www/mod_cband
FreeBSD office19.resnet.nd.edu 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1 10:10:12 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Hello everyone. Every time I try to use the mod_cband module in my apache22 webserver, apache segfaults upon restart. Things work fine when I disable the module from httpd.conf. Is this module broken, and if so, what comparable alternatives are there? -- -- Best, David Karapetyan http://davidkarapetyan.homeunix.com University of Notre Dame Department of Mathematics 255 Hurley Hall Notre Dame, IN 46556-4618 Phone: 574-631-5706 Cell: 202-460-5173 Fax: 574-631-6579 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
On Fri, Oct 17, 2008 at 12:57:41PM -0400, David Karapetyan wrote: FreeBSD office19.resnet.nd.edu 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1 10:10:12 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Hello everyone. Every time I try to use the mod_cband module in my apache22 webserver, apache segfaults upon restart. Things work fine when I disable the module from httpd.conf. Is this module broken, and if so, what comparable alternatives are there? Be aware that mod_cband has quite a horrible bug. This is a Debian bug report, but the same problem applies to FreeBSD. Be sure to read the entire bug, not just the original report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418645 Regarding alternatives: there aren't. Bandwidth limiting is a long-standing feature of Apache that's missing, which is a huge disappointment. The best solution I've found on FreeBSD is to use pf(4) with ALTQ, and give each VirtualHost its own IP address, then rate-limit the IP address using pf(4). Yes, I realise this is impractical for sites which have many vhosts and use name-based virtualhosts. Welcome to my world... -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
On Friday 17 October 2008 19:53:59 Jeremy Chadwick wrote: Regarding alternatives: there aren't. Bandwidth limiting is a long-standing feature of Apache that's missing, which is a huge disappointment. Never used it, but www/mod_bw is not a real world alternative? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
On Fri, Oct 17, 2008 at 08:31:29PM +0200, Mel wrote: On Friday 17 October 2008 19:53:59 Jeremy Chadwick wrote: Regarding alternatives: there aren't. Bandwidth limiting is a long-standing feature of Apache that's missing, which is a huge disappointment. Never used it, but www/mod_bw is not a real world alternative? http://www.ivn.cl/apache/files/txt/mod_bw-0.8.txt I believe the problem I ran into with this module was that it would only work with static content, and not with interpreted languages (such as PHP) or other things. I know there's a directive in the module to tell it what output types it supports, but I don't think it worked quite right. I'd have to go back and try it. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
--- On Fri, 10/17/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: Problem with www/mod_cband To: David Karapetyan [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org, [EMAIL PROTECTED] Date: Friday, October 17, 2008, 1:53 PM On Fri, Oct 17, 2008 at 12:57:41PM -0400, David Karapetyan wrote: FreeBSD office19.resnet.nd.edu 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1 10:10:12 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Hello everyone. Every time I try to use the mod_cband module in my apache22 webserver, apache segfaults upon restart. Things work fine when I disable the module from httpd.conf. Is this module broken, and if so, what comparable alternatives are there? Be aware that mod_cband has quite a horrible bug. This is a Debian bug report, but the same problem applies to FreeBSD. Be sure to read the entire bug, not just the original report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418645 Regarding alternatives: there aren't. Bandwidth limiting is a long-standing feature of Apache that's missing, which is a huge disappointment. The best solution I've found on FreeBSD is to use pf(4) with ALTQ, and give each VirtualHost its own IP address, then rate-limit the IP address using pf(4). Yes, I realise this is impractical for sites which have many vhosts and use name-based virtualhosts. Welcome to my world... IMHO, that solution is considerably sexier than what mod_cband claims to do (having read only pkg-descr). It seems possible, however, that mod_cband's functionality could be replicated by a simple script that watches the access log files and makes an update to a .htaccess file for the virtualhost when the virtualhost in question exceeds a given bandwidth limit which would be configured in the script. Think `tail -f`. Functionality is handled outside of apache so no danger of crashes. Just create the .htaccess in such a way that the end-user can't delete/modify it, and have it do a Redirect. For robustness' sake, move any existing .htaccess file to .htaccess.X and move it back when the virtualhost is back in compliance or paid up or whatever. - mdh __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
On Friday 17 October 2008 20:47:38 mdh wrote: IMHO, that solution is considerably sexier than what mod_cband claims to do (having read only pkg-descr). It seems possible, however, that mod_cband's functionality could be replicated by a simple script that watches the access log files I don't think you fully understand the problem. Apache writes a served file to the log when a download is *completed*. Consider a 700MB iso download and you quickly see your solution will not work. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
On Fri, Oct 17, 2008 at 11:47:38AM -0700, mdh wrote: It seems possible, however, that mod_cband's functionality could be replicated by a simple script that watches the access log files and makes an update to a .htaccess file for the virtualhost when the virtualhost in question exceeds a given bandwidth limit which would be configured in the script. Well, that's assuming you want to use the maximum aggregate bandwidth per site every month concept. I, for one, do not, because all it takes is one prick wget -r'ing the site and pow, the site is down for everyone. You could block based on IP, but believe me, they'll find or get another. (I've personally seen this with Italian users, where they'd switch to another IP to get around pf(4) blocks I put in place.) I personally prefer to just bandwidth limit sites, only permitting XXX Kbyte/sec across *all visitors*. It's the only safe way to deal with 95th-percentile billing in co-locations. Also, don't forget that Apache only writes an entry to the log file *after* the transfer is finished, not when the request is submit. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
