Not the answer you need?
Register and ask your own question!

Percona hangs on post-install script and on syslctrl start on Ubuntu 18.04

jpsantosjpsantos EntrantCurrent User Role Novice
It wasn't a fresh install, so I purged all packages, percona-server-server percona-server-common percona-server-client and I'm still getting the same problems. Made a backup of the database as well and cleared all data just in case, problem still happens.

Server actually appears to start, but sysctrl hangs on startup as if it didn't complete, and apt always hangs when installing any packages or upgrades because the post-installation script initially failed.

Here's what I see in the /var/log/mysql/error.log file:


2019-12-03T20:40:21.907769Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.17-8) Percona Server (GPL), Release '8', Revision '868a4ef'.
2019-12-03T20:40:22.170248Z 0 [Warning] [MY-011807] [Server] Failed to connect to systemd notification socket named /run/systemd/notify. Error: 'Permission denied'
2019-12-03T20:40:22.480010Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.17-8) starting as process 30719
2019-12-03T20:40:22.968596Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-12-03T20:40:22.991620Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.17-8' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Percona Server (GPL), Release '8', Revision '868a4ef'.
2019-12-03T20:40:23.117218Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock'
2019-12-03T20:40:23.117399Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060


Please help, this is annoying, my system things it has a broken install. When I used dpkg --configure -a it runs into the same problem, which appears that the sysctrl scripts just won't complete on startup.

Comments

  • jpsantosjpsantos Entrant Current User Role Novice
    I have recreated this problem on several different installs and I have yet to get a single response from anyone. Does Percona not take this seriously?
  • sudobashsudobash Entrant Current User Role Novice
    I would recommend Debian 10 Buster instead of Ubuntu. I was able to install Percona Server 8 no problem. Start with a barebones install not installing anything but the XFCE desktop. Ubuntu has too much bloatware like Windows or Mac OSX to be a proper server OS.

    If you want to go even more secure, do a barebones install with no desktop and uncheck all additional packages at the installation manager. You could install KickSecure on top of the barebones Debian 10 install.

    Follow the instructions here to install Kicksecure over Debian 10 Barebones:

    https://www.whonix.org/wiki/Kicksecure/Debian

    It's best to start from the foundation up, secure your OS first, then build on top of that.
  • jpsantosjpsantos Entrant Current User Role Novice
    sudobash wrote: »
    I would recommend Debian 10 Buster instead of Ubuntu. I was able to install Percona Server 8 no problem. Start with a barebones install not installing anything but the XFCE desktop. Ubuntu has too much bloatware like Windows or Mac OSX to be a proper server OS.

    If you want to go even more secure, do a barebones install with no desktop and uncheck all additional packages at the installation manager. You could install KickSecure on top of the barebones Debian 10 install.

    Follow the instructions here to install Kicksecure over Debian 10 Barebones:

    https://www.whonix.org/wiki/Kicksecure/Debian

    It's best to start from the foundation up, secure your OS first, then build on top of that.

    We are using Ubuntu because of the 5 year support on 18.04. It is possible to install a server without bloatware, and it shouldn't be a question of which OS this is installed on. The startup script is not finishing execution though the server is running, causing APT to fail with an error. It should be a pretty straightforward thing to address. I've switched back to a standard mysql installation which doesn't have this problem. It appears that it's a known issue for prior versions of percona, it's been resolved in 5.7, but not in version 8.0.
  • jriverajrivera Percona Support Engineer Percona Staff Role
    >> It wasn't a fresh install, so I purged all packages, percona-server-server percona-server-common percona-server-client and I'm still getting the same problems.
    >> I have recreated this problem on several different installs

    Can you confirm this happens on a fresh install? I wonder what other packages may have been removed when you "purged all packages".

    For what it's worth, I tried installing on a fresh install and it works fine following the instructions in the manual on how to install Percona Server for MySQL
  • jpsantosjpsantos Entrant Current User Role Novice
    jrivera wrote: »
    >> It wasn't a fresh install, so I purged all packages, percona-server-server percona-server-common percona-server-client and I'm still getting the same problems.
    >> I have recreated this problem on several different installs

    Can you confirm this happens on a fresh install? I wonder what other packages may have been removed when you "purged all packages".

    For what it's worth, I tried installing on a fresh install and it works fine following the instructions in the manual on how to install Percona Server for MySQL

    Yes, an out of the box install of Ubuntu 18.04, and it hangs. I purge all percona and percona related files, as well as mysql libs etc.

    What else would need to be purged for a start-up script to work?
  • jriverajrivera Percona Support Engineer Percona Staff Role

    Can you share the output of:

    dpkg -l | grep -i 'mysql\|percona'

Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.