On 12/10/18 3:32 PM, Danny Horne via users wrote:
On 10/12/2018 11:26 pm, Rick Stevens wrote:
>
> Keep in mind that you're really running mariadb and the command to start
> it is "systemctl start mariadb" even though the daemon will show up as
> mysqld in a process list.
>
[root@hawking ~]# systemctl start mariadb
Failed to start mariadb.service: Unit mariadb.service not found.
Well, that's interesting. Do you have the mariadb-server RPM installed
or are you actually running mysqld (from their community download)?
> Nothing useful in the logs? Try
>
> journalctl -b0 | egrep '(maria|mysql)'
>
> and see if anything shows up.
>
Dec 10 23:30:44 hawking.trisect.uk systemd[1]: mysqld.service: Main
process exited, code=exited, status=1/FAILURE
Dec 10 23:30:44 hawking.trisect.uk systemd[1]: mysqld.service: Failed
with result 'exit-code'.
Dec 10 23:30:44 hawking.trisect.uk audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=mysqld comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
My guess those are because systemctl didn't find mariadb-server for
some reason. Again, the functionality of MySQL for Fedora is normally
handled by MariaDB. You _CAN_ download and install MySQL from their
repos, in which case my references to mariadb are moot.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- "Daddy, why doesn't this magnet pick up this floppy disk?" -
----------------------------------------------------------------------