Bug ID 1102224
Summary libmysqlclient.so.18 missing after update from Leap 42.3 leads to critical software problems
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.0
Hardware x86-64
OS Other
Status NEW
Severity Critical
Priority P5 - None
Component Upgrade Problems
Assignee bnc-team-screening@forge.provo.novell.com
Reporter studio@anchev.net
QA Contact jsrain@suse.com
Found By ---
Blocker ---

I have compiled Bacula from source in 2016. Since then I have updated openSUSE
more than once but never had any problems with Bacula after that.

Last night I updated to Leap 15. Now my bacula-dir.service won't start:

----------------
# systemctl status bacula-dir.service
��� bacula-dir.service - LSB: bacula director
   Loaded: loaded (/etc/init.d/bacula-dir; generated; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2018-07-23 13:19:17 EEST; 58min
ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2548 ExecStart=/etc/init.d/bacula-dir start (code=exited, status=7)

Jul 23 13:19:17 pc systemd[1]: Starting LSB: bacula director...
Jul 23 13:19:17 pc bacula-dir[2548]: Starting the Bacula Director:
/usr/sbin/bacula-dir: error while loading shared libraries:
libmysqlclient.so.18: cannot open shared object file: No such file or directory
Jul 23 13:19:17 pc startproc[2556]: startproc:  exit status of parent of
/usr/sbin/bacula-dir: 127
Jul 23 13:19:17 pc bacula-dir[2548]: ..done
Jul 23 13:19:17 pc systemd[1]: bacula-dir.service: Control process exited,
code=exited status=7
Jul 23 13:19:17 pc systemd[1]: Failed to start LSB: bacula director.
Jul 23 13:19:17 pc systemd[1]: bacula-dir.service: Unit entered failed state.
Jul 23 13:19:17 pc systemd[1]: bacula-dir.service: Failed with result
'exit-code'.

# zypper search libmysqlclient
Loading repository data...
Reading installed packages...
No matching items found.
----------------

Breaking backup software is critical.


You are receiving this mail because: