RedpointArchive / phabricator

A Docker image that runs Phabricator, an open source software engineering tool
https://hub.docker.com/r/redpointgames/phabricator/
307 stars 98 forks source link

INFO exited: phd (exit status 0; not expected) #80

Closed yannpeng closed 7 years ago

yannpeng commented 7 years ago

phd exits. Paste the log as below

Waiting for /run/sshd-phabricator.pid to appear...
/srv/phabricator/phabricator /
Reading /etc/sysconfig and updating the system...
Reading configuration from: /srv/aphlict.conf
Launching daemons:
(Logs will appear in "/var/tmp/phd/log/daemons.log".)

    (Pool: 1) PhabricatorRepositoryPullLocalDaemon
    (Pool: 1) PhabricatorTriggerDaemon
    (Pool: 4) PhabricatorTaskmasterDaemon

Writing logs to: /dev/stdout
/
/
2017-05-06 00:21:13,490 INFO exited: phd (exit status 0; not expected)
2017-05-06 00:21:14,491 INFO success: postfix entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-06 00:21:14,491 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-06 00:21:14,491 INFO success: aphlict entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-06 00:21:14,493 INFO spawned: 'phd' with pid 261
2017-05-06 00:21:14,494 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-06 00:21:14,494 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-06 00:21:14,494 INFO success: ssh entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-06 00:21:14,494 INFO success: nginx-ssl entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-06 00:21:14,494 INFO success: iomonitor entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
/srv/phabricator/phabricator /
/
2017-05-06 00:21:14,670 INFO exited: phd (exit status 0; not expected)
Rebuilding /etc/aliases.db.
2017-05-06 00:21:15,512 INFO gave up: phd entered FATAL state, too many start retries too quickly
rebuilding /etc/postfix/virtual.db
rebuilding /etc/postfix/transport.db
rebuilding /etc/postfix/access.db
rebuilding /etc/postfix/canonical.db
rebuilding /etc/postfix/sender_canonical.db
rebuilding /etc/postfix/relocated.db
rebuilding /etc/postfix/sasl_passwd.db
rebuilding /etc/postfix/relay_ccerts.db
rebuilding /etc/postfix/helo_access.db
rebuilding /etc/postfix/relay.db
..done
hach-que commented 7 years ago

Are the daemons still running in this scenario? If daemons are working and the expected number of daemons is running, then as far as I'm concerned this is mostly a cosmetic thing which I don't plan on changing.

yannpeng commented 7 years ago

yep, you are right, it doesn't affect the running daemons. Close it.