Search results

you can protect the server status with a password request. Example (/etc/httpd/conf/httpd.conf): <Location / server-status> SetHandler server-status Order deny, allow Deny from all Allow from 127.0.0.1 AuthUserFile /var/www/.htpasswd AuthName server status AuthType...

CentOS Linux 7.9.2009 Courier Plesk Obsidian Version 18.0.31 Update 2, installed: 1.12.2020 Everything was normal at first, but yesterday the server was restarted and since then the customers have received all emails "twice" I found this created just yesterday...

There are already very good, detailed instructions for upgrading mariadb. https://support.plesk.com/hc/en-us/articles/213403429--How-to-upgrade-MySQL-5-5-to-5-6-5-7-or-MariaDB-5-5-to-10-x-on-Linux- What would be of interest to me would be whether you carry out a direct update from 10.1 to 10.4...

for about an hour i have been receiving error messages from various servers. why is the update looking for 18.0.39, we're only at 30#2?

why is this bug https://support.plesk.com/hc/en-us/articles/360002323774-With-piped-logs-enabled-in-Apache-HTTPS-traffic-is-still-put-to-access-log-processed-during-statistics-calculation assigned to onyx if it is still present in the current obsidian?

can someone please give me feedback ? The defined update days and times are also completely ignored when updating from 29 to 30.

you need to migrate from centos 6 to 7 please see: https://talk.plesk.com/threads/php-7-4-when.354492/page-2#post-882557

Why are the update days and periods specified in the panel.ini completely ignored when updating from 18.0.28 to 18.0.29 ? today dozens of servers do the updates "at noon" at the same time. high cpu load on the nodes, phone calls why there are 504 or 502 messages (nginx restart) etc. has the...

Yes, there will be no php7.4 for centos 6 presumably because centos 6 is November 30, 2020 end of life. and then there will probably be no more plesk updates for centos 6 at some point

the versions used are "more up-to-date" than you indicated. the bug is still there. However, one can say that there are only a few servers where the cron cleans a lot of sessions. most servers only clean a handful sessions if they run every 3-6 hours.

Sorry, I have no other ideas. maybe plesk support should take a look at this directly on the server.

did you check the abandoned systemd scope units on the server ?

16 days after the 18.0.29 appeared, the first servers receive the automatic update but the panel.ini values [updates] updateDays = friday,saturday timeFrameStart = 01 timeFrameEnd = 05 are completely ignored and the updates run during the day. :confused:

I would fix the error first and then do the update

could be this bug https://support.plesk.com/hc/en-us/articles/115004603434-Plesk-fails-to-restart-services-control-script-doesn-t-exist-or-isn-t-executable

Quote from the error message: "Please use mysql_upgrade to fix this error" try MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin

in the past, these updates ran automatically at some point. unless there are messages during the update that prevent this. As I said, it can only take weeks until the updates are made automatically. I can't say whether something has been changed here regarding 18.0.29.

this can take several weeks. with some servers the update never comes automatically and you should do it by hand to see if there are any messages that prevent the automatic update.

Yes, the CT`s with centos 7 ran on VZ 6 without systemd problems. The problems have only existed since the CT's were migrated to VZ 7.

I'm beginning to suspect that this also has something to do with the kernel used and the virtualization platform. With Virtuozzo 6 there was never a problem and the cron script was not necessary. We migrated some servers to virtuozzo 7 and suddenly all servers have this bug and the cron deletes...