Search results

I've managed to complete the update with OS Ubuntu 20.x rather than AlmaLinux8. Here are two articles that helped... How to Upgrade MariaDB Server to a Newer Version in Ubuntu https://community.hetzner.com/tutorials/how-to-install-mariadb-10-6-on-ubuntu-20-04 I started with the first article...

Thanks Maarten for the point about login credentials. And also about Plesk support. I'll check both these out.

Thanks Bitpalast. The outputs for journalctl -xe and /var/log/messages are shown below. /var/log/syslog produces no output. I'm afraid the output gives me no clues as to the problem or how to solve it. Plesk support is a paid for option and may not be possible as my Plesk licence is in the name...

[peterkaye@128 etc]$ journalctl -xe -u mariadb Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages. Pass -q to turn off this notice. -- Logs begin at Fri 2024-10-04 11:13:25 UTC, end at...

Thanks. Is this what you want? [peterkaye@128 mysql]$ sudo systemctl start mysqld Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.

Thanks Bitpalast. You were spot on - it includes an error message! Here's the content of my.cnf... # This group is read both both by the client and the server # use it for options that affect everything # [client-server] # # include all files from the config directory # !includedir...

I have completed the install of MariadB 10.6 , server, client, common and shared without any error messages. [see below]. However when I try and start MariaDB sudo systemctl start mariadb , I get this error message... . Job for mariadb.service failed because the control process exited with...

Thanks scsa20 for pointing me to whether or not root login was enabled and also encouraging me to go back to the hosting provider.

Problem solved as follows: logging in to PuTTY using the administrator credentials when server configured and then sudo enabled me to edit /etc/ssh/sshd_config to set PermitRootLogin yes With this change, I can now use SSH within Plesk and also login to PuTTY as root with the same password I...

Thanks Maarten. Admin Access is disabled (root account sudo access). Accessing SSH from within Plesk fails with the message "SSH Terminal is not available" and a pointer to this this link. But the commands in the link require SSH access! So without a PuTTY login, I can't solve the problem of...

I can login in Plesk with user root and the password I gave for the admin user when Plesk was configured by the hosting company. But these credentials don't work in PuTTY. Any ideas on how I can fix this? Thanks.

Spot on Peter! Pasting the entire contents into the password prompt gets mariadb-upgrade to run successfully. Thank you. And thanks to everyone else who've solved this for me. And increased my Plesk knowledge - never knew about auto-generated admin password or ever looked at .psa.shadow.

Thanks Maarten. And for the hashing explanation. I never realised Plesk had its own, internally generated, db access password. Your command line looked really hopeful but, sadly, it doesn't pick up the password location, it still prompts for entry.

Thanks, Peter. I have found .psa.shadow but it's a long string and I'm not clear which bit is the admin password. None of the characters correspond to any password I've created. Here's the string... I've tried the various bits separately but each time I get access denied. I found this post...

Thanks scsa20. When I run mariadb-upgrade as root, I get a fatal error... Same error when using PuTTY. When I insert the credentials ( user=, password=, host= ) for root or a user the administrator privileges, I get the same error. The instructions say the user must have write access to...

I'm sure you have the answer. Thanks. I read the message quickly and didn't see the connecting hyphen in mariadb-upgrade and so didn't pick up it was a utility, not an instruction to 'upgrade MariaDB'! mariadb-upgrade is documented here. Compicated, but it looks like most of the parameters are...

The Database Export option within Plesk shows this error. Exporting from phpMyAdmin works fine. Tools and settings > Database Servers shows the MariaDB version correctly as 10.5.22. It was manually updated from the default build version 5 which might well have been 5.05.22 - as per the error...

An update to complete the story on this... The ftp problem appears to be part of a bigger issue. Whether related to the nydus-ex and nydus-ex-api issue raised in the Web Host's (Heart Internet) warning message (see #5) I don't know. Shortly after the ftp problem SSH connectivity was lost. Heart...

Thanks. I think it was browser cache and/or DNS propagation as the site now displays correctly. But your checklist is useful if this reoccurs. Thanks again for your help.

I have deleted the default index.html as per this post but the default web page still shows. Another site on the same server correctly displays preview and web view. What am I doing wrong?