New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CoreOS/SystemD Service Start Fix #327
Conversation
Hi @clintonskitson, I'm assigning this to you for testing. I validated it on CoreOS (SystemD) and CentOS 7 (SystemD) to verify that REX-Ray now uses SystemD for starting, stopping, and checking the service status. I then verified that on Ubuntu 12.04 (SystemV) REX-Ray still does things the old way for SCM commands. |
Hi @clintonskitson, You can file your PR for the doc fix to add to this PR if you like. That way both changes are documented in a single PR. |
Ok, testing now. |
@akutz This tests out good for me, great job. I have another doc PR which is a bit broader so I think it makes sense to file it separately. I can move it here if you disagree. |
Hi @clintonskitson, I only mentioned collapsing the commits into this PR because when I checked this morning I did not see your PR listed. I'm sure it's fine separately as well. I'm going to first create a PR bumping the release train to RC6 for active dev, and then I'll merge this. |
This patch is a fix for issue rexray#326, where CoreOS is placing SSH sessions into a CGroup, thus killing any REX-Ray daemons not specifically launched via SystemD. This path actually adjusts REX-Ray's behavior for not just CoreOS systems, but any Linux using SystemD. All SystemD-based systems now prefer SystemD for service-control-management (SCM) commands.
6078ded
to
47f2500
Compare
ENHANCEMENTS - Improved installation documentation rexray#331 FIXES - Fixes issue with daemon process getting cleaned as part of SystemD Cgroup rexray#327
This patch marks the release of REX-Ray 0.3.2! NEW FEATURES * Support for Docker 1.10 and Volume Plugin Interface 1.2 rexray#273 * Stale PID File Prevents Service Start rexray#258 * Module/Personality Support rexray#275 * Isilon Preemption rexray#231 * Isilon Snapshots rexray#260 * boot2Docker Support rexray#263 * ScaleIO Dynamic Storage Pool Support rexray#267 ENHANCEMENTS * Improved installation documentation rexray#331 * ScaleIO volume name limitation rexray#304 * Docker cache volumes for path operations rexray#306 * Config file validation rexray#312 * Better logging rexray#296 * Documentation Updates rexray#285 BUG FIXES * Fixes issue with daemon process getting cleaned as part of SystemD Cgroup rexray#327 * Fixes regression in 0.3.2 RC3/RC4 resulting in no log file rexray#319 * Fixes no volumes returned on empty list rexray#322 * Fixes "Unsupported FS" when mounting/unmounting with EC2 rexray#321 * ScaleIO re-authentication issue rexray#303 * Docker XtremIO create volume issue rexray#307 * Service status is reported correctly rexray#310 UPDATES * <del>Go 1.6 rexray#308</del> THANK YOU * Dan Forrest * Kapil Jain * Alex Kamalov
This patch is a fix for issue #326, where CoreOS is placing SSH sessions into a CGroup, thus killing any REX-Ray daemons not specifically launched via SystemD.
This patch actually adjusts REX-Ray's behavior for not just CoreOS systems, but any Linux using SystemD. All SystemD-based systems now prefer SystemD for service-control-management (SCM) commands.
1. Verifying the version
2. Become the
root
user3. Starting REX-Ray via
rexray start
asroot
4. Dropping to a normal user session on CoreOS
5. Checking the status of REX-Ray via
rexray status
as a normal user6. Verifying REX-Ray's PID
7. Exiting the SSH session to CoreOS
8. Reconnecting to CoreOS via SSH and verifying REX-Ray is still running