Closed hvhol closed 1 year ago
Same here, the first time it took ages to start but eventually did. Now it keeps showing the spinning indicator saying it's starting but never does. Log:
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service base-addon-banner: starting
s6-rc: info: service base-addon-banner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service base-addon-log-level: starting s6-rc: info: service fix-attrs successfully started Log level is set to DEBUG s6-rc: info: service base-addon-log-level successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-tasmoadmin: starting s6-rc: info: service init-nginx: starting [15:09:21] DEBUG: Symlinking data directory to persistent storage location... s6-rc: info: service init-tasmoadmin successfully started s6-rc: info: service php-fpm: starting s6-rc: info: service php-fpm successfully started [15:09:21] INFO: Starting PHP-FPM server... s6-rc: info: service init-nginx successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting [15:09:21] INFO: Starting NGINX server... s6-rc: info: service legacy-services successfully started
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Problem/Motivation
Expected behavior
Actual behavior
Steps to reproduce
Proposed changes