centos mongodb package not signed - linux

ok this might be a stupid question and this is because centos is not part of my "strong points list" but i am trying to install mongodb and mongodb-server
i followed the steps found here
a link!
they missed a step ... what happens if after centos downloads the packages ... it tells me that they are not signed
i also tried importing this gpg key (as a last desperate attempt before coming here)
a link!
so how do i get pass this? :(
thanks,
Rares

This is what worked for me to ignore "package not signed" message:
yum install --nogpgcheck <your-package-name>
Changing gpgcheck to 0 in /etc/yum.conf didn't help. Security warning: you should use this option ONLY if you trust the installation sources.

You are correct, the package is not signed. It is planned to be done in the future, and the relevant tracking ticket for the implementation of signing is SERVER-8770 (for watching and voting purposes) but there is no definite timeframe for implementation as of writing this response.
Hence, you must install with gpgcheck=0 for the time being as noted on the page you linked to: Install MongoDB on Redhat/CentOS/Fedora

Related

how to update etherpad-lite properly?

I keep totally failing to update an etherpad-lite server. The problem: Even a Google search for the update procedure brings up hardly any information, only that one should run "git pull origin".
I have now tried this in many different ways. The update usually works, but afterwards one of these errors occurs:
Plugins can no longer be installed
The service can no longer be started (TypeError: log4js.replaceConsole is not a function)
The entire admin panel no longer works.
I tried uninstalling or updating all plug-ins before, but both hardly brought any improvements, only other errors. The update of the plugins in the admin console fails, I tried it via the updatePlugins.sh script. Here a message appears that at least etherpad-lite 1.8,6 must be installed. I am currently at version 1.8.4 and would like to update to the latest version 1.8.12. However, some of the plug-ins are still updated. A very strange behaviour.
I would be happy if someone could tell me how to properly update the etherpad-lite instance step by step. (ubuntu 20)
Thank you!
I have recently updated Etherpad-lite from version 1.8.6 to 1.8.13.
For me, executing git pull origin and then checking out the 1.8.13 release tag, with git checkout 1.8.13, made the work.
It is important, despite having Etherpad configured as a service, to run it for the first time using:
src/bin/run.sh.
Node v12.22.1
npm 6.14.12
Ubuntu 20.04.2
I hope it has been useful to you.

Why does pip3 want to create a kdewallet after installing/updating packages on Ubuntu 20.04?

I recently updated my system from Ubuntu 18.04 to 20.04. Afterwards I tried to update all of my pip3 packages using the shell command mentioned here (I changed "pip" to "pip3").
After it updated a couple of packages, this prompt came up:
KDE Wallet Service
Since I never saw it while updating/installing a package, I cancelled it which resulted in an instant reopening of the same prompt and the terminal showed following warning:
WARNING: Keyring is skipped due to an exception: Failed to unlock the keyring!
I pressed CTRL+C after the same happend with the next package it tried to install. Ever since when I try to install a package the same happens.
Example:
pip3 install numpy
WARNING: Keyring is skipped due to an exception: Failed to unlock the keyring!
WARNING: Keyring is skipped due to an exception: Failed to unlock the keyring!
Collecting numpy
WARNING: Keyring is skipped due to an exception: Failed to unlock the keyring!
Using cached numpy-1.19.2-cp38-cp38-manylinux2010_x86_64.whl (14.5 MB)
Installing collected packages: numpy
WARNING: The scripts f2py, f2py3 and f2py3.8 are installed in '/home/gesuchter/.local/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed numpy-1.19.2
I already tried to fix my issue with reinstalling python3-pip.
Here are hopefully some helpful information:
pip3 --version
pip 20.0.2 from /usr/lib/python3/dist-packages/pip (python 3.8)
ls ~/.local/share/keyrings
default login.keyring user.keystore
find ~/.config/kwalletrc
find: ‘/home/gesuchter/.config/kwalletrc’: No such file or directory
This solved it for me:
python3 -m keyring --disable
Running it adds:
[backend]
default-keyring=keyring.backends.null.Keyring
to the file ~/.config/python_keyring/keyringrc.cfg.
Presumably PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring mentioned at https://stackoverflow.com/a/68504137/895245 offers an environment variable way to achieve the same result.
Without this, it would show the annoying KDE keyring popup every time I try to install a package:
Google, index this:
The KDE Wallet System
The application '/usr/lib/python3/dist-packages/pip/__main__.py' has requested to create a new wallet named 'kdewallet'. This is used to store sensitive data in a secure fashion. Please choose the new wallet's type below or click cancel to deny the application's request.
Classic, blowfish encrypted file
Use GPG encryption, for better protection
Related: https://askubuntu.com/questions/1205161/annoying-kde-wallet-service-popup-the-application-kded5-has-requested-to-open
Tested on Ubuntu 21.04, Python 3.9.5, pip3 20.3.4, keyring==22.2.0.
This issue was reported upstream, see https://github.com/pypa/pip/issues/8090 and the other issues linked from that thread.
tl;dr: new versions of pip too eagerly search keyrings for credentials that might be required to access some package downloads. If it ends up querying a keyring (such as kdewallet) which doesn't exist yet, the prompt you noticed shows up. It's not yet clear how exactly and in which release this will be fully fixed.
EDIT: Please note that stackoverflow is not the right place for bug reports: pip maintainers are unlikely to see this, and as far as I can tell it's also not really in scope for stackoverflow. It could be a question for another stackexchange community (superuser maybe?). But since you were already sure that this was a problem with pip, the best place for a report would have been any of the communication channels indicated in the README on https://github.com/pypa/pip
You can add this to your startup file
export PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring
Credit to jrd's comment on a python bug

CentOS 7 ask for cabextract even when is installed

I wanted to install msttfonts on CentOS 7. Following this guide everything goes fine, until I got to run the command:
# rpmbuild -bb msttcorefonts-2.5-1.spec
The system then throws this message:
cabextract is needed by msttcorefonts-2.0-1.noarch
It is pretty obvious that I've to install cabextract, so I did. By Downloading source from here, extracting, and then ./config... make... make install... (you know guys: all the routine). And I confirm the installation was successful with
# cabextract --version
Which answers with
cabextract version 1.6
So, I go back with my command rpmbuild... But the system stills answer me
cabextract is needed by msttcorefonts-2.0-1.noarch
And now, the questions:
What I'm doing wrong? Do I need to reboot the server? Is there a kind of command to tell the server "hey! this cabextract thing is already installed"?
... and well, while I was writting this question, I could resolve it thanks to this post. So I just leave this question just for further reference.
Thanks in advance.
You need to install the cabextract package (by running yum install cabextract).
The message you are seeing is a dependency error: the msttcorefonts-2.5-1.spec file lists a dependency on cabextract, but because you have installed it from source there is no information about it in the local packages database.

sudo dpkg -i mod-pagespeed-*.deb giving "not a debian format archive" error

The following apparently trivial two initial steps to install mod-pagespeed resulted in the error,
'mod-pagespeed-stable_current_amd64.deb' is not a debian format archive
even though the first (wget) step appeared to work properly.
wget https://dl-ssl.google.com/dl/linux/direct/mod-pagespeed-stable_current_amd64.deb
sudo dpkg -i mod-pagespeed-*.deb
What might be going wrong and how to fix that?
In my case the .deb file was much smaller than expected and its content indicated that "this product is not available in your country," even though the server was meant to be in the UK, and https://www.countryipblocks.net/ agreed that it was in the UK. (http://whatismyipaddress.com/ip-lookup said it was in the US.)
The solution was simply to go to the Google download page for the module, https://developers.google.com/speed/pagespeed/module/download, do a local download (eg right click the appropriate link and do "Save link as ..." in Firefox), and then upload that to the server.
It then built fine.
(I found this solution in a comment about a different problem at http://www.turnkeylinux.org/forum/support/20120514/how-do-i-install-modpagespeed, which speculated that "server's IP was somehow mistraced by Google to some weird country or something" - could this be the underlying cause?)
Edit: Possible gotcha: Later problems with apt-get update with a GPG error (fatal) with the mod-pagespeed installation being the very smoky gun. It was a mess to sort out.

How to resolve "Error code: sec_error_invalid_algorithm"?

I am failed to load Google in my Firefox and getting the following error :
error
Secure Connection Failed.
An error occurred during a connection to WWW.Google.com.
security library: invalid algorithm.
** (Error code: sec_error_invalid_algorithm)**
The page you are trying to view cannot be shown because the authenticity of the received
data could not be verified.
Please contact the website owners to inform them of this problem. Alternatively, use the
command found in the help menu to report this broken site.
This problem came after i had tried to install Google chrome.I am using centos6.
How can I solve this?
This is a bug and it is mentioned for CentOS. Please see the url :- http://osdir.com/ml/centos/2013-11/msg00670.html
It would be better if you can use firefox only or try to use an alternative old version of chrome compatible with CentIS.
Thanks & Regards,
Alok Thaker
I had the same issue after installing Skype v4.3 on a Centos 6.4 system. Seems the issue was the lack of nss-softokn* and nss-softokn-freebl* packages.
You can check if theses packages are installed with:
rpm -qa | grep nss-softokn
You can install the packages like so:
yum install nss-softokn*

Resources