Tag Info

Hot answers tagged

4

This is nothing to do with Azure, this is the limit imposed by Windows Server on remote administration, you can only have 2 administrators connecting to a server to manage it at once. If you need more than two connections then this is no longer remote administration, you are running a remote desktop server and providing applicaitons to users, which means ...


2

Looks like someone is scanning your website on different ports and looking for a specific file (r.php) which could be a backdoor or something similar. As the file does not exist it throws errors (which is good)... I see this kind of log entries from time to time as well. Stick to these answers on how to secure LAMP in general: Tips for Securing a LAMP ...


2

According to that blog post, Please note, that it’s not possible to embed variables in error_log directives, as any potential error would not be able to be logged if the file cannot be written. With that in mind, it is not possible to have the error log automatically rotated with the naming format error-$year-$month-$day.log using that Nginx method. ...


2

See my comment above, and cpburnz's reasoning, but if you really want to proceed: You could write a script which writes just the log commands to an include file, with the current date hard-coded. You'd have that included into your nginx config file, and your script would restart or reload nginx after writing the log commands to the include file. Something ...


2

Yes, your VPS is always under attack. But no, that's not what this log entry shows. This is legitimate activity. It's anacron, running the daily /etc/cron.daily/lighttpd job, as you saw. In the (corrected) lighttpd cron script, you can see that the script is running su www-data, and the log file shows root changing user to www-data.


1

you must have something like that at your rsyslog config file *.*;auth,authpriv.none -/var/log/syslog If you take a look, you are registering ALL severities from ALL facilities, to the syslog file, except auth and authpriv facilities. Simply add the facility wich you don't want to log, plus the "none" severity. I.E: local6: ...


1

For the 2nd question: it's possible for the logfiles to have been rotated since the service started (meaning the logs are now in some other files). For the issue: it's possible for the "is already running" message to be misleading: usually it takes a rather long time (tens of seconds) between when a server process exits without cleanly closing the ...


1

Update 1: The verbose option will list in long format and so includes the UNIT: [root@localhost]# journalctl --unit newnginx -o verbose -- Logs begin at Sun 2015-04-05 10:36:30 BST, end at Mon 2015-06-01 08:17:58 BST. -- Sun 2015-05-31 10:27:38.344553 BST ...


1

This is not the best answer I am offering you, but as per your requirement I found something to share which might be helps you to accomplish this task please have a look. You can use the Auditing page in the Office 365 Compliance Center to quickly access the audit reports for your Exchange Online organization. For more details please have a look: ...


1

Check to see if you have more than one server block in your config. In my case I think it was caused by having an HTTP redirect like below. The HTTP requests were being logged in the default log path, but the HTTPS requests were logged where I expected. server { listen 80 default_server; listen [::]:80 default_server ipv6only=on; return 301 ...


1

Looks like a simple monitoring system, especially with the fixed 30 sec interval.


1

I doubt that the HEAD requests are related to your reduced pageviews. Like @mschuett said, it looks like a monitoring system of some kind is paging your server every 30 seconds to check that it is responding. That request requires very few resources so it's a good one for basically pinging the server and making sure the http service is responding. It ...



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