[MDEV-14044] mysql_safe_helper not found Created: 2017-10-10  Updated: 2018-01-31  Resolved: 2017-10-13

Status: Closed
Project: MariaDB Server
Component/s: Packaging
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Tüske Máté Assignee: Daniel Black
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-15142 mariaDB starting error Closed

 Description   

Hello,

I'm building MariaDB with the yocto environment. I tried from the master branch til the morty branch but I'm always getting the "/usr/bin/mysqld_safe: line 152: mysqld_safe_helper: command not found" error. What could be wrong? mysql_safe_helper does not exist, and I have no idea where from this issue comes from.

thanx

 Comments   
Comment by Elena Stepanova [ 2017-10-11 ]

Which version is it, how exactly do you build it, and how do you install it?

Comment by Tüske Máté [ 2017-10-11 ]

I've tried several, from the master branch it was the 5.5.57, and i tried more bact to 5.5.52. Now I'm using the version 5.5.55 sources from here: http://downloads.mariadb.com/MariaDB/mariadb-5.5.55/source/ .
Since I use the yocto environment I attach the recipe: http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/mysql/mariadb.inc?h=pyro

Comment by Daniel Black [ 2017-10-11 ]

thorn looks like a yocto bug where in the mariadb.inc file 

FILES_${PN}-server

doesn't include mysqld_safe_helper

elenst
btw mariadb could take this patch http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/mysql/mariadb/0001-disable-ucontext-on-musl.patch?h=pyro based on http://www.openwall.com/lists/musl/2016/02/04/4

Comment by Tüske Máté [ 2017-10-13 ]

thank you, this solved the problem

Comment by Daniel Black [ 2017-10-13 ]

Thanks for getting back to us. If you can inform the yocto maintainers to make this change that would be appreciated too.

Comment by Tüske Máté [ 2017-10-26 ]

I did made a commit about it to the yocto. Thank you again.

Generated at Thu Feb 08 08:10:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.