installing percona server on mac OS Symbol not found: _clock_gettime - mysql

I recently installed percona-server through brew and got this exception when running mysql.server start:
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
Referenced from: /usr/local/Cellar/percona-server/5.7.16-10/bin/mysqld
Expected in: /usr/lib/libSystem.B.dylib
What's going on?

For the moment, until the patch will be released, manually editing the source code as described in this pull request will fix this issue.
Then I did:
1) Edit the the source code percona-server.rb (vim /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/percona-server.rb) adding lines following lines at line 76 more or less (after ']' and before '# PAM...')
if MacOS.version == "10.11" && MacOS::Xcode.installed? && MacOS::Xcode.version >= "8.0"
args << "-DHAVE_CLOCK_GETTIME:INTERNAL=0"
end
2) Reinstall with modified source:
brew reinstall -s percona-server
3) Start the server
mysql.server start
or to start automatically the service at boot time
brew services start percona-server
For me worked, waiting from pull to be released...
Thanks for #njt1982 which create the pull and share how to do those things and mostly to #ilovezfs which create/share the patch for some packets still useful for those issues!
SR

So apparently there were issues using el capitan and what solved my problem was brew installing percona-server56 as so:
brew uninstall percona-server
brew install percona-server56

Related

Wireguard refuses to run on Fedora 31: protocol not supported

