I am running a shell script that installs elasticsearch. I was previously running 7.x on the ec2 instance and I'm upgrading to version 8.
When I run the script, I get the message that a configuration file has changed with the below instructions.
Since I can't select anything, it defaults to keeping my current version and that's not what I want.
I want to install the package maintainer's version.How can I run my script to automate the process?
Instruction that pops up during installation
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
**deployment script that handles elasticsearch installation **
Yes | Sudo DEBIAN_FRONTEND=noninteractive apt-get install elasticsearch
Yes|Sudo apt-get
I tried adding a yes to my sudo apt-get hoping to automate every interaction. I also turned off Debian interaction.
Yes | Sudo DEBIAN_FRONTEND=noninteractive apt-get install elasticsearch
Related
As stated in documentation, plugins can be installed through the following command:
$ sudo bin/elasticsearch-plugin install analysis-icu
However, when installing with more than one plugins, the system prompted the followings
$ sudo bin/elasticsearch-plugin install analysis-icu repository-s3
ERROR: Found multiple arguments for option [arguments], but you asked for only one
https://github.com/elastic/elasticsearch/blob/master/docs/plugins/plugin-script.asciidoc
As of the latest version ES 7.5.2, you can only install one plugin at a time.
The ability to install multiple plugins at once has been added very recently and will only be available from ES 7.6 onwards, which has not yet been released. 7.6 should be coming out anytime now since there are only 2 issues and 4 PRs left open. Stay tuned...
I'm on Fedora 30. I am trying to install "epel-release".
I am following this guide: https://www.phusionpassenger.com/library/install/standalone/install/oss/el7/ -- I am unable to successfully run the command:
$ sudo yum install -y epel-release yum-utils
I get as a result:
No match for argument: epel-release
So, I tried the following commands from this article: https://www.liquidweb.com/kb/enable-epel-repository/
$ cd /tmp
$ wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
$ yum install ./epel-release-latest-*.noarch.rpm
No such luck - this is the output:
Error:
Problem: problem with installed package fedora-release-workstation-30-1.noarch
- package epel-release-7-11.noarch conflicts with fedora-release provided by fedora-release-workstation-30-1.noarch
- package epel-release-7-11.noarch conflicts with fedora-release provided by fedora-release-workstation-30-4.noarch
- conflicting requests
I have also tried:
$ sudo dnf install epel-relase
which that didn't work either, here's the results:
No match for argument: epel-release
Error: Unable to find a match
I have come across several different articles basically saying to either use the first command listed or variations of the second command I've tried - all unsuccessful. side note: Is this because Fedora 30 was just "recently" released?
My end goal is to deploy a Ruby on Rails web app internally using Nginx. For that, I am following this guide: https://www.phusionpassenger.com/library/walkthroughs/deploy/ruby/ownserver/nginx/oss/el7/deploy_app.html
Any direction for how to install epel-release would be great as I can't move forward until passenger is installed.
Note that EPEL is not suitable for use in Fedora! Fedora is not Enterprise Linux. EPEL provides "a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL)". Put simply, Enterprise Linux is a term that refers to Red Hat Enterprise Linux or one of its clones. And Fedora is not a Red Hat clone.
That is why you cannot install the "epel-release" package in Fedora. It simply does not exist. Don't try to use EPEL on Fedora.
As noted before, the Fedora repositories provide most (if not all) of the EPEL packages. Additional software for Fedora is available in the RPMFusion repositories. In their own words, RPMFusion is "an extension of Fedora" that "provides software that the Fedora Project or Red Hat doesn't want to ship." RPMFusion can not be used on Enterprise Linux. You could see RPMFusion as the "EPEL alternative" for Fedora, but be aware that the software collections provided by RPMFusion and EPEL are entirely unrelated and uncomparable.
EPEL is managed from within the Fedora project, and thus part of Red Hat. RPMFusion is an independent organization. You can consider their repositories reliable, but always be cautious when you install software from external sources.
Finally - on a sidenote - on recent Fedora versions, 'dnf' has replaced 'yum'.
Okay, so turns out that this can be simplified to just:
$ sudo dnf install passenger
Crazy that they have an entire tutorial for how to install passenger when it can just be simplified to this one line.
you'll need to install the EPEL (Extra Packages for Enterprise Linux) repository.
The EPEL project is run by the Fedora team.
When you install third-party repositories on Red Hat and CentOS systems.
Install in centos:
sudo yum install yum-plugin-priorities epel-release
When the installation completes, navigate to the /etc/yum.repos.d directory,
and open the CentOS-Base.repo file in your favorite text editor.
After the last line of the base, updates, and extras sections, add the line: priority=1.
After the last line of the centosplus section, add the line:
priority=2.
Save the file and close the editor.
Now, Open the epel.repo file for editing.
After the last line of the epel section,add the line:
priority=10.
After the last line of each remaining section, add the line:
priority=11.
Update the system and then create a list of the installed and available packages by running:
sudo yum upgrade
sudo yum list > yum_list.txt
For RHEL - dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
Try with the above command to install epel-release in RHEL 8
I have nvm:
nvm ls
v8.11.3
v8.11.4
-> v11.1.0
default -> 8.11.4 (-> v8.11.4)
node -> stable (-> v11.1.0) (default)
stable -> 11.1 (-> v11.1.0) (default)
I installed yarn with:
sudo apt-get install --no-install-recommends yarn
I also added in .bashrc alias node=nodejs. But when I try yarn install I see:
Yarn requires Node.js 4.0 or higher to be installed.
How can I fix it?
This gist helped on this problem.
Run the following commands
echo "==> Installing Yarn package manager"
rm -rf ~/.yarn
curl -o- -L https://yarnpkg.com/install.sh | bash
# Yarn configurations
export PATH="$HOME/.yarn/bin:$PATH"
yarn config set prefix ~/.yarn -g
And add the following in ~/.bashrc
export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
It should then work properly without the warning after restarting the shell.
First uninstall the nodejs package:
sudo apt remove nodejs
Ubuntu 16.04 contains a version of Node.js in its default repositories that can be used to easily provide a consistent experience across multiple systems. At the time of writing, the version in the repositories is v4.2.6. This will not be the latest version, but it should be quite stable and sufficient for quick experimentation with the language.
In order to get this version, we just have to use the apt package manager. We should refresh our local package index first, and then install from the repositories:
sudo apt-get update
sudo apt-get install nodejs
If the package in the repositories suits your needs, this is all you need to do to get set up with Node.js. In most cases, you’ll also want to also install npm, which is the Node.js package manager. You can do this by typing:
sudo apt-get install npm
This will allow you to easily install modules and packages to use with Node.js.
Because of a conflict with another package, the executable from the Ubuntu repositories is called nodejs instead of node. Keep this in mind as you are running software.
To check which version of Node.js you have installed after these initial steps, type:
nodejs -v
Screenshot for nodejs version
I just want to mention that my configuration file looked something like that
export PATH=$PATH:`yarn global bin`
#NVM INITIALIZATION STUFF
(yarn docs recommended $PATH)
the export was before my nvm initialization. Which meant node was not available during the runtime of that line. So I just switched my configuration file to be
#NVM INITIALIZATION STUFF
export PATH=$PATH:`yarn global bin`
I had the same issue. by putting nvm path above yarn path didn't solve the issue then I looked up for a solution in man page and solve the issue by setting default node version on a shell.
Current lts version is v14.17.6 so i install it use it and set default node version on a shell.
nvm install --lts
nvm use --lts
nvm alias default <version>
Additional you can set always default to the latest available node version on a shell by running below command.
nvm alias node <version>
I do not know how to check for this via command line. I do know that you can do this for through the GUI; however, I want to implement this in my script. Anyone know how to do this? (I haven't found anything about this).
Ubuntu updates are managed through the apt package manager.
If you're looking to run daily updates you'll want to do something like:
sudo apt update # updates apt packages index
sudo apt upgrade # runs upgrades on all packages
I'm writing a Bash script that sets up a Drupal development environment for people using Ubuntu. To test this out I've installed a fresh copy of Ubuntu in VirtualBox and am constantly using the snapshot feature to get back my fresh install after every run of the script.
Currently however my script is re-downloading all the packages that need to be installed every time I run the script. Is there a way I can get apt-get to install these packages from local storage?
Perhaps downloading them, but not installing them at once. Taking a snapshot then, and then usage of apt-get that will use the local packages that were downloaded.
How would I go about doing this? Is there perhaps some apt-get magic that will do the trick?
apt-get --download-only install should do the trick.
Then make the snapshot, then run apt-get install again without --download-only.