Page MenuHomePhabricator
Create Task
Maniphest T12111

Daemons keep failing but then I can't restart
Closed, InvalidPublic
Actions

Description

Running phabricator on Ubuntu 16.04.
Last updated September 6, 2016.

Phabricator keeps warning me daemons are not running: Phabricator Daemons Are Not Running
But in the command line I get:

# ./phd start
phd start: Unable to start daemons because daemons are already running.

You can view running daemons with 'phd status'.
You can stop running daemons with 'phd stop'.
You can use 'phd restart' to stop all daemons before starting new daemons.
You can force daemons to start anyway with --force.

However, restart seems to work:

# ./phd restart
Interrupting process 10916...
Interrupting process 30210...
Process 10916 exited.
Terminating process 30210...
Killing process 30210...
There are processes running that look like Phabricator daemons but have no corresponding PID files:

23416 php ./exec_daemon.php PhabricatorTaskmasterDaemon
23537 php ./exec_daemon.php PhabricatorTaskmasterDaemon
23593 php ./exec_daemon.php PhabricatorTaskmasterDaemon
23607 php ./exec_daemon.php PhabricatorTaskmasterDaemon
30211 php ./exec_daemon.php PhabricatorRepositoryPullLocalDaemon
30212 php ./exec_daemon.php PhabricatorTriggerDaemon


Stop these processes by re-running this command with the --force parameter.
Freeing active task leases...
Freed 6 task lease(s).
Starting daemons as phab-daemon
Launching daemons:
(Logs will appear in "/var/tmp/phd/log/daemons.log".)

    PhabricatorRepositoryPullLocalDaemon (Static)
    PhabricatorTriggerDaemon (Static)
    PhabricatorTaskmasterDaemon (Autoscaling: group=task, pool=4, reserve=0)

Done.

Related Objects

Event Timeline

pmatos created this task.Jan 16 2017, 9:14 AM
chad added a subscriber: chad.Jan 16 2017, 3:29 PM

Please follow the guidelines in Contributing Bug Reports. Specifically this ticket is missing reproduction steps we can follow locally to see the bug, and version information. We don't accept incomplete bug reports. Thanks!

chad edited projects, added Bug Report (Needs Information); removed Bug Report.Jan 16 2017, 3:29 PM
rabahmeradi added a subscriber: rabahmeradi.Jan 16 2017, 5:28 PM

We also encountered this bug but after updating it disappeared.

epriestley closed this task as Invalid.Jan 17 2017, 4:45 PM
epriestley added a subscriber: epriestley.

Closing for lack of feedback.

We also encountered this bug but after updating it disappeared.

This is very common: we receive many reports describing bugs we've already fixed. That's why we ask users to upgrade to the latest version of Phabricator before filing reports.

epriestley mentioned this in T12134: Develop a Nuance-based Phabricator reporting/support flow.Jan 20 2017, 5:32 PM
pmatos added a comment.Feb 10 2017, 7:57 AM

@epriestley I understand it's upsetting for someone to report a bug like I did. The problem here is that having no experience with Phabricator internals or webapps, I have no clue how to even give you the slightest hint of how to reproduce. For example, in my case, I got as I mentioned a problem with the daemons. I needed some further help from your side to actually create a bug report that actually helps you.

However you have dismissed it instead. I have read the 'Contributing Bug Reports' page and it's unfortunately far from helpful. It doesn't explain how to actually get you to reproduce a failure in the daemons. For example, my daemons turn out to be dying with:

Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000] svn: E210002: Network connection closed unexpectedly
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]  at [<phutil>/src/future/exec/ExecFuture.php:369]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000] arcanist(head=stable, ref.master=c58f1b9a2507, ref.stable=9503b941cc02), phabricator(head=stable, ref.master=fde02c4b4edf, ref.stable=2604c5af55f6), phutil(head=stable, ref.master=d4e36c61b1ac, ref.stable=10963f771f11)
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #0 <#2> ExecFuture::resolvex() called at [<phabricator>/src/applications/repository/storage/PhabricatorRepository.php:491]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #1 <#2> PhabricatorRepository::execxRemoteCommand(string, string, string) called at [<phabricator>/src/applications/repository/worker/commitchangeparser/PhabricatorRepositorySvnCommitChangeParserWorker.php:797]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #2 <#2> PhabricatorRepositorySvnCommitChangeParserWorker::getSVNLogXMLObject(PhabricatorRepository, string, string) called at [<phabricator>/src/applications/repository/worker/commitchangeparser/PhabricatorRepositorySvnCommitChangeParserWorker.php:32]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #3 <#2> PhabricatorRepositorySvnCommitChangeParserWorker::parseCommitChanges(PhabricatorRepository, PhabricatorRepositoryCommit) called at [<phabricator>/src/applications/repository/worker/commitchangeparser/PhabricatorRepositoryCommitChangeParserWorker.php:36]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #4 <#2> PhabricatorRepositoryCommitChangeParserWorker::parseCommit(PhabricatorRepository, PhabricatorRepositoryCommit) called at [<phabricator>/src/applications/repository/worker/PhabricatorRepositoryCommitParserWorker.php:51]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #5 <#2> PhabricatorRepositoryCommitParserWorker::doWork() called at [<phabricator>/src/infrastructure/daemon/workers/PhabricatorWorker.php:123]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #6 <#2> PhabricatorWorker::executeTask() called at [<phabricator>/src/infrastructure/daemon/workers/storage/PhabricatorWorkerActiveTask.php:171]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #7 <#2> PhabricatorWorkerActiveTask::executeTask() called at [<phabricator>/src/infrastructure/daemon/workers/PhabricatorTaskmasterDaemon.php:22]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #8 PhabricatorTaskmasterDaemon::run() called at [<phutil>/src/daemon/PhutilDaemon.php:181]
Daemon 159 STDE [Thu, 09 Feb 2017 07:17:12 +0000]   #9 PhutilDaemon::execute() called at [<phutil>/scripts/daemon/exec/exec_daemon.php:131]
Daemon 159 FAIL [Thu, 09 Feb 2017 07:17:12 +0000] Process exited with error 255.

This is with an updated phabricator from last week from stable branch.
How can I help you reproduce this if we have different databases, settings, repos, etc?

Let me thank you for your time in advance. I understand your position but some users need more help than others. Trust me, I know.

avivey added a subscriber: avivey.Feb 10 2017, 12:26 PM

@pmatos, Have you seen the Providing Reproduction Steps page? What kind of instructions can we add to it to make it better?

Were you looking for instructions on:

  • How to find daemons' error logs?
  • How to debug environmental problems in your install?

I think we used to have a "send us a VM image" or "instructions on building a VM" as an option, but we must have dropped it at some point.

Phabricator · Built by Phacility