Hot answers tagged logging
Here are your rules again: -A INPUT -s z.z.z.z/32 -j DROP -A INPUT -s y.y.y.y/32 -j DROP -A INPUT -s a.a.a.a/32 -j DROP -A INPUT -m limit --limit 5/min -j LOG --log-prefix "iptables denied: " --log-level 7 The first will will silently drop any packet matching it. As will the second and third. By the time you hit the "limit" rule, you have already ...
An amazing recipe is given in the nginx Dockerfile: # forward request and error logs to docker log collector RUN ln -sf /dev/stdout /var/log/nginx/access.log RUN ln -sf /dev/stderr /var/log/nginx/error.log Simply, the app can continue writing to it as a file, but as a result the lines will go to stdout & stderr!
I'd say that if the syslog messages about sessions opening and closing are getting through, then rsyslog is presumably doing its thing at both ends (but confirm it by sending to syslog on the gateway using logger). Also, the fact that the log file gets created on the gateway suggests that the log messages are being mishandled on the gateway, rather than ...
You could add a postrotate script to your current block in order to delete files older than n days with the following : find /var/log/apache2 -name "*.log.gz" -maxdepth 1 +mtime <n> -delete &>/dev/null Wait for the next rotation then remove it and let logrotate do its normal job again.
First, I'm using docker 1.1.2 for both client and server, this answer may be obsolete for newer versions of docker as docker evolve quickly. Location of the file Find your docker directory. On systems that use apt/debian style system, the package installed by the docker repository https://get.docker.com/ubuntu use /var/lib/docker. Chances are that ...
Only top voted, non community-wiki answers of a minimum length are eligible