Hot answers tagged

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 ...


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 ...


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

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 ...


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 ...



Only top voted, non community-wiki answers of a minimum length are eligible