https://help.openclovis.com/index.php?action=history&feed=atom&title=AmsDbXMLPrint_timeout 2026-06-15T02:01:57Z Revision history for this page on the wiki MediaWiki 1.20.2 https://help.openclovis.com/index.php?title=AmsDbXMLPrint_timeout&diff=24176&oldid=prev 2013-03-28T16:10:31Z

<p>safplus_console amsdbxmlprint timeout, safplus_info forest timeout</p> <p><b>New page</b></p><div>==Symptom Statement==<br /> <br /> *The safplus_console command &quot;amsdbxmlprint console&quot; can hang.<br /> *The safplus_info command &quot;forest&quot; times out.<br /> <br /> ==Diagnosis==<br /> <br /> These commands can timeout if the rmem_default/max buffer in the kernel gets exceeded which results in packet drops. This will happen with a large model since the amsdbxmlprint command dumps the entire cluster configuration as XML data. If the &quot;console&quot; modifier is removed, the command should work since it dumps into file on the controller.<br /> The default rmem_default/max is around 128k.<br /> <br /> ==Solution==<br /> <br /> <br /> Increase the rmem defaults through a proc write:<br /> &lt;code&gt;&lt;pre&gt;<br /> echo 10000000 &gt; /proc/sys/net/core/rmem_default<br /> echo 10000000 &gt; /proc/sys/net/core/rmem_max<br /> &lt;/pre&gt;&lt;/code&gt;<br /> &lt;br&gt;<br /> Now try the amsdbxmlprint console command and see it work. Of course, the cluster has to be up with SAFplus running.<br /> &lt;br&gt;<br /> Make it persistent across reboots with a /etc/sysctl.conf entry:<br /> &lt;code&gt;&lt;pre&gt;<br /> net.core.rmem_default = 10000000<br /> net.core.rmem_max = 10000000<br /> &lt;/pre&gt;&lt;/code&gt;</div>

Stone