• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Unable to open logs after raname of error_log of Apache

M

MorrisM

Guest
Hi, I hope someone of you can help me solve a (i hope... a little) problem. I was deleting all logs processed in rotation on my server with Plesk Panel 9.0.0 and CentOS 5, in the folder "domain/statistics/logs". By mistake I renamed "error_log" file and now Apache can restart. When in Putty I send the command "service httpd restart", it fails giving me the error "Unable to open logs". I just renamed the error_log file to the original but the problem remain.

I tried to access to the Plesk Panel, I went on the "Web Hosting Settings" for the specific domain, I unchecked "Custom Error Documents", applied the modidy and re-checked the option: nothing, Apache don't want to restart.

So, I have a strage situation: Apache is currently running correctly (it seems), but I can't restart it.

Please, someone can help me solve that problem? I searched in this forum and googled for a solution but... nothing...

Thank you very much for your support.
 
For some reasons Apache can't get access to logs. Maybe it is caused by limit for open files. Try 'ulimit -n 2048' at least.
 
Thank you for your answer, but it don't solve the problem... maybe I have to create the file with the same permissions but i'm not sure how.
 
i solved... i renamed the error_log with the original name, "pkill httpd", and rested Apache... now it seems to run correctly.

Anyway, thank you very much for your support.
 
Back
Top