Search results for query: "apache" "logrotate"

We are still having this problem every day at midnight Every day we receive many emails alerts like that, always at exactly 6:00PM in my timezone, which equals to midnight in server's time I think logrotate restart the apache daemon How can i change the time that logrotate runs?

I use the default settings, same as our other servers which doesn't have any problem I don't see any cron job related to logrotate, but for every single other cron job in the Scheduled Tasks, I changed the time, so there are no cron jobs running at 00:00 as far as I know

I have done all settings in Plesk to have a daily log rotation (and keep the files 7 days). It works for the access_log and access_ssl_log (and I don't use apache at all, since I have disabled proxy mode), but i is not applied to the nginx proxy_access_ssl_log. There is always just one file...

Since 2 weeks on every logrotate (midnight) I receive this error: [ E 2021-06-28 00:02:52.0639 463459/T0 apa/Hooks.cpp:750 ]: Unexpected error in mod_passenger: Cannot connect to the Passenger core at unix:/tmp/passenger.tWygnUX/agents.s/core Backtrace: in 'Passenger::FileDescriptor...

Hi basdebruin, I am facing exact the same issue for a long time and don;t know how to solve this. [ E 2022-03-19 20:36:10.0633 32442/T0 apa/Hooks.cpp:751 ]: Unexpected error in mod_passenger: Cannot connect to the Passenger core at unix:/var/passenger/passenger.laVvB0R/agents.s/core...

I upgraded my server but the data I backed up to my previous Yandex disk is encrypted by Plesk. When I restore these backups fail, I cannot access my files. How do I solve this? Most of the files have .tzst extensions. the SSH command i use Output please a lot of help part of my xml file...

@juanisrael, there is something wrong with the quotes in your post, so it's not quite clear if you're having issues and what they are. As for the log rotation, the exact time depends on your OS defaults and whether you've made any configuration changes. E.g. for CentOS 7, that would be...

Hello there! Several days ago I've run upgrade of Plesk from version 12.5.30 to 17.8.11 via GUI interface. This upgrade was failed, because we haven't free space (I found this issue later - my mistake). After space clean (now we have 17GB free space) I am trying to run upgrade once again, but...

Hello Volks, I received today night a error message from my server by mail. /etc/cron.daily/logrotate: Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details. I have checked my server by Plesk...

Happy New Year :) CentOS 7.4 with Plesk Version 17.5.3 Update #34, last updated on Dec 19, 2017 01:10 PM Just created a new subscription in the panel on a hosting plan which has log rotation enabled in the Logs & Statistics tab with the following settings: Log rotation condition: by size...

[QU thank you so much guy this helped me to correct my problem OTE="Chris1, post: 789724, member: 169790"]Here is my /etc/logrotate.d/httpd file: /var/log/httpd/*log { missingok notifempty sharedscripts delaycompress postrotate /bin/systemctl reload httpd.service > /dev/null...

Hello, On May 19th and for no apparent reason, I stopped working the server logrotate, may have to do with some update plesk? Everything worked properly, but now nothing. If you manually pass these processes, for example for apache logs, you do it correctly, but it has to be done manually...

Hello, You can try to disable the logrotate cronjob, but I do not think it's the current issue. Have you check the 14MB of error logs you have ? It may help you to find the issue

I have the same Problems with same results . file_get_contents (internal.domain) ANY INTERNAL DOMAIN ON SERVER NOT WORKING 502 oder 404 or White unkown Site coming likte this BUT file_get_contents (Google) working great any extrenal domain And the same results is in WGET Command on...

Thank you for your answer Peter. I've fixed the problem by commenting out the postrotate commands in the logrotate config of mod_security. I would post the solution here, if anyone else has the same problem. But before, I would like to know, if commenting out the reload of apache in the...

@hozone The comment by @virtubox is right: it certainly is not the logrotate process (and it will never be with your logs of relatively small size). The most common culprits of Apache resource usage are cronjobs executed by a specific application. For instance, WordPress cronjobs are...

I remember a recent case where /etc/logrotate.d/mod_security had a restart command in it. mod_security cannot restart Apache, but logrotate can, and when logrotate should be executed, it will read the apache file and mod_security log rotation configuration and might restart Apache a second time...

Logrotate can cause Apache crashs. In other cases, a second or third restart attempt while the first or first two were not yet completed has caused Apache to crash. These additional Apache restarts could be defined in postrotate directives in service configuration files (the conf files in...

Hello Every domain is affected when this issues happens. I think it happens when he tries to logrotate. How would we proceed dealing with issue globally? Atm we have these settings: Apache restart interval is 60 sec piped logs are not activated Mpm mode prefork Can't see anywhere mod_ruid2...

Very difficult. I think that this article has the correct solution for your situation: http://serverfault.com/questions/627521/why-is-logrotate-causing-apache-to-seg-fault-each-time