Search results

I suggest to rather find /var/www/vhosts/domain.tld/httpdocs/ -type d -exec chmod 0750 {} \;

Shortening log rotation intervals on that one big client installation is a good idea. Removing AWStats might be too much. It's an issue in that software, but sooner or later that will be solved. Instead, develop a short script that monitors the process list for long running AWStats processes and...

A reboot of that instance might solve it.

I think there is not true technical issue in Plesk with it. Rather check whether the domain is consistently routed to the desired IP or whether it might have several A- or AAAA-records that are pointing to another server, too.

Admin privileges are not required for "show function". I suggest to open phpMyAdmin and run a test: SHOW FUNCTION STATUS WHERE Db = 'dbase_name'; in the SQL dialog box. Maybe the system is right that mysql.proc has a problem? Was MariaDB updated lately? Was mysql_upgrade --force run afterwards...

What does "skip_name_resolve" have to do with the issue described by @seqoi? Why is your @HHawk case "this issue as well" when you post a totally different description that is in no way linked to the initial post? I suggest you post your issue with a detailed description in your own thread...

It does not show errors, because there are none. The bug seems to be that a restore of files or directories restores them with pcacln group, not psaserv group where required. That should be investigated by Plesk.

This might be the cause. The question is whether it is expected that file ownership is restored when only single files are extracted. Bug or not?

Was it a website restore or did you select single files or directories?

I think the repository from where the updated files are coming is not the MariaDB repository, but a MySQL repository. Check /etc/yum.repos.d, find the SQL repository (repositories maybe), e.g. mariadb.repo. It should contain a section that points to a MariaDB source such as [mariadb-main] name...

I think it's a very basic, general issue with AWStats. We started seeing it once we moved from CentOS 7 to Alma 8. It preferrably occurs on "localhost", rarely on a client domain, but sometimes on a client domain, too. It might be caused by log files too large and a bug in AWStats that get's...

From ChatGPT - without warranty: That specific error usually means InnoDB’s internal stats tables in the mysql system database are damaged. You must be careful here, because a wrong command can cause data loss. I’ll outline the usual options from least to most destructive, and you can choose...

"activating" is not "active". So is it "activating" or is it "active"? What's logged in the journal? # journalctl -u mariadb

Is the database service running?

In the 18.0.73 #4 version, the file manager editor still shows the Beta icon, although according to Important - Plesk Obsidian Releases it should not be a beta any more. A customer complained that HTML is not processed properly. I was able to reproduce it. No issues with Plesk updates though, so...

What's the content of /etc/hosts? It should not only resolve to localhost, but resolve the local IP address to the hostname, e.g. # IPv4 127.0.0.1 localhost.localdomain localhost 123.123.222.111 <my.host.com> myhost where "myhost" and my.host.com are just examples of your local host...

It might not be caused by a real cron, but by one specific website. For example it could be a backup plugin of a specific website that is triggered by the Wordpress internal cron (which won't show up in the cron logs). To find out what the top transactions really are, run MYSQL_PWD=`cat...

Try to run plesk bin admin --disable-access-domain on the command line, then try the URL again.

Line 103 could be in an "include", counting the total number of lines from line 0 of wp-config.php to line 103 when you imagine the include was inline in wp-config.php. Besides that, I cannot answer the questions as that would require checking it on the installation.

Race condition, yes, but it seems that not all sni files are processed, because a simple restart after the finished upgrade won't help in many situations. The faulty files must be edited or removed, else the restart will fail.