1# OTBR Docker 2 3This file contains troubleshooting for common issues with OTBR Docker. 4 5## rsyslog cannot start 6 7If `rsyslog` cannot start successfully (there is no response) during the OTBR Docker image booting-up: 8 9``` 10+ sudo service rsyslog status 11 * rsyslogd is not running 12+ sudo service rsyslog start 13 * Starting enhanced syslogd rsyslogd 14``` 15 16This is caused by the high limit number of file descriptors (`LimitNOFILE`). `rsyslog` takes a long time to run a for loop to close all open file descriptors when this limit is high (for example, `1073741816`). 17 18To solve this issue, add the following configuration to `/etc/docker/daemon.json`: 19 20``` 21 "default-ulimits": { 22 "nofile": { 23 "Name": "nofile", 24 "Hard": 1024, 25 "Soft": 1024 26 }, 27 "nproc": { 28 "Name": "nproc", 29 "Soft": 65536, 30 "Hard": 65536 31 } 32 } 33``` 34 35And then reload & restart the `docker` service: 36 37``` 38sudo systemctl daemon-reload 39sudo systemctl restart docker 40``` 41