Closed frosenlind closed 2 weeks ago
@frosenlind had the same issue (identical log ouput) while trying to set up a dev environment. For me it happened at the first start as well. I tried a few env variables and at some point it just ran. For some reason i can't really reproduce the issue at this point. But this one works for me now:
services:
humhub:
image: mriedmann/humhub:latest
ports:
- 8090:80
environment:
HUMHUB_DB_USER: user-humhub
HUMHUB_DB_PASSWORD: humhub
HUMHUB_DB_HOST: db
HUMHUB_DB_NAME: humhub
HUMHUB_AUTO_INSTALL: 1
HUMHUB_ADMIN_LOGIN: admin
HUMHUB_ADMIN_PASSWORD: humhub
WAIT_FOR_DB: 1
HUMHUB_DEBUG: 1
HUMHUB_PROTO: https
HUMHUB_HOST: localhost
volumes:
- ./config:/var/www/localhost/htdocs/protected/config
- ./modules:/var/www/localhost/htdocs/protected/modules
db:
image: mariadb:10.4
environment:
MYSQL_ROOT_PASSWORD: humhub
MYSQL_DATABASE: humhub
MYSQL_USER: user-humhub
MYSQL_PASSWORD: humhub
volumes:
- ./mysql:/var/lib/mysql
volumes:
config: {}
modules: {}
I had this issue as well and fixed it by adding a volume for the logs and manually adding an empty app.log
file there. But it seems this is an issue in the supervisor configuration
After some additional testing with help from a friend it we also solved it by mounting the following:
When starting the container for the first time everything works fine. When taking my stack down and then up again the HumHub container doesn't work and I get the following:
Added 127.0.0.1 to Reverseproxy Whitelist \ /docker-entrypoint.sh: Configuration complete; ready for start up \ /docker-entrypoint.sh: Entrypoint finished! Launching ... \ 2024-04-21 18:57:02,951 WARN exited: humhub-log (exit status 1; not expected)
I'm running on an Unraid server and tried this on two different machines and different humhub-container-tags.
Link to log: https://pastebin.com/9tMvyixz
Compose-file