I just installed a fresh copy of Leap 42.2 a few days ago (minimal x window) as I’m trying to create a webserver for the first time.
I have been following the SDB Lamp guide to get everything set up.
When I try to start mysql with
**systemctl start mysql**
I get the following:
linux-77k0:~ # systemctl start mysql
Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.
systemctl satus mysql.service gives:
linux-77k0:~ # systemctl status mysql.service
● mysql.service - MySQL server
Loaded: loaded (/usr/lib/systemd/system/mysql.service; enabled; vendor preset: disabled)
Active: activating (start-post) (Result: exit-code) since Sun 2017-08-06 19:11:57 CDT; 12s ago
Process: 28441 ExecStart=/usr/lib/mysql/mysql-systemd-helper start (code=exited, status=127)
Process: 28429 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade (code=exited, status=0/SUCCESS)
Process: 28419 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install (code=exited, status=0/SUCCESS)
Main PID: 28441 (code=exited, status=127); : 28442 (mysql-systemd-h)
Tasks: 2 (limit: 512)
CGroup: /system.slice/mysql.service
└─control
├─28442 /bin/bash /usr/lib/mysql/mysql-systemd-helper wait
└─28496 sleep 1
Aug 06 19:11:57 linux-77k0 systemd[1]: Starting MySQL server...
Aug 06 19:11:57 linux-77k0 mysql-systemd-helper[28442]: Waiting for MySQL to start
Aug 06 19:11:57 linux-77k0 mysql-systemd-helper[28441]: /usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: pcre_stack_guard
Aug 06 19:11:57 linux-77k0 systemd[1]: mysql.service: Main process exited, code=exited, status=127/n/a
and the output of journalctl -xe is:
linux-77k0:~ # journalctl -xe
Aug 06 19:11:56 linux-77k0 systemd[1]: Failed to start MySQL server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 06 19:11:56 linux-77k0 systemd[1]: mysql.service: Unit entered failed state.
Aug 06 19:11:56 linux-77k0 systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 06 19:11:57 linux-77k0 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 06 19:11:57 linux-77k0 systemd[1]: Stopped MySQL server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Aug 06 19:11:57 linux-77k0 systemd[1]: Starting MySQL server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Aug 06 19:11:57 linux-77k0 mysql-systemd-helper[28442]: Waiting for MySQL to start
Aug 06 19:11:57 linux-77k0 mysql-systemd-helper[28441]: /usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: pcre_stack_guard
Aug 06 19:11:57 linux-77k0 systemd[1]: mysql.service: Main process exited, code=exited, status=127/n/a
I’m not sure what either of those are telling me other than a bad symlink?
I’ve searched around but most similar problems are from corrupted db after an upgrade.
This is a fresh install on a freshly installed system.
Thanks for any help.
Before installing a major application and <especially> after a brand new install (unless it’s an online install), you should always update your system. Although you should have updated before installing, you can also update your system now. You can do this by executing the following in an elevated browser
zypper up
Then, try starting your service.
If the above doesn’t work, you need to describe or post info about your mysql server… Is it mariadb? Did you install it standalone or as part of the LAMP pattern? How did you install, using YaST Software Manager or zypper referencing a specific package or pattern? Or, did you install as a download from somewhere else like Oracle?
Is this an initial LAMP installation with nothing configured?
Or, have you configured anything at all yet?
A simple search suggests it’s likely a bug in one of your libpcre packages, but only if you haven’t started to configure anything at all (starting mysql/mariadb for the first time).
You can try a more recent version (than what is generally available), for example libpcre1 v 8.41 is currently available in the security repo
After installing the OS I installed the the meta package patterns-openSUSE-lamp_server.
After that I realized I needed more help so I turned to the guide referenced in my OP.
Do you think it would be easier to start over? I’ve literally got no actual data on the server yet, just some sshd configuration and whatever I have done to mysql to tick it off.
Since I had nothing to lose, I hosed the entire system and just reinstalled. I no longer have the problem and have a fully functioning LAMP server :good:.
I’m guessing I somehow messed up mysql/mariadb but since I was hadn’t any data on the system yet I went for the easy route.