Hello to all on the list.
For the last two months I have had a problem with backhand running
reliably. Though backhand starts up with no problem and runs for hours,
after anywhere from 4 hours to two days, backhand starts serving and
starts placing a gratuitious number of the following error messages into
my apache error log file:
[Fri Oct 4 21:49:12 2002] [error] (111)Connection refused: Child 6079
failed to establish umbilical to moderator!
This is a "dumb front end" tier 1 box only has a single html file
basically stating that the site is down and to come back later. The rest
of the website (www.linuxguru.net) is actually on a backend box (normally
two, but one threw a hard drive)
I am using the following versions of software:
---cust here
name developer debian
version version
backhand 1.2.1 1.2.1-1.2
apache 1.3.26 1.3.26-1.1
Linux 2.4.18 n/a
---cust here
The backhand pertinant part of my httpd.conf looks thusly:
---cut here
LoadModule backhand_module /usr/lib/apache/1.3/mod_backhand.so
AddModule mod_backhand.c
UnixSocketDir /var/run/libapache-mod-backhand
MulticastStats 192.168.2.1:4445
AcceptStats 192.168.2.0/24
<Location "/backhand/">
SetHandler backhand-handler
</Location>
---cut here
When things are normally working, a ps aux shows apache processes along
these lines:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
www-data 8129 0.0 1.2 3360 1628 ? S 13:19 0:00 /usr/sbin/apache
I have noticed that on occasion these processes jump up in their RSS size
all the way up to 32 megabytes occasionally. I think that this is somehow
related but I am not sure. (To be honest, I suspected that its a memory
leak caused when the umbilical is lost.)
Oh, one other thing. I am unable to reproduce this at will, though it
happens frequently enough (anywhere from semidaily to bidaily) that I can
look into things while it's not working. When I stress test the site, it works
fine, so the umbilical loss seems to not be related to load.
General stats for the site:
---cut here
- Average page build on the backend machine is .60 seconds
- Usual page size (including images) around 80k
- Frontend server is a Athlon 500 w/ 128 megs of ram
- Frontend server has 128 megs of ram.
- Site gets approximately 1500 page views a day
---cut here
--
GnuPG fingerprint AAE4 8C76 58DA 5902 761D 247A 8A55 DA73 0635 7400
James Blackwell -- Director http://www.linuxguru.net
For the last two months I have had a problem with backhand running
reliably. Though backhand starts up with no problem and runs for hours,
after anywhere from 4 hours to two days, backhand starts serving and
starts placing a gratuitious number of the following error messages into
my apache error log file:
[Fri Oct 4 21:49:12 2002] [error] (111)Connection refused: Child 6079
failed to establish umbilical to moderator!
This is a "dumb front end" tier 1 box only has a single html file
basically stating that the site is down and to come back later. The rest
of the website (www.linuxguru.net) is actually on a backend box (normally
two, but one threw a hard drive)
I am using the following versions of software:
---cust here
name developer debian
version version
backhand 1.2.1 1.2.1-1.2
apache 1.3.26 1.3.26-1.1
Linux 2.4.18 n/a
---cust here
The backhand pertinant part of my httpd.conf looks thusly:
---cut here
LoadModule backhand_module /usr/lib/apache/1.3/mod_backhand.so
AddModule mod_backhand.c
UnixSocketDir /var/run/libapache-mod-backhand
MulticastStats 192.168.2.1:4445
AcceptStats 192.168.2.0/24
<Location "/backhand/">
SetHandler backhand-handler
</Location>
---cut here
When things are normally working, a ps aux shows apache processes along
these lines:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
www-data 8129 0.0 1.2 3360 1628 ? S 13:19 0:00 /usr/sbin/apache
I have noticed that on occasion these processes jump up in their RSS size
all the way up to 32 megabytes occasionally. I think that this is somehow
related but I am not sure. (To be honest, I suspected that its a memory
leak caused when the umbilical is lost.)
Oh, one other thing. I am unable to reproduce this at will, though it
happens frequently enough (anywhere from semidaily to bidaily) that I can
look into things while it's not working. When I stress test the site, it works
fine, so the umbilical loss seems to not be related to load.
General stats for the site:
---cut here
- Average page build on the backend machine is .60 seconds
- Usual page size (including images) around 80k
- Frontend server is a Athlon 500 w/ 128 megs of ram
- Frontend server has 128 megs of ram.
- Site gets approximately 1500 page views a day
---cut here
--
GnuPG fingerprint AAE4 8C76 58DA 5902 761D 247A 8A55 DA73 0635 7400
James Blackwell -- Director http://www.linuxguru.net