How to get steam to run on Ubuntu 20.04 - nvidia

Steam won't run =( Here's what I've tried:
I have a fresh install of Ubuntu 20.04 (via Ubuntu Server Live Installer + ubuntu-desktop package) with nvidia drivers:
$ nvidia-smi
Mon Jun 22 10:26:49 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.64 Driver Version: 440.64 CUDA Version: 10.2 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce RTX 2070 Off | 00000000:01:00.0 On | N/A |
| 28% 31C P8 22W / 175W | 303MiB / 7981MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1542 G /usr/lib/xorg/Xorg 53MiB |
| 0 7835 G /usr/lib/xorg/Xorg 124MiB |
| 0 8086 G /usr/bin/gnome-shell 111MiB |
+-----------------------------------------------------------------------------+
Attempt 1: .deb
Download deb from https://store.steampowered.com/about/
$ sudo dpkg -i steam_latest.deb
$ steam
Steam needs to install these additional packages:
libgl1-mesa-dri:i386, libgl1:i386, libc6:i386
Enter sudo password and to install them, and it installs a 49 *:i386 packages
"Updating Steam..." windows pops up and downloads and runs stuff for a bit, then!
CRASH!
[2020-06-22 17:00:18] Installing update...
[2020-06-22 17:00:19] Cleaning up...
[2020-06-22 17:00:19] Update complete, launching...
[2020-06-22 17:00:19] Shutdown
Restarting Steam by request...
Traceback (most recent call last):
File "/usr/bin/steamdeps", line 484, in <module>
sys.exit(main())
File "/usr/bin/steamdeps", line 460, in main
if dep.is_available():
File "/usr/bin/steamdeps", line 96, in is_available
return is_provided(self.name)
File "/usr/bin/steamdeps", line 68, in is_provided
(name, version) = provider.split()
ValueError: too many values to unpack (expected 2)
Running Steam on ubuntu 20.04 64-bit
STEAM_RUNTIME has been set by the user to: /home/username/.local/share/Steam/ubuntu12_32/steam-runtime
Found newer runtime version for 64-bit libGLU.so.1. Host: 1.3.1 Runtime: 1.3.8004
Found newer runtime version for 64-bit libdbusmenu-glib.so.4. Host: 4.0.12 Runtime: 4.0.13
Found newer runtime version for 64-bit libvulkan.so.1. Host: 1.2.131 Runtime: 1.2.135
Forced use of runtime version for 64-bit libcurl.so.4. Host: 4.6.0 Runtime: 4.2.0
Found newer runtime version for 32-bit libvulkan.so.1. Host: 1.2.131 Runtime: 1.2.135
Steam client's requirements are satisfied
/home/username/.local/share/Steam/ubuntu12_32/steam
[2020-06-22 17:00:34] Startup - updater built Jun 4 2020 05:50:42
Installing breakpad exception handler for appid(steam)/version(1591251555)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
SteamUpdateUI: An X Error occurred
X Error of failed request: GLXBadContext
SteamUpdateUI: An X Error occurred
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 51
xerror_handler: X failed, continuing
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 52
xerror_handler: X failed, continuing
Installing breakpad exception handler for appid(steam)/version(1591251555)
[2020-06-22 17:00:34] Verifying installation...
[2020-06-22 17:00:35] Verification complete
Loaded SDL version 2.0.13-5893924
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
(steam:32777): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
/usr/share/themes/Yaru/gtk-2.0/main.rc:775: error: unexpected identifier `direction', expected character `}'
(steam:32777): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
/usr/share/themes/Yaru/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Steam: An X Error occurred
X Error of failed request: GLXBadContext
Major opcode of failed request: 152
Serial number of failed request: 64
xerror_handler: X failed, continuing
Steam: An X Error occurred
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 152
Value in failed request: 0x0
Serial number of failed request: 63
xerror_handler: X failed, continuing
Steam: An X Error occurred
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 152
Serial number of failed request: 65
xerror_handler: X failed, continuing
assert_20200622170034_1.dmp[32831]: Uploading dump (out-of-process)
/tmp/dumps/assert_20200622170034_1.dmp
/home/username/.local/share/Steam/steam.sh: line 750: 32777 Segmentation fault (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$#"
Subsequent attempts to run steam result in the update window flashing and then same crash.
Attempt #2 via multiverse repo, per linuxconfig.org
$ sudo add-apt-repository multiverse
'multiverse' distribution component is already enabled for all sources.
$ sudo apt update
$ sudo apt install steam
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
steam-launcher
The following NEW packages will be installed:
steam:i386 steam-launcher
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,980 kB of archives.
After this operation, 3,163 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://repo.steampowered.com/steam precise/steam amd64 steam-launcher all 1:1.0.0.62 [2,972 kB]
Get:2 http://repo.steampowered.com/steam precise/steam i386 steam i386 1:1.0.0.62 [8,052 B]
Fetched 2,980 kB in 1s (3,294 kB/s)
Selecting previously unselected package steam-launcher.
(Reading database ... 158744 files and directories currently installed.)
Preparing to unpack .../steam-launcher_1%3a1.0.0.62_all.deb ...
Unpacking steam-launcher (1:1.0.0.62) ...
Selecting previously unselected package steam:i386.
Preparing to unpack .../steam_1%3a1.0.0.62_i386.deb ...
Unpacking steam:i386 (1:1.0.0.62) ...
Setting up steam-launcher (1:1.0.0.62) ...
Setting up steam:i386 (1:1.0.0.62) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
$ steam
CRASH! Same errors as the first method.

I recently had the same issue, but had a fix. I hope this works for you.
Here is what I did:
Install steam from the steam website. https://store.steampowered.com/about/
Run this line in a terminal STEAM_RUNTIME=0 steam
You should get a line telling you the missing dependencies
Running Steam on ubuntu 20.04 64-bit
STEAM_RUNTIME is disabled by the user
Error: You are missing the following 32-bit libraries, and Steam may not run:
libXtst.so.6
libXrandr.so.2
libXrender.so.1
libgobject-2.0.so.0
libglib-2.0.so.0
libgio-2.0.so.0
libgtk-x11-2.0.so.0
libpulse.so.0
libgdk_pixbuf-2.0.so.0
libva.so.2
libbz2.so.1.0
libvdpau.so.1
libva.so.2
libva-x11.so.2
Can't find 'steam-runtime-check-requirements', continuing anyway
/home/timothy/.local/share/Steam/ubuntu12_32/steam
Once you get the missing dependencies run this line in the terminal for every missing dependency. sudo apt install (Dependency name)
EXAMPLE (sudo apt install libXtst.so.6)
"libXtst.so.6" was part of the list of dependencies that was given to me by the terminal
Once you installed all those dependencies steam should open up.
Let steam install what it needs to and login in, it should work
If you have any issues just leave a reply.
Other Forums/Community where I got most of the idea from
https://steamcommunity.com/app/221410/discussions/0/530645446314818582/

As #Helper Shoes mentioned, it is highly probable that you have missing 32 bit libraries.
Installing the following libraries made it work for me:
$ sudo dpkg --add-architecture i386
$ sudo apt update
$ sudo apt install libxtst6:i386 libxrandr2:i386 libgtk2.0-0:i386 libsm6:i386 libpulse0:i386 ffmpeg:i386

Related

osx homebrew elasticsearch service Bootstrap failed: 5: Input/output error

This is running on an OSX M1 laptop, and if I try to run the elastic by typing elasticsearch it works just fine. So far it appears it is only the services.
Anyone run into this and know how to fix? I have been at this for hours now.
Warning: Calling plist_options is deprecated! Use service.require_root instead.
Please report this issue to the elastic/tap tap (not Homebrew/brew or Homebrew/homebrew-core), or even better, submit a PR to fix it:
/opt/homebrew/Library/Taps/elastic/homebrew-tap/Formula/elasticsearch-full.rb:68
Bootstrap failed: 5: Input/output error
Try re-running the command as root for richer errors.
Error: Failure while executing; `/bin/launchctl bootstrap gui/502 /Users/.../Library/LaunchAgents/homebrew.mxcl.elasticsearch-full.plist` exited with 5.
Here are details when running info on elasticsearch...
➜ .myconfigurations git:(feature/grok-trunk-live) brew info elasticsearch
==> Downloading https://formulae.brew.sh/api/formula.json
######################################################################## 100.0%
==> Downloading https://formulae.brew.sh/api/cask.json
######################################################################## 100.0%
==> elasticsearch: stable 7.10.2
Distributed search & analytics engine
https://www.elastic.co/products/elasticsearch
Disabled because it is switching to an incompatible license. Check out `opensearch` instead!
Not installed
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/elasticsearch.rb
License: Apache-2.0
==> Dependencies
Build: gradle#6 ✔
Required: openjdk ✔
==> Caveats
Data: /opt/homebrew/var/lib/elasticsearch/
Logs: /opt/homebrew/var/log/elasticsearch/elasticsearch_runner.log
Plugins: /opt/homebrew/var/elasticsearch/plugins/
Config: /opt/homebrew/etc/elasticsearch/
==> Analytics
install: 24 (30 days), 119 (90 days), 14,912 (365 days)
install-on-request: 24 (30 days), 117 (90 days), 14,905 (365 days)
build-error: 4 (30 days)

GPU Acceleration with WSL 2

I'm trying to setup tensorflow to use GPU acceleration with WSL 2 running Ubuntu 20.04. I'm following this tutorial and am running into the error seen here. However, when I follow the solution there and try to start docker with sudo service docker start I get told docker is an unrecognized service. However, considering I can access the help menu and whatnot, I know docker is installed. While I can get docker to work with the desktop tool, since it doesn't support Cuda as mentioned in the SO post from earlier, it's not very helpful. It's not really giving me error logs or anything, so please ask if you need more details.
Edit:
Considering the lack of details, here are a list of solutions I've tried to no avail. 1 2 3
Update: I used sudo dockerd to get the container started and tried running the nvidia benchmark container only to be met with
INFO[2020-07-18T21:04:05.875283800-04:00] shim containerd-shim started address=/containerd-shim/021834ef5e5600bdf62a6a9e26dff7ffc1c76dd4ec9dadb9c1fcafb6c88b6e1b.sock debug=false pid=1960
INFO[2020-07-18T21:04:05.899420200-04:00] shim reaped id=70316df254d6b2633c743acb51a26ac2d0520f6f8e2f69b69c4e0624eaac1736
ERRO[2020-07-18T21:04:05.909710600-04:00] stream copy error: reading from a closed fifo
ERRO[2020-07-18T21:04:05.909753500-04:00] stream copy error: reading from a closed fifo
ERRO[2020-07-18T21:04:06.001006700-04:00] 70316df254d6b2633c743acb51a26ac2d0520f6f8e2f69b69c4e0624eaac1736 cleanup: failed to delete container from containerd: no such container
ERRO[2020-07-18T21:04:06.001045100-04:00] Handler for POST /v1.40/containers/70316df254d6b2633c743acb51a26ac2d0520f6f8e2f69b69c4e0624eaac1736/start returned error: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: driver error: failed to process request\\\\n\\\"\"": unknown
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: driver error: failed to process request\\\\n\\\"\"": unknown.
ERRO[0000] error waiting for container: context canceled
Update 2: After installing windows insider and making everything as up to date as possible, I encountered a different error.
Run "nbody -benchmark [-numbodies=<numBodies>]" to measure performance.
-fullscreen (run n-body simulation in fullscreen mode)
-fp64 (use double precision floating point values for simulation)
-hostmem (stores simulation data in host memory)
-benchmark (run benchmark to measure performance)
-numbodies=<N> (number of bodies (>= 1) to run in simulation)
-device=<d> (where d=0,1,2.... for the CUDA device to use)
-numdevices=<i> (where i=(number of CUDA devices > 0) to use for simulation)
-compare (compares simulation results running once on the default GPU and once on the CPU)
-cpu (run n-body simulation on the CPU)
-tipsy=<file.bin> (load a tipsy model file for simulation)
NOTE: The CUDA Samples are not meant for performance measurements. Results may vary when GPU Boost is enabled.
Error: only 0 Devices available, 1 requested. Exiting.
I have a GTX 970, so I'm not sure why it's not being detected. After running sudo lshw -C display, it was confirmed that my graphics card isn't being detected. I got:
*-display UNCLAIMED
description: 3D controller
product: Microsoft Corporation
vendor: Microsoft Corporation
physical id: 4
bus info: pci#941e:00:00.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list
configuration: latency=0

sdk grails and lazybones init fatal error

I can't use grail and lazybones installed via sdkman.
I have got fatal errors.
OS: Ubuntu 16.04
$ java -version
openjdk version "9-internal"
OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src)
OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src, mixed mode)
$ sdk version
SDKMAN 5.7.2+323
$ sdk install grails
$ grails -version
| Grails Version: 3.3.8
| Groovy Version: 2.4.15
| JVM Version: 9-internal
$ sdk install lazybones
$ lazybones -version
Lazybones version 0.8.3
$ grails create-app --stacktrace helloworld
Resolving dependencies..
| Error Error occurred running Grails CLI: Received fatal alert: handshake_failure (NOTE: Stack trace has been filtered. Use --verbose to see entire trace.)
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:436)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:643)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at org.apache.http.impl.client.DecompressingHttpClient.execute(DecompressingHttpClient.java:137)
at org.eclipse.aether.transport.http.HttpTransporter.execute(HttpTransporter.java:287)
at org.eclipse.aether.transport.http.HttpTransporter.implGet(HttpTransporter.java:243)
at org.eclipse.aether.spi.connector.transport.AbstractTransporter.get(AbstractTransporter.java:59)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:447)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:320)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:217)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.resolveCachedArtifactDescriptor(DefaultDependencyCollector.java:535)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.getArtifactDescriptorResult(DefaultDependencyCollector.java:519)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:409)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:254)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:341)
at org.springframework.boot.cli.compiler.grape.AetherGrapeEngine.resolve(AetherGrapeEngine.java:318)
at org.springframework.boot.cli.compiler.grape.AetherGrapeEngine.resolve(AetherGrapeEngine.java:300)
at org.springframework.boot.cli.compiler.grape.AetherGrapeEngine.resolve(AetherGrapeEngine.java:292)
at org.grails.cli.boot.GrailsDependencyVersions.<init>(GrailsDependencyVersions.groovy:54)
at org.grails.cli.boot.GrailsDependencyVersions.<init>(GrailsDependencyVersions.groovy:50)
at org.grails.cli.profile.repository.MavenProfileRepository.<init>(MavenProfileRepository.groovy:53)
at org.grails.cli.GrailsCli.createMavenProfileRepository(GrailsCli.groovy:334)
at org.grails.cli.GrailsCli.execute(GrailsCli.groovy:235)
at org.grails.cli.GrailsCli.main(GrailsCli.groovy:159)
| Error Error occurred running Grails CLI: Received fatal alert: handshake_failure
$ lazybones list
Can't connect to pledbrook/lazybones-templates: Unable to make member of class sun.net.www.protocol.https.HttpsURLConnectionImpl accessible: module java.base does not export sun.net.www.protocol.https to unnamed module #75f65e45
To me that looks like an SSL handshake error when grails is doing some of its initialisation work for create app. It might be attempting to pull down some required jar files etc.
What does sdk list grails show?
What does which grails and which javareturn?
I've not used jdk 9 heaps so might be worthwhile investigating changing that also. I think you'll find switching to jdk8 will have better results. Each jdk comes with a list of standard root certificate authorities it trusts.
Maybe with the recent security issues like the one surrounding the Symantec CAs jdk9 might have removed these but the server grails is connecting to is still using one perhaps.
Edit: I think you may also have been using an internal development build version of Java 9 jdk. as you reported to using build 9-internal+0-2016-04-14-195246.buildd
Try using jdk 8 or installing a newer version of Java 9.

