I am trying to update cygnus to the last version.
My curent version is 0.13.
when I try to install cygnus-common and cygnus-ngsi I got the error no package is available:
$ sudo yum install cygnus-common
Loaded plugins: fastestmirror
Fiware | 951 B 00:00:00
Loading mirror speeds from cached hostfile
* base: distrib-coffee.ipsl.jussieu.fr
* extras: distrib-coffee.ipsl.jussieu.fr
* updates: mirror.in2p3.fr
No package cygnus-common available.
Error: Nothing to do
My Fiware yum configuration repo is under this file "/etc/yum.repos.d/fiware.repo"
[Fiware]
name=FIWARE repository
baseurl=http://repositories.testbed.fi-ware.eu/repo/rpm/x86_64/
gpgcheck=0
enabled=1
what have I missed?
Thanks in advance for your help!
The pakages are now in the FIWARE repository. Specifically:
cygnus-common_hadoopcore_1.2.1-1.2.0-0.gbd4790e.x86_64.rpm
cygnus-ngsi-1.2.0-0.gbd4790e.x86_64.rpm
I.e. those about the 1.2.0 version of Cygnus.
Related
I am trying to configure Cygnus in my FIWARE instance. Following the readthedocs tutorial I execute the following command:
yum install java-1.7.0-openjdk-devel
And the following error is listed:
Loaded plugins: fastestmirror, presto
Setting up Install Process
Loading mirror speeds from cached hostfile
*base: mirror.gadix.com
*epel: mirror.airenetworks.es
*extras: mirror.gadix.com
*updates: mirror.airenetworks.es
http://repositories.lab.fiware.org/repo/rpm/6/repodata/repomd.xml:
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
Error: Can not retrieve repository metadata (repomd.xml) for repository: fiware. Please verify your path and try again
Anyone have any idea what it can be and how to solve it? I'm new to Linux environment.
It is working fine for me, please refer to this answer to clean the metadata and try installing again.
RHEL documentation mentions similar commands for OpenJdk devel installation.
or run the following commands and try installing it again:
yum clean all
yum makecache
yum update
Java version was changes in the past and newest Cygnus version (1.12.0 by the time being) uses Java 1.8, so probably you should run:
yum install java-1.8.0-openjdk-devel
I'd recommend to have a look to the RUN statement in Dockerfile. The same procedure used to build the docker container can be done to do local installations of Cygnus.
I'm trying to install Google-Chrome on CentOS7(Linux 3.10.0-514.el7.x86_64).
The file (libappindicator3.so.1()(64bit)) is needed, but there is no such file on the https://pkgs.org/.
So please help me fix this problem, thanks.
[leohu#SpaceX Downloads]$ rpm -ivh google-chrome-stable_current_x86_64.rpm
warning: google-chrome-stable_current_x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY
error: Failed dependencies:
libappindicator3.so.1()(64bit) is needed by google-chrome-stable-66.0.3359.117-1.x86_64
Google-Chrome : The file (libappindicator3.so.1()(64bit)) is needed
"libappindicator-gtk3" is in the EPEL repo https://fedoraproject.org/wiki/EPEL
# yum install epel-release (the "extras" must be enabled)
# yum install libappindicator-gtk3
If any issues, you can get the latest epel repo files = epel-release-7-11.noarch.rpm from https://mirrors.dotsrc.org/fedora-epel/7/x86_64/Packages/e/epel-release-7-11.noarch.rpm ... and do # yum install Downloads/epel-release-7-11.noarch.rpm ... ( The version in "extras" is currently epel-release-7-9.noarch ).
Trying to install Bolt v2.2.4 with the following commands:
git clone git://github.com/bolt/bolt.git bolt
cd bolt
git checkout v2.2.4
composer install
Then I get the following error:
$ composer install
Loading composer repositories with package information
Installing dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for m6web/symfony2-coding-standard dev-master#dev -> satisfiable by m6web/symfony2-coding-standard[dev-master].
- m6web/symfony2-coding-standard dev-master requires squizlabs/php_codesniffer ~1.0 -> no matching package found.
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.
Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
I just ran into the same issue under bolt 2.1.9
I 'fixed' it for me for the moment by changing 1.5.* to ~2 for squizlabs/php_codesniffer in composer.json
Are you on IPv6 per chance? If so, do a composer self-update.
I read this article in fedoramagzine.org and followed the process. Since then I am unable to perform updates, installation etc from both yum and dnf.
This is the error I get from DNF
Abhinav#localhost ~$ sudo dnf update
[sudo] password for Abhinav:
Error: Failed to synchronize cache for repo 'fedora' from
'https://mirrors.fedoraproject.org/metalink?repo=fedora-21&arch=x86_64':
Cannot prepare internal mirrorlist: Curl error: Timeout was reached
for
https://mirrors.fedoraproject.org/metalink?repo=fedora-21&arch=x86_64
[Connection timed out after 120002 milliseconds]
and this is the error I get when using YUM
Abhinav#localhost ~$ sudo yum update Loaded plugins: langpacks
One of the configured repositories failed (Fedora 21 - x86_64), and
yum doesn't have enough cached data to continue. At this point the
only safe thing yum can do is fail. There are a few ways to work
"fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable fedora
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=fedora.skip_if_unavailable=true
Cannot retrieve metalink for repository: fedora/21/x86_64. Please
verify its path and try again
I even emptied all the repos in /etc/yum.repos.d except for the original 3 repos you get when you install distro.
UPDATE ::
#Etan Reisner Here is the output of rpm -qa nss\*
Abhinav#localhost ~$ rpm -qa nss\*
nss-softokn-freebl-3.17.3-1.fc21.x86_64
nss-util-devel-3.17.3-1.fc21.x86_64 nss-sysinit-3.17.3-2.fc21.x86_64
nss-util-3.17.3-1.fc21.x86_64 nss-tools-3.17.3-2.fc21.x86_64
nss-softokn-freebl-3.17.3-1.fc21.i686 nss-3.17.3-2.fc21.x86_64
nss-softokn-freebl-devel-3.17.3-1.fc21.x86_64
nss-mdns-0.10-15.fc21.x86_64 nss-mdns-0.10-15.fc21.i686
nss-util-3.17.3-1.fc21.i686 nss-softokn-3.17.3-1.fc21.i686
nss-devel-3.17.3-2.fc21.x86_64 nss-softokn-devel-3.17.3-1.fc21.x86_64
nss-3.17.3-2.fc21.i686 nss-softokn-3.17.3-1.fc21.x86_64
UPDATE 2
Formatted my laptop and re-installed Fedora 21. After 3 sudo dnf updates. I am stuck with this problem again. This time i didn't follow the steps on the previous article.
On further google search I found https://fedorahosted.org/fedora-infrastructure/ticket/4517 which talks about same error. It is closed but I can't find a proper solution again.
If you sit behind a proxy, you have to configure dnf accordingly. (Even if the user's proxy settings are fine, you have to set them for dnf anyway.) The dnf settings are stored in /etc/dnf/dnf.conf. The syntax is:
proxy=<protocol>://<ip or name>:<port>
If this is not your problem, try to download the metadata with the browser to ensure, that your network connection to the url is working.
The file to receive should be an xml file. If you cannot download the metadata via the browser, chances are, that either port 443 (for https) is blocked or there is something wrong with your internet connection.
Issue
Had similar errors with kubernete (k83) while starting Fedora 23 VM master with vagrant
Error: Failed to synchronize cache for repo 'updates' from
System Spec
OS
Darwin Kernel Version 15.6.0: Wed Nov 2 20:30:56 PDT 2016; root:xnu-3248.60.11.1.2~2/RELEASE_X86_64 x86_64
Vagrant
Installed Version: 1.9.2 Latest Version: 1.9.2
Fedora
Fedora23 x86_64
RCA
While logged into fedora23VM , running yum update in verbose mode
sudo yum --verbose update a curl timeout on downloading from each of the repository presented in the metalink.
e.g
error: Curl error (56): Failure when receiving data from the peer for http://ftp.polytechnic.edu.na/pub/fedora/linux/updates/23/x86_64/repodata/af3c46471b1d685f22c72a5e16d7383d333fb89db278711b2b8c794e29a91eaa-filelists.xml.gz [Recv failure: Connection reset by peer] (http://ftp.polytechnic.edu.na/pub/fedora/linux/updates/23/x86_64/repodata/af3c46471b1d685f22c72a5e16d7383d333fb89db278711b2b8c794e29a91eaa-filelists.xml.gz).
2.Tried curl download without the ssl certificate verification and it worked
i.e
curl -k -O https://www.ftp.saix.net/linux/distributions/fedora/linux/updates/23/x86_64/repodata/repomd.xml
Solution
Disable ssl certificate verification during the yum update i.e
sudo yum --verbose update --setopt "sslverify=0" -y
I am facing an issue between the Zenoss core installation and MySQL rpms.
The Zenoss core installation won't complete, complaining about mysql-client and mysql-shared versions, even though I have newer versions installed. As suggested in this Quest/answer ,
I also tried to install a 5.5.41 client package but it did not change anything. Here's the situation:
[root#bstfe1032 Zenoss]# yum -y --nogpgcheck localinstall zenoss-4.2.0.el6.x86_64.rpm
[...]
--> Finished Dependency Resolution
Error: Package: zenoss-4.2.0-1586.el6.x86_64 (/zenoss-4.2.0.el6.x86_64)
Requires: mysql-client >= 5.5.13
Error: Package: zenoss-4.2.0-1586.el6.x86_64 (/zenoss-4.2.0.el6.x86_64)
Requires: mysql-shared >= 5.5.13
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root#bstfe1032 Zenoss]# rpm -qa|grep -i mysql
MySQL-client-5.6.22-1.el6.x86_64
MySQL-server-5.6.22-1.el6.x86_64
MySQL-shared-5.6.22-1.el6.x86_64
The Zenoss core install doc points to MySQL packages from mysql.org and this is where I got them.
Any idea of what I should try next ? I am using CentOS 6, this is a testbed and not a production machine because I wanted to give Zenoss core a test drive.
You are mixing "old" packages (zenoss-4.2.0) with too new one (MySQL 5.6) and it's not probably handled correctly in Zenoss core packages.
The best option for you is to use autodeploy script - https://github.com/zenoss/core-autodeploy/blob/4.2.5/core-autodeploy.sh
It will download last Zenoss packages from http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/
and MySQL packages from ftp://mirror.anl.gov/pub/mysql/Downloads/MySQL-5.5/
See http://wiki.zenoss.org/Install_Zenoss for more information.