Installing Mysql innodb cluster v8 with ansible - mysql

I want to install mysql v8 with ansible by downloading repo ( mysql-apt-config_0.8.15-1_all.deb )
and install it with dpkg,when i want to manually without ansible install, it prompts a window to choose version and some configs and then i should click ok for adding the repo and updating the apt repo and so on
The problem comes in when i want to install repo and mysql package with ansible
Now how can i do this and solve my problem with prompt window in ansible?
Thanks for your answer.

Related

Installing MySQL and MySQLWorkbench In Offline Red Hat 7 Machine

I am trying to install mysql workbench on a system without network. I downloaded the mysql-workbench-community, mysql-community-{server, client, common, libs} which were noted in the "Installing RPM Packages" section of MySQL Install Manual. It states that these are the standard rpm packages needed for a basic functional install of mysql community. So with that I downloaded all the rpm packages and attempted to manually install each using:
sudo rpm -ivh mysql-community-package-name.rpm
Unfortunately I keep getting dependency errors. I found this link to obtain all the dependencies for a package. So on my second attempt I ran the following:
Repoquery -R --resolve --recursive mysql-community-server | xargs -r yumdownloader
Which gave me about 100 rpm packages. I transferred them onto my machine and unfortunately more dependencies like mysql-connectors-community and mysql-=tools-community came up which were never documented or mentioned as dependencies with the script.
What am i doing wrong? Is there a way to download all the rpms and bundle them together as a custom RPM in the future? I see ubuntu has a apt-offline command mentioned here. Is there a similar method I can apply for redhat?
Update1:
I have an idea to create a container rhel7 instance, mounting /root/tmpkg and running this example. But is there another way I should consider?

Can't install phpmyadmin to AlmaLinux 8.7 via Putty (Can't find phpmyadmin, when installing)

I am trying to get phpmyadmin installed with yum. I am a beginner regarding this and I have sofar managed to install the EPEL repo and also remi. But when I try to execute yum install phpMyAdmin it tells me it can't be found. I am thankful for any response!
I have tried many different things including what is shown in the picture, but also here it tells me that the php72w-fpm and php72w-opcache cannot be found.
enter image description here
php72w package are from webtatic which is a dead project for 3 years and does not provide anything for EL-8 or EL-9
For a proper configuration / usage of "remi" repository, follow the wizard instructions.
phpMyAdmin is in "remi" repository, which is not enabled by default as it replace some base packages.
So, once PHP is installed
dnf --enablerepo=remi install phpMyAdmin

Cannot retrieve and install ejabberd contribution modules

I have installed ejabberd 16.03 from binary source (ejabberd-16.03-osx-installer.app.zip)
My os is OS X Yosemite
After installation completed I started ejabberd:
cd ejabberd_directory/bin
./ejabberdctl start
I even checked the status to make sure it is started. Then I tried to retrieve the list of available modules:
./ejabberdctl modules_update_specs
and it says ok!
But I get nothing by running this:
./ejabberdctl modules_available
And I cannot install any module.
I would appreciate any help..
Github made some changes and we have to adapt the code to be able to install modules again. You will need ejabberd 16.06 to use this feature.
Workaround:
./ejabberdctl modules_update_specs
this command creates an empty folder ~/.ejabberd_modules/sources
cd ~/.ejabberd_modules/sources
git clone https://github.com/processone/ejabberd-contrib.git
and then you get module list and install them:
./ejabberdctl modules_available
But keep in mind that running ./ejabberdctl modules_update_specs will empty your sources folder and delete the modules.

Mercurial on Jenkins, installing and configuring

I have a Mercurial repository (on Bitbucket) with some code (Java) and I want to do CI builds on a cloud-based Jenkins server (at Jelastic, running on CentOS). My problem is that I haven't been able to do a proper installation of Mercurial on the Jenkins server.
The Jenkins build fails with the following message:
ERROR: Failed to clone https://bitbucket_jenkins_user:some_password#bitbucket.org/repo_owner/my_repository because hg could not be found; check that you've properly configured your Mercurial installation
Setup information
It's a private Mercurial repository, hosted at Bitbucket
In Bitbucket I have set up a Service to trigger the Jenkins build, after a Push has happened
I have defined a specific bitbucket jenkins user in my Mercurial repository, it has only read rights and it logs in using simple https authentication
Jenkins runs on a Tomcat 7, hosted in a Jelastic cloud environment, on CentOS 6
The Mercurial plugin was installed through the Jenkins interface, by Manage plugins
The build is configured as being triggered remotely (by the service defined in Bitbucket)
Build results are the same when started manually and when triggered from a push to the repository
When I first did this I was under the impression that installing the Mercurial plugin in Jenkins would be enough, that it would also install the needed Mercurial binaries to be able to connect to the repository and get the code. I have realized that I was wrong and that on the Manage Jenkins / Configure System page I need to specify my Mercurial installation.
Questions
Is it possible to create a Mercurial installation without ssh access and doing a "yum install mercurial"?
In the Jenkins interface, what can I specify when choosing the "Install Automatically" option?
When defining an installer, I have experimented with the "Extract zip/tar.gz" option, but what can I write as the "Download URL for binary archive"?
Jenkins also offers an installer option of "Run command". What kind of commands could that be, maybe a "yum install ..." or "rpm ..."?
Since my server is cloud based, getting ssh access is a paid add-on which I would prefer to avoid. But if that is my only option I will of course do it, thereby getting access to running commands on the server. However, running "yum install mercurial" on Centos seems to only give the 1.4 version of Mercurial. Current version when I write this is 2.6.3, would I need to download the sources and compile it myself or is it possible to get that as a binary for Centos somewhere?
The Mercurial Plugin page has a section on how to use the Auto Installation options to install Mercurial using ArchLinux packages.
"The plugin supports generic tool auto-installation methods for your Mercurial installation, though it does not publish a catalog of Mercurial versions. For users of Linux machines (with Python preinstalled), you can use ArchLinux packages. For example, in /configure under Mercurial installations, add a Mercurial installation with whatever Name you like, Executable = INSTALLATION/bin/hg, Install automatically, Run Command, Label = linux (if desired to limit this to slaves configured with the same label), Command = [ -d usr ] || wget -q -O - http://www.archlinux.org/packages/extra/i686/mercurial/download/ | xzcat | tar xvf - (or …/x86_64/… for 64-bit slaves), Tool Home = usr, and configure a job with this installation tied to a Linux slave."
see https://wiki.jenkins-ci.org/display/JENKINS/Mercurial+Plugin

What is a yum package conflict?

When running the transaction check to install mysql i'm getting:
Processing Conflict: mysql55-5.5.29-1.w6.x86_64 conflicts mysql < 5.5
I guess this means i'm attempting to install a package called mysql55-5.5.29-1.w6.x86_64 on to a system with mysql already installed but somehow there is a conflict?
yum says that mysql isn't installed so it was installed without using the repositories. In that case how does yum know there is confict?
it would be good to better under what 'confict' means.
There are many online yum repo available and all are free opensource contribute. So source packages are compiled with different options in each repo. So when we add 2 or more yum repo at a time, it may happen that 2 or more packages are of same version are selected and we get a conflict error.
In your case you added some repo which is providing mysql 5.5 which is already available with some other name in some other repo or already installed but new mysql package is selected by yum for any other package as dependency. Try removing one of the repo or try installing it as yum install mysql-5.5*
You can try this : yum list | grep mysql. It will list mysql in different packages, then you can make a decision to remove one of them and install mysql again.