# How to resolve the warning message?
**URL:** https://meta.discourse.org/t/how-to-resolve-the-warning-message/36048
**Category:** Self-hosting
**Created:** [11월 26, 2015, 10:02오전 UTC](https://meta.discourse.org/t/how-to-resolve-the-warning-message/36048 "2015-11-26T10:02:28Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@doudou](https://meta.discourse.org/u/doudou)
#### Post date: [11월 26, 2015, 10:02오전 UTC](https://meta.discourse.org/t/how-to-resolve-the-warning-message/36048/1 "2015-11-26T10:02:28Z")
The ./launcher logs app shows warnings:
1. 42:M 26 Nov 09:22:44.646 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
2. rsyslogd: invalid or yet-unknown config file command ‘KLogPermitNonKernelFacility’ - have you forgotten to load a module? [try [http://www.rsyslog.com/e/3003](http://www.rsyslog.com/e/3003) ]
rsyslogd: warning: ~ action is deprecated, consider using the ‘stop’ statement instead [try [http://www.rsyslog.com/e/2307](http://www.rsyslog.com/e/2307) ]
rsyslogd: Could no open output pipe ‘/dev/xconsole’: No such file or directory [try [http://www.rsyslog.com/e/2039](http://www.rsyslog.com/e/2039) ]
Server listening on 0.0.0.0 port 22.
3. nginx: [warn] invalid parameter “spdy”: ngx\_http\_spdy\_module was superseded by ngx\_http\_v2\_module in /etc/nginx/conf.d/discourse.conf:38
nginx: [warn] invalid directive “spdy\_keepalive\_timeout”: ngx\_http\_spdy\_module was superseded by ngx\_http\_v2\_module in /etc/nginx/conf.d/discourse.conf:39
nginx: [warn] invalid directive “spdy\_headers\_comp”: ngx\_http\_spdy\_module was superseded by ngx\_http\_v2\_module in /etc/nginx/conf.d/discourse.conf:55
4. fail: nginx: runsv not running
5. fail: unicorn: runsv not running
6. fail: redis: runsv not running
7. fail: postgres: runsv not running
8. fail: sshd: runsv not running
### Warning 1: I have add net.core.somaxconn = 1024 to /etc/sysctl.conf
and cat /proc/sys/net/core/somaxconn is 1024, even after reboot the value is 1024
but after ./launcher rebuild app, logs still shows this warning.
### rsyslogd warning, what does that mean?
### nginx spdy warning, why?
Thanks.
---
### Author:  [@doudou](https://meta.discourse.org/u/doudou)
#### Post date: [11월 26, 2015, 11:58오전 UTC](https://meta.discourse.org/t/how-to-resolve-the-warning-message/36048/2 "2015-11-26T11:58:56Z")
Maybe docker can’t read host’s configure setting. The redis server in the docker may be related to this.
When you ./launcher enter app into the container, the somaxconn is still not changed.
`cat /proc/sys/net/core/somaxconn`
the value is 128.
How to change the value in the container ?
Or the container can read hosts’ /proc/sys settings?
#### PS.
I mount container’s /proc in a writable directory, so we can edit the kernel value from 128 to 1024 or higher. But when rebuild docker or reboot the host system, the somaxconn was reset to 128. Problem reoccurs.
> Maybe it is the docker’s problem.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [11월 12, 2018, 11:03오전 UTC](https://meta.discourse.org/t/how-to-resolve-the-warning-message/36048/3 "2018-11-12T11:03:25Z")
A post was merged into an existing topic: [How do you set net.core.somaxconn in the docker container?](https://meta.discourse.org/t/how-do-you-set-net-core-somaxconn-in-the-docker-container/64577/6)