Bug 1073217
| Summary: | /var/lock/subsys/glusterfsd missing | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Viktor Villafuerte <viktor.villafuerte> |
| Component: | glusterfs | Assignee: | Kaleb KEITHLEY <kkeithle> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | barumuga, gluster-bugs, humble.devassy, joe, jonathansteffan, kkeithle, lmohanty, ndevos, silas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-12 19:58:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1110456 | ||
|
Description
Viktor Villafuerte
2014-03-06 04:02:32 UTC
How are you sure stop never executes?
init doesn't keep track of which services were started, it just runs the scripts based on their sorted filenames when they start with K (stop) or S (start) that reside (or are symlinked) in /etc/rc.d/rc{runlevel}.d as that runlevel is entered.
If you check "service glusterfsd status", you'll see a list of pids that it will kill during the stop process.
as discussed on #gluster, the init script is only called when subsys file present. larsks supplied: https://gist.github.com/larsks/9383107 REVIEW: http://review.gluster.org/7194 (glusterd init script: fix glusterfsd stop() not running at system shutdown or reboot) posted (#1) for review on release-3.4 by Joe Julian (me) REVIEW: http://review.gluster.org/7195 (glusterd init script: fix glusterfsd stop() not running at system shutdown or reboot) posted (#1) for review on master by Joe Julian (me) REVIEW: http://review.gluster.org/7196 (glusterd init script: fix glusterfsd stop() not running at system shutdown or reboot) posted (#1) for review on release-3.5 by Joe Julian (me) That patch will allow /etc/rc.d/rc to run the K*glusterfsd script, killing the bricks before network stop() to prevent the clients from experiencing ping-timeout. REVIEW: http://review.gluster.org/7196 (glusterd init script: fix glusterfsd stop() not running at system shutdown or reboot) posted (#2) for review on release-3.5 by Joe Julian (me) REVIEW: http://review.gluster.org/7195 (glusterd init script: fix glusterfsd stop() not running at system shutdown or reboot) posted (#2) for review on master by Joe Julian (me) REVIEW: http://review.gluster.org/7194 (glusterd init script: fix glusterfsd stop() not running at system shutdown or reboot) posted (#2) for review on release-3.4 by Joe Julian (me) /etc/init.d/glusterfsd (glusterfsd.init) is only in the Fedora and Gluster Community packaging. We'll make the suggested fix there. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. |