Each time I make a configuration change, I am alerted that I have an unresolved setup issue. Following the instructions given, I restart the daemons (./bin/phd restart). Upon doing so, I now have a new set of daemons running alongside the old. The old daemons still report "This daemon is running with an out of date configuration and should be restarted".
Description
Description
Event Timeline
Comment Actions
Typically this is a user account issue where the daemons that aren't dying were started as a different user.
Try
sudo ./bin/phd stop ./bin/phd start
The first command should kill all the daemons regardless of what user account started them. The second should start the daemons under the active user account; be sure to amend this command as appropriate so the proper user account starts the daemons.
Comment Actions
That does not resolve the issue
ubuntu@ip-10-0-0-xxx:/phabricator/phabricator$ sudo ./bin/phd stop
Interrupting daemon 'PhabricatorRepositoryPullLocalDaemon' (1039)...
Interrupting daemon 'PhabricatorGarbageCollectorDaemon' (1044)...
Interrupting daemon 'PhabricatorTaskmasterDaemon' (1056)...
Interrupting daemon 'PhabricatorTaskmasterDaemon' (1093)...
Interrupting daemon 'PhabricatorTaskmasterDaemon' (1098)...
Interrupting daemon 'PhabricatorTaskmasterDaemon' (1103)...
Daemon 1039 exited.
Daemon 1044 exited.
Daemon 1056 exited.
Daemon 1093 exited.
Daemon 1098 exited.
Daemon 1103 exited.
There are processes running that look like Phabricator daemons but have no corresponding PID files:
That does not resolve the issue
ubuntu@ip-10-0-0-xxx:/phabricator/phabricator$ sudo ./bin/phd stop
Interrupting daemon 'PhabricatorRepositoryPullLocalDaemon' (1039)...
Interrupting daemon 'PhabricatorGarbageCollectorDaemon' (1044)...
Interrupting daemon 'PhabricatorTaskmasterDaemon' (1056)...
Interrupting daemon 'PhabricatorTaskmasterDaemon' (1093)...
Interrupting daemon 'PhabricatorTaskmasterDaemon' (1098)...
Interrupting daemon 'PhabricatorTaskmasterDaemon' (1103)...
Daemon 1039 exited.
Daemon 1044 exited.
Daemon 1056 exited.
Daemon 1093 exited.
Daemon 1098 exited.
Daemon 1103 exited.
There are processes running that look like Phabricator daemons but have no corresponding PID files:
0 1405 php ./exec_daemon.php PhabricatorTaskmasterDaemon --load-phutil-library=/busy/services/phabricator/arcanist/src --load-phutil-library=/phabricator/phabricator/src --log=/var/tmp/phd/log/daemons.log --
Stop these processes by re-running this command with the --force parameter.
ubuntu@ip-10-0-0-xxx:/phabricator/phabricator$ sudo ./bin/phd start
Freeing active task leases...
Freed 0 task lease(s).
Preparing to launch daemons.
NOTE: Logs will appear in '/var/tmp/phd/log/daemons.log'.
Launching daemon "PhabricatorRepositoryPullLocalDaemon".
Launching daemon "PhabricatorGarbageCollectorDaemon".
Launching daemon "PhabricatorTaskmasterDaemon".
Launching daemon "PhabricatorTaskmasterDaemon".
Launching daemon "PhabricatorTaskmasterDaemon".
Launching daemon "PhabricatorTaskmasterDaemon".
Done.
Comment Actions
I'm not sure which user should be starting the daemons. I'm not very experienced with server admin
Comment Actions
try
sudo ./bin/phd stop --force
(Note the output from the first "stop" command said to try this to fix the issue.)
In terms of "which account should run the daemons" the most important parts of that are 1) that the user account has the necessary permissions to do what needs to be done and 2) you are consistent about which user account to avoid getting into issues with rogue daemons. Some additional information can be found here - https://secure.phabricator.com/book/phabricator/article/managing_daemons/ - though its not that useful for answering the "which account should run the daemons" question.
Comment Actions
Presuming this resolved. In general if you have questions on Phabricator administration, many other admins are available on IRC to answer questions. irc.freenode.net #phabricator