Docker installation issues on CentOS 7.1

I was trying to install docker with these instructions:
https://docs.docker.com/engine/installation/linux/centos/
It went well without any error, just one warning. But nothing seems to be get installed. I tried it a few times with different approaches on two different machines. Result was the same. It did not install.
Here is the console output:
[root#myhostname ~]# cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)
[root#myhostname ~]# uname -r
3.10.0-229.el7.x86_64
[root#myhostname ~]# cat /etc/yum.repos.d/docker.repo
[dockerrepo]
name=Docker Repository
baseurl=https://yum.dockerproject.org/repo/main/centos/$releasever/
enabled=1
gpgcheck=1
gpgkey=https://yum.dockerproject.org/gpg
[root#myhostname ~]# sudo yum install docker-engine
Loaded plugins: fastestmirror, langpacks, rhnplugin
This system is receiving updates from RHN Classic or Red Hat Satellite.
dockerrepo | 2.9 kB 00:00:00
dockerrepo/7/primary_db | 11 kB 00:00:00
Loading mirror speeds from cached hostfile
apel-7-x86_64 | 1.0 kB 00:00:00
epel-7-x86_64 | 1.5 kB 00:00:00
ipel-7-x86_64 | 1.0 kB 00:00:00
spacewalk-client-el7-x86_64 | 1.2 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package docker-engine.x86_64 0:1.10.1-1.el7.centos will be installed
--> Processing Dependency: docker-engine-selinux >= %{epoch}:1.10.1-1.el7.centos for package: docker-engine-1.10.1-1.el7.centos.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_97)(64bit) for package: docker-engine-1.10.1-1.el7.centos.x86_64
--> Processing Dependency: libsystemd.so.0(LIBSYSTEMD_209)(64bit) for package: docker-engine-1.10.1-1.el7.centos.x86_64
--> Processing Dependency: libsystemd.so.0()(64bit) for package: docker-engine-1.10.1-1.el7.centos.x86_64
--> Running transaction check
---> Package device-mapper-libs.x86_64 7:1.02.93-3.el7_1.1 will be updated
--> Processing Dependency: device-mapper-libs = 7:1.02.93-3.el7_1.1 for package: 7:device-mapper-1.02.93-3.el7_1.1.x86_64
---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7_2.1 will be an update
---> Package docker-engine-selinux.noarch 0:1.10.1-1.el7.centos will be installed
---> Package systemd-libs.x86_64 0:208-20.el7_1.6 will be updated
--> Processing Dependency: systemd-libs = 208-20.el7_1.6 for package: systemd-208-20.el7_1.6.x86_64
---> Package systemd-libs.x86_64 0:219-19.el7_2.4 will be an update
--> Running transaction check
---> Package device-mapper.x86_64 7:1.02.93-3.el7_1.1 will be updated
--> Processing Dependency: device-mapper = 7:1.02.93-3.el7_1.1 for package: 7:device-mapper-event-1.02.93-3.el7_1.1.x86_64
---> Package device-mapper.x86_64 7:1.02.107-5.el7_2.1 will be an update
---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated
--> Processing Dependency: systemd = 208-20.el7_1.6 for package: systemd-sysv-208-20.el7_1.6.x86_64
--> Processing Dependency: systemd = 208-20.el7_1.6 for package: systemd-python-208-20.el7_1.6.x86_64
--> Processing Dependency: systemd = 208-20.el7_1.6 for package: libgudev1-208-20.el7_1.6.x86_64
---> Package systemd.x86_64 0:219-19.el7_2.4 will be an update
--> Processing Dependency: kmod >= 18-4 for package: systemd-219-19.el7_2.4.x86_64
--> Running transaction check
---> Package device-mapper-event.x86_64 7:1.02.93-3.el7_1.1 will be updated
--> Processing Dependency: device-mapper-event = 7:1.02.93-3.el7_1.1 for package: 7:lvm2-libs-2.02.115-3.el7_1.1.x86_64
---> Package device-mapper-event.x86_64 7:1.02.107-5.el7_2.1 will be an update
--> Processing Dependency: device-mapper-event-libs = 7:1.02.107-5.el7_2.1 for package: 7:device-mapper-event-1.02.107-5.el7_2.1.x86_64
---> Package kmod.x86_64 0:14-10.el7 will be updated
---> Package kmod.x86_64 0:20-5.el7 will be an update
---> Package libgudev1.x86_64 0:208-20.el7_1.6 will be updated
---> Package libgudev1.x86_64 0:219-19.el7_2.4 will be an update
---> Package systemd-python.x86_64 0:208-20.el7_1.6 will be updated
---> Package systemd-python.x86_64 0:219-19.el7_2.4 will be an update
---> Package systemd-sysv.x86_64 0:208-20.el7_1.6 will be updated
---> Package systemd-sysv.x86_64 0:219-19.el7_2.4 will be an update
--> Running transaction check
---> Package device-mapper-event-libs.x86_64 7:1.02.93-3.el7_1.1 will be updated
---> Package device-mapper-event-libs.x86_64 7:1.02.107-5.el7_2.1 will be an update
---> Package lvm2-libs.x86_64 7:2.02.115-3.el7_1.1 will be updated
--> Processing Dependency: lvm2-libs = 7:2.02.115-3.el7_1.1 for package: 7:lvm2-2.02.115-3.el7_1.1.x86_64
---> Package lvm2-libs.x86_64 7:2.02.130-5.el7_2.1 will be an update
--> Running transaction check
---> Package lvm2.x86_64 7:2.02.115-3.el7_1.1 will be updated
---> Package lvm2.x86_64 7:2.02.130-5.el7_2.1 will be an update
--> Processing Dependency: device-mapper-persistent-data >= 0.5.5-1 for package: 7:lvm2-2.02.130-5.el7_2.1.x86_64
--> Running transaction check
---> Package device-mapper-persistent-data.x86_64 0:0.4.1-2.el7 will be updated
---> Package device-mapper-persistent-data.x86_64 0:0.5.5-1.el7 will be an update
--> Processing Conflict: systemd-219-19.el7_2.4.x86_64 conflicts initscripts < 9.49.28-1
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package initscripts.x86_64 0:9.49.24-1.el7 will be updated
---> Package initscripts.x86_64 0:9.49.30-1.el7 will be an update
--> Processing Conflict: systemd-219-19.el7_2.4.x86_64 conflicts dracut < 033-243
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package dracut.x86_64 0:033-241.el7_1.5 will be updated
--> Processing Dependency: dracut = 033-241.el7_1.5 for package: dracut-config-rescue-033-241.el7_1.5.x86_64
--> Processing Dependency: dracut = 033-241.el7_1.5 for package: dracut-network-033-241.el7_1.5.x86_64
---> Package dracut.x86_64 0:033-360.el7_2 will be an update
--> Running transaction check
---> Package dracut-config-rescue.x86_64 0:033-241.el7_1.5 will be updated
---> Package dracut-config-rescue.x86_64 0:033-360.el7_2 will be an update
---> Package dracut-network.x86_64 0:033-241.el7_1.5 will be updated
---> Package dracut-network.x86_64 0:033-360.el7_2 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
====================================================================================================================================
Package Arch Version Repository Size
====================================================================================================================================
Installing:
docker-engine x86_64 1.10.1-1.el7.centos apel-7-x86_64 9.6 M
Updating:
dracut x86_64 033-360.el7_2 centos-7-updates-x86_64 311 k
initscripts x86_64 9.49.30-1.el7 centos-7-base-x86_64 429 k
Installing for dependencies:
docker-engine-selinux noarch 1.10.1-1.el7.centos apel-7-x86_64 28 k
Updating for dependencies:
device-mapper x86_64 7:1.02.107-5.el7_2.1 centos-7-updates-x86_64 252 k
device-mapper-event x86_64 7:1.02.107-5.el7_2.1 centos-7-updates-x86_64 167 k
device-mapper-event-libs x86_64 7:1.02.107-5.el7_2.1 centos-7-updates-x86_64 169 k
device-mapper-libs x86_64 7:1.02.107-5.el7_2.1 centos-7-updates-x86_64 304 k
device-mapper-persistent-data x86_64 0.5.5-1.el7 centos-7-base-x86_64 350 k
dracut-config-rescue x86_64 033-360.el7_2 centos-7-updates-x86_64 49 k
dracut-network x86_64 033-360.el7_2 centos-7-updates-x86_64 90 k
kmod x86_64 20-5.el7 centos-7-base-x86_64 114 k
libgudev1 x86_64 219-19.el7_2.4 centos-7-updates-x86_64 65 k
lvm2 x86_64 7:2.02.130-5.el7_2.1 centos-7-updates-x86_64 1.0 M
lvm2-libs x86_64 7:2.02.130-5.el7_2.1 centos-7-updates-x86_64 872 k
systemd x86_64 219-19.el7_2.4 centos-7-updates-x86_64 5.1 M
systemd-libs x86_64 219-19.el7_2.4 centos-7-updates-x86_64 357 k
systemd-python x86_64 219-19.el7_2.4 centos-7-updates-x86_64 98 k
systemd-sysv x86_64 219-19.el7_2.4 centos-7-updates-x86_64 52 k
Transaction Summary
====================================================================================================================================
Install 1 Package (+ 1 Dependent package)
Upgrade 2 Packages (+15 Dependent packages)
Total download size: 19 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for centos-7-updates-x86_64
No Presto metadata available for centos-7-base-x86_64
(1/19): device-mapper-1.02.107-5.el7_2.1.x86_64.rpm | 252 kB 00:00:00
(2/19): device-mapper-event-1.02.107-5.el7_2.1.x86_64.rpm | 167 kB 00:00:00
(3/19): device-mapper-event-libs-1.02.107-5.el7_2.1.x86_64.rpm | 169 kB 00:00:00
(4/19): device-mapper-libs-1.02.107-5.el7_2.1.x86_64.rpm | 304 kB 00:00:00
(5/19): device-mapper-persistent-data-0.5.5-1.el7.x86_64.rpm | 350 kB 00:00:00
warning: /var/cache/yum/x86_64/7/apel-7-x86_64/packages/docker-engine-1.10.1-1.el7.centos.x86_64.rpm: Header V4 RSA/SHA512 Signature, key ID 2c52609d: NOKEY
Public key for docker-engine-1.10.1-1.el7.centos.x86_64.rpm is not installed
(6/19): docker-engine-1.10.1-1.el7.centos.x86_64.rpm | 9.6 MB 00:00:01
(7/19): docker-engine-selinux-1.10.1-1.el7.centos.noarch.rpm | 28 kB 00:00:00
(8/19): dracut-033-360.el7_2.x86_64.rpm | 311 kB 00:00:00
(9/19): dracut-config-rescue-033-360.el7_2.x86_64.rpm | 49 kB 00:00:00
(10/19): dracut-network-033-360.el7_2.x86_64.rpm | 90 kB 00:00:00
(11/19): initscripts-9.49.30-1.el7.x86_64.rpm | 429 kB 00:00:00
(12/19): kmod-20-5.el7.x86_64.rpm | 114 kB 00:00:00
(13/19): libgudev1-219-19.el7_2.4.x86_64.rpm | 65 kB 00:00:00
(14/19): lvm2-2.02.130-5.el7_2.1.x86_64.rpm | 1.0 MB 00:00:00
(15/19): lvm2-libs-2.02.130-5.el7_2.1.x86_64.rpm | 872 kB 00:00:00
(16/19): systemd-219-19.el7_2.4.x86_64.rpm | 5.1 MB 00:00:01
(17/19): systemd-libs-219-19.el7_2.4.x86_64.rpm | 357 kB 00:00:00
(18/19): systemd-python-219-19.el7_2.4.x86_64.rpm | 98 kB 00:00:00
(19/19): systemd-sysv-219-19.el7_2.4.x86_64.rpm | 52 kB 00:00:00
------------------------------------------------------------------------------------------------------------------------------------
Total 1.5 MB/s | 19 MB 00:00:13
Public key for docker-engine-selinux-1.10.1-1.el7.centos.noarch.rpm is not installed
[root#myhostname ~]# sudo service docker start
Redirecting to /bin/systemctl start docker.service
Failed to issue method call: Unit docker.service failed to load: No such file or directory.
INDEED:
[root#myhostname tmp]# ls /etc/systemd/system/docker.service
ls: cannot access /etc/systemd/system/docker.service: No such file or directory
I faced the similar issue and for me "rpm --import https://yum.dockerproject.org/gpg" didn;t work.
"yum clean all" worked for me. Looks like there was something wrong with the cache. After clean up it worked fine.

ejabberd incompatiblity with p1_yaml library

I have installed erlang/OTP 17.1 from source & I have installed ejabberd from GitHub. Both have installed successfully. But when i am starting ejabberd server, i am getting the following error in error.log.
2016-01-08 16:13:57.700 [error] <0.100.0> unable to load p1_yaml NIF: {error,{bad_lib,"Library version (2.8) not compatible (with 2.6)."}}
2016-01-08 16:13:57.700 [error] <0.99.0> CRASH REPORT Process <0.99.0> with 0 neighbours exited with reason: {{bad_lib,"Library version (2.8) not compatible (with 2.6)."},{p1_yaml_app,start,[normal,[]]}} in application_master:init/4 line 133
2016-01-08 16:13:57.769 [critical] <0.38.0>#ejabberd:exit_or_halt:133 failed to start application 'p1_yaml': {error,
{{bad_lib,
"Library version (2.8) not compatible (with 2.6)."},
{p1_yaml_app,start,[normal,[]]}}}
You likely have a p1_yaml.so file around that was build with a different version of Erlang runtime than the one you are using.
You should rebuild ejabberd (or just p1_yaml) with the correct Erlang version.

Resources