codebrowse startup scripts should check that things are running
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
Might be related to bug #225256.
"The startup scripts for codebrowse should verify the successful start of the service, and identify running instances that cannot be stopped. If the daemon's pid file is indeed stored in the source tree, it should be moved. "
After a recent NDT, codebrowse stopped responding. This had to be noticed manually. Restarting the processes was not sufficient to bring it up and running again. Instead the process needed to be killed manually and then started.
Also note:
No errors were reported by the init scripts when the services did not start correctly. The stop script simply reported "no pid file found", which is typical when stopping a service that isn't running. As noted by spm, "codebrowse leaves it's pid in the source tree. so if you rename the tree away - via softlinks, it can't find it any more."
