# Lots of warnings about rsyslogd, locks up discourse
**URL:** https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311
**Category:** Self-hosting
**Created:** [5 mei 2014 om 03:01 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311 "2014-05-05T03:01:43Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@shadowhand](https://meta.discourse.org/u/shadowhand)
#### Post date: [5 mei 2014 om 03:01 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/1 "2014-05-05T03:01:43Z")
I just installed Discourse on a Rackspace server, using the same general instructions as for Digital Ocean. No issues with the install, everything works great **until** I restart the server, at which point this starts appearing in my logs and eventually crashes the server completely, requiring a hard reboot to restore it.
```
rsyslogd: WARNING: rsyslogd is running in compatibility mode. Automatically generated config directives may interfer with your rsyslog.conf settings. We suggest upgrading your config and adding -c5 as the first rsyslogd option.
Pidfile (and pid) already exist.
```
I have no idea where to start with this issue… help?
---
### Author:  [@shadowhand](https://meta.discourse.org/u/shadowhand)
#### Post date: [5 mei 2014 om 03:02 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/2 "2014-05-05T03:02:11Z")
Ah, I just noticed that the install instructions recommend Ubuntu 14, not 12. I will try upgrading the host OS to latest and report back.
---
### Author:  [@shadowhand](https://meta.discourse.org/u/shadowhand)
#### Post date: [5 mei 2014 om 03:38 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/3 "2014-05-05T03:38:42Z")
No luck with Ubuntu 14, still getting the same errors after using `./launcher restart app`:
```plaintext
2014-05-05 03:36:50 UTC LOG: database system is ready to accept connections
supervisor pid: 39 unicorn pid: 47
rsyslogd: WARNING: rsyslogd is running in compatibility mode. Automatically generated config directives may interfer with your rsyslog.conf settings. We suggest upgrading your config and adding -c5 as the first rsyslogd option.
Pidfile (and pid) already exist.
config/unicorn_launcher: line 36: kill: (47) - No such process
config/unicorn_launcher: line 10: kill: (47) - No such process
exiting
ok: run: redis: (pid 14) 1s
ok: run: postgres: (pid 16) 1s
ok: run: copy_env: (pid 18) 1s
supervisor pid: 55 unicorn pid: 57
rsyslogd: WARNING: rsyslogd is running in compatibility mode. Automatically generated config directives may interfer with your rsyslog.conf settings. We suggest upgrading your config and adding -c5 as the first rsyslogd option.
Pidfile (and pid) already exist.
```
These last two lines repeat every second until I restart the host server. Weirdly, it **only** throws warnings when the app is restarted, not on the first run.
EDIT: actually that last statement seems to be wrong. After rebooting the host, `start app` also shows the same errors in logs. I’ll try to use the app and see if it hard locks the machine again.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5 mei 2014 om 06:32 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/4 "2014-05-05T06:32:27Z")
What is the output of `docker info` and `docker version`?
---
### Author:  [@shadowhand](https://meta.discourse.org/u/shadowhand)
#### Post date: [5 mei 2014 om 15:37 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/5 "2014-05-05T15:37:17Z")
as requested
```plaintext
% docker info
Containers: 2
Images: 11
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Dirs: 15
Execution Driver: native-0.1
Kernel Version: 3.13.0-24-generic
WARNING: No swap limit support
```
and
```plaintext
% docker version
Client version: 0.10.0
Client API version: 1.10
Go version (client): go1.2.1
Git commit (client): dc9c28f
Server version: 0.10.0
Server API version: 1.10
Git commit (server): dc9c28f
Go version (server): go1.2.1
Last stable version: 0.10.0
```
the app has now been running for about 12 hours, and the logs are piling up, but still working.
```plaintext
% ./launcher logs app | grep rsyslogd | wc -l
WARNING: No swap limit support
42956
```
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [6 mei 2014 om 04:23 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/6 "2014-05-06T04:23:05Z")
OK, I’m getting the same thing. Looks like the PID files aren’t getting cleaned up on container startup:
```
root@dhost:~# cat /var/run/rsyslogd.pid
23
root@dhost:~# ps -p 23
PID TTY TIME CMD
23 ? 00:00:00 nginx
```
We should clean up pid files, etc. on startup. Looking into it.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [6 mei 2014 om 04:25 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/7 "2014-05-06T04:25:51Z")
What are we using rsyslogd for btw?
Also, I feel our logging story for nginx/pg/cron/ssh should be much improved, for one we are throwing away all logs on container rebuild. Perhaps we should shift /var/logs out of the container?
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [6 mei 2014 om 05:42 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/8 "2014-05-06T05:42:08Z")
> [@sam](#):
>
> What are we using rsyslogd for btw?
nginx logs, redis logs, general daemon logs.
> [@sam](#):
>
> Perhaps we should shift /var/logs out of the container?
Totally agree! Unfortunately, blocked by:
[https://github.com/dotcloud/docker/issues/5489](https://github.com/dotcloud/docker/issues/5489)
Here’s a preview of THE FUTURE:
[https://github.com/Supermathie/discourse\_docker/commit/9ccd3738cc913a995309a82744e9af0978719970](https://github.com/Supermathie/discourse_docker/commit/9ccd3738cc913a995309a82744e9af0978719970)
It’ll let us safely clean up some stale state from the container before firing everything up.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [7 oktober 2014 om 07:10 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/9 "2014-10-07T07:10:57Z")
Was this resolved? Can this be closed?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [7 oktober 2014 om 08:31 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/10 "2014-10-07T08:31:44Z")
Yeah, this should be fine
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [7 oktober 2014 om 08:31 UTC](https://meta.discourse.org/t/lots-of-warnings-about-rsyslogd-locks-up-discourse/15311/11 "2014-10-07T08:31:47Z")