I recently install wireguard-tools and restarted my machine several times. However, it will simply not run. I get this error every time:
Warning: `/etc/wireguard/myprovider.conf' is world accessible
[#] ip link add myprovider type wireguard
Error: Unknown device type.
Unable to access interface: Protocol not supported
[#] ip link delete dev myprovider
Cannot find device "provider"
I then ran dkms status and it came up entirely blank, even after a restart. Looking online, it doesn't seem like anyone else's dkms went blank. My kernel version is 5.5.13-200.fc31.x86_64, which is the latest I can go to. I've tried the general advice of cleaning packages, updating and then reinstalling wireguard but it has not worked. What should I do from here? Does this require a reinstall of the whole OS?
What does modinfo wireguard show?
Wireguard is included Linux 5.6 and higher. On your 5.5 kernel you'll need to install the a kernel module.
I'm a Debian user, but on fedora this should work:
$ sudo dnf copr enable jdoss/wireguard
$ sudo dnf install wireguard-dkms wireguard-tools
wireguard-tools only install's the tools, wireguard-dkms the kernel module, this will do the actual work.
reference
I solved it by upgrading wireguard :
sudo apt-get upgrade wireguard
Here is the terminal results:
(...)
Preparing to unpack .../92-wireguard-dkms_1.0.20200520-0ppa1~18.04_all.deb ...
-------- Uninstall Beginning --------
Module: wireguard
Version: 1.0.20200401
Kernel: 5.3.0-46-generic (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
wireguard.ko:
- Uninstallation
- Deleting from: /lib/modules/5.3.0-46-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
DKMS: uninstall completed.
-------- Uninstall Beginning --------
Module: wireguard
Version: 1.0.20200401
Kernel: 5.3.0-51-generic (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
wireguard.ko:
- Uninstallation
- Deleting from: /lib/modules/5.3.0-51-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 1.0.20200401
completely from the DKMS tree.
------------------------------
Done.
(...)
Then sudo wg-quick up {conf_name} worked again.

404 error when using brew to install mysql - macOS Sierra

This question has been asked before here (404 error when using brew to install mysql), but unfortunately the fix doesn't work for me. I have already ran brew update, so I'm up to date.
I'm on the latest version of MacOS 10.12 and I am running Xcode 8 if that matters.
brew install mysql
Warning: You are using OS X 10.12.
We do not provide support for this pre-release version.
You may encounter build failures or other breakages.
==> Downloading https://cdn.mysql.com/Downloads/MySQL-5.7/mysql-boost-5.7.11.tar.gz
curl: (22) The requested URL returned error: 404 Not Found Error:
Failed to download resource "mysql" Download failed:
https://cdn.mysql.com/Downloads/MySQL-5.7/mysql-boost-5.7.11.tar.gz
I know it says this is a pre-release version, but is there any hope here?
Thanks
The 5.7.11 mysql download you reference no longer exists (it certainly is 404).
Looking at the homebrew formula for mysql, it has been updated to point to the latest mysql version.
So it seems that you are not in fact up to date. Try running brew update twice, then brew doctor and fix any warnings.
There have been some big changes in homebrew over the last 9 months, if you have an old install it might be easier to uninstall totally. There are also several ownership and directory location changes that need to be straightened out with the upgrade to homebrew 1.0
I followed the steps laid out here: Brew Update not working after mac 10.9
In case that's not visible anymore, here's that answer:
cd `brew --prefix`
git fetch origin
git reset --hard origin/master
After that, you should be able to brew update and then brew install mysql
For those who are still struggling to resolve this.
Please try:
brew update-reset
brew update
I found this gem here.
P.S.: If you have a shallow clone, after brew update-reset command, run the following command to unshallow:
git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core fetch --unshallow

Homebrew - can't install Sphinx

I'm trying to get Sphinx (and thinking Sphinx working). It have worked before - but it stopped working tonight after my colleague installed Node, php and some other stuff.
It first complained about a locked pid file:
FATAL: failed to lock pid file
After this I tried to reinstall Sphinx:
brew uninstall sphinx
And:
brew install sphinx.
I already have mysql so I skipped --mysql. This results in the following:
This is not sphinx - the Python Documentation Generator.
To install sphinx-python: use pip or easy_install,
Sphinx has been compiled with libstemmer support.
Sphinx depends on either MySQL or PostreSQL as a datasource.
You can install these with Homebrew with:
brew install mysql
For MySQL server.
brew install mysql-connector-c
For MySQL client libraries only.
brew install postgresql
For PostgreSQL server.
We don't install these for you when you install this formula, as
we don't know which datasource you intend to use.
When running searchd I get this:
FATAL: no readable config file (looked in /usr/local/Cellar/sphinx/2.2.6/etc/sphinx.conf, ./sphinx.conf).
And when trying to start thinking-sphinx for my rails app I get:
Failed to start searchd. Check the log files for more information.
And the log file still says:
FATAL: failed to lock pid file
I'm not sure what is causing this, or how I can fix it. Thought that reinstalling Sphinx would be enough - but I'm stuck at square one.
Any ideas on how I can get it to work again?
How about uninstalling sphinx and giving this a go:
brew install sphinx --pgsql --mysql

OSX Lion Homebrew "brew install mysql -v" problems

I am working to install mysql locally using home brew and it keeps blowing up. When I run brew doctor I do not get any errors, and the full verbose output of attempting to install mysql is https://gist.github.com/2424859, ending with:
MAKEFLAGS: -j4
Error: Failed executing: cmake . -DCMAKE_INSTALL_PREFIX=/usr/local/Cellar/mysql/5.5.20 -DMYSQL_DATADIR=/usr/local/var/mysql -DINSTALL_MANDIR=/usr/local/Cellar/mysql/5.5.20/share/man -DINSTALL_DOCDIR=/usr/local/Cellar/mysql/5.5.20/share/doc/mysql -DINSTALL_INFODIR=/usr/local/Cellar/mysql/5.5.20/share/info -DINSTALL_MYSQLSHAREDIR=share/mysql -DWITH_SSL=yes -DDEFAULT_CHARSET=utf8 -DDEFAULT_COLLATION=utf8_general_ci -DSYSCONFDIR=/usr/local/etc -DWITH_UNIT_TESTS=OFF -DWITH_READLINE=yes (mysql.rb:77)
These existing issues may help you:
https://github.com/mxcl/homebrew/issues/8063
https://github.com/mxcl/homebrew/issues/9142
https://github.com/mxcl/homebrew/issues/11710
https://github.com/mxcl/homebrew/issues/11754
Otherwise, please report the bug:
https://github.com/mxcl/homebrew/wiki/reporting-bugs
. I am running osx lion, full xcode 4.3.2.
any ideas on what the primary issue is?
after posting on the homebrew github issues:https://github.com/mxcl/homebrew/issues/11762
here is how I fixed the issue:
cd /usr/local
brew uninstall cmake
git checkout 948c2769 Library/Formula/cmake.rb
brew install mysql

Rails/Mysql2/Lion [FATAL] failed to allocate memory

I seem to be getting this issue when trying to run a Rails 3.x site with POW using the mysql2 gem and on OSX Lion.
[FATAL] failed to allocate memory
Also I am running Rails 2.x apps successfully with the same setup under POW.
I'm assuming this is an issue related to Lion + MySQL2 as other errors seem to indicate this to be the source but I can't seem to locate the issue.
Any ideas?
I had the same problem when I used to mysql-connector-c & mysql. The problem was in mysql-connector-c which had old dylib. So problem resolved by removing mysql-connector-c, the next you have to change shell variable DYLD_LIBRARY_PATH or make symbol link for libmysqlclient.18.dylib. You should reinstall mysql2 gem after this.
To change DYLD_LIBRARY_PATH insert export DYLD_LIBRARY_PATH=/usr/local/Cellar/mysql/5.5.20/lib/:$DYLD_LIBRARY_PATH in your ~/.baschrc and reload shell
To make symbol link for libmysqlclient.18.dylib evaluate in your shell this command:
ln -s /usr/local/Cellar/mysql/5.5.20/lib/libmysqlclient.18.dylib /usr/local/lib/
I used here directory where my mysql installed. Change it to your's if you have another mysql location.
This turned out to be a problem with node (installed using Homebrew) for me.
So I uninstalled and reinstalled node using Homebrew
first:
brew uninstall node
then:
brew install node