Launchpad itself

codebrowse is writing its PID file into the scripts subdirectory

Bug #888420 reported by Steve McInerney
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

eg:
/srv/codebrowse.staging.launchpad.net/staging/launchpad/scripts/loggerhead.pid
/srv/codebrowse.qastaging.launchpad.net/qastaging/launchpad/scripts/loggerhead.pid
and similar for prod.

This actually breaks on staging as old and new versions get rolled out; and thus codebrowse needs to be manually killed to force a stop.
Ideally, this is something that would be written to /var/run
eg. /var/run/loggerhead-staging.pid or similar

Steve McInerney (spm)
tags: added: canonical-losa-lp
Raphaël Badin (rvb)
Changed in launchpad:
assignee: nobody → Canonical LOSAs (canonical-losas)
importance: Undecided → High
status: New → Triaged
Revision history for this message
William Grant (wgrant) wrote :

This is a code bug. scripts/start-loggerhead.py does this:

home = os.path.realpath(os.path.dirname(__file__))
pidfile = os.path.join(home, 'loggerhead.pid')

Changed in launchpad:
assignee: Canonical LOSAs (canonical-losas) → nobody
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 888420] Re: codebrowse is writing it's PID file into the scripts subdirectory

This will require a code change to permit it to happen.

Colin Watson (cjwatson)
summary: - codebrowse is writing it's PID file into the scripts subdirectory
+ codebrowse is writing its PID file into the scripts subdirectory
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.