Redhat5系统启动服务说明
2010-12-08 17:36
281 查看
ip_conntrack: table full, dropping packet
Last week, I found myself with a server under low load, but it couldn't make or receive network connections. When I ran
ip_conntrack: table full, dropping packet
I'd seen this message before, but I headed over to Red Hat's site for more details. It turns out that the server was running iptables, but it was under a very heavy load and also handling a high volume of network connections. Generally, the ip_conntrack_max is set to the total MB of RAM installed multiplied by 16. However, this server had 4GB of RAM, but ip_conntrack_max was set to 65536:
# cat /proc/sys/net/ipv4/ip_conntrack_max
65536
I logged into another server with 1GB of RAM (RHES 5, 32-bit) and another with 2GB of RAM (RHES 4, 64-bit), and both had ip_conntrack_max set to 65536. I'm not sure if this is a known Red Hat issue, or if it's just set to a standard value out of the box.
If you want to check your server's current tracked connections, just run the following:
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_count
If you want to adjust it (as I did), just run the following as root:
# echo 131072 > /proc/sys/net/ipv4/ip_conntrack_max本文出自 “让爱走吧~!” 博客,请务必保留此出处http://ylj798.blog.51cto.com/110701/1061936
Last week, I found myself with a server under low load, but it couldn't make or receive network connections. When I ran
dmesg, I found the following line repeating over and over:
ip_conntrack: table full, dropping packet
I'd seen this message before, but I headed over to Red Hat's site for more details. It turns out that the server was running iptables, but it was under a very heavy load and also handling a high volume of network connections. Generally, the ip_conntrack_max is set to the total MB of RAM installed multiplied by 16. However, this server had 4GB of RAM, but ip_conntrack_max was set to 65536:
# cat /proc/sys/net/ipv4/ip_conntrack_max
65536
I logged into another server with 1GB of RAM (RHES 5, 32-bit) and another with 2GB of RAM (RHES 4, 64-bit), and both had ip_conntrack_max set to 65536. I'm not sure if this is a known Red Hat issue, or if it's just set to a standard value out of the box.
If you want to check your server's current tracked connections, just run the following:
# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_count
If you want to adjust it (as I did), just run the following as root:
# echo 131072 > /proc/sys/net/ipv4/ip_conntrack_max本文出自 “让爱走吧~!” 博客,请务必保留此出处http://ylj798.blog.51cto.com/110701/1061936
相关文章推荐
- 关闭redhat系统启动进度条,显示服务启动信息
- redhat设置系统启动/关机过程中处理自动启动服务命令
- redhat和ubuntu下的系统运行级别,服务的启动
- Windows服务 示例简要说明(系统事件日志、运行批处理、安装卸载、启动调试)
- 【windows】将程序启动加载到系统服务
- 在系统启动时至少有一个服务或驱动程序产生错误,详细信息,请使用事件查看器查看事件日志
- 系统启动流程及GRUB文件说明
- 将解压版的Tomcat作为系统服务启动
- Android系统在新进程中启动自定义服务过程(startService)的原理分析
- 在系统启动时至少有一个服务或驱动程序产生错误。详细信息,请使用事件查看器查看事件日志
- CentOs7 安装Tengine 并设置成系统服务,开机自动启动。
- 修改系统服务的启动类型并启动服务
- 笔记:Windows XP 启动过程概述 剖析Linux系统启动过程--redhat
- tomcat6.0.24怎么设置成系统自启动服务和定时启动关闭
- windows系统下将nginx作为系统服务启动
- windows xp 安装xmanager连接linux redhat系统通过Telnet服务并安装oracle10g
- android系统服务启动分析-binder
- CentOS7 下配置Keepalived为系统服务,开机自动启动。
- centos 下 apache启动脚本加入系统服务列表
- centos7用shell创建守护进程,并设置为系统服务,开机自动启动