Description of problem: mysql sql from mysql repo doesnt' start Version-Release number of selected component (if applicable): mysql-workbench-community-8.0.12-1.fc28.x86_64 mysql-shell-8.0.12-1.fc28.x86_64 mysql-community-client-8.0.12-1.fc28.x86_64 mysql80-community-release-fc28-1.noarch mysql-community-libs-8.0.12-1.fc28.x86_64 mysql-community-common-8.0.12-1.fc28.x86_64 mysql-community-server-8.0.12-1.fc28.x86_64 mysql-connector-python3-8.0.12-1.fc28.x86_64 mysql-connector-python-8.0.12-1.fc28.x86_64 mysql-connector-java-8.0.12-1.fc28.noarch How reproducible: every single time - always Steps to Reproduce: 1. sudo systemctl start mysqld 2. sudo systemctl status mysqld 3. journalctl -xe Actual results: service doens't start because consume to much CPU time and canceled anormaly Expected results: start service Additional info: sudo systemctl start mysqld Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details. sudo systemctl status mysqld ● mysqld.service - MySQL Server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2018-09-15 16:33:21 CEST; 36s ago Docs: man:mysqld(8) http://dev.mysql.com/doc/refman/en/using-systemd.html Process: 31229 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS (code=exited, status=1/FAILURE) Process: 31207 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS) Main PID: 31229 (code=exited, status=1/FAILURE) Status: "SERVER_BOOTING" Error: 2 (No such file or directory) CPU: 6.472s sep 15 16:33:11 localhost-localdomain systemd[1]: Starting MySQL Server... sep 15 16:33:21 localhost-localdomain systemd[1]: mysqld.service: Main process exited, code=exited, status=1/FAILURE sep 15 16:33:21 localhost-localdomain systemd[1]: mysqld.service: Failed with result 'exit-code'. sep 15 16:33:21 localhost-localdomain systemd[1]: Failed to start MySQL Server. sep 15 16:33:21 localhost-localdomain systemd[1]: mysqld.service: Consumed 6.472s CPU time journalctl -xe -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit mysqld.service completed and consumed the indicated resources. sep 15 16:33:21 localhost-localdomain sudo[31199]: pam_unix(sudo:session): session closed for user root sep 15 16:33:21 localhost-localdomain audit[31199]: USER_END pid=31199 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limit$ sep 15 16:33:21 localhost-localdomain audit[31199]: CRED_DISP pid=31199 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="$ sep 15 16:33:37 localhost-localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostnam$ sep 15 16:33:37 localhost-localdomain systemd[1]: fprintd.service: Consumed 44ms CPU time -- Subject: Resources consumed by unit runtime -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit fprintd.service completed and consumed the indicated resources. sep 15 16:33:57 localhost-localdomain audit[31309]: USER_ACCT pid=31309 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localus$ sep 15 16:33:57 localhost-localdomain sudo[31309]: hhlp : TTY=pts/1 ; PWD=/home/hhlp ; USER=root ; COMMAND=/usr/bin/systemctl status mysqld sep 15 16:33:57 localhost-localdomain audit[31309]: USER_CMD pid=31309 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/hhlp" cmd=73797374656D63746C207374617$ sep 15 16:33:57 localhost-localdomain audit[31309]: CRED_REFR pid=31309 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="$ these original bugs about mysql version 8 reported by me https://bugzilla.redhat.com/show_bug.cgi?id=1628815 https://bugzilla.redhat.com/show_bug.cgi?id=1628814 https://bugzilla.redhat.com/show_bug.cgi?id=1540946 Regards.,
mysql-community-server-8.0.12-1.fc28.x86_64 packages are coming from upstream's repository. So, if there is an issue with the service of MySQL, it will be needed to be fixed in upstream's RPMs, so, please, contact them. If you see the same issue with Fedora RPMs (community-mysql-server package), please, change the component. At this point, we (Fedora maintainers) are not able to help you, sorry.
As mentioned, please submit a bug report to bugs.mysql.com. It would also be helpful if you include any [ERROR] lines from your server log
This is what I did, there isn't a process to migrate from one version to another https://bugs.mysql.com/bug.php?id=92476 thx fedora folks
Was the 8.0 version you were trying to upgrade from pre-GA? I.e. Older than 8.0.11? MySQL supports upgrades from previous major version (5.7, and previous minor versions (8.0.x), but does not support upgrading from dmr or rc releases.
this is the process was i follow., https://bugzilla.redhat.com/show_bug.cgi?id=1540946 regards.,
Right, it looks like you were upgrading from 8.0.4 to 8.0.12, which isn't supported. In-place upgrades from 8.0.11+ are supported.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.