net_ratelimit: 102 callbacks suppressed 로그와 arp failure 로그
방화벽으로 사용중인 장비에서 아래의 내용으로 시스템 메시지를 계속 뿌려주고 있습니다.
찾아보니 net_ratelimit은 동일한 로그가 임계치 이상 들어오면 제한하는 기능으로 되어있더군요.
아마 May 16 10:14:35 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure이 로그가
동시에 여러개 발생해서 생기는 로그로 보입니다.
근데 user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure 의 의미가 무엇인지 아무리 찾아봐도 정보가 없습니다.
skb 라는걸 찾아보니 프로토콜 구분을 빨리 하기 위한 소켓 분류 모듈(?) 같은 거 같던데요.
일반적인 로그는 아닌 것 같고 특정한 경우에 발생하는 로그로 보입니다.
혹시 짐작가시는 부분이 있다면 도움 부탁드리겠습니다.
방화벽 자체에서 쉘모드 접속이 안되게 막아놓아서 확인 할 수 있는 방법이 없습니다 ㅠ
May 16 10:14:35 (none) user.warn kernel: net_ratelimit: 102 callbacks suppressed
May 16 10:14:35 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:36 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:36 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:36 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:36 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:36 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:36 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:36 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:36 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:36 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.warn kernel: net_ratelimit: 118 callbacks suppressed
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
May 16 10:14:42 (none) user.err kernel: outdev_skb_destructor: it should be called only in case of skb purging on arp failure
댓글 달기