# Enable core dumps for booster crashes

## For Debian

<p class="callout danger">It is important that you undo this after the issue has been identified.</p>

## Step-by-step guide

1. edit this file:  
    `<strong>sudo vi /usr/local/etc/filewave/supervisor/supervisord-booster.conf</strong>`
2. Uncomment this line:  
    `<strong>command=/bin/bash -c "ulimit -c unlimited && /usr/local/sbin/fwbooster</strong>`
3. restart the booster:
    
    `<strong>sudo /etc/init.d/fw-booster restart</strong>`
4. edit this file:
    
    `<strong>sudo vi /etc/sysctl.conf</strong>`
5. Add the lines below:
    
    `<strong>kernel.core_uses_pid = 1</strong>`
    
    `<strong>kernel.core_pattern = /tmp/core-%e-%s-%u-%g-%p-%t</strong>`
    
    `<strong>fs.suid_dumpable = 2</strong>`
6. Reload the settings in /etc/sysctl.conf:
    
    `sysctl -p`
7. **Open the limits configuration file:  
    `sudo vi /etc/security/limits.conf`**
8. **Add the following lines** to set unlimited core dump sizes for all users:
    
    `* soft core unlimited`
    
    `* hard core unlimited`
9. **Save and close** the file. **Note**: Changes take effect upon the next login. You may need to restart the system or re-login for the settings to apply.

<p class="callout info">For testing purpose:  
Kill booster process e.g:  
(ps ax | grep fw)  
`kill -6 3014`  
  
Check if a core dump is generated under /tmp.  
Should be something like this:  
core-fwbooster-6-0-0-8440-1509016449</p>