web12

Well-Known Member
Nov 20, 2002
240
0
166
Hi,

I know this problem has been well talked about here on these very forums, but mine seems to be slightly more frequent than everyone elses... Here is a c & p of my error_log just to show you how often it actually is.

[Thu Jan 30 11:24:44 2003] [notice] SIGUSR1 received. Doing graceful restart
[Thu Jan 30 11:24:44 2003] [notice] Apache/1.3.27 (Unix) DAV/1.0.3 mod_log_bytes/0.3 mod_bwlimited/1.0 PHP/4.2.3 FrontPage/5.0.2.25$
[Thu Jan 30 11:24:44 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Thu Jan 30 11:24:44 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Thu Jan 30 11:24:46 2003] [notice] SIGUSR1 received. Doing graceful restart
[Thu Jan 30 11:24:47 2003] [notice] Apache/1.3.27 (Unix) DAV/1.0.3 mod_log_bytes/0.3 mod_bwlimited/1.0 PHP/4.2.3 FrontPage/5.0.2.25$
[Thu Jan 30 11:24:47 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Thu Jan 30 11:24:47 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Thu Jan 30 11:24:50 2003] [notice] SIGUSR1 received. Doing graceful restart
[Thu Jan 30 11:24:50 2003] [notice] Apache/1.3.27 (Unix) DAV/1.0.3 mod_log_bytes/0.3 mod_bwlimited/1.0 PHP/4.2.3 FrontPage/5.0.2.25$
[Thu Jan 30 11:24:50 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Thu Jan 30 11:24:50 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)


Surely this cant be right can it? Everything appears to be working correctly, but as you can imagine, my log is getting filled very quickly.

Any ideas?
 

ciphervendor

Well-Known Member
Aug 26, 2002
1,052
0
166
That really isn't normal. Check to make sure Apache isn't getting pounded with traffic, you may also want to verify the integrity of your hard disk(s) and/or RAM.

If everything comes back okay, try recompiling Apache.
 

web12

Well-Known Member
Nov 20, 2002
240
0
166
Hi ciphervendor,

Thanks for the reply.

This problem doesnt seem to be particular to a time of day, it seems to always do it. Checking traffic, it doesnt seem to be exceptionally high either.

Apache was re-compiled only a few days ago due to a problem i was having with FD_SETSIZE. So it was compiled with a higher setting.

IS there a way to verify integrity on RAM and HDD? I checked in PHPSysinfo and the physical memory is continously high, like around 90-99% (in the red).

Anything I could try?
 

ciphervendor

Well-Known Member
Aug 26, 2002
1,052
0
166
Check dmesg to see if your system has reported any disk or ram errors.

Was Apache recompiled with buildapache?
 

web12

Well-Known Member
Nov 20, 2002
240
0
166
Hi Again,

/var/log/dmesg seems to be fine, I cant see anything out of the ordinary in there... No reports of failures or bad sectors or anything.

I am unsure if Apcahe was recompiled with buildapache or not, as it was done by the DC.
 

ciphervendor

Well-Known Member
Aug 26, 2002
1,052
0
166
/var/log/dmesg won't show any errors, execute /bin/dmesg

