https://www.ejabberd.im/node/609 en https://www.ejabberd.im/node/609#comment-1319 <p>No error messages appear on the ejabberd server, I checked the ejabberd.log, sasl.log, and the server logs. All of the errors appeared on the Jab_simul server.</p> <p>I figured out that everytime the server crashed the ejabberd server, the jab_simul server had run out of disk space. I assumed this was unrelated, but setup a cron job to delete the tmp log files. This did make the error go away, and I was able to run a simulation for 70 hours this weekend with no errors. I had 500 users with a message frequency of 100 ms using 160MB of memory.</p> <p>I was able to recreate the error even with these settings by adding an additional 300 users, bringing me to 800 total. The job runs for 5 minutes, then I start getting Kolejka za dluga, pakiet anulowany! errors. Shortly after that I get POLLERR: Connection terminated and POLLERR: Connection refused errors. </p> <p>Checking my ejabberd server, my beam service has become a zombie process, and is still running, but refuses all connections. The memory usage on the server spiked and then came back down after the beam service crashed.</p> <p>If I dial the message frequency back to 500 ms with 800 users, it runs for at least 10 minutes, but I'm testing that as I type.</p> <p>I don't understand the interaction between ejabberd and jab_simul enough to understand why this is happening, but I am concerned that the POLLERR errors are causing my ejabberd server to crash. I was unable to find any metion of this problem, has anything like it occured before?</p> Mon, 30 Jan 2006 16:44:26 +0000 bbarnes comment 1319 at https://www.ejabberd.im https://www.ejabberd.im/node/609#comment-1312 <div class="quote-msg"> <div class="quote-author"><em>bbarnes</em> wrote:</div> <p>Hello,<br /> The test will run with no errors for about an hour with message frequency of 500 ms, then in the space of 5 minutes the memory usage will spike from 400MB to 2GB and the swap space usage will jump from 0MB to 1GB. Then all current connections are dumped and all further connections are refused. Even if I restart the ejabberd service I am unable to log in, and have to restart the server before I can connect again. </p></div> <p>I didn't have this problem when running my test, but I had less than 1 GB of RAM and my tests were more about connections than about routing messages.</p> <p>Do any suspicious error or warning messages appear on ejabberd.log or sasl.log?</p> Sun, 29 Jan 2006 16:48:51 +0000 mfoss comment 1312 at https://www.ejabberd.im