New answers tagged

1

The most obvious issue with symlinking it to /dev/null would be that you would then be unable to read its contents. If you do not need to read the contents of the log file, then there is no problem symlinking to /dev/null - although you may want to look into the ability to simply disable the logging facility of the software in question in the first place. ...


0

It's all ok if you dont want them. No worry there. I did that tip on a xenserver, as by default the install partition is done small by the installer, thus the filesystem was hitting 90%+ of usage. (even with logrotation or log compression added)


2

There are multiple issues with your configuration file. The modifier ^~ is for prefix locations and not regex locations (despite the presence of a tilde). See this document for details. In order to give a regex location precedence over another regex location, it simply needs to appear first. The location block needs to be complete. nginx will not take ...


3

Yes, that is the standard notation for port numbers when describing TCP / UDP connection endpoints.


3

Although this particular requesting client resolves to search.msn.com, the Request is of a nature that is often malicious, where the "normal" text is encoded to attempt to evade filtering, pass executable code, etc. If you monitor your web logs, you will often see this type of activity. You can mitigate against this by dialing down your LimitRequestLine ...


1

The problem re-appeared. Therefore I cannot accept user208998's answer anymore. The cause was cron. One of my cronjobs exited unsuccessfully. I didn't notice that because the actual task was performed correctly. Because I didn't set the MAILTO environment variable, cron tried to inform user root by email. For unknown reasons cron thinks my host name is ...


0

Using this tip, I edited /etc/init.d/atop As the manual page says "four weeks", it was clearly there this command: find $LOGPATH -name 'atop_*' -mtime +28 -exec rm {} \; So, 28 days old files will be kept... I changed it to find $LOGPATH -name 'atop_*' -mtime +1 -exec rm {} \; And ran this command: sudo service atop _cron Now the logs are only at most ...


1

Always read the man page. Always. If you would have done so, you would have seen this: When atop is installed, the script atop.daily is stored in the /etc/atop directory. This scripts takes care that atop is activated every day at midnight to write compressed binary data to the file /var/log/atop/atop_YYYYMMDD with an interval of 10 minutes. ...


1

First, make sure your item actually gets these error lines. Check Monitoring -> Latest data. If it does not, that's an active agent configuration problem, not log monitoring problem. Verify that the agent hostname (agent daemon configuration file, parameter Hostname) matches the host name in the frontend - note that it is case sensitive. If you item had ...


0

If no change occurs for 30 seconds THEN alarm Did you set monit to run every 30 second ? Monit is not mean for such metric as it check every (2) minute(s) from default configuration. Also to detect that a timestamp didn't change every 30 second is not the same as check each second if not older than 30 second Also for such specific case, use a custom ...



Top 50 recent answers are included