thr3ads.net - Gluster users - [Gluster-users] Missing gsyncd and dependency issues with gluster on AWS AMI host [Apr 2015]

If this information is useful, please help other people find it:
Share via:

Eric Berg

2015-Apr-08 16:13 UTC

[Gluster-users] Missing gsyncd and dependency issues with gluster on AWS AMI host

I'm setting up geo-replication from a cluster in our colo facility to a
gluster cluster in amazon.  I set up the amazon instances as AMI builds
(probably a mistake), by enabling gluster epel repo from download.gluster.org.

While trying to set up geo-replication, I could not find gsyncd, so I tried to
update the existing 3.6.2-1.el6 versions, and I get the following, indicating
that a) it's looking at el7 packages, when 6 is clearly stated in the
gluster-epel.repo file and b) there are unmet dependencies for systemd-units and
rsyslog-mmjsonparse.

I'm thinking that I should just rebuild these instances as ubuntu 14.x
boxes, like the ones in our datacenter, but it might be easier to solve this
problem.

Anybody have any thoughts on the matter?

Here's the output of the install command:

# yum install -y glusterfs{-fuse,-server}
Loaded plugins: priorities, update-motd, upgrade-helper
epel/x86_64/metalink                                                            
|  16 kB     00:01
glusterfs-epel/x86_64                                                           
| 2.9 kB     00:00
Not using downloaded repomd.xml because it is older than what we have:
  Current   : Fri Jan 23 06:00:21 2015
  Downloaded: Fri Jan 23 06:00:19 2015
glusterfs-noarch-epel                                                           
| 2.9 kB     00:00
Not using downloaded repomd.xml because it is older than what we have:
  Current   : Fri Jan 23 06:00:23 2015
  Downloaded: Fri Jan 23 06:00:20 2015
# Place this file in your /etc/yum.repos.d/ directory
975 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package glusterfs-fuse.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-fuse.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: glusterfs = 3.6.2-1.el7 for package:
glusterfs-fuse-3.6.2-1.el7.x86_64
---> Package glusterfs-server.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-server.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: glusterfs-libs = 3.6.2-1.el7 for package:
glusterfs-server-3.6.2-1.el7.x86_64
--> Processing Dependency: glusterfs-cli = 3.6.2-1.el7 for package:
glusterfs-server-3.6.2-1.el7.x86_64
--> Running transaction check
---> Package glusterfs.x86_64 0:3.6.2-1.el6 will be updated
--> Processing Dependency: glusterfs = 3.6.2-1.el6 for package:
glusterfs-api-3.6.2-1.el6.x86_64
---> Package glusterfs.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: systemd-units for package:
glusterfs-3.6.2-1.el7.x86_64
--> Processing Dependency: systemd-units for package:
glusterfs-3.6.2-1.el7.x86_64
---> Package glusterfs-cli.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-cli.x86_64 0:3.6.2-1.el7 will be an update
---> Package glusterfs-libs.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-libs.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: rsyslog-mmjsonparse for package:
glusterfs-libs-3.6.2-1.el7.x86_64
--> Running transaction check
---> Package glusterfs.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: systemd-units for package:
glusterfs-3.6.2-1.el7.x86_64
--> Processing Dependency: systemd-units for package:
glusterfs-3.6.2-1.el7.x86_64
---> Package glusterfs-api.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-api.x86_64 0:3.6.2-1.el7 will be an update
---> Package glusterfs-libs.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: rsyslog-mmjsonparse for package:
glusterfs-libs-3.6.2-1.el7.x86_64
--> Finished Dependency Resolution
Error: Package: glusterfs-3.6.2-1.el7.x86_64 (glusterfs-epel)
           Requires: systemd-units
Error: Package: glusterfs-libs-3.6.2-1.el7.x86_64 (glusterfs-epel)
           Requires: rsyslog-mmjsonparse
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles -nodigest

Thanks for any help you may provide.

Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150408/3b152da5/attachment.html>

Eric Berg

2015-Apr-08 22:09 UTC

head link

[Gluster-users] Missing gsyncd and dependency issues with gluster on AWS AMI host

I rebuilt my AWS instances as Ubuntu and this problem is no longer valid.  For
me.

Thanks.