If your DC did it, they probably recompiled from source (if they don't know cpanel). I would ask them to find out exactly what they did.

Edit: run /bin/dmesg was a poor choice of words. Edited.
 

web12

Well-Known Member
Nov 20, 2002
240
0
166
Here is a C & P of it... I'm still learning this stuff so I am trying my best to understand each part of it....

Linux version 2.4.19 ([email protected]) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 Fri Nov 15 13:01:19 EST 2002
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001dff0000 (usable)
BIOS-e820: 000000001dff0000 - 000000001dff3000 (ACPI NVS)
BIOS-e820: 000000001dff3000 - 000000001e000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
479MB LOWMEM available.
On node 0 totalpages: 122864
zone(0): 4096 pages.
zone(1): 118768 pages.
zone(2): 0 pages.
Kernel command line: auto BOOT_IMAGE=linux ro root=301 BOOT_FILE=/boot/vmlinuz
Initializing CPU#0
Detected 1693.139 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 3381.65 BogoMIPS
Memory: 483376k/491456k available (1142k kernel code, 7696k reserved, 464k data, 92k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: Before vendor init, caps: 3febfbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 12K, L1 D cache: 8K
CPU: L2 cache: 256K
CPU: After vendor init, caps: 3febfbff 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
CPU: Common caps: 3febfbff 00000000 00000000 00000000
CPU: Intel(R) Pentium(R) 4 CPU 1.70GHz stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfb450, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router default [1039/0650] at 00:00.0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Journalled Block Device driver loaded
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SIS5513: IDE controller on PCI bus 00 dev 15
SIS5513: detected chipset, but driver not compiled in!
SIS5513: chipset revision 208
SIS5513: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x4000-0x4007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x4008-0x400f, BIOS settings: hdc:DMA, hdd:pio
keyboard: Timeout - AT keyboard not present?(ed)
keyboard: Timeout - AT keyboard not present?(f4)
hda: ST360021A, ATA DISK drive
hdc: ST360021A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63
hdc: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=116301/16/63
Partition check:
hda: hda1 hda2 hda3 hda4 & hda5 hda6 &
hdc: unknown partition table
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
(recovery.c, 252): journal_recover: JBD: recovery, exit status 0, recovered transactions 221990 to 222604
(recovery.c, 255): journal_recover: JBD: Replayed 4525 and revoked 0/0 blocks
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 92k freed
Adding Swap: 522072k swap-space (priority -1)
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide0(3,1), internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide0(3,3), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide0(3,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide0(3,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
8139too Fast Ethernet driver 0.9.25
eth0: RealTek RTL8139 Fast Ethernet at 0xde848000, 00:10:dc:a6:8f:f6, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139B'
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
ip_tables: (C) 2000-2002 Netfilter core team
hdc: hdc1
hdc: hdc1
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide1(22,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { DriveStatusError }
TCP: drop open request from 217.35.154.18/2384
TCP: drop open request from 217.35.154.18/2385
TCP: drop open request from 217.35.154.18/2386
TCP: drop open request from 217.35.154.18/2387
TCP: drop open request from 217.35.154.18/2388
TCP: drop open request from 217.35.154.18/2389
TCP: drop open request from 217.35.154.18/2390
TCP: drop open request from 217.35.154.18/2391
TCP: drop open request from 217.35.154.18/2392
TCP: drop open request from 217.35.154.18/2393
NET: 613 messages suppressed.
UDP: bad checksum. From 213.183.17.11:4738 to 66.246.28.169:1434 ulen 384
TCP: Treason uncloaked! Peer 216.176.37.84:1779/80 shrinks window 1215777184:1215778208. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1779/80 shrinks window 1215777184:1215778208. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1779/80 shrinks window 1215777184:1215778208. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1779/80 shrinks window 1215777184:1215778208. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1793/80 shrinks window 1325712398:1325713422. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1793/80 shrinks window 1325712398:1325713422. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1793/80 shrinks window 1325712398:1325713422. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1793/80 shrinks window 1325712398:1325713422. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1798/80 shrinks window 1355491176:1355492200. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1798/80 shrinks window 1355491176:1355492200. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.84:1798/80 shrinks window 1355491176:1355492200. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.24:4322/80 shrinks window 3074101862:3074102886. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.24:4322/80 shrinks window 3074101862:3074102886. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.24:4322/80 shrinks window 3074101862:3074102886. Repaired.
TCP: Treason uncloaked! Peer 216.176.37.24:4322/80 shrinks window 3074101862:3074102886. Repaired.
TCP: Treason uncloaked! Peer 165.106.209.166:3065/80 shrinks window 511557813:511563653. Repaired.
TCP: Treason uncloaked! Peer 165.106.209.166:3065/80 shrinks window 511557813:511563653. Repaired.
TCP: Treason uncloaked! Peer 165.106.209.166:3065/80 shrinks window 511557813:511563653. Repaired.
211.172.208.13 sent an invalid ICMP error to a broadcast.
211.172.208.5 sent an invalid ICMP error to a broadcast.
211.172.208.17 sent an invalid ICMP error to a broadcast.
UDP: bad checksum. From 200.207.217.200:59111 to 66.246.37.183:80 ulen 11
212.68.201.197 sent an invalid ICMP error to a broadcast.
62.2.180.2 sent an invalid ICMP error to a broadcast.
212.68.201.69 sent an invalid ICMP error to a broadcast.
 

Website Rob

Well-Known Member
Mar 23, 2002
1,504
1
318
Alberta, Canada
cPanel Access Level
Root Administrator
Please advise as to how one would &run& the scripts listed within /bin
Thanks
 

ciphervendor

Well-Known Member
Aug 26, 2002
1,052
0
166
Everything looks fine, this line NET: 613 messages suppressed.
is a little much, like a mini attack or something.

Did you get a hold of your data center about how they compiled apache?
 

web12

Well-Known Member
Nov 20, 2002
240
0
166
Hi,

I have just had word back from the DC that Apache would have been compiled from source.

Does that help in any way?
 

ciphervendor

Well-Known Member
Aug 26, 2002
1,052
0
166
buildapache should always be used on a cpanel box. They may have broken something which is causing the issues you are currently experiencing.
 

tAzMaNiAc

Well-Known Member
Feb 16, 2003
559
0
166
Sachse, TX
I have the same prob, i notice it all the time in logs but things run ok. It's just annoying and i wonder how to fix it, really..
 

rastoma

Well-Known Member
Aug 27, 2001
158
0
316
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { DriveStatusError }



i get that too on a few of my machines but there are no apparant problems happening. what is causing that?
 

Danks

Active Member
Oct 10, 2001
26
1
303
one of my customers had the same problem. It turned out to be cpanellogd causing the problem. Once I killed cpanellogd the error never returned.