Skip to content

Deployment hacks

Jump to bottom Edit New page
willyaranda edited this page Sep 17, 2012 · 2 revisions

  1. RabbitMQ disk space nodes must be monitored. If the disk space falls below a certain level (10%?), it stops answering petitions, thus stopping the service. Also if it reaches a high use of RAM memory.

  2. Ulimit for files should be really high for WS, since websockets use unix sockets in node, which are file descriptors. Keep in mind that might be necessary to format ext disks with a high number of inodes.

  3. Debug files go to /var/log/push_server. If it's set to "debug" will be A LOT of debug. Keep in mind that node crashes if there is no free space.

  4. IPtables, be aware that there can be some problems with not reaching ports because they are blocked.

Add a custom footer
Add a custom sidebar
Clone this wiki locally