Bug#918988: AW: Bug#918988: AW: [debian-mysql] Bug#918988: libmariadbclient18: conflict with libmysqlclient18
to 18. huhtik. 2019 klo 11.27 Daniel Högele - adelphi (hoeg...@adelphi.de) kirjoitti: > > >Maybe if you have apache compiled with the version X of the library, > and then you upgrade Apache but not keeping in sync the libraries if > might break down. > > Never compiled anything. Just simple "apt install" from debian repositories. I mean that you installed form Debian repos binary revision X built with Y, and then upgraded Y but binary X stays the same. So something is compiled with some versions by Debian, and then you get problems when you mix and match. Proper dependency declarations should however automatically mitigate issues like this. > >With the information provided I cannot reproduce the issue or debug it, > >sorry. > > How can we help you? What information do you need? Bernard an me are not the > only one, having this issue. See: > http://ask.ocsinventory-ng.org/10396/http-error-500-after-system-upgrade-mariadb > http://ask.ocsinventory-ng.org/10571/child-exit-signal-segmentation-fault-11 > > Any recommended tests, e.g. uninstall / reinstall apache + mariaDB? If you can write down steps for me on how to reproduce the error it would help. Fill in here: docker run -it debian:jessie bash # Which Debian release did you start with? apt-get update apt-get install X Y Z # What software did you have installed? echo "X hold" | dpkg --set-selections # What software did you not update? service apache2 restart curl localhost/x # what works sed 's/jessie/buster/g' -i /etc/apt/sources.list apt-get update && apt-get dist-upgrade curl localhost/x # what stopped working?
Bug#918988: AW: Bug#918988: AW: [debian-mysql] Bug#918988: libmariadbclient18: conflict with libmysqlclient18
>Maybe if you have apache compiled with the version X of the library, and then you upgrade Apache but not keeping in sync the libraries if might break down. Never compiled anything. Just simple "apt install" from debian repositories. >With the information provided I cannot reproduce the issue or debug it, sorry. How can we help you? What information do you need? Bernard an me are not the only one, having this issue. See: http://ask.ocsinventory-ng.org/10396/http-error-500-after-system-upgrade-mariadb http://ask.ocsinventory-ng.org/10571/child-exit-signal-segmentation-fault-11 Any recommended tests, e.g. uninstall / reinstall apache + mariaDB?
Bug#918988: AW: [debian-mysql] Bug#918988: libmariadbclient18: conflict with libmysqlclient18
> >This is probably the core issue. Does it start working if you run 'apt > >remove libmysqlclient18' > > No, it did not start working. Still getting errors in apache log: > [Wed Apr 17 15:42:14.536746 2019] [core:notice] [pid 22785] AH00052: child > pid 55325 exit signal Segmentation fault (11) I am out of ideas and there is no setup I can replicate and debug the issue myself. Maybe if you have apache compiled with the version X of the library, and then you upgrade Apache but not keeping in sync the libraries if might break down. With the information provided I cannot reproduce the issue or debug it, sorry.
Bug#918988: AW: [debian-mysql] Bug#918988: libmariadbclient18: conflict with libmysqlclient18
>This is probably the core issue. Does it start working if you run 'apt remove >libmysqlclient18' No, it did not start working. Still getting errors in apache log: [Wed Apr 17 15:42:14.536746 2019] [core:notice] [pid 22785] AH00052: child pid 55325 exit signal Segmentation fault (11)
