Hi,
(I posted this on -net but no response, and some more info added...)
I am maintaining two large-volume HTTP server. It is with one em0
gigabit NIC, and running apache(or thttpd) for users to download
relatively big(>200k) files.
I started this service using 4.5R. The server is Pentium III 1G, 1G
RAM, 36G SCSI HDD). Server load was very high(>50) but I heard it's
characteristic of apache server and I decided to upgrade to recent
system and use thttpd instead of apache. When I tried to use thttpd,
it shows the load under 1(wow!).
2 days ago I updated the system to 4.6-RELEASE. Whether or not using
apache or thttpd, under some traffic(about >200Mbit/sec), it shows
"watchdog timeout" repeatedly:
Jun 16 11:36:18 gigatest /kernel: em0: Link is Down
Jun 16 11:36:18 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex
Jun 16 11:40:49 gigatest /kernel: em0: watchdog timeout -- resetting
Jun 16 11:40:51 gigatest /kernel: em0: Link is Down
Jun 16 11:40:51 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex
Jun 16 11:40:51 gigatest /kernel: em0: Link is Down
Jun 16 11:40:51 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex
Jun 16 11:44:23 gigatest /kernel: em0: watchdog timeout -- resetting
Jun 16 11:44:24 gigatest /kernel: em0: Link is Down
Jun 16 11:44:24 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex
Jun 16 11:50:28 gigatest /kernel: em0: watchdog timeout -- resetting
Jun 16 11:50:29 gigatest /kernel: em0: Link is Down
Jun 16 11:50:29 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex
Jun 16 11:50:30 gigatest /kernel: em0: Link is Down
Jun 16 11:50:30 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex
Jun 16 11:50:30 gigatest /kernel: em0: Link is Down
Jun 16 11:50:30 gigatest /kernel: em0: Link is up 1000 Mbps FullDuplex
Jun 16 11:50:30 gigatest /kernel: em0: Link is Down
Jun 16 11:50:30 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex
I updated em0 driver to 1.3.8 from Intel webpage, but it no helps.
After that day, I downgraded the system to 4.5R-p6. It still has a
problem.
Here is my sysctl.conf:
kern.ipc.maxsockbuf=20480000
kern.ipc.somaxconn=8192
kern.ipc.maxsockets=60000
kern.maxfiles=65536
kern.maxfilesperproc=32768
net.inet.tcp.rfc1323=1
net.inet.tcp.delayed_ack=0
net.inet.tcp.sendspace=65536
net.inet.tcp.recvspace=16384
net.inet.udp.recvspace=16384
net.inet.udp.maxdgram=57344
net.local.stream.recvspace=65536
net.local.stream.recvspace=65536
net.local.stream.sendspace=65536
net.inet.tcp.msl=1000
net.inet.icmp.drop_redirect=1
net.inet.icmp.log_redirect=1
net.inet.ip.redirect=0
net.inet6.ip6.redirect=0
net.link.ether.inet.max_age=1200
net.inet.ip.sourceroute=0
net.inet.ip.accept_sourceroute=0
net.inet.icmp.bmcastecho=0
net.inet.icmp.maskrepl=0
and /boot/loader.conf.local:
kern.ipc.nmbclusters="131072"
accf_http_load="YES
--
+++ Any opinions in this posting are my own and not those of my employers +++
CHOI Junho [sleeping now] <http://www.kr.FreeBSD.org/~cjh>
[while sleeping] <cjh @ kr.FreeBSD.ORG> <cjh @ FreeBSD.ORG> <cjh @ wdb.co.kr>
Korea FreeBSD Users Group <www.kr.FreeBSD.org> Web Data Bank<www.wdb.co.kr>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message