Cant run daemons with phd.trace

Phabricator Version Information

Library Version Date Branchpoint
phabricator 324445589b5e Wed, Jul 22
arcanist 2565cc7b4d1d Sat, Jul 11

Other Version Information

Binary Version Path
php 7.4.8 fpm-fcgi
diff 3.7 /usr/bin/diff
git 2.20.1 /usr/bin/git
hg Not Available
pygmentize 2.3.1 /usr/bin/pygmentize
svn Not Available

Phabricator Version Information

Library Version Date Branchpoint
phabricator 324445589b5e Wed, Jul 22
arcanist 2565cc7b4d1d Sat, Jul 11

Other Version Information

Binary Version Path
php 7.4.8 fpm-fcgi
diff 3.7 /usr/bin/diff
git 2.20.1 /usr/bin/git
hg Not Available
pygmentize 2.3.1 /usr/bin/pygmentize
svn Not Available

Actually im running on docker container, which all this packages are being installed with the base image on debian buster slim
dockerfile here

local.json config:
{
“phd.trace”: “true”,
}

trows this exception and does not start the daemons:

[23-Jul-2020 14:34:19 America/Sao_Paulo] [2020-07-23 14:34:19] EXCEPTION: (RuntimeException) posix_isatty(): supplied resource is not a valid stream resource at [<arcanist>/src/error/PhutilErrorHandler.php:263]
[23-Jul-2020 14:34:19 America/Sao_Paulo] arcanist(head=stable, ref.stable=2565cc7b4d1d), phabricator(head=stable, ref.stable=324445589b5e)
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #0 PhutilErrorHandler::handleError
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #1 posix_isatty called at [<arcanist>/src/console/PhutilConsoleFormatter.php:35]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #2 PhutilConsoleFormatter::getDisableANSI called at [<arcanist>/src/console/PhutilConsoleFormatter.php:71]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #3 PhutilConsoleFormatter::interpretFormat called at [<arcanist>/src/console/PhutilConsoleFormatter.php:46]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #4 PhutilConsoleFormatter::formatString called at [<arcanist>/src/console/format.php:7]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #5 phutil_console_format called at [<arcanist>/src/console/PhutilConsoleServer.php:154]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #6 PhutilConsoleServer::writeText called at [<arcanist>/src/console/PhutilConsoleServer.php:39]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #7 PhutilConsoleServer::handleMessage called at [<arcanist>/src/console/PhutilConsole.php:204]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #8 PhutilConsole::writeMessage called at [<arcanist>/src/console/PhutilConsole.php:187]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #9 PhutilConsole::writeTextMessage called at [<arcanist>/src/console/PhutilConsole.php:153]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #10 PhutilConsole::writeLog called at [<arcanist>/src/serviceprofiler/PhutilServiceProfiler.php:202]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #11 PhutilServiceProfiler::echoListener called at [<arcanist>/src/serviceprofiler/PhutilServiceProfiler.php:53]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #12 PhutilServiceProfiler::beginServiceCall called at [<arcanist>/src/future/Future.php:123]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #13 Future::startServiceProfiler called at [<arcanist>/src/future/Future.php:65]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #14 Future::startFuture called at [<arcanist>/src/future/FutureIterator.php:396]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #15 FutureIterator::moveFutureToWork called at [<arcanist>/src/future/FutureIterator.php:372]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #16 FutureIterator::updateWorkingSet called at [<arcanist>/src/future/FutureIterator.php:199]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #17 FutureIterator::next called at [<arcanist>/src/future/FutureIterator.php:190]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #18 FutureIterator::rewind called at [<arcanist>/src/future/FuturePool.php:53]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #19 FuturePool::resolve called at [<phabricator>/src/infrastructure/daemon/PhutilDaemonOverseer.php:196]
[23-Jul-2020 14:34:19 America/Sao_Paulo]   #20 PhutilDaemonOverseer::run called at [<phabricator>/scripts/daemon/launch_daemon.php:24]

Try bin/phd debug <daemon> as a workaround, e.g., bin/phd debug taskmaster.

This is a legitimate bug, but I’m likely to “resolve” it at least partially by removing phd.trace, which I haven’t used diagnostically in at least several years.

1 Like

Actually im trying to investigate why the deamons are loosing statuses or dying after a day.
And i cant find any errors that explains why the deamon hang up

I removed phd.trace (and phd.verbose) in https://secure.phabricator.com/D21426.

Actually im trying to investigate why the deamons are loosing statuses or dying after a day.
And i cant find any errors that explains why the deamon hang up

I can’t reproduce this on any system I administrate. If another user confirms that your dockerfile reproduces a daemon failure after a day I’m happy to look at it, but this reproduction case is to complicated for me to pursue without confirmation.

which php version do you recommend for running phabricator daemons?

PHP 7.4.8 is a great version of PHP.

To explain better my scenario, im running phabricator in docker on Azure vm, the MySQL database its on version 5.5.54 and its running on AWS on RDS (The choice its because Azure does not support some database engines that phabricator needs, and both are running on different clouds but same region.). So, nowdays i’m running this infrastructure on production, sometimes, the daemon tries to run PhabricatorApplicationTransactionPublishWorker task, and all the daemons dies. The stranger thing is that im not receiving any trace errors, im running on verbose mode, and it does log any error in the same timestamp that the daemon dies.

@epriestley, there are two tables running MyISAM, which its not supported by Managed MySQL on Azure, is there any roadmap for support InnoDB on these tables?

See T11741 (and T12985). There’s no current customer interest in Azure/Google Cloud SQL so these aren’t anywhere on the roadmap today.

https://secure.phabricator.com/T11741
https://secure.phabricator.com/T12985

1 Like