• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Error when trying to access erro_log file

yossefelbaz

New Pleskian
Hi. (my first post here)

I am new to servers. I just started using SSH terminal.

The issue i am experiencing is error 13 when i am trying to view error_log file for the server errors.
The reason i am doing so is that i am getting failed message by email every morning that scheduled backup has failed.

I am accessing the server with putty software and i am login in with my username and password.
After that i am typing su - command and password again.
So my access level is in root.

I am typing the command /var/log/sw-cp-server/error_log and getting the error 13: permission denied.

Any suggestions?
 
Try the following:

nano /var/log/sw-cp-server/error_log

This will use the nano text editor to view the file.

If you've used the Plesk Backup Manager to schedule the backup, there may be information about failure reason on the Current Backup Tasks tab.
 
Last edited:
nano command not found.

I tried to install updates too, but i got error message:
Installation started in background
Error: Failed to run the Yum utility.
The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please, contact product technical support.


I had to run service psa start command.

After that i got it started with:
starting postgresql service... failed
starting drwebd service... failed
 
Try using:

vi /var/log/sw-cp-server/error_log

In regards to yum issue, search the forum, I think that issue has been covered recently.
 
Back
Top