From: Eric Berg <eric.berg at yodle.com<mailto:eric.berg at
yodle.com>>
Date: Wednesday, April 8, 2015 at 12:13 PM
To: "gluster-users at gluster.org<mailto:gluster-users at
gluster.org>" <gluster-users at gluster.org<mailto:gluster-users
at gluster.org>>
Subject: [Gluster-users] Missing gsyncd and dependency issues with gluster on
AWS AMI host

I'm setting up geo-replication from a cluster in our colo facility to a
gluster cluster in amazon.  I set up the amazon instances as AMI builds
(probably a mistake), by enabling gluster epel repo from download.gluster.org.

While trying to set up geo-replication, I could not find gsyncd, so I tried to
update the existing 3.6.2-1.el6 versions, and I get the following, indicating
that a) it's looking at el7 packages, when 6 is clearly stated in the
gluster-epel.repo file and b) there are unmet dependencies for systemd-units and
rsyslog-mmjsonparse.

I'm thinking that I should just rebuild these instances as ubuntu 14.x
boxes, like the ones in our datacenter, but it might be easier to solve this
problem.

Anybody have any thoughts on the matter?

Here's the output of the install command:

# yum install -y glusterfs{-fuse,-server}
Loaded plugins: priorities, update-motd, upgrade-helper
epel/x86_64/metalink                                                            
|  16 kB     00:01
glusterfs-epel/x86_64                                                           
| 2.9 kB     00:00
Not using downloaded repomd.xml because it is older than what we have:
  Current   : Fri Jan 23 06:00:21 2015
  Downloaded: Fri Jan 23 06:00:19 2015
glusterfs-noarch-epel                                                           
| 2.9 kB     00:00
Not using downloaded repomd.xml because it is older than what we have:
  Current   : Fri Jan 23 06:00:23 2015
  Downloaded: Fri Jan 23 06:00:20 2015
# Place this file in your /etc/yum.repos.d/ directory
975 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package glusterfs-fuse.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-fuse.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: glusterfs = 3.6.2-1.el7 for package:
glusterfs-fuse-3.6.2-1.el7.x86_64
---> Package glusterfs-server.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-server.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: glusterfs-libs = 3.6.2-1.el7 for package:
glusterfs-server-3.6.2-1.el7.x86_64
--> Processing Dependency: glusterfs-cli = 3.6.2-1.el7 for package:
glusterfs-server-3.6.2-1.el7.x86_64
--> Running transaction check
---> Package glusterfs.x86_64 0:3.6.2-1.el6 will be updated
--> Processing Dependency: glusterfs = 3.6.2-1.el6 for package:
glusterfs-api-3.6.2-1.el6.x86_64
---> Package glusterfs.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: systemd-units for package:
glusterfs-3.6.2-1.el7.x86_64
--> Processing Dependency: systemd-units for package:
glusterfs-3.6.2-1.el7.x86_64
---> Package glusterfs-cli.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-cli.x86_64 0:3.6.2-1.el7 will be an update
---> Package glusterfs-libs.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-libs.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: rsyslog-mmjsonparse for package:
glusterfs-libs-3.6.2-1.el7.x86_64
--> Running transaction check
---> Package glusterfs.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: systemd-units for package:
glusterfs-3.6.2-1.el7.x86_64
--> Processing Dependency: systemd-units for package:
glusterfs-3.6.2-1.el7.x86_64
---> Package glusterfs-api.x86_64 0:3.6.2-1.el6 will be updated
---> Package glusterfs-api.x86_64 0:3.6.2-1.el7 will be an update
---> Package glusterfs-libs.x86_64 0:3.6.2-1.el7 will be an update
--> Processing Dependency: rsyslog-mmjsonparse for package:
glusterfs-libs-3.6.2-1.el7.x86_64
--> Finished Dependency Resolution
Error: Package: glusterfs-3.6.2-1.el7.x86_64 (glusterfs-epel)
           Requires: systemd-units
Error: Package: glusterfs-libs-3.6.2-1.el7.x86_64 (glusterfs-epel)
           Requires: rsyslog-mmjsonparse
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles -nodigest

Thanks for any help you may provide.

Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150408/d66ff446/attachment.html>

Gluster users - Apr 2015 - Missing gsyncd and dependency issues with gluster on AWS AMI host

[Gluster-users] Missing gsyncd and dependency issues with gluster on AWS AMI host

[Gluster-users] Missing gsyncd and dependency issues with gluster on AWS AMI host