eth0: can't fill rx buffer (force 0)! 에러입니다.
서버 a 에서 서버 b로 ftp4개를 띄워서 1g정도 파일4개를 b로 보냈습니다.
보내는중 b에서 cksum ~ 작업을 하니 딱 멈추더군요..
네트워크 연결은 안되구요..
직접가서 로그보니
Apr 21 07:52:08 data kernel: eth0: can't fill rx buffer (force 0)!
Apr 21 07:53:06 data kernel: 0.
Apr 21 07:53:07 data kernel: eth0: can't fill rx buffer (force 1)!
Apr 21 07:53:08 data last message repeated 8 times
Apr 21 08:01:49 data kernel: eepro100: wait_for_cmd_done timeout!
Apr 21 08:01:59 data last message repeated 6 times
Apr 21 08:19:03 data sshd(pam_unix)[5279]: session closed for user jinwan
Apr 21 08:19:03 data su(pam_unix)[5316]: session closed for user root
Apr 21 08:52:27 data proftpd[5363]: data.aaa.co.kr (10.0.0.183[10.0.0.183]) - Data transfer stall timeout: 3600 seconds
Apr 21 08:52:27 data kernel: eepro100: wait_for_cmd_done timeout!
Apr 21 08:52:27 data kernel: eepro100: wait_for_cmd_done timeout!
Apr 21 08:52:27 data proftpd[5366]: data.aaa.co.kr (10.0.0.183[10.0.0.183]) - Data transfer stall timeout: 3600 seconds
Apr 21 08:52:27 data kernel: eepro100: wait_for_cmd_done timeout!
Apr 21 08:52:27 data kernel: eepro100: wait_for_cmd_done timeout!
Apr 21 08:52:27 data proftpd[5364]: data.aaa.co.kr (10.0.0.183[10.0.0.183]) - Data transfer stall timeout: 3600 seconds
Apr 21 08:52:27 data kernel: eepro100: wait_for_cmd_done timeout!
Apr 21 08:52:27 data kernel: eepro100: wait_for_cmd_done timeout!
Apr 21 08:52:27 data proftpd[5268]: data.aaa.co.kr (10.0.0.183[10.0.0.183]) - Data transfer stall timeout: 3600 seconds
Apr 21 08:52:27 data kernel: eepro100: wait_for_cmd_done timeout!
Apr 21 08:52:37 data last message repeated 15 times
장애서버에서 ping같은 외부로 테스트 하니 연결은 안되고
wait_for_cmd_done timeout! 에러가 떳습니다.
그리고 /etc/rc.d/init.d/network restart하니 제대로 네트워크가 살았구요.
eth0이나 eepro100 보니 네트워크 관련 버퍼에러같은데요..어떤원인이 있을까요?
사양은 p3 700 * 2 1G mem입니다.
Do you see "can't fill rx buffer" messag
Do you see "can't fill rx buffer" messages?
If so, then your load is too big, and memory management is incapable of
freeing memory in time.
Right now the kernel doesn't allow to increase atomic allocation
reservation (which is a serious misfeature), so you need to hack and
change the reservation in the kernel.
If the network doesn't come alive when you remove the load, it's a second
problem, a bug in the driver. I've seen such reports, but they aren't
frequent. On my computer, the driver resumes operations well.
Why the driver can't do it for some people needs deep investigations.
이거군요.. 순간적인 메모리 부족.. 그런데 ftp를 끊었는데도 네트워크가 안살아났다면.. 드라이버 버그라네요..-_-;;;;
댓글 달기