[Bug 1102224] New: libmysqlclient.so.18 missing after update from Leap 42.3 leads to critical software problems
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224 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: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224#c1
Stephan Kulow
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224#c2
--- Comment #2 from George Anchev
Not sure what opensuse versions you updated
13.2 -> 42.1 -> 42.2 -> 42.3 -> 15.0 (the last one mentioned in the subject here)
create a container for your self compiled app
May I ask for link with info explaining how to do that please? I am not a sysadmin (in the professional sense) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224#c3
Sergio Lindo
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224#c4
--- Comment #4 from George Anchev
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224#c5
--- Comment #5 from George Anchev
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224#c6
--- Comment #6 from Stephan Kulow
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224#c7
--- Comment #7 from George Anchev
it was renamed to be .so.19 to mark an incompatible version. Be warned your service might explode
Are you sure? zypper info --provides libmariadb-devel shows: libmysqlclient_r18 = 10.2.10 Doesn't "r_18" suggest that it is version 18 (not 19 as you say)? How can this be checked? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224
http://bugzilla.opensuse.org/show_bug.cgi?id=1102224#c8
Andreas Stieger
participants (1)
-
bugzilla_noreply@novell.com