| View previous topic :: View next topic |
| Author |
Message |
imbezol
n00b
Joined: 29 Sep 2002
Posts: 37
Location: Alberta, Canada
|
 Posted: Mon May 02, 2005 1:33 am Post subject: Apache 1.3.33-r1 /server-status stats not counting |
 |
|
| Code: | Server Version: Apache
Server Built: Apr 19 2005 10:29:49
_________________________________________________________________
Current Time: Sunday, 01-May-2005 19:23:47 MDT
Restart Time: Sunday, 01-May-2005 18:58:48 MDT
Parent Server Generation: 0
Server uptime: 24 minutes 59 seconds
Total accesses: 0 - Total Traffic: 0 kB
CPU Usage: u0 s0 cu0 cs0
0 requests/sec - 0 B/second -
4 requests currently being processed, 2 idle servers
|
The rest of the stats, like what pages are being accessed, show up properly. The counters for accesses, traffic, and cpu usage are not increasing though.
Is this a bug with the new build? I didn't have this problem with 1.3.32 |
|
| Back to top |
|
 |
imbezol
n00b
Joined: 29 Sep 2002
Posts: 37
Location: Alberta, Canada
|
| Posted: Mon May 02, 2005 12:53 pm Post subject: |
|
|
| Is anyone else even seeing this problem? |
|
| Back to top |
|
|
imbezol
n00b
Joined: 29 Sep 2002
Posts: 37
Location: Alberta, Canada
|
| Posted: Mon May 02, 2005 7:37 pm Post subject: |
|
|
..some more interesting info..
| Code: | [Mon May 2 13:32:43 2005] [notice] Apache configured -- resuming normal operations
[Mon May 2 13:32:43 2005] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon May 2 13:32:43 2005] [notice] Accept mutex: sysvsem (Default: sysvsem)
No log handling enabled - turning on stderr logging
Cannot rename //var/lib/net-snmp/snmpapp.conf to //var/lib/net-snmp/snmpapp.0.conf
Cannot unlink //var/lib/net-snmp/snmpapp.conf
read_config_store open failure on //var/lib/net-snmp/snmpapp.conf
read_config_store open failure on //var/lib/net-snmp/snmpapp.conf
read_config_store open failure on //var/lib/net-snmp/snmpapp.conf
No log handling enabled - turning on stderr logging
Cannot rename //var/lib/net-snmp/snmpapp.conf to //var/lib/net-snmp/snmpapp.0.conf
Cannot unlink //var/lib/net-snmp/snmpapp.conf
read_config_store open failure on //var/lib/net-snmp/snmpapp.conf
read_config_store open failure on //var/lib/net-snmp/snmpapp.conf
read_config_store open failure on //var/lib/net-snmp/snmpapp.conf
No log handling enabled - turning on stderr logging
Cannot rename //var/lib/net-snmp/snmpapp.conf to //var/lib/net-snmp/snmpapp.0.conf
Cannot unlink //var/lib/net-snmp/snmpapp.conf
read_config_store open failure on //var/lib/net-snmp/snmpapp.conf
read_config_store open failure on //var/lib/net-snmp/snmpapp.conf
read_config_store open failure on //var/lib/net-snmp/snmpapp.conf
|
| Code: |
[Mon May 2 13:27:02 2005] [notice] child pid 14760 exit signal Aborted (6)
*** glibc detected *** corrupted double-linked list: 0x0954ee98 ***
*** glibc detected *** corrupted double-linked list: 0x0954ee98 ***
[Mon May 2 13:27:03 2005] [notice] child pid 9624 exit signal Aborted (6)
[Mon May 2 13:27:03 2005] [notice] child pid 5688 exit signal Aborted (6)
*** glibc detected *** corrupted double-linked list: 0x0954ee98 ***
[Mon May 2 13:27:04 2005] [notice] child pid 22947 exit signal Aborted (6)
*** glibc detected *** corrupted double-linked list: 0x0954ee98 ***
[Mon May 2 13:27:05 2005] [notice] child pid 18555 exit signal Aborted (6)
*** glibc detected *** corrupted double-linked list: 0x0954ee98 ***
[Mon May 2 13:27:06 2005] [notice] child pid 12701 exit signal Aborted (6)
*** glibc detected *** corrupted double-linked list: 0x0954ee98 ***
*** glibc detected *** corrupted double-linked list: 0x0954ed28 ***
|
..etc
I've recompiled apache. I use mod_log_sql for logging and recompiled that as well. Also, it is not logging to mysql any longer either. |
|
| Back to top |
|
|
fury
n00b
Joined: 01 May 2003
Posts: 34
Location: California
|
| Posted: Mon Jun 06, 2005 1:16 am Post subject: |
|
|
| imbezol wrote: |
I've recompiled apache. I use mod_log_sql for logging and recompiled that as well. Also, it is not logging to mysql any longer either. |
I'm having the same "corrupted double-linked list" problem also. I can't find a solution. |
|
| Back to top |
|
|
imbezol
n00b
Joined: 29 Sep 2002
Posts: 37
Location: Alberta, Canada
|
| Posted: Mon Jun 06, 2005 1:48 am Post subject: |
|
|
My MySQL table was full. I'd been running the logs into that same table for about 9 months and hit the 4 gig limit. That limit was imposed by MySQL, not my filesystem as it would have been with ext2 or ext3. You can get around it by initially creating your table with larger integers so that MySQL can access past that limit but of course hind-site is 20-20.
Hope that helps, though by your message I kind of get the idea that you're setting up mod_log_sql new and so your problem may differ. |
|
| Back to top |
|
|
|
Networking & Security
