Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 511710 - sys-cluster/swift-1.13.1 - /etc/init.d/swift-* scripts fails to stop services
Summary: sys-cluster/swift-1.13.1 - /etc/init.d/swift-* scripts fails to stop services
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Matthew Thode ( prometheanfire )
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: keepdir-var-run_lock
  Show dependency tree
 
Reported: 2014-05-28 17:45 UTC by Thomas Capricelli
Modified: 2015-04-05 10:19 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Capricelli 2014-05-28 17:45:21 UTC
i have the same problem with all init.d script : 
   swift-container
   swift-account
   swift-object
   swift-proxy

I check actual service with
   ps aux | grep swift

starting with a clean system (ps gives nothing)
I can start a service with
    /etc/init.d/swift-proxy  start
then ps shows the process as expected

i can stop
    /etc/init.d/swift-proxy  start
and it says ok in green

But actually, the processes still show with ps (there are three)
Killing the first one with
    kill <pid>
is enough to ends it, no even need for -9
Comment 1 Thomas Capricelli 2014-05-28 20:35:27 UTC
I know why it fails and i know how to fix it. I had to change the PIDFILE in init.d scripts.

Maybe those have changed in openstack icehouse ?

Anyway, here's what i got now and it works pretty well.

verdi ~ # grep ^PIDF /etc/init.d/swift-*
/etc/init.d/swift-account:PIDFILE=/var/run/swift/account-server.pid
/etc/init.d/swift-container:PIDFILE=/var/run/swift/container-server.pid
/etc/init.d/swift-object:PIDFILE=/var/run/swift/object-server.pid
/etc/init.d/swift-proxy:PIDFILE=/var/run/swift/proxy-server.pid
Comment 2 Thomas Capricelli 2014-11-11 19:50:40 UTC
I can confirm the bug AND that my fix still works as of today, using sys-cluster/swift-2.1.0 from the main portage tree.

The init.d scripts are plain broken, and it prevents normal use of swift in gentoo. I've found the problem, explained why and proposed a solution.

All of this several months ago.

Why isn't it fixed since then ???

Do you kinda disagree with what i've said ?
Comment 3 Matthew Thode ( prometheanfire ) archtester Gentoo Infrastructure gentoo-dev Security 2015-01-13 03:23:35 UTC
No, don't necessarily disagree, but getting swift init scripts happy will take setting it up, which takes time :(
Comment 4 Thomas Capricelli 2015-01-13 13:52:39 UTC
Might be. But there's a bug here, i provide a fix, an explanation. The whole thing seems rather trivial, has been there for months and is still not applied.... !?
Comment 5 Thomas Capricelli 2015-03-04 02:21:08 UTC
Please fix the init files !
Comment 6 Matthew Thode ( prometheanfire ) archtester Gentoo Infrastructure gentoo-dev Security 2015-04-05 02:33:53 UTC
You have init files I can use?  Not using swift myself makes this harder :(
Comment 7 Matthew Thode ( prometheanfire ) archtester Gentoo Infrastructure gentoo-dev Security 2015-04-05 02:40:24 UTC
actually, I'm blind, your fix is applied (changed /var/run to /run though).
Comment 8 Thomas Capricelli 2015-04-05 10:19:47 UTC
You right for /run indeed.

Thanks for applying the